Search Results msc_errors_s

Overview

MSC_CL_COLLECTION is the core collection orchestration package body in the Oracle Advanced Supply Chain Planning (ASCP) schema, APPS. It coordinates the extraction, staging, and loading of source data from operational systems into the MSC (Advanced Planning) staging and ODS tables that feed the planning engine. In Oracle EBS 12.1.1 and 12.2.2, this package drives the "Collections" concurrent process, which gathers supply, demand, item, BOM, routing, WIP, RPO, and setup data from sources such as Oracle Inventory, Purchasing, Order Management, and Work in Process. It manages worker launch, monitoring, error logging via MSC_ERRORS_S, staging-table purging, and key generation for items and trading partners. The package body is classified as OTHER and is valid in the APPS schema.

Key Procedures and Functions

• LAUNCH_WORKER — Starts individual collection worker processes that pull a specific data category.
• LAUNCH_MONITOR / LAUNCH_MONITOR_CONT / LAUNCH_MON_PARTIAL / LAUNCH_MONITOR_DET_SCH — Monitor running workers, manage the overall collection run, and support partial and detailed scheduling modes.
• DELETE_PROCESS — Removes a collection process record after completion or failure.
• ALTER_TEMP_TABLE / TRUNCATE_MSC_TABLE / DELETE_MSC_TABLE — Perform DDL and DML maintenance on staging and MSC tables.
• PURGE_STAGING_TABLES / PURGE_STAGING_TABLES_SUB — Clear obsolete staging rows before or after collection.
• GENERATE_ITEM_KEYS / GENERATE_TRADING_PARTNER_KEYS — Create surrogate keys required by the planning engine.
• ENTER_MODELLED_INFO — Insert modelled/simulated planning information.
• Q_PARTIAL_TASK — Manage partial-task queueing.
• LOG_MESSAGE — Write diagnostic messages, including to MSC_ERRORS_S and FND_FILE outputs.
• IS_MSCTBL_PARTITIONED — Detect partitioning to choose an appropriate load/purge strategy.
• INITIALIZE / INITIALIZE_LOAD_GLOBALS — Set up global variables and collection parameters.
• COMPUTE_RES_AVAIL — Calculate resource availability data.

Tables Accessed

• MSC_COLLECTION_S — Master collection run record; drives status and control.
• MSC_ERRORS_S — Stores collection errors and messages, central to diagnostics.
• MSC_COLL_PARAMETERS — Collection parameters controlling scope and behaviour.
• MSC_PLANS, MSC_APPS_INSTANCES, MSC_COMPANIES, MSC_SOURCING_HISTORY, MSC_TRADING_PARTNERS — Plan, instance, company, sourcing, and partner metadata.
• FND_LOOKUP_VALUES, FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS — EBS lookup and configuration data.
• ALL_SOURCE, ALL_TABLES, AD_DDL, DBMS_LOCK — Dynamic SQL, metadata, and locking utilities.

Usage Notes

The package is invoked primarily through the Collections concurrent program and related ASCP manager requests rather than from forms. Administrators launch collections from the Planning Manager responsibility; internally, MSC_CL_COLLECTION calls ODS-load packages such as MSC_CL_ITEM_ODS_LOAD, MSC_CL_BOM_ODS_LOAD, MSC_CL_DEMAND_ODS_LOAD, MSC_CL_SUPPLY_ODS_LOAD, and MSC_CL_WIP_ODS_LOAD. Because it writes to MSC_ERRORS_S, the user search term "msc_errors_s" maps directly here: failed or partial collections are diagnosed by querying this table and MSC_COLLECTION_S. The package is referenced by 19 other ASCP packages but is not itself referenced by external database objects, confirming its role as a top-level orchestration entry point. Custom interfaces should call the Collections concurrent program rather than the package directly to preserve dependency integrity.