Search Results load_wip_demand

Overview

MSC_CL_WIP_ODS_LOAD is an Oracle Applications (APPS) PL/SQL package that belongs to the MSC (Advanced Supply Chain Planning / Oracle Planning Central) schema components shipped with Oracle E-Business Suite. Its header comment ($Header: MSCLWIPS.pls 120.0 2007/04/12) confirms it originated as part of the MSC "WIP" interface source, consolidated into the collection-loading layer. The package name encodes its role: MSC (the planning product), CL (collection or "collection load"), WIP (Work in Process), and ODS (Operational Data Store). In practice, the package loads Work-in-Process job, demand, and resource data from the transactional EBS tables into the MSC staging and ODS tables used by the supply chain planning engine. It is the inbound pipeline that populates WIP-derived demand and capacity information prior to a planning run.

Key Procedures and Functions

• LOAD_JOB_DETAILS — Loads discrete job and job-operation detail, capturing job structure and operation-level records required for planning visibility.
• LOAD_WIP_DEMAND — Populates demand records derived from WIP jobs, making component and job demand available to the planning data model.
• LOAD_RES_REQ — Loads resource requirement records, i.e., the capacity and resource demand associated with WIP operations.
• LOAD_RES_INST_REQ — Loads resource instance requirements, handling the more granular instance-level resource demand (e.g., specific machine or resource instances).
• LOAD_ODS_RES_REQ — Documented in the ETRM 12.2.2 metadata as an additional procedure for loading resource requirements into the ODS tables; complements LOAD_RES_REQ by targeting ODS-specific structures.

Five procedures are documented; no parameter lists are specified in the available source metadata, and none are invented here.

Tables Accessed

The package reads and writes the following tables (referenced via APPS synonyms):

• MSC_DEMANDS and MSC_ST_DEMANDS — demand records and their staging counterparts, populated by LOAD_WIP_DEMAND.
• MSC_JOB_OPERATIONS, MSC_JOB_OPERATION_NETWORKS, MSC_JOB_OP_RESOURCES, MSC_JOB_OP_RES_INSTANCES, MSC_JOB_REQUIREMENT_OPS — the job-operation, network, resource and requirement operation tables used by LOAD_JOB_DETAILS and the resource loaders.
• MSC_RESOURCE_REQUIREMENTS and MSC_ST_RESOURCE_REQUIREMENTS; MSC_RESOURCE_INSTANCE_REQS and MSC_ST_RESOURCE_INSTANCE_REQS — resource requirement and resource-instance requirement records with staging equivalents, targeted by LOAD_RES_REQ, LOAD_RES_INST_REQ and LOAD_ODS_RES_REQ.
• MSC_ITEM_ID_LID — the item surrogate/ID lookup used to resolve item identifiers during load.

The MSC_ST_* tables are staging tables, while the corresponding MSC_* tables are the ODS/target tables consulted by the planner.

Usage Notes

MSC_CL_WIP_ODS_LOAD is a backend collection package and is not exposed through an EBS form. It is typically invoked from the MSC collection/ODS loading framework — historically via the Advanced Supply Chain Planning collection programs (such as the "Load WIP" / collection loader concurrent processes) or chained from the parent collection driver. The metadata indicates it is referenced by one other package, which drives execution as part of the larger MSC collection load flow. Oracles' ETRM classifies the API as OTHER, not as a public or open interface, so custom code should not call it directly; integrations should use the standard collection concurrent programs. Because its work is staging-oriented, it is invoked during the data-collection phase immediately preceding a plan run, ensuring WIP job, demand and resource requirement data is refreshed before the planning engine reads the ODS.