MSC:Select Sourcing Rules In ATP Based On Profile Does Not Work For Request Date
Last updated on JUNE 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 18.104.22.168 and later
Information in this document applies to any platform.
On : 22.214.171.124 version, User Interface
When setting the profile MSC:Select Sourcing Rules In ATP Based On set on the request date it does not use the time based sourcing.
Further debugging of the code has narrowed down to code issue with the MSC_ATP_PVT package.
Usage of NVL on user defined types has no effect and the request date variable is not being populated due to which the source rule is identified based on the system date rather than the request date.
sourcing should be based on the effective dates from the sourcing rules
The issue can be reproduced at will with the following steps:
1. define sourcing rules with effectivity dates
2. add to assignment set
3. run collections and plan
4. schedule sales order. When using a request date which falls into the future sourcing it still uses the current one
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms