E1: 42: 47: Blanket Order Release via EDI 850 Transaction Set Fails to Populate Related Order Information in Sales Order Detail Table (F4211) for Generated Order
(Doc ID 2914486.1)
Last updated on DECEMBER 08, 2022
Applies to:
JD Edwards EnterpriseOne EDI - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Where the EDI transaction set 850 is used to release from an existing sales blanket order, the required fields to identify the blanket are populated in the EDI detail table (F47012), but these fields are NOT copied over to the F4211 table on the generated order. Field names OKCO, OCTO, and OGNO are not copied over; only field OORN (Related Order Number) is copied over correctly.
STEPS TO DUPLICATE
- Create a sales blanket order (SB) for a specific item and customer.
- Configure the EDI 850 process via the P47010 application; populate the Related Order number/Order Type/Company/Line Number as required, in order to trigger blanket release.
- Configure the R47011 to call a version of P4210 where blanket order processing is activated.
- Execute the R47011, confirm that the order is generated, and that the Original Order number field (OORN) holds the value of the blanket order. Further confirm that the F4211 fields for related Company/Order Type and Line Number fields are blank.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |