Last updated on JUNE 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 11.5 to 12.1 [Release 11.5 to 12.1]
Information in this document applies to any platform.
In Legacy Collections:
Pre-process monitor for MSC_ST_BOM_COMPONENTS flags most of the records in (MSC_ST_BOM_COMPONENTS table with error_text = "MSC_PP_DATE_OVERLAP".
Context: Our solution for data load in ASCP is to populate staging table (MSC_ST_BOM_COMPONENTS) and run pre-process monitor and ODS load to load data in MSC_ST_BOM_COMPONENTS.
We have multiple records for org, assembly name and component combinations with different effective date and disable date ranges (no overlaps) as the requirement is to have different usage quantity by months.
This can also happen with other types of Flat file loads in Legacy Collections
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