Results for “msc_demands”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_DEMANDS is the central demand repository within Oracle Advanced Supply Chain Planning (MSC). It stores every independent and dependent demand considered during a planning run, serving as the input side of the planning engine that matches requirements against supplies. The table resides in the MSC schema and is populated during the data collection and plan generation phases, drawing from sources such as sales orders, forecasts, work-in-process (WIP) component requirements, and inter-org transfers.

The documented description clarifies a critical design distinction: for dependent demands, DISPOSITION_ID functions as a foreign key to MSC_SUPPLIES; for independent demands, DISPOSITION_ID holds MRP_SCHEDULE_DATES.MPS_TRANSACTION_ID. This dual-purpose column is essential for pegging and sup/demand matching logic.

Based on the foreign key structure mined from the ETRM metadata, MSC_DEMANDS leans toward a satellite classification in Data Vault modeling terms. It enriches planning keys (PLAN_ID, SR_INSTANCE_ID, DEMAND_ID) with descriptive attributes and measures, while referencing multiple hub-like entities such as MSC_SYSTEM_ITEMS, MSC_TRADING_PARTNERS, and MSC_PROJECTS. The table also contains self-referencing links via PARENT_ID, reinforcing its satellite-leaning role within the broader supply chain data vault.

Key Information Stored

The surrogate primary key is composed of PLAN_ID, SR_INSTANCE_ID, and DEMAND_ID (constraint MSC_DEMANDS_PK). A unique business-key candidate exists on (PLAN_ID, DEMAND_ID, SR_INSTANCE_ID) via MSC_DEMANDS_U1, effectively reinforcing the same uniqueness with a different column ordering.

The most operationally significant columns include:

• DEMAND_ID – Unique identifier for each demand record within a plan and source instance.
• PLAN_ID – The specific plan to which the demand belongs.
• SR_INSTANCE_ID – The source application instance that originated the demand.
• INVENTORY_ITEM_ID – The item being demanded; joins to MSC_SYSTEM_ITEMS.
• ORGANIZATION_ID – The organization (warehouse, plant) holding the demand.
• DEMAND_TYPE and DEMAND_CLASS – Classify the demand (e.g., sales order, forecast, WIP component).
• ORIGINATION_TYPE – Identifies the source system (order entry, forecast, etc.).
• DISPOSITION_ID – Links dependent demands to MSC_SUPPLIES or independent demands to MRP transaction IDs.
• PARENT_ID – Self-referencing parent demand for hierarchical or dependent relationships.
• CUSTOMER_ID and CUSTOMER_SITE_ID – Reference the trading partner and site for the demand.
• QUANTITY_BY_DUE_DATE and PROMISE_DATE – Key quantity and date measures for planning calculations.
• DEMAND_PRIORITY, FORECAST_PRIORITY, and SALES_ORDER_PRIORITY – Priority ranking for allocation and pegging decisions.
• UNMET_QUANTITY and DMD_SATISFIED_DATE – Track satisfaction status and shortfalls.
• PROJECT_ID and TASK_ID – Associate demand with project accounting structures.

Common Use Cases and Queries

Planners and analysts frequently query MSC_DEMANDS to reconcile demand against supply, investigate pegging, and validate plan outputs. A typical query retrieves all demands for a given plan and item:

SELECT demand_id, inventory_item_id, organization_id, demand_type, quantity_by_due_date, promise_date FROM msc_demands WHERE plan_id = :plan_id AND inventory_item_id = :item_id;

Pegging analysis joins MSC_DEMANDS to MSC_FULL_PEGGING on DEMAND_ID to trace which supplies satisfy specific demands. Disposition reconciliation compares DISPOSITION_ID against MSC_SUPPLIES to identify orphan demands or matching gaps. Forecast consumption reporting filters by DEMAND_TYPE = 'FORECAST' and DEMAND_CLASS to evaluate forecast accuracy. Exception queries use UNMET_QUANTITY > 0 to surface shortages requiring planner intervention. Load verification scripts cross-check record counts by SOURCE_ORGANIZATION_ID and ORIGINATION_TYPE after data collection.

Related Objects

MSC_DEMANDS references and is referenced by several key planning tables:

• MSC_SUPPLIES – Joined via PLAN_ID and DISPOSITION_ID for dependent demands.
• MSC_SYSTEM_ITEMS – Joined on INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID for item attributes.
• MSC_FULL_PEGGING – References MSC_DEMANDS via PLAN_ID and DEMAND_ID; fundamental for pegging analysis.
• MSC_FORECAST_UPDATES – References PLAN_ID and FORECAST_DEMAND_ID to track forecast changes.
• MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES – Provide customer and ship-to information via CUSTOMER_ID and CUSTOMER_SITE_ID.
• MSC_DEMANDS (self) – Self-referencing on PLAN_ID and PARENT_ID for dependent/hierarchical demands.
• MSC_PROJECTS and MSC_PROJECT_TASKS – Join on PROJECT_ID and TASK_ID for project-driven demand.
• MSC_DESIGNATORS – Linked via SCHEDULE_DESIGNATOR_ID for schedule grouping.