Skip to content
EBS Reference

MSC_DEMANDS

Schema: MSCtransactionPer inventory org

Every demand row a plan considered — sales orders, forecasts, and the dependent demand exploded from supplies, each with its due date, quantity, and origin

Module: PlanningInventory-org partitioned (ORGANIZATION_ID)
Grain note

Independent AND dependent demand share the table — segment ORIGINATION_TYPE or exploded component demand mixes into top-level order counts; always filter one PLAN_ID; rate-based rows carry rates, not discrete quantities

Notes

DISPOSITION_ID points at the generating supply for dependent demand — the pegging thread. Item/org ids are planning-instance copies, as on the supplies table.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

15 fields · 3 key

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1DEMAND_IDThe demand row id — plan-scopedNUMBER
Key
2PLAN_IDThe plan — every query filters oneNUMBER
Key
3SR_INSTANCE_IDThe collected source instance — part of the keyNUMBER
Key
4ORGANIZATION_IDPlanning-instance copy of the org idNUMBER
5INVENTORY_ITEM_IDPlanning-instance copy of the demanded itemNUMBER
6USING_ASSEMBLY_ITEM_IDThe parent assembly generating dependent demandNUMBER
7USING_ASSEMBLY_DEMAND_DATEThe demand due date — the analysis dateDATE
Filter date
8USING_REQUIREMENT_QUANTITYThe required quantityNUMBER
9DISPOSITION_IDThe generating supply (dependent demand) or the schedule entry behind independent demand — the pegging threadNUMBER
10ORIGINATION_TYPEWhere the demand came from — sales order, forecast, dependent…; numeric, undecodedNUMBER
11DEMAND_TYPE1 = discrete demand, 2 = rate-based (per the data dictionary's own comment) — rate rows carry rates, not quantitiesNUMBER
12DEMAND_PRIORITYPriority input to plan schedulingNUMBER
13ASSEMBLY_DEMAND_COMP_DATEThe using assembly's completion dateDATE
14PLANNING_GROUPPlanning group of the demandVARCHAR2
15DAILY_DEMAND_RATEThe daily rate on rate-based rowsNUMBER

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading MSC_DEMANDSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : MSC_DEMANDS — Every demand row a plan considered — sales orders, forecasts, and the dependent demand exploded from supplies, each with its due date, quantity, and origin
-- Purpose: Column-selected read of MSC_DEMANDS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + DEMAND_ID + PLAN_ID + SR_INSTANCE_ID
-- Caution: Independent AND dependent demand share the table — segment ORIGINATION_TYPE or exploded component demand mixes into top-level order counts; always filter one PLAN_ID; rate-based rows carry rates, not discrete quantities
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.DEMAND_ID AS "The demand row id — plan-scoped",
  t.PLAN_ID AS "The plan — every query filters one",
  t.SR_INSTANCE_ID AS "The collected source instance — part of the key",
  t.ORGANIZATION_ID AS "Planning-instance copy of the org id",
  t.INVENTORY_ITEM_ID AS "Planning-instance copy of the demanded item",
  t.USING_ASSEMBLY_ITEM_ID AS "The parent assembly generating dependent demand",
  t.USING_ASSEMBLY_DEMAND_DATE AS "The demand due date — the analysis date",
  t.USING_REQUIREMENT_QUANTITY AS "The required quantity",
  t.DISPOSITION_ID AS "The generating supply (dependent demand) or the schedule entry behind independent demand — the pegging thread",
  t.ORIGINATION_TYPE AS "Where the demand came from — sales order, forecast, dependent…; numeric, undecoded",
  t.DEMAND_TYPE AS "1 = discrete demand, 2 = rate-based (per the data dictionary's own comment) — rate rows carry rates, not quantities",
  t.DEMAND_PRIORITY AS "Priority input to plan scheduling",
  t.ASSEMBLY_DEMAND_COMP_DATE AS "The using assembly's completion date",
  t.PLANNING_GROUP AS "Planning group of the demand",
  t.DAILY_DEMAND_RATE AS "The daily rate on rate-based rows"
FROM <catalog>.<schema>.MSC_DEMANDS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.DEMAND_ID = <DEMAND_ID>
  -- AND t.PLAN_ID = <PLAN_ID>
  -- AND t.SR_INSTANCE_ID = <SR_INSTANCE_ID>
  -- AND t.USING_ASSEMBLY_DEMAND_DATE >= DATE '<DATE_FROM>'
  -- AND t.USING_ASSEMBLY_DEMAND_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DEMAND_ID;

9 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DEMAND_ID>, <PLAN_ID>, <SR_INSTANCE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • MSC_DEMANDSMSC_PLANSforeign key · N:1
    ON MSC_DEMANDS.PLAN_ID = MSC_PLANS.PLAN_ID AND MSC_DEMANDS.ORGANIZATION_ID = MSC_PLANS.ORGANIZATION_ID
  • MSC_DEMANDSMSC_SYSTEM_ITEMSforeign key · N:1
    ON MSC_DEMANDS.INVENTORY_ITEM_ID = MSC_SYSTEM_ITEMS.INVENTORY_ITEM_ID AND MSC_DEMANDS.PLAN_ID = MSC_SYSTEM_ITEMS.PLAN_ID AND MSC_DEMANDS.SR_INSTANCE_ID = MSC_SYSTEM_ITEMS.SR_INSTANCE_ID AND MSC_DEMANDS.ORGANIZATION_ID = MSC_SYSTEM_ITEMS.ORGANIZATION_ID
  • MSC_DEMANDSMSC_SUPPLIESforeign key · N:1
    ON MSC_DEMANDS.DISPOSITION_ID = MSC_SUPPLIES.TRANSACTION_ID AND MSC_DEMANDS.PLAN_ID = MSC_SUPPLIES.PLAN_ID AND MSC_DEMANDS.SR_INSTANCE_ID = MSC_SUPPLIES.SR_INSTANCE_ID AND MSC_DEMANDS.ORGANIZATION_ID = MSC_SUPPLIES.ORGANIZATION_ID

Browse more Planningtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.