Search Results msd_dem_schema

Overview

MSD_DEM_SOP is an Oracle EBS Advanced Supply Chain Planning (ASCP) package body owned by APPS and classified as OTHER in the ETRM repository. It belongs to the MSD (Master Scheduling/MRP Demand) module family, whose objects support demand planning and the integration of supply plan data between Oracle EBS and the Strategic Network Optimization (SNO) / Advanced Supply Chain Planning engines. The package is responsible for orchestrating the load of plan-level, member-level, cost, and series data required by downstream planning processes, and for coordinating the interaction between the EBS database and external planning schemas.

Version headers in the source (msddemsopb.pls 120.17) confirm the object has been maintained as a component of the 12.1.1 baseline and remains present in 12.2.2. The package declares a global variable g_schema and exposes a set of private helper functions, notably GET_PLAN_ID and GET_PLAN_TYPE, which resolve a supply plan's identifiers dynamically against the table returned by MSD_DEM_COMMON_UTILITIES.get_lookup_value for the lookup type MSD_DEM_TABLES / SUPPLY_PLAN. This dynamic SQL pattern allows the package to target the correct supply plan table regardless of deployment configuration.

Key Procedures and Functions

The documented procedure and function surface consists of fifteen public entry points:

• LOAD_PLAN_DATA, LOAD_PLAN_DATA_WO_PDS, LOAD_PLAN_DATA_WO_ODS — load plan-level data, with variants that skip PDS (planning data store) or ODS (operational data store) processing paths.
• SET_PLAN_ATTRIBUTES — initialises or updates attributes on the target plan before or during a load.
• LOAD_PLAN_MEMBERS — populates the plan member hierarchy from source planning tables.
• LOAD_ITEM_COST / LOAD_COST — extract and stage item cost data for use in plan costing.
• LOAD_SERIES_DATA_BATCH — batch load of demand/supply series data into MSD_DEM_SERIES.
• POST_DOWNLOAD_HOOK — post-processing hook executed after a download completes.
• WAIT_UNTIL_DOWNLOAD_COMPLETE — polling routine that blocks until the external download finishes.
• COLLECT_SCI_DATA / LAUNCH_SCI_DATA_LOADS — collect and launch Supply Chain Intelligence data loads.
• GET_WO_SUPPLY_ID_FROM_DEMAND / GET_WO_SUPPLY_ID_FROM_SUPPLY — resolve work order supply identifiers from demand or supply records.
• KILL_JOBS — terminates background jobs, using DBMS_JOB and USER_JOBS.

Tables Accessed

The package reads and writes the core ASCP planning tables: MSC_PLANS (plan definitions and plan types), MSC_PLAN_MEMBERS equivalents via MSC_PLAN_BUCKETS, MSC_PLAN_ORGANIZATIONS, and MSC_PLAN_SCHEDULES, which together hold planning calendar and bucket metadata. MSC_APPS_INSTANCES identifies the source EBS instance. MSD_DEM_SERIES stores the time-series demand and supply data loaded by LOAD_SERIES_DATA_BATCH. DBA_OBJECTS supports metadata validation, while DBMS_JOB, DBMS_LOCK, DBMS_RANDOM, and USER_JOBS provide job submission, locking, and concurrency control during the load lifecycle.

Usage Notes

MSD_DEM_SOP is invoked indirectly rather than from a form. It is referenced by two other packages and is typically driven by concurrent programs or scheduled batch jobs that perform plan data downloads and uploads for the demand/supply planning schema. Because it manipulates MSC_PLANS and MSD_DEM_SERIES directly, it must be executed in the context of an active ASCP plan and with the appropriate MSD_DEM_DEBUG profile option set when diagnostic logging is required. Custom code should invoke the public procedures only; the GET_PLAN_ID, GET_PLAN_TYPE, LOG_DEBUG, and LOG_MESSAGE routines are private and subject to change between patch levels.