Mapping Overview
A map is a set of instructions you define in the Sterling Gentran:Server® Application Integration subsystem that defines the relationship between your application file and the EDI standards, and defines how the system should translate data.
For inbound mapping, the system translates your trading partner’s EDI standard formatted business document to your file format. To translate inbound data, you need to create an export map in Sterling Gentran:Server Application Integration (because the system is exporting to your application file).
For outbound mapping, the system translates your file format to EDI standard formats, so you can send documents to your partners. To translate outbound data, you need to create an import map and a system import map in the Sterling Gentran:Server Application Integration subsystem. You need to create an import map because the system is importing from your application file.
The import map defines how to move data from your application file (flat file definition), which may contain multiple documents, to the EDI standard-formatted documents that your partners expect to receive from you. You need to create a system import map to determine which trading relationship (established in Partner Editor) corresponds to each document in the application file, so the system knows which import map to use to process the document.
Translation Objects
The map you create is the source from which you compile a translation object. A translation object is a set of instructions the translator uses to convert a file from one format to another. Every function performed during translation requires a translation object. Translation objects control all the functions of Sterling Gentran:Server EDI translation. Translation objects can belong to one of the following categories:
- system translation objects
- user translation objects
System translation objects control the creation and separation of interchanges, functional groups, and transaction sets. They are also used to generate and reconcile functional acknowledgements. User translation objects control data entry, importing, exporting, document turnaround, and creating printed reports. All required system translation objects are automatically installed with the Sterling Gentran:Server system.
The Application Integration subsystem enables you to generate import, export, and turnaround translation objects. Once you generate a translation object using the Application Integration subsystem, you must register the translation object with Sterling Gentran:Server. In addition, you must set up relationships for all trading partners from which you receive or to which you send data. During the process of establishing a trading relationship, you need to specify the name of the appropriate translation object that the translator uses to translate the data. See the IBM® Sterling Gentran:Server for Microsoft Windows User Guide for more information about trading partners.
Inbound and Outbound Translation Process
The following diagram shows a high-level view of the inbound EDI to application and outbound application to EDI translation processes.
When you create an export map, you need to define to Sterling Gentran:Server the EDI standard format in which your partners sends documents and your application file format (how the data needs to be formatted for your application to process it). When you create an import map, you must define to Sterling Gentran:Server your application file format (your data that you will send to your partners) and the EDI standard format in which your partners expect to receive the documents.