Search Results msc_bor_requirements_s

Overview

MSC_CL_BOM_ODS_LOAD is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and validated in release 12.1.1 and 12.2.2. Its role is to load bill of material, routing, resource, and process effectivity data into the Advanced Supply Chain Planning (ASCP) operational data store from the MSC staging tables. The package forms part of the MSC_CL collection layer, where the prefix "CL" denotes the collection process that moves source data from the transactional tables into the planning schema MSO/MSC structures. It consolidates multiple source entities, including BOMs, components, substitutes, routings, resources, department resources, resource setups and charges, setup transitions, resource instance changes, and process effectivity records, into the normalized planning tables. The object is not referenced by any database object, meaning it operates as a top-level load driver rather than a shared utility. Its external dependencies include FND_MESSAGE, FND_PROFILE, MSC_GET_NAME, MSC_UTIL, MSC_CL_COLLECTION, MSC_CL_ITEM_ODS_LOAD, and MSC_CL_EXCHANGE_PARTTBL.

Key Procedures and Functions

The ETRM metadata documents ten load procedures. LOAD_BOM and LOAD_BOM_COMPONENTS move bill of material headers and component requirements into the operational data store. LOAD_BOR populates bill of resources records. LOAD_COMPONENT_SUBSTITUTE handles approved substitute component relationships. LOAD_RESOURCE and LOAD_RESOURCE_SETUP load resource definitions and their setup attributes, while LOAD_RESOURCE_CHARGES loads cost or charge data associated with resources. LOAD_SETUP_TRANSITION loads setup transition rules used in constraint-based planning. LOAD_RES_INST_CHANGE loads resource instance change records. LOAD_PROCESS_EFFECTIVITY loads process manufacturing effectivity data into MSC_PROCESS_EFFECTIVITY. Each procedure draws from the corresponding MSC_ST_% staging table created by the collection extract process.

Tables Accessed

The package reads from and writes to the MSC operational data store. Staging tables include MSC_ST_BOMS, MSC_ST_BOM_COMPONENTS, MSC_ST_COMPONENT_SUBSTITUTES, MSC_ST_BILL_OF_RESOURCES, MSC_ST_BOR_REQUIREMENTS, MSC_ST_ROUTINGS, MSC_ST_DEPARTMENT_RESOURCES, MSC_ST_DEPT_RES_INSTANCES, MSC_ST_RESOURCE_GROUPS, MSC_ST_RESOURCE_SETUPS, MSC_ST_RES_INSTANCE_CHANGES, MSC_ST_SETUP_TRANSITIONS, MSC_ST_PROCESS_EFFECTIVITY, and MSC_ST_SIMULATION_SETS. Target tables populated include MSC_BOMS, MSC_BOM_COMPONENTS, MSC_COMPONENT_SUBSTITUTES, MSC_BILL_OF_RESOURCES, MSC_BOR_REQUIREMENTS, and their _S snapshot counterparts, MSC_DEPARTMENT_RESOURCES, MSC_DEPT_RES_INSTANCES and its _S twin, MSC_RESOURCE_GROUPS, MSC_RESOURCE_SETUPS, MSC_RES_INSTANCE_CHANGES, MSC_SETUP_TRANSITIONS, MSC_PROCESS_EFFECTIVITY and MSC_PROCESS_EFFECTIVITY_S, MSC_BOR_REQUIREMENTS, and MSC_BOR_REQUIREMENTS_S. Supporting tables MSC_COLL_PARAMETERS, MSC_ITEM_ID_LID, MSC_UNITS_OF_MEASURE, and MSC_SIMULATION_SETS supply collection parameters, item identifiers, unit conversions, and simulation context. The MSC_PROCESS_EFFECTIVITY_S table is of particular interest to users searching for process effectivity structures, as it stores the effective-dated effectivity snapshots consumed by planning.

Usage Notes

This package is invoked during the ASCP data collection cycle, typically launched by concurrent programs that execute the MSC_CL collection set. It is called after the extraction phase has populated the MSC_ST staging tables and before the planning engine consumes the operational data store. The procedures honor collection parameters retrieved from MSC_COLL_PARAMETERS, allowing selective loads by plan, organization, or simulation set. FND_PROFILE and FND_MESSAGE are used for session context and error reporting. Because the package is not referenced by other database objects, integrations should not call it directly unless replicating the standard collection flow; the recommended invocation path is through the standard MSC collection concurrent programs. Simulations are supported via MSC_SIMULATION_SETS and the MSC_ST_SIMULATION_SETS staging table.