My Oracle Support Banner

MSC:Select Sourcing Rules In ATP Based On Profile Does Not Work For Request Date (Doc ID 1634732.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Advanced Supply Chain Planning - Version 11.5.10.3 and later
Information in this document applies to any platform.

Symptoms

On : 11.5.10.3 version, User Interface

ACTUAL BEHAVIOR
---------------
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.

EXPECTED BEHAVIOR
-----------------------
sourcing should be based on the effective dates from the sourcing rules

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Order management
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


Cause

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
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.