Processing Inbound EDI Transactions

To effectively manage inbound EDI transactions in M2M, follow these key steps:

1. Import inbound transactions. For more information, refer to the Import Inbound Transactions section.
2. Review intermediate records that failed during import. For more information, refer to the Review Failed Import Records section.
3. Create documents from the imported transactions. For more information, refer to the Create Documents from Imported Transactions section.
4. Address the exceptions logged in the appropriate exception log. For more information, refer to the Handle Logged Exceptions section.
5. Review EDI Processing Statistics. For more information, refer to the Review EDI Processing Statistics section
6. Check the EDI transaction history. For more information, refer to the Check EDI Transaction History section.

Import Inbound Transactions

Use the EDI Inbound Transaction Import (XIN) window to import the transactions.

To import inbound transactions:

1. Open the EDI Inbound Transaction Import (XIN) window using one of the following methods:
   • On the Electronic Data Interchange tab. In the General Information group, click Import/Export > EDI Inbound Transaction Import.
   • Enter EDI Inbound Transaction Import (XIN) in Navigation bar, and click Enter.
2. In the Transaction area, select the transaction type that you want to import.
3. Click Import. A message will appear indicating that the system has completed the import.
4. Click OK.

Note: To view details of exceptions that occurred during the import, open the EDI Statistics (XSTATS) window.

Review Failed Import Records

M2M EDI processes and validates the inbound EDI documents via API. The validation checks include the following:

• EDI ID of the trading partner sending the file.
• Permissions of the EDI trading partner.
• Structure of the file.

Records that fail validation are stored in temporary files. Made2Manage provides the following screens to view the failed records:

• EDI 820 Transactions (X820CR): Displays failed EDI 820 transactions. The EDI 820 document is a Payment Order Remittance that tracks payments received from customers, including amounts, invoice numbers, payment dates, and adjustments. You can edit or add data to failed transactions in this screen.
• EDI 830 Transactions (X830PO): Displays failed EDI 830 transactions. The EDI 830 document, a Planning Schedule with Release capability, includes information on expected item quantities, delivery dates, and billing and shipping details. You can edit or add data to failed transactions in this screen.
• EDI 840 Transactions (X840QT): Displays failed EDI 840 transactions. The EDI 840 document is a Request for Quotation, which formally requests pricing and details from suppliers. It includes product descriptions, quantities, delivery dates, and special requirements. You can edit or add data to failed transactions in this screen.
• EDI 850 Transactions (X850PO): Displays failed EDI 850 transactions. The EDI 850 document is a Purchase Order that specifies items, prices, and quantities required from a supplier. You can edit or add data to failed transactions in this screen.
• EDI 860 Transactions (X860PO): Displays failed EDI 860 transactions. The EDI 860 document is a Purchase Order Change Request that communicates modifications to existing purchase orders, such as changes in quantities, delivery dates, or product specifications. You can edit or add data to failed transactions in this screen.
• EDI 862 Transactions (X862PO): Displays failed EDI 862 transactions. The EDI 862 document is a Shipping Schedule that outlines the quantities of products needed and their shipping dates. It includes item numbers, quantities, shipping dates, and any special instructions. You can edit or add data to failed transactions in this screen.

Note: Currently, only the EDI 830 and EDI 850 transactions are certified for use.

Create Documents from Imported Transactions

Note: This section is relevant only if you use interactive transaction processing to import transactions.

After importing transactions, you can create M2M documents related to the EDI transactions. Use the appropriate Document Automation window to generate the M2M documents from the imported transactions.

To create M2M documents from imported inbound transactions:

1. Open the appropriate Document Automation window using one of the following methods:

   • On the Electronic Data Interchange tab. In the required EDI group, click EDI<nnn> Document Automation.

   Note: <nnn> refers to document number.

   • Enter EDI<nnn> Document Automation(X<nnn>DA) in Navigation bar, and click Enter.

2. In the grid, check the boxes in the Select column to choose the transactions for which you want to create documents.

3. Click Create <document name>. A message will appear indicating that the document has been created.

4. Click OK.

If an exception occurs during document creation, the process will stop, and the exceptions will be logged. Open the log file corresponding to the document created to review the details of the exceptions.

Handle Logged Exceptions

Exceptions may occur during the import of EDI transactions. To address these exceptions, open the appropriate Automation Exception window.

To handle logged exceptions during import:

