EDI Transactions

EDI transactions can be categorized into two types:

• Inbound Transactions: Involves receiving and translating EDI files.
• Outbound Transactions: Involves generating and sending EDI files.

The figure below illustrates the basic flow of M2M EDI inbound and outbound transactions.

Inbound Transactions

The following figure depicts the flow of M2M inbound transaction processing.

EDI One/Aptean EDI provides a flexible computer interface for the dissemination of information between parties. It plays a crucial role in processing inbound transactions by formatting the received data into a suitable format for Made2Manage (M2M) and generating an intermediate file.

The inbound transaction processing in M2M involves several key components:

• Inbound Transaction Import (XIN): This window is used to import EDI transactions into the M2M system.

• EDI M2M Format Groupings (XGROUP): This window allows for the creation of groupings for M2M formats.

  M2M’s Electronic Data Interchange Infrastructure (EDI) identifies each transaction type with a unique three-digit number and a screen ID, which corresponds to the resulting M2M document. The M2M EDI processes the following inbound transactions:

• 830 - Planning Schedules with Release Capability (SO): This transaction creates or updates a Sales Order.

• 850 - Purchase Order (PO): This transaction creates a new Sales Order.

The M2M EDI supports two transaction processing schemes:

• Interactive Processing: This method requires manual initiation of both the import and document automation processes.
• Unattended Processing: This method allows the system to automatically handle both the import and document automation processes.

Interactive Transaction Processing (Inbound)

The interactive inbound transaction process in M2M involves the following steps:

1. Transaction Reception and Formatting: EDI One receives transactions from trading partners and formats the data according to the M2M fixed file format.

2. File Storage: EDI One stores the formatted file in its storage system.

3. Data Retrieval: Made2Manage calls the EDI One API to retrieve the transactions from storage.

4. Transaction Import: Upon receiving the API call, EDI One retrieves the requested transactions. You can use the Inbound Transaction Import (XIN) window to import these transactions.

   Exceptions like the following may arise during the import process:

   • The intermediate file does not exist.

   • The intermediate file cannot be opened.

   • The data in the intermediate file is not properly organized.

     The M2M EDI system handles exceptions based on the exception-handling scheme you choose:

   • Interactive Exception Handling: If an exception occurs, the system halts the import process.

   • Unattended Exception Handling: If an exception occurs, the system also halts the import process but logs the exceptions, which can be reviewed in the EDI Statistics (XSTATS) window.

5. Document Creation: In the relevant Document Automation Server window (X830DA or X850DA), generate documents from the imported transactions.

6. Exception Handling: Address any logged exceptions in the relevant Exception Log (X830EX or X850EX). The system provides a link from the log to the specific document where the exception occurred, allowing you to manually correct the data.

Unattended Transaction Processing (Inbound)

The M2M EDI unattended inbound transaction process involves the following steps:

1. Transaction Reception and Formatting: EDI One receives transactions from trading partners and formats the data according to the M2M fixed file format.
2. File Storage: EDI One stores the formatted file in its storage system.
3. Data Retrieval: Made2Manage calls the EDI One API to retrieve the transactions from storage.
4. Automatic Processing: According to an established schedule, the Made2Manage Processor Services automatically start the import process and create the document.
5. Exception Logging: The M2M system logs both import and document creation exceptions in the EDI Statistics (XSTATS) window.
6. Exception Handling: Address any logged exceptions in the appropriate Exception Log (X830EX or X850EX). For exceptions related to document creation, the system provides a direct link from the log to the specific document where the exception occurred, allowing you to manually correct the data.

Outbound Transactions

The following figure depicts the flow of M2M outbound transaction processing.

The outbound transaction processing in M2M involves several key components:

• EDI Outbound Transaction Export (XOUT): This window is used to export EDI transactions.
• EDI M2M Format Groupings (XGROUP): This window is used to create groupings for M2M formats.

The M2M EDI processes the following outbound transactions:

• 810 - Accounts Receivable Invoice (ARINV): Creates an invoice document.
• 855 - Purchase Order Acknowledgment (SO): Creates a Sales Order acknowledgment.
• 856 - Advanced Shipping Notice (ASN): Provides details for miscellaneous or sales order shipments.

Note: The 856/810 file can be exported only once; PROC does not support resending files.

Note: The 856/810 file can be exported only once; PROC does not support resending files.

The M2M EDI supports two transaction processing schemes for outbound transactions:

• Interactive: Requires manual initiation of the export process.
• Unattended: Automatically initiates the export process.

Interactive Transaction Processing (Outbound)

The interactive outbound transaction process in M2M involves the following steps:

1. Transaction Export: Use the EDI Outbound Transaction Export (XOUT) window to export the transactions.
2. Exception Handling: During export, exceptions may occur, such as:

   • The intermediate file cannot be created.

   • The intermediate file cannot be opened.

     The M2M EDI handles these exceptions based on the chosen exception-handling scheme:

   • Interactive Exception Handling: If an exception occurs, the system stops exporting transactions.

   • Unattended Exception Handling: If an exception occurs, the system stops exporting transactions but logs the exceptions in the EDI Statistics (XSTATS) window.

3. File Processing: The EDI One communication software processes the transactions in the intermediate file and moves the file to your EDI One network.

Unattended Transaction Processing (Outbound)

Unattended outbound transaction processing is specifically applicable for EDI 856 - Advanced Shipping Notice (ASN). The process involves the following steps:

1. Automatic Export: M2M EDI automatically exports transactions when documents reach a particular status, as defined during the setup procedure.
2. Exception Logging: The M2M system logs any exceptions related to import and document creation in the EDI Statistics (XSTATS) window.
3. File Storage and Transfer: Your host communication software stores the transactions in an intermediate file and transfers the file to the EDI One or Aptean EDI host’s network.