MAC-PAC Homecontact ussupport login 
Documentation > MAC-PAC Reference Library > Distribution > Electronic Data Interchange > Key Concepts and Procedures > MAC-PAC's EDI Capabilities > Exception Processing

Exception Processing

 

All inbound EDI transactions (sales orders, purchase order acknowledgments, and purchase order receipts) are validated.  As they are processed, the status field on the transaction files is updated.  The following table tracks the status of each transaction.

 

Transaction
(program)


Successful


Not Successful

After Error Resolution

Sales Orders
(ED140E)

deleted

E (error)

blank

Purchase Order Acknowledgments
(ED100E)

deleted

1 (header error)
2 (line error)

blank

Purchase Order Receipts
(ED120E)

3

1 (header error)
2 (line error)

blank

 

If an inbound EDI transaction cannot be processed, an exception report will be generated listing each transaction in error at the header, line, and comment levels.  These reports can be used to identify required corrections or modifications.

If any part of a transaction is invalid, an associated online exception review program (ED110E, ED130E, ED150E) can facilitate correction.  Each of these conversations displays the erroneous transaction, along with any associated error messages.  When working with a transaction record, you have several processing options:  you can reenter correct data; you can delete the entire transaction using the function key F14-Delete; or, in certain cases, you can delete a transaction line using the function key F18-Delete Line/Comment.

If you choose to modify the transaction, after you are done, you will need to resubmit it for processing.  Because the exception program resets the status fields on the transaction files to blanks, the records are able to be reprocessed by the appropriate MAC-PAC conversation¾the same as regular inbound transactions.  If you choose to delete the transaction, you may either re-create it manually through the appropriate MAC-PAC conversation, or request that it be retransmitted from the sender.

Correcting Transaction Data

The online exception resolution conversation displays the erroneous transaction, along with any associated error messages.  It then allows you to resolve errors and resubmit the transaction for processing.  There are, however, some restrictions that apply when correcting transaction data.

For example, there are fields that refer to the trading partner who sent the information.  These fields, listed in the following table, cannot be changed because they refer to the trading partner's transaction, and therefore you are not able to verify whether they are accurate.

 

Inbound EDI Transactions


Sales Orders

Purchase Order Acknowledgments


Purchase Order Receipts

Customer PO Number

PO Number

PO Number

Customer PO Line Number

PO Line Number

PO Line Number

Ship-to Customer

Vendor SO Number

Vendor SO Number

Bill-to Customer

Vendor SO Line Number

Vendor SO Line Number

 

Order Type

Vendor BOL Number

 

 

Order Type

 

If there are problems with any of the key fields above, you must delete the transaction and either enter it manually through the appropriate MAC-PAC conversation or request that the customer resend it with correct data.

Other circumstances can also occur where errors prohibit transaction processing.  This happens when order information cannot be processed by the system.  Frequently the field in error will not appear in the Exceptions conversations.  If this is the case, MAC-PAC will generate an error message displayed at the bottom of the screen and you must stop processing the transaction, apply the necessary changes to your database, then begin reprocessing the transaction.

Processing Deletions

If a transaction's errors cannot be fixed, several options exist for deleting inbound transactions.  The deletion options available depend on the type of transaction being processed.

Inbound Purchase Order Receipts

If an inbound purchase order receipt transaction's errors cannot be fixed, the system will not process any part of that transaction.  All records associated with a transaction selected for deletion will be deleted from the transaction files within the error resolution program.  Also, all records associated with a selected or deleted transaction will no longer be available in the error resolution program.  If you delete a purchase order receipt transaction in error, all information associated with the purchase order receipt will be deleted, including header and line records.

Inbound Purchase Order Acknowledgments

Inbound purchase order acknowledgment transactions will be processed as long as there is a valid header record.  If you delete a purchase order acknowledgment transaction line that is in error, only the current acknowledgment line will be deleted.  This means that if the header record is deleted, all associated lines will also be deleted.  However, if the header record is valid, only the transaction line in error will be deleted.

Inbound Sales Orders

If you delete a sales order with a header-level error, all information associated with the sales order will be deleted, including header, line, comment, option, and multi-site records.  If you delete a sales order transaction line or comment that is in error, only the current line or comment will be deleted, along with its associated details.  For line, comment, or options errors, you can choose to delete the entire sales order transaction or just the corresponding line or comment, along with its associated details.  However, for header-level and multi-site-level errors, you will only be able to delete the entire transaction and its associated lines.

A sales order will not be created unless all information received for that transaction is valid (including the header, all lines, options, comments, and multi-site records).