1. Open the appropriate Document Exception window using one of the following methods:

   • On the Electronic Data Interchange tab. In the required EDI group, click EDI<nnn> Automation Exception.

   Note: <nnn> refers to document number.

   • Enter EDI<nnn> Automation Exception (X<nnn>EX) in Navigation bar, and click Enter.

2. In the grid, locate the document identified by the order number, item number, and release number that you need to correct, and double-click the row. The document form will appear along with a message explaining the exception.

3. Make the necessary corrections and click Save.

   The following windows will display records that failed during import:

   • EDI 820 Transactions (X820CR)
   • EDI 830 Transactions (X830PO)
   • EDI 840 Transactions (X840QT)
   • EDI 850 Transactions (X850PO)
   • EDI 860 Transactions (X860PO)
   • EDI 862 Transactions (X862PO)

Note: Currently, only EDI 830 and EDI 850 are certified for use.

4. If there are additional exceptions for the same document, the next exception message will be displayed.

   Note: Repeat the above steps for all other documents with exceptions and address all exception messages for each document.

5. After handling all exceptions, recreate the documents for which you have imported transactions. For more information, refer to the Create Documents from Imported Transactions section.

Review EDI Processing Statistics

Use the EDI Statistics (XSTATS) window to review Electronic Data Interchange (EDI) transaction import and export statistics.

The EDI Statistics (XSTATS) window contains Inbound and Outbound tabs.

The Inbound tab has the following sections:

• 820 - Payment Order/ Remittance Advice
• 830 - Planning Schedules with Release Capability (SO) - Creates or Updates SO
• 840 - Request For Quotation
• 850 - Purchase Order (PO) - Creates New Purchase Order
• 860 - Purchase Order Change
• 862 - Shipping Authorization

The Outbound tab has the following sections:

• 810 - Accounts Receivable Invoice (ARINV)
  • 846 - Inventory Advice(Export Statistics)
  • 855 - Purchase Order Acknowledgment (SO)
  • 856 - Advanced Ship Notice/Manifest (SHIP)
• 861- Receiving Advice/Acceptance Certificate
  • 862 - Shipping Schedule
  • 865 - Purchase Order Change Acknowledgment

Note: Currently, only EDI 830 and EDI 850 on the Inbound tab, and EDI 810, EDI 855, and EDI 856 on the Outbound tab are certified for use.

To check EDI import and export statistics:

1. Open the EDI Statistics (XSTATS) window using one of the following methods:
   • On the Electronic Data Interchange tab. In the General Information group, click Statistics > EDI Statistics (XSTATS).
   • Enter EDI Statistics (XSTATS) in Navigation bar, and click Enter.
2. Click the appropriate tab:
   • Inbound to view the import statistics.
   • Outbound to view the export statistics.
3. Click the section relevant to the transaction for which you want to view statistics.
4. Click Refresh.

The following details are displayed:

• Begin Date: The date and time the process began.
• End Date: The date and time the process ended.
• Passed: The number of transactions that were successfully processed.
• Failed: The number of transactions that failed processing.
• Messages: Details of any exceptions that occurred during processing.

5. Review the statistics.

Check EDI Transaction History

To review EDI transaction history, use the EDI Transaction History (XHIST) window. For viewing an item’s release history, use the EDI Release Item History (XITMHIST) window.

EDI Transaction History (XHIST) Window

The EDI Transaction History (XHIST) window allows you to audit EDI transactions. It displays information including the document ID, revision number, transaction date and time, and transaction reference in a grid.

To check EDI transaction history:

1. Open the EDI Transaction History (XHIST) window using one of the following methods:
   • On the Electronic Data Interchange tab. In the General Information group, click Statistics > EDI Transaction History.
   • Enter EDI Transaction History (XHIST) in Navigation bar, and click Enter.
2. Review the transactions listed in the grid.

EDI Release Item History (XITMHIST) Window

When importing an EDI 830 file, M2M verifies whether a related Sales Order (SO) item exists. If the SO item is found, M2M then checks for associated releases. If a release exists and is not yet shipped, M2M deletes the release and re-adds it based on the imported EDI 830 file. If a release has already been shipped, it remains unchanged. For partially shipped releases, M2M updates the release with the actual shipped quantity, deletes the remaining quantity, and re-adds it from the EDI 830 file. All changes, including deletions, additions, and modifications, are logged.

To view the release history of an item, use the EDI Release Item History (XITMHIST) window. This window can only be accessed if there is existing history for the SO item.