My Oracle Support Banner

E1: 40R: Enhancement to Prevent Shipment Lines from Being Orphaned when Demand Detail Quantity is Reduced (Doc ID 3038224.1)

Last updated on JULY 30, 2024

Applies to:

JD Edwards EnterpriseOne Demand Scheduling Execution - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

If there are multiple sales order lines against a single demand detail (F40R11) record with 2 shipments and the demand detail quantity is reduced either manually or due to a new release coming in, after ship confirming the first shipment line the second shipment line will become orphaned because all of the available quantity in demand detail gets consumed and the (F40R11) demand detail record gets deleted and moved to the F40R41. CUMs will not be adjusted in F40R12 for the 2nd shipment, and the ASN will be missing the Demand Detail related field in the ASN (F470371). This issue was reported in Bug 36106120 - ORPHAN SHIPMENT CREATED FOR DEMAND SCHEDULING SALES ORDER and development returned it as functioning as designed for the following reason.

When the user decreases the demand and the P4210 processing option "Status Code Limit for Changes" is set to not update the sales order status and re-running the R40R010, error  “Next status not Cancellable/Change” is set and can be seen in the Work Center. This is expected. The user needs to consider the error in the work center before processing the shipment. Once after the demand is satisfied the system will go ahead and delete the F40R11 which is functioning as designed.

Workaround:
Use a different version of P4210 where "Status Code Limit for Changes" processing option is not enabled when rerunning the R40R010 if there is a change in demand.

The above workaround will not work for the customer for the following reasons:

If you use a different version of P4210 that allows changes up until after an order has been shipped, it will delete/update lines that you really don't want updated. For instance, if one has 2 pallets wrapped and about to get loaded on the truck and the customer changes their order/decreases it to 1 pallets 5 minutes before shipping, we are not going to accept that decrease and will ship the full quantity that is prepped to be shipped. This is very common in the automotive industry to be a "previous day shipper" that you ship based off the previous days demand that was sent.  

The enhancement request is to keep the F40R11 records out there with a pending delete until all lines in the F4211 using that demand key are cleared out and moved to history. Otherwise the risk of orphaned records is incredibly high. 

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


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