Processing incoming messages

Transformation processes messages of different origin:

• Transformation processes messages from a communication client. These are EDI messages from external communication partners in a standardized message format.
• Transformation processes BOD messages from ION. These BOD messages come from other applications that are connected to ION.
• Transformation processes headerless and proprietary EDI messages for APAC OEM trading partners through Exchange Services (EXS).

  These EDI messages are received from APAC trading partners. The files do not contain standard envelope headers or explicit message identifiers.

  For these EDI messages, the trading partner and message type are identified from EXS-provided metadata. The metadata consists of the Data Source Name (DSN) and the EXS Partner Name.

  The identification process works consistently across supported communication protocols, such as FTP, OFTP2, and AS2.

  Note: For proprietary headerless files for APAC trading partners, one message per file is expected. If a source file contains multiple messages, you must split the file before you send the file to AE.

If configured, the messages are transformed into another structured format before they are processed.