E1: 42: 47: EDI Inbound Purchase Order Edit/Create (R47011) Populates Sales Order Detail File (F4211) With Expired/Canceled Blanket Order Details (Doc ID 2904863.1)

Last updated on FEBRUARY 27, 2024

Applies to:

Symptoms

Using the Inbound EDI Order Inquiry application (P47010), the EDI transaction set 850 is configured to release from a blanket order, but the blanket order is expired, with a Cancel Date in the past. Running the EDI Inbound Purchase Order Edit/Create (R47011) correctly ignores the blanket order price, but still links the generated sales order to the blanket via the Original Order number field.

Steps to Duplicate:

1. Create a sales blanket order (SB) for a specific item and customer, and ensure that the Cancel Date is for a past value, less than today’s date.
2. Configure the EDI 850 process via the P47010 application; populate the ‘expired’ related order number/type/company/line number as required, in order to trigger blanket release. Set a value in the Unit Price field that is noticeable different to the item’s base price, or that in the blanket order.
3. Configure the R47011 to call a version of P4210 where blanket order processing is activated.
4. Execute the R47011, confirm that the order is generated with the unit price specified in the EDI detail table. Check the F4211 table for the generated SO number, the expired blanket order’s details are all populated. As the order quantity was not released from this blanket, these fields should not be populated.

Changes

Cause

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