Order Management - EBS (MOSC)

MOSC Banner

RLM CUM Receipts

edited Nov 26, 2013 10:45AM in Order Management - EBS (MOSC) 3 commentsAnswered
Customers send in an 830/862 with a SHP segment containing the CUMULATIVE Receipt Quantity and associated date range.  The actual FST Demand is Discrete quantiites.  Currently this CUM receipt quantity and dates are not mapped to the item_detail_subtype as "CUM', nor the DATE_TYPE_CODE_INT = "FROM_TO", If SHP01 = 02 then QTY_TYPE_CODE_INT= "CUMULATIVE", and SHP04 = START_DATE_TIME_DET, SHP05 = END_DATE_TIME rules.

So to clarify, if we just map these elements there is there a need to setup CUM keys for the SF/ST/Items based on this CUM receipt quantity sent?    Or is there value into setting the CUM keys up for some other Demand Processor calculations and in-transit calculations?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center