Need to Prevent 'Reschedule In' Prior to Sourcing Rule Effectivity
Last updated on MARCH 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.3 and later
Information in this document applies to any platform.
In a VCP 12.2.3 Instance:
After running an unconstrained ASCP plan,
an internal requisition (IR) is not getting sourced correctly when there are multiple TRANSFER FROM organizations defined for different date ranges.
When there are multiple 'Transfer from Org' sourcing rules, the system is not adhering to the rule properly and taking the prior rule. Here is the scenario:
The M1 org is going to buy the product from the M2 Org until 31-DEC-2017.
After that date (as of 01-JAN-2018), it will buy from the M3 org. Therefore, sourcing rules are placed accordingly:
SR 1 - Transfer from M2 - valid from today's date until 31-DEC-2017
SR 2 - Transfer from M3 - valid from 01-JAN-2018 onwards
The planning engine will often peg 2018 planned order supplies to 2017 demands. In the Planners Workbench (PWB), the recommendation will then be to 'Reschedule In'.
When doing so, the sourcing org is then incorrect (as it is prior to the effectivity date of the sourcing rule for that org).
This is affecting the planning for the components.
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