Defining a Record

 When developers are working with record definitions, they must follow certain configuration rules. Typically, every record definition must have one key field. If a record definition is part of a parent child relationship, the record must include the same key values as its parent record, in the same order, and include at least one additional key field. If a record definition uses effective dated field, the EFFDT field must be a key field in descending order. Key fields will be at the top of the list on the record definition.

In step number two we created field definitions. In this step, we will combine these field definitions into a record definition. We will set additional attributes in Application Designer called record field properties. After setting these properties we will be ready to build the record definition. The record definition can serve as the basis for SQL tables, sub records, temp tables and views.

 When you open a record definition in application designer, the display buttons on the toolbar appear and enable you to access the different properties of the record definition. You can also use the view menu to see different record displays.

In addition to record field properties, the record definition has properties that apply to the record definition as its own entity. Record properties include documentation, record relationships, audit, information, mobile properties, and auto update information.

To create a record definition:

1. Open a new record definition. 

2. Insert the necessary fields. 

3. Set the record field properties. 
                           

  
4. Save the record definition. 

When you have inserted all of the fields that the specifications indicate are needed, save the record definition.  Depending on the settings, you may have to document the record definition and select the tablespace name.