Search Results msc_demands_f




Overview
Explore in AI Chat

Overview

MSC_DEMANDS_F is a fact table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite (validated in 12.1.1 and 12.2.2). It stores the fully exploded and populated demand stream that the ASCP engine consumes during a plan run. Every record represents a discrete independent or dependent demand element — a sales order line, a forecast entry, an inter-org requisition, or a service demand — associated with a specific plan, plan run, organization, and inventory item. Because the table is regenerated per plan run (keyed partially by PLAN_ID and PLAN_RUN_ID), it functions as a transient staging and reporting surface rather than a master reference table.

The ETRM metadata classifies MSC_DEMANDS_F heuristically as standalone under the Data Vault model. This is a modeling suggestion: the table holds no enforced foreign keys to parent hubs beyond an incidental reference to WMS_ZONES_B via ZONE_ID, and its natural composite key (PLAN_ID, PLAN_RUN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, plus demand-specific attributes) does not resolve to a single conventional hub. It is best treated as a fact or satellite-style structure whose grain is one demand record per plan run.

Key Information Stored

The table comprises 72 documented columns. The most operationally significant are:

Common Use Cases and Queries

Typical scenarios include demand pegging analysis, forecast-versus-actuals reconciliation, OTIF performance reporting, and late-order trending. A representative query retrieves demand by item for a given plan run:

  • SELECT inventory_item_id, organization_id, SUM(demand_qty) FROM msc_demands_f WHERE plan_id = :p AND plan_run_id = :r GROUP BY inventory_item_id, organization_id;
  • SELECT demand_class, SUM(forecast_qty), SUM(sales_order_qty) FROM msc_demands_f WHERE plan_id = :p GROUP BY demand_class;
  • SELECT organization_id, SUM(late_order_qty), SUM(late_order_value) FROM msc_demands_f WHERE PLAN_RUN_ID = :r GROUP BY organization_id;

Because PLAN_RUN_ID changes with each plan execution, always constrain queries by both PLAN_ID and PLAN_RUN_ID to avoid mixing historic runs.

Related Objects

MSC_DEMANDS_F sits within the ASCP planning schema alongside several closely linked objects:

  • MSC_DEMANDS_F.ZONE_ID → WMS_ZONES_B — The only documented FK relationship, linking demand to a warehouse zone definition.
  • MSC_PLANS / MSC_PLAN_RUNS — Parent plan and run definitions that scope every demand record.
  • MSC_SUPPLIES_F — The supply-side counterpart used in pegging and netting analysis.
  • MSC_SYSTEM_ITEMS_B — Item master providing descriptions and attributes for INVENTORY_ITEM_ID.
  • MSC_ORG_ORGS — Organization hierarchy reference for ORGANIZATION_ID and OWNING_ORG_ID.
  • MSC_CUSTOMER_SITES_V / MSC_CUSTOMERS_V — Validation and enrichment for CUSTOMER_ID and CUSTOMER_SITE_ID.

These joins allow complete demand-to-supply and demand-to-customer traceability across the ASCP planning cycle.