Mapping Rules for EDI Translators
The following rules apply to EDI translators:
Outbound and Inbound Transactions
If you use descriptive flexfields, you must define them in the Oracle Application. They require custom changes to the EDI translator data map for correct placement in the EDI standard or application.
Rely on the record number on every record in Positions 92-95 to identify the record content.
Outbound Transactions Only
A given data element may have both internal Oracle application values and corresponding external values made up of one to five distinct fields.
For a given data element, the first place to find data is the external fields. If the External field is empty, move data from the internal fields. Apply code conversion if necessary.
Inbound Transactions Only
The EDI Gateway can only use the data defined as internal data for the application open interface tables. Either the EDI Gateway or the EDI translator must determine the internal code given the external data found in the transaction. If the code conversion for a data element is enabled by the Assign Categories window, EDI Gateway performs the code conversion even if the code conversion was already performed in the EDI translator and there is data in the internal field.
If both internal and external data elements are present in a standard transaction for a given piece of business data, the EDI translator should move the data from the standard transaction to the internal and external field in the data file.
