Last updated on MARCH 08, 2017
Applies to:Oracle Value Chain Planning Integration Base Pack - Version 2.5 and later
Information in this document applies to any platform.
Customer does the following:
1. Run UBE for sales orders
2. Run Collect sales history
3. Check t_ep_site table on demantra schema and find duplicate values when the user either (1) changes the alpha name of the address book number in P01012 or (2) if the parent AB# is changed in the 'Related Address' tab.
-- lowest level is ship to combination
-- next level is bill to combination
Customer has sys_params (system tab) set to accumulatedOrUpdate = Update
Issue is with loading complete sales history. Instead of net change, the customer used "Customer Request Date (CRD)" as the demand date, since they can have multiple shipments for a SO.
All shipments have the sames CRD date, in update mode it will update the quantity, for instance:
Sales Order Qty is 300 LB with CRD of 01-JUL-2011
Jul shipment 100LB
demantra load 100 LB with CRD of 01-JUL-2011
Aug shipment 100LB
demantra load 100 LB with CRD of 01-JUL-2011 (JUL 100 is overwritten)
Sep shipment of 100LB
demantra load 100 LB with CRD of 01-JUL-2011 (Aug 100 is overwritten)
Demantra shows 100 LB instead of 300 LB after Sep load, this is wrong
So, the customer chose to load complete sales history instead of net change.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms