| Definitions of Conversion Setups (ecedi5511m000) |  |
| Use this session to list conversion setup definitions for incoming messages, which you can maintain or display in the Definitions of Conversion Setups (ecedi5111s000) session. The data shown in this session is based on the conversion setup information entered in the Conversion Setups (Names) (ecedi5110m000) session. Note If you started this session by zooming, you can only find and select a record. Related topics To use an overview session To maintain records in an overview/maintain session
Fields | Description
Organization | A code that represents a set of standards (such as ANSI X12, UN/EDIFACT, and VDA) used in EDI communication.
Organization | The description or name of the code.
Direction | The direction of the EDI message.
EDI Message | The incoming and/or outgoing messages that are supported by the application. These messages can be active (actually used within the company) or not. Related topics Using supported EDI messages
EDI Message | The description or name of the code.
Field Type | The ASCII file format. Note A conversion setup can be created for files in which the fields areseparated by a field separator, or that have a fixed length.
Conversion Setup Code | The code that identifies the conversion setup.
Conversion Setup | The description or name of the code.
Destination | The destination of the field in the incoming message, as defined in the Conversion Setups (Relationships) (ecedi5112m000) session.
Field | The name of the field, for example, tdsls400.ofbp. For outgoing conversion setups, you can also use constants. Constants must start with double quotation marks ("). All text following the double quotes and preceding a closing quotation mark (if present) is placed in the message.
Sequence Number | The sequence number of the field. The same field can be included more than once. If the field appears only once within the conversion setups, you can set this field to 0 or 1. If the field appears more than once in the conversion setup definition, the sequence number can be increased by an increment of 1 for each occurrence of the field within the conversion setup definition.
Processing Sequence | The sequence in which the field will be processed.
Level | The level defined in the Conversion Setups (Relationships) (ecedi5112m000) session.
Start Position Key | The position of the field in the line.
Length | The physical length of the field.
Read Next Record | If this check box is selected, a new record will be read at this level for incoming messages, and a new record of the table that belongs to the field will be read for outgoing messages. If this check box is cleared, new records will not be read, but the current records remain active. Note This field indicates whether a new record must be read in order to process the contents of the field. Based on the value of this field, you can determine when a new line is ready to be read from the same file.
Sequence when Iterative Level | The sequence number that indicates where the cursor must move after processing the field. This field is only used if this record is for the last field of an iterative level or for the last field of the conversion setup. For example: You want to enter a text field that contains data from an ASCII file in an order header, that is performed iteratively. Once the last text field is filled, the cursor is returned to the field with sequence number 3, by using the Sequence Number field. The key and three text fields are included in each line of level 2.
Field | Level | Sequence Number | Iterative Level
Order No. | 1 | 1 |
Reference | 1 | 2 |
Text Field | 2 | 3 |
Text Field | 2 | 4 |
Text Field | 2 | 5 | 3
Sequence when Key does not Match | The sequence number that indicates where the cursor must move if the key is not valid or the key changes. This field only needs to be filled in if the New record is Yes. Example 1 - Iterative processing After all text fields have been processed, the customer number is read. Level 2 is iterative.
Field | Level | Sequence in | Back | Back | New
Iter. | Key | record |  |  |
Order No. | 1 | 1 |  |  |
Reference | 1 | 2 |  |  |
Text Field | 2 | 3 |  | 6 | yes
Text Field | 2 | 4 |  |  |
Text Field | 2 | 5 | 3 |  |
Customer | 1 | 6 |  |  |
Example 2 - Sequential processing When all order lines have been filled (level 2) a new order can be introduced (level 1).
Field | Level | Sequence in | Back | Back | New
Iter. | Key | record |  |  |
Order No. | 1 | 1 |  |  | yes
Reference | 1 | 2 |  |  |
Customer | 1 | 3 |  |  |
Item | 2 | 4 |  | 1 | yes
Quantity | 2 | 5 |  |  |
Delivery Date | 2 | 6 | 4 |  |
Write Record | If this check box is selected, a record must be added to the relevant table after a field for an incoming message has been processed, depending on the result of the output expression. The destination of the field (overhead, header, or line) determines the table where messages will be saved. Example 1
Field | Destination | Write record
Order No. | header |
Reference | header |
Customer | header | yes
Item | line |
Quantity | line |
Delivery Date | line | yes
Fields processed after a write action for the same destination are not added to the relevant table. You cannot start several write actions for the same record (for example: order line). Due to the hierarchy of destinations, ERP LN checks whether or not all higher destinations have been written. If the higher destination has not been written, the relevant destinations are written before the specified destination is written. The hierarchy is: Overhead Header Line Example 2
Field | Destination | Write record
Order No. | header |
Reference | header |
Customer | header |
Item | line |
Quantity | line |
Delivery Date | line | yes
Because no header has been written yet, the header is written first, followed by the line. If there is no overhead, the line is written before the header.
Convert Field | If this check box is selected, the relevant conversion table is used to convert the field. If this check box is cleared, the code matches the corresponding code in ERP LN and does not need to be converted. Note Any field that can be included on an incoming message, can be converted. If this check box is cleared, the code in the message matches the one in ERP LN and need not be converted.