Setting Up EDX Exception Workflow

When using inbound electronic data exchange (EDX) messages, it may be desirable for exception conditions to be noted and brought to the attention of various people within the purchasing and inventory management organizations. These require processes to notify the procurement and inventory management organizations and ensure that appropriate measures are taken to react to these conditions.

When loading Item Catalog EDX messages, possible exceptions include price changes outside of expected tolerances, unknown items, and other exceptions. Receiving these exceptions should trigger notification to personnel in the buying and inventory management organizations to review and approve the changes. This ensures supplier compliance with buying arrangements and identification of errors before transactions are processed.

When loading Purchase Order Acknowledgement EDX messages, exceptions such as rejecting the purchase order or changing it must be addressed by the buyer to determine whether the changes are acceptable or require any additional follow up.

When you receive inbound Purchase Order Acknowledgment (X.12 855) and Item Catalog (X.12 832) EDX messages that have exceptions, the system provides exception notifications to resources in the buying organization.