Global ASL Attributes Not Considered In ASCP Plan When Local ASL Attributes Exist
(Doc ID 2214587.1)
Last updated on JUNE 01, 2023
Applies to:
Oracle Advanced Supply Chain Planning - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
When ASL is created as global and some local attributes are setup, global
attributes are not considered in ASCP.
Since ASL is global, at least global attributes should be considered in ASCP
plan.
Item A is on a local AND a global ASL with both the local and
global ASL having the same supplier and in the ASCP plan output you
do find the supplier listed as the supplier, but no capacity data is
displayed
item B is also on a local AND global ASL like item A,
except B has 2 suppliers on the ASL's and in the ASCP plan output you do find just the supplier 1 listed as the
supplier, but no capacity data is displayed.
item C only has a global ASL and displays the expected data in the
ASCP workbench?
The expectation is that if a local and a global ASL is assigned to item then
the global ASL should be used in the ASCP plan.
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 |