Why Are Shipments Not Updating "CUM" Quantity In Release Management? (Doc ID 1397024.1)

Last updated on OCTOBER 06, 2015

Applies to:

Oracle Release Management - Version 12.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 06-OCT-2015***

Goal

Currently have CUM enabled for the ship from/ship to level and CUM keys have been
created. After ship confirmation, the Interface Trip Stop & DSNO runs, why doesn't
the system update CUMS in RLM?


Solution

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