DSNO Not Generated On Ship Confirm and Cum Also Not Updated
(Doc ID 1342565.1)
Last updated on MARCH 31, 2022
Applies to:Oracle Release Management - Version 22.214.171.124 and later
Information in this document applies to any platform.
Interface Trip Stop
Customer is facing issue with DSNO not being generated for a trading partner and CUM is also not updated upon ship confirmation for 862 SSSi file which was processed for the first time. The Interface Trip Stop log file shows the following error.
CUM Management Type is CUM_BY_DATE_ONLY
Unable to find CUM Shipment/Received Information on the schedule
ERROR OCCURRED IN RLM CUM QTY API
Exiting WSH_DSNO.SUBMIT_TRIP_STOP )
INTERFACETRIPSTOP: RESULT OF DSNO SUBMISSION FOR STOP_ID 50001 = WARNING
We have done all the necessary setups for a trading partner and processed the file and in turn shipped some items.
-- We have checked that CUM is not updated and DSNO is also not generated. Interface trip stop program goes into warning.
-- We have found that some descriptive flexfield setup was missing for this trading partner Application: Shipping Execution, Title: Additional Automotive TP Line/LPN Information
-- Again we have completed those setups and values were defaulted properly at delivery lines.
-- Now we again did the shipment but still CUM is not updated and DSNO is also not generated.
-- So, we have processed new schedule and new demand came to sales order and try to process new demand.
For these new demand CUM is updated and DSNO is also generated. Still the users are having issue with the
demand which was there from the first file and no CUM updating or DSNO generation is happening for those
demands after ship confirm.
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