EDI File Format
The EDI file must contain all the information that you expect to receive from your partner (if the map is inbound) or need to send to your partner (if the map is outbound).
The Application Integration subsystem generates an EDI file for you, based on the standard (agency), version, transaction set, and release (for TRADACOMS only) that you selected. The system includes all the groups, segments, composites, and elements that are defined by the standards agency for the version of the document you selected. If you are creating an import or export map, you typically need to customize the system-generated EDI file by modifying the properties of the map components and using specialized Sterling Gentran:Server® functions to manipulate the EDI file structure.
The specific EDI map components that you use depends on the type of map you are creating. This includes the standard, version, and transaction set (document) selected, and which groups, segments, composites, and elements your company requires. We recommend that you determine which map components you are using before generating or defining an EDI file.
The system activates all of the groups, segments, composites, and elements that are defined as mandatory by the standard. The system does not enable you to deactivate the mandatory groups, segments, composites, and elements. By default, Sterling Gentran:Server displays active map components with a black font, and inactive map components with a grey (dimmed) font.
When translating data, the system does not process groups, segments, composites, and elements (or records and fields) that are not activated. Therefore, you must activate the groups, segments, composites, and elements that are not defined as mandatory by the standard, but that you have determined that you need to use in mapping.
If you want to use a specialized version of an EDI standard that is not available in the Sterling Gentran:Server standards database, it may be appropriate for you to define the EDI file yourself.
This table describes the map components Sterling Gentran:Server uses to define the EDI file.
| Component | Icon | Description |
|---|---|---|
| Group |  |
This is a looping structure that contains related segments 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. Groups are defined by the EDI standards. A group that is subordinate to another group is a subgroup (this corresponds to a nested looping structure – a loop within a loop). The EDI file is a group and is visually represented the same way as other groups and subgroups in the Application Integration subsystemt. |
| Segment |  |
Contains a group of related elements or composite data elements that combine to communicate useful data. Segments are defined by the EDI standards. A segment can occur once or can repeat multiple times. |
| Composite |  |
This is a data element that contains two or more component data elements or subelements. Composites are defined by the EDI standards that use them (EDIFACT, TRADACOMS, and certain ANSI X12 standards). |
| Element |  |
This is the smallest piece of information defined by the EDI standards. An element is the EDI map component that is mapped (linked) to a corresponding application field to move data to and from the EDI file. |
- When an element has a mapping operation performed against it, a red checkmark is displayed over the element 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.