| EDI Messages (ecedi0105s000) |  |
| Use this session to define messages used in EDI. Related topics To use a details session Creating EDI messages Using EDI messages Using a single ASCII file Using multiple ASCII files EDI message levels and file layouts
Fields | Description
EDI Message | An electronic document (for example, an electronic order acknowledgment) that consists of an organization and a message. Incoming and/or outgoing messages are processed in specific libraries invoked by EDI communication sessions (for example, in the Sales Control (SLS), Sales Invoicing (SLI), Accounts Payable (ACP), Cash Management (CMG), Purchase Control (PUR), Inventory Handling (INH), and Electronic Data Interchange (EDI) modules). Note Depending on the direction, it identifies an incoming or outgoing message.
Description | The description or name of the code.
Change Order | If this check box is selected, the message represents or refers to an order change request. If this check box is cleared, the message represents or refers to a new order request. Note This field is relevant for the order and order acknowledgment messages: outgoing purchase orders, incoming sales orders, and incoming and outgoing order acknowledgments. Example If the message is an incoming order, an existing sales order will be updated with the data specified in the message (examples of this include the ANSI X12 860 and the UN/EDIFACT ORDCHG). If the message is an outgoing order acknowledgment, this field can be used to indicate that the message is in response to a received order change message, for example the ANSI X12 865. If the message is an incoming order, a new sales order will be generated with the data specified in the message (examples of this include the ANSI X12 850 and the UN/EDIFACT ORDERS). If the message is an outgoing order acknowledgment, this field can be used to indicate that the message is in response to a received new order request, for example the ANSI X12 855, and the UN/EDIFACT ORDRSP.
Library Incoming | The object name of the library (DLL) that is used to convert incoming messages into data in the ERP LN application. Examples of libraries used to process the EDI messages, converting message data from and to the ERP LN application include the following:
- | Incoming | Outgoing
Orders | otdslsdll4280 | otdpurdll4280
Acknowledgments | otdpurdll4281 | otdslsdll4281
Shipment Notices | owhinhdll3201 | owhinhdll4231
Error Notifications | owhinhdll4232 | oecedidll3201
Receipt Discrepancies | owhinhdll3221 | owhinhdll3220
Invoices | otfacpdll1250 | ocislidll2003
Schedules (planning and shipping releases) | otdslsdll4284 | otdpurdll4283
Sequenced Schedules | owhinhdll4283 | otdpurdll4283
Remittance Advice | otfcmgdll5201 | -
Receive Message Status | ecedidll7280 | -
Library Incoming | The description or name of the code.
Library Outgoing | The object name of the library (DLL) that is used to convert data from the ERP LN application into message data. Examples of libraries used to process the EDI messages, converting message data from and to the ERP LN application include the following:
- | Incoming | Outgoing
Orders | otdslsdll4280 | otdpurdll4280
Acknowledgments | otdpurdll4281 | otdslsdll4281
Shipment Notices | owhinhdll3201 | owhinhdll4231
Error Notifications | owhinhdll4232 | oecedidll3201
Receipt Discrepancies | owhinhdll3221 | owhinhdll3220
Invoices | otfacpdll1250 | ocislidll2003
Schedules (planning and shipping releases) | otdslsdll4284 | otdpurdll4283
Sequenced Schedules | owhinhdll4283 | otdpurdll4283
Remittance Advice | otfcmgdll5201 | -
Receive Message Status | ecedidll7280 | -
Library Outgoing | The description or name of the code.
Release Type | The schedule release type to which this message corresponds. This field is used only in schedule-related messages (the ANSI X12 830, 862, 866, or the UN/EDIFACT DELFOR, DELJIT messages).
Incoming Message Processing Type | Indicate the way in which the incoming EDI messages will be processed. Note The value defined here, at the message level, serves as the default value for the EDI Messages Supported by Business Partner (ecedi0111s000) session.
File Layout | The type of file layout used for the specific EDI message. Related topics Using a single ASCII file Using multiple ASCII files
Level Identification Position | The position in the message (ASCII file) record of the Level Identification field defined in the Conversion Setups (Relationships) (ecedi5112m000) session. This can be the starting position of the field or the field number, depending on the field type specified in the Networks (ecedi0120s000) session. Note You must check the message's conversion setup definition to ensure that no other field is defined as residing in the same position(s). This field only applies if the File Layout field is Single, and is used in the processing of incoming single-file messages. Related topics EDI message levels and file layouts
Level Identification Length | The length of the Level Identification field defined in the Conversion Setups (Relationships) (ecedi5112m000) session. Note The maximum length is six. This field only applies if the File Layout field is Single and the Field Type field in the Networks (ecedi0120s000) session is Fixed Length. Related topics EDI message levels and file layouts