My Oracle Support Banner

E1: 42/49: Changing Sales Order Quantity (F4211.UORG) After Shipment Confirmation Causes Data Integrity (Doc ID 2358262.1)

Last updated on FEBRUARY 05, 2019

Applies to:

JD Edwards EnterpriseOne Sales Order Processing - Version 9.1 and later
JD Edwards EnterpriseOne Transportation Management - Version 9.1 and later
Information in this document applies to any platform.


The order quantity field is not locked after ship confirm. This allows the user to change the quantity after the item has shipped, resulting in a data integrity problem between the Item Ledger (F4111) and General Ledger (F0911) when the order is processed by Sales Update (R42800)

Changes to the QTY quantity fields in Sales Order Entry are allowed after the order has been ship confirmed. When inventory is set to hard commit at time of ship confirm, allowing changes to the quantity causes downstream issues.
1. New items, per quantity increase, are not allowed to be ship confirmed as system has already processed this line for initial quantity and the actual ship date ADDJ is assigned.
2. If decreasing quantity, actual customer credit is not performed and inventory is not updated
2. Invoice reflects quantity changes for customer billing.
3. Sales update creates Journal Entries and processes sales records using value for changed quantity.
4. F42101/Cardex record remains at initial quantity ordered and is not updated to reflect quantity changes at time of sales update causing inventory integrity issues.

The customer needs to be able to change some fields after ship confirm, but would like to be restricted from changing the quantity on the sales order after performing shipment confirmation .

When a Sales Order Line has been Ship Confirmed and the On Hand Updated (SO02) field on the Sales Order Detail (F4211) line is updated, Sales Order Entry (P4210) should lock the Quantity Ordered field ort issue a hard error stating the quantity cannot be changed after the order has been shipped. Although users should check if an order has been shipped before processing a change they don't always do it.

1. Use the status code locking functionality behind Sales Order Entry <P4210/P42101> to prevent revisions to orders after ship confirm.
2. Use the approval process, so when an order line is changed it must be approved by someone (to acknowledge a change) and then identify how the inventory is going to actually get shipped.
3. Enter a new line on the sales order rather than changing quantity on existing sales order line(s)
4. Relieve inventory at the time of sales update instead of at ship confirm


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

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