Application File Format
If you are creating an import or export map, you must define your application to the Application Integration subsystem. In Sterling Gentran:Server® terminology, your application file is also referred to as a fixed-format file or a positional file. Your application file must contain all the information that you need to either extract from your partner’s document (if the map is inbound) or send to your partner (if the map is outbound).
This table describes the map components that you use to define your application file.
| Component | Icon | Description |
|---|---|---|
| Group |  |
This is a looping structure that contains related records and/or groups that repeat in sequence until either the group data ends or the maximum number of times that the loop is allowed to repeat is exhausted. If you create a group that is subordinate to another group (a subgroup), this corresponds to a nested looping structure (a loop within a loop). The application (positional) file is a group and therefore, it is visually represented the same way as other groups and subgroups in the Application Integration subsystem. |
| Record |  |
Contains a group of related fields. A record can occur once or can repeat multiple times. |
| Field |  |
This is the smallest piece of information defined in the application file. A field is the application map component that is mapped (linked) to a corresponding EDI element. When an element contains a standard rule a black asterisk appears to the right of the element icon. |
- When a field has a mapping operation performed against it, a red checkmark is displayed over the field icon.
- When a field contains a standard or extended rule a black asterisk appears to the right of the element icon.
- When a group contains an extended rule, a yellow asterisk appears to the right of the group icon.
Before you define your application file format, you should obtain a layout of the necessary records, fields, and groups. Each map component is arranged sequentially in the order that it is most logical for the system to process. Therefore, each level of your application file must be created sequentially. For example, your application file contains records and groups. The records contain fields and the groups contain records and/or subgroups. This means that you must create records and groups before you create the subordinate fields.