VEH_CUS_ITEM_CUM_KEY_ID : CUMS Keys UOM Defaults to Primary UOM When INTERFACE TRIP STOP IS RAN
(Doc ID 2746193.1)
Last updated on AUGUST 09, 2021
Applies to:
Oracle Shipping Execution - Version 11.5.10.2 and laterOracle Release Management - Version 11.5.10.2 and later
Information in this document applies to any platform.
Symptoms
On : 12.2.10 version, Interface Trip Stop
When attempting to run Interface Trip Stop (ITS)
the following error occurs.
OBSERVATION
-------------------
Whenever any Trip is ship confirmed then ITS is submitted automatically which
updates the CUM key with shipped quantity of that item. it is observed that ITS is
not updating the CUM key (of all the items of that particular Trip for which ITS is
submitted) with shipped Qty if there is an item having different UOM in CUM key
set up & at sale order line.In this case, it completes in warning and do not update
the Cum keys.
ERROR
-----------------------
CUM Management Type is CUM_BY_DATE_ONLY
profile Option Value XXC06836_USE_BUSINESS_CALENDAR : Y
p_in_chr_entity_type :ORGANIZATION
l_chr_cal_code :FRD_MFG
Date:30-OCT-20
Order line will be associated with the following CUM Key ID: nnn20
User-Defined Exception
ERROR OCCURRED IN RLM CUM QTY API
Exiting WSH_DSNO.SUBMIT_TRIP_STOP
INTERFACETRIPSTOP: RESULT OF DSNO SUBMISSION FOR STOP_ID 2060139 = WARNING
STEPS
-----------------------
1. Responsibility: Order Management Super User
2. Run > Interface Trip Stop
3. Completes with Error: ERROR OCCURRED IN RLM CUM QTY API
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |