Creating a System Import Map
A system import map is used by the system to find the partner relationship for a document (flat file definition), to determine which import map is used to translate the data. The system import map builds the key that the translator uses to find the partner relationship. The sole function of the system import map is to identify the appropriate partner relationship; the system import map does not map any data.
There are two ways to build the key in a system import map. The method that we recommend requires six EDI-specific fields in the header record: partner key, standard, version, transaction set, release (for TRADACOMS only), and test/production status. The combination of these six fields defines a unique key that identifies the appropriate partner relationship. We recommend using this method because it is very flexible. You typically use this method when you are defining your application from scratch and can easily add the EDI-specific fields that are not already present in the header record.
The second method is easier to build because it only requires three fields in the header record (partner key, application ID or application alias value, and test/production status). The combination of these three fields defines a unique key that identifies the appropriate partner relationship. However, because only three fields are combining to build the key, this method is not as flexible as the preferred method. You typically use this method when you are using a legacy (existing) application definition, and you do not want to add EDI-specific information.
Use this procedure to create a system import map.