DATAFIX - Trip Stop Is Failing With "Error Occurred In Release Management (RLM ) Cumulative (CUM) Qty API"

(Doc ID 1339641.1)

Last updated on AUGUST 02, 2017

Applies to:

Oracle Release Management - Version 11.5.10.2 and later
Information in this document applies to any platform.
***Checked for currency 26-APR-2016***

Symptoms

On : 11.5.10.2 version, RLM Cumulative Issues

When attempting to run Trip Stop it is failing with "ERROR OCCURRED IN RLM CUM QTY API"
the following error occurs.

ERROR
EXITING OE_ORDER_PUB.PROCESS_ORDER
Trip Stop ID: 8379669
Delivery ID: 940538258
Order Line ID: 1328255
Actual Shipment Date: 06-JUL-11
Shipped Quantity: 1
CUM Management Type is CUM_BY_DATE_ONLY
ORA-01422: exact fetch returns more than requested number of rows
ERROR OCCURRED IN RLM CUM QTY API
Exiting WSH_DSNO.SUBMIT_TRIP_STOP (07/07/2011 09:22:51 AM, 7.41 seconds)
INTERFACETRIPSTOP: RESULT OF DSNO SUBMISSION FOR STOP_ID 8379669 = WARNING
Entering WSH_SHIP_CONFIRM_ACTIONS.UPDATE_COMPLETION_STATUS (WSHDDSHB.pls 115.310.11510.16) (07/07/2011 09:22:51 AM)


STEPS
1. Responsibility: Order Management Super User.
2. Navigate to: Shipping > Interfaces > Interface Trip Stop - SRS
3. Observe: CUM Management Type is CUM_BY_DATE_ONLY
ORA-01422: exact fetch returns more than requested number of rows
ERROR OCCURRED IN RLM CUM QTY API
 

Cause

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