DATAFIX: CUM Key Created On Previous CUM Key (JAN-2015) Instead The New CUM Key (JAN-2016)

(Doc ID 2107629.1)

Last updated on FEBRUARY 17, 2016

Applies to:

Oracle Release Management - Version 12.1.3 and later
Information in this document applies to any platform.


Q1: Why shipments are reflecting in a CUM Key of 01-JAN-2015 instead of the new CUM Key 01-Jan-2016?​
Q2: Where can we find the cum key that will be affected once a sales order line (that is in AWAITING SHIPPING status) is shipped?

Summary of Issue
For customers with an active Cum Management
Customer sends their schedules every day and they send a new CUM Key every year.
We have sales order lines for dates after 01-Jan-2016 that were created on Dec-2015 because customer sends a 30day
firm vision of demand on their schedules. So these lines were created when de CUM Key was 01-JAN-2015, but customer
reset their CUM Key on the schedule received on 01-JAN-2016.

​​New CUM Key was created in CUM Workbench for the 01-JAN-2016 but some shipments still reflecting on the CUM Key
01-JAN-2015 causing errors on the demand reconciliation.

We ran the request CUM Transactions CUM Key Adjustment, but this only corrects the shipments that were already closed
and put those on the correct CUM Key. We need to fixed the CUM Key that is associated with the order lines that are not
shipped yet so once they ship it automatically affects the correct CUM Key (01-JAN-2016)​


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