My Oracle Support Banner

E1: 47: Inbound Purchase Order Change Edit/Update (860/ORDCHG) (R47131/P47130/R47002C/P4210) (Doc ID 1340444.1)

Last updated on MARCH 01, 2024

Applies to:

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. This process is not for creating a new sales order and is only for sales orders that already exist in the system tables (F4201/F4211 - SO Header/Detail).

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:

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!

In this Document
 EDI Purchase Order Change Header - Inbound (F47131)
 EDI Purchase Order Change Detail - Inbound (F47132)
 EDI Order Address Information (F4706)
 EDI Order Text Lines - Header (F4714)
 EDI Order Text Lines - Detail (F4715)
 Processing Options for the EDI Inbound Purchase Order Change Edit/Create (R47131)
 Example of EDI Sales Order Changed
 EDI Fields That are Passed into Sales Order Entry:
 Adding NEW Lines to Existing Sales Orders Using EDI
 Updating Sales Orders With Kits
 Changing Lines From Future Committed to Current 
 Updating Sales Transfer (ST/OT) Orders
 Checklists for New Implementations
 What to Check for Work Center Errors
 What to Check if the Desired Field is Not Updated As Expected
 Frequently Asked Questions
 Question 1: After populating data into F47131/F47132 through the P47130 program, the EDI Inbound Purchase Order Change Edit/Create (R47131) ends in error.
 Question 2: When attempting to process an order change to a three line order using the EDI Inbound Purchase Order Change Edit/Create (R47131) only the first line is changed. The work center has errors for the second two lines relating to "Fetch from Cache Failed'.
 Question 3: When attempting to change an existing sales order via Inbound 860/R47131, error "47E01 - Address and GLN supplied are blank" is displayed in work center, even though F47131.SYITAN (Address number Invoice To) is populated with the correct address book number.  In this scenario the 'Invoice To' address book number is not set up with Global Locator number (GLN), and no F0101G records are created for the Invoiced To address book number.
 Question 4:  The EDI Inbound 860 (R47131) is changing the currency code from foreign to domestic on the sales order. Why is this occurring?
  Question 5: Can lines be added to a sales order in the SO history tables F42019/ F42119?
 Question 6: Do fields with UDC tables cause errors on the program even when you cannot tell which UDC they are in the report?
 Question 7: How can an entire sales order and/or sales detail lines be cancelled?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.