Earliest Ship Date Assumes The Value From Not Before Date When New PO Is Injected Via RIB XOrder Interface
(Doc ID 2225879.1)
Last updated on FEBRUARY 01, 2017
Applies to:Oracle Retail Merchandising System - Version 14.1.2 and later
Information in this document applies to any platform.
How Earliest Ship Date Is Calculated When New PO Is Injected Via RIB XOrder Interface?
In XOrder interface there is no place holder for earliest and latest ship date in XOrder payload.
If "Not Before Date" is passed as part of the message, the "Earliest Ship Date" will be set same as the "Not Before Date".
This behavior is to support the orders which might be getting created well in advance.
For example, an order is created 2 months in advance and not before date is kept after 2 months in the message.
If supplier lead time is 3 days, retailer may not want to set the earliest ship date 3 days down the line from current date as they don't want supplier to start shipping order so early.
On screen user has the option to change the earliest ship date and latest ship date.
However since RIB payload doesn't have these fields, their values are driven from not before date.
If the "Not Before Date" and "Not After Date" are not passed in XOrder message, then the "Earliest Ship Date" will be calculated based on the supplier lead time and same will be used in the order.
If has been noticed that as per current implementation "Earliest Ship Date" is defaulted with "Not Before Date" value even if the value is not passed in XOrder interface.
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