Global ASL Attributes Not Considered In ASCP Plan When Local ASL Attributes Exist
Last updated on MAY 05, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.3 and later
Information in this document applies to any platform.
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
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
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
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.
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