This acronym stands for American National Standards Institute. ANSI is the central body responsible for the identification of a single consistent set of voluntary standards called American National Standards. ANSI is also the US representative to nontreaty standards organizations.

A subdirectory that contains generated messages that must be read by an internal company.

The directory that stores all messages generated by EDI. This directory is where your translation/communication software will retrieve files for export. This directory is not included in a multicompany (internal EDI) network.

A directory of temporary files that are used to build up text blocks. Records exist in this directory if a message contains any text fields.

The directory that stores all messages to be received into the LN application. This directory is where the translation/communication software will write files that must be processed and imported by EDI.

This is not included in multicompany (internal EDI) network.

The rules that state how characters from the ERP application are translated before they are placed in a message.

A code used in the ERP application that must be translated before sending the message: for example, the order type or the business partner (customer or supplier) code.

A standard code used in a specific EDI message that must be translated to or from a value in your ERP application: for example, the EDI message contains a unit of measure that can differ from the one used in LN. This unit of measure must be translated to ensure that the correct unit of measure is transmitted in the EDI message.

In Electronic Commerce, a directory used for semaphores.

Use the semaphore, or flagging, mechanism to communicate with third-party translation/communication software to ensure that the third-party software and ERP EDI do not attempt to access files at the same time. This semaphore mechanism uses the creation and deletion of empty files in this subdirectory to indicate when certain processes are active or can be activated.

The number of times the connection with a specific network should be established.

The time the connection with a specific network is established.

A code that defines the layout of the ASCII file that contains the message data. This code contains information on the mapping of data elements between ERP application tables and the ASCII files. Although predefined conversion setups are available, you can create your own custom conversion setups.

The method used to translate EDI messages.

A code for the basic translation of the message header (global overhead) and one or more codes for the way(s) in which messages can be translated. The code is defined for each organization, message, and direction (and field type).

An ERP application table that stores different code conversion values and their relationships between an external code (code in message) and the code in the ERP application.

An ASCII file that contains EDI data.

The file contains the following data:

• Networks
• Messages supported by application
• Messages supported by organization
• Organizations
• Code tables
• Conversion setups
• EDI expressions
• Processing sessions for supported outgoing messages

This acronym stands for Electronic Data Interchange for Administration, Commerce, and Transport. A worldwide organization developing standards for electronic data interchange.

There are other similar organizations (for example, Odette), each using its own subset of standard EDIFACT messages.

When you define messages, you can use the naming convention that coincides with the standard naming conventions to which you are accustomed.

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).

A protocol defined at national and international levels to define the process, procedures, and format of electronically transmitted data (messages) between two business partners.

The computer-to-computer transmission of a standard business document in a standard format. Internal EDI refers to the transmission of data between companies on the same internal company network (also referred to as multicompany). External EDI refers to the transmission of data between your company and external business partners.

The expression that indicates which lines of a conversion setup definition are executed and which are not and which fields in the ASCII field are filled and which are not.

A format that indicates for incoming messages whether the data for the message will reside in a single file or in multiple files. In a single file, the Level Identification Position field indicates the position of the level identifier (as defined within the conversion setup), which identifies the record in the ASCII file (for example, header, header text, and line).

The EDI messages that are marked for generation but have not yet been included in ASCII files.

A code that identifies a communication network used to manage data flow through an intermediary (such as communication through a Value Added Network (VAN) via an EDI-translator) or directly, without translation, to a sister company that uses the same software.

A code used to identify users/business partners in a network. Generally, these addresses are assigned by the network manager.

A code used to determine the character or function of an order and, consequently, of the message.

Examples:

• Normal order versus return order
• Invoice versus credit note

The classification that determines which sessions (in which sequence) are part of the order procedure. You can also assign one of the following categories to the order type: cost order, collect order, return order, and subcontracting order.

Order type codes are required in the ERP EDI messages that relate to a single order. EDI messages that relate to single orders include messages that process:

• Orders (ANSI X12 850, UN/EDIFACT ORDERS).
• Order changes (ANSI X12 860, UN/EDIFACT ORDCHG).
• Order acknowledgments (ANSI X12 855 and 865, UN/EDIFACT ORDRSP).
• Invoices (ANSI X12 810, UN/EDIFACT INVOIC).

A code that represents a set of standards (such as ANSI X12, UN/EDIFACT, and VDA) used in EDI communication.

The messages that are created by specific ERP sessions, by organization.

The numbering system used to identify outgoing messages. This number uniquely identifies the message and is created when an EDI message is generated. Because the actual data belonging to the message is distributed over multiple ASCII levels, this number is also used to identify which parts of the message belong together.

The saved EDI message data that is read when processing incoming EDI messages.

A directory that logs all received messages.

A directory that logs all sent messages.

The incoming and/or outgoing messages that are supported by the application. These messages can be active (actually used within the company) or not.

The EDI messages used by specific business partners. Only after a business partner and a specific message (incoming and/or outgoing) have been linked, the business partner can communicate with your ERP application for that particular message.

A directory that contains the created log (trace) files.

A file that contains process data about read or created ASCII files.

A complete business document such as a purchase order, invoice, or sales order. A transaction set is synonymous with document or message.

A company that provides communications services for EDI, such as line speed conversion and protocol matching.

Acronym for Verband der Automobilindustrie; A standard for automotive electronic interchange of business transactions in Germany. This particular standard uses a fixed length field/record format.

The ANSI standard for interindustry electronic interchange of business transactions within the US. The accredited subcommittee of American National Standards Institute has a mandate to develop standard data formats for business transactions with cross-industry applications.