Order Scheduling Not Honoring a Decimal for Transit Time (Delivery Lead Time)
(Doc ID 2230685.1)
Last updated on FEBRUARY 06, 2017
Applies to:Oracle Global Order Promising - Version 12.2.5 and later
Information in this document applies to any platform.
Intransit days are entered as decimal quantities. They expect the delivery lead times to be the same. Order Scheduling does not honor a decimal for transit times when it is coming as a delivery lead time at sales order line level. Although at setup level, the system will allow decimal that means if either Intransit days is 1.59, in that case delivery lead time is 2.
Another example is if intransit days is 2.59, in that case delivery lead time will be 3.
Is it standard functionality that decimals are not supported in the delivery lead time?
Need to validate the following examples:
1) If the number of Intransit Days = 1.59 or 1.10 or 1.90, then
the delivery lead time will be 2.
2) If the number of Intransit Days = 0.59 or 0.99 or 0.65, then
the delivery lead time will be 1.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!