E1: 47: Inbound Purchase Order Change Edit/Update (860/ORDCHG) (R47131/P47130/R47002C/P4210)
(Doc ID 1340444.1)
Last updated on APRIL 30, 2020
JD Edwards EnterpriseOne EDI - Version XE and later Information in this document applies to any platform.
When a customer sends you purchase order changes (860/ORDCHG), the translator software maps the data to a flat file, and the Flat File Conversion program copies it to the EDI inbound interface tables. After this data is in the EDI inbound interface tables, you must run the Inbound Edit/Update program for Customer Order Changes to compare the received changes to the original data on the open sales order. The Inbound Edit/Update program retrieves the data from the EDI inbound interface tables and compares it to the applicable sales orders.
When the Inbound Edit/Update program compares the data in the EDI inbound interface tables with the data in the sales order management application tables, the system:
Prints an Inbound PO Change Discrepancy Report listing the customer orders with changed data.
Advances the status of the customer order, if changes are found, according to the parameters you set in the processing options.
Places the order on hold, if changes are found, according to the parameters you set in the processing options.
Marks the corresponding records in the EDI inbound interface tables as processed. Any record that has been processed cannot be reprocessed.
Performs kit balancing and enables changes depending on the statuses of the component items and whether the components have been processed individually.
After the Inbound Edit/Update program identifies the changed orders, you can use the Sales Order Entry program (P4210) to update the changed orders.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!