| Conversion setups |  |
| Messages are identified with a code that relates to a particular standard (ORDERS for the UN/ EDIFACT purchase order, and 850 for the ANSI X12 purchase order. Conversion setups define the file layout of the ASCII files received into and generated from ERP EDI for a particular EDI message. In addition, conversion setups define the mapping relationship between the ASCII file fields and the ERP LN application fields as well as the rules for each field's validation and translation (conversion). You can define more than one conversion setup by organization and message type. The only restriction is that the format of the ASCII files must be identical for each organization and message type. This restriction means that relationships are defined for a combination of organization and message type in the Conversion Setups (Relationships) (ecedi5112m000) session. ERP LN records general message data once for each organization and message type. General message data is referred to as overhead and applies to all conversion setups for the organization and message type concerned. A conversion setup consists of a name, a definition, and a relationship table. When the module is installed, the basic data is loaded, which allows you to start working immediately. First, choose a similar conversion setup that can be copied. If you cannot find an appropriate conversion setup, you can create a new setup. When you zoom to the definition, an empty definition is generated. In the definition, you can only modify fields with the destination header and line. |