Skip to content
EBS Reference

MSC_PLANS

Schema: MSCcontrolPer inventory org

The ASCP plan registry — one row per plan with its user-visible name, owning org, type, planning horizon, and run timestamps; every plan-output query starts by picking a row here

Module: PlanningInventory-org partitioned (ORGANIZATION_ID)
Notes

COMPILE_DESIGNATOR is the plan name users see. Plan output tables are scoped by PLAN_ID — nothing in them means anything without choosing a plan first.

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

13 fields · 1 key

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1PLAN_IDThe plan id every plan-output row is scoped byNUMBER
Key
2COMPILE_DESIGNATORThe plan name users seeVARCHAR2
3SR_INSTANCE_IDThe collected source instanceNUMBER
4ORGANIZATION_IDThe org that owns the planNUMBER
5PLAN_TYPEMRP, DRP, or MPS plan — numeric, names documented, codes notNUMBER
6CURR_START_DATEStart of the planning horizonDATE
7CURR_CUTOFF_DATEEnd of the planning horizonDATE
8PLAN_START_DATEWhen the plan run startedDATE
9PLAN_COMPLETION_DATEWhen the plan run completed — the recency checkDATE
Filter date
10DATA_START_DATESnapshot startDATE
11DATA_COMPLETION_DATESnapshot completionDATE
12CURR_SCHEDULE_DESIGNATORThe schedule the plan ran againstVARCHAR2
13DEMAND_TIME_FENCE_FLAGWhether the demand time fence was appliedNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading MSC_PLANSon 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_PLANS — The ASCP plan registry — one row per plan with its user-visible name, owning org, type, planning horizon, and run timestamps; every plan-output query starts by picking a row here
-- Purpose: Column-selected read of MSC_PLANS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + PLAN_ID
-- 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.PLAN_ID AS "The plan id every plan-output row is scoped by",
  t.COMPILE_DESIGNATOR AS "The plan name users see",
  t.SR_INSTANCE_ID AS "The collected source instance",
  t.ORGANIZATION_ID AS "The org that owns the plan",
  t.PLAN_TYPE AS "MRP, DRP, or MPS plan — numeric, names documented, codes not",
  t.CURR_START_DATE AS "Start of the planning horizon",
  t.CURR_CUTOFF_DATE AS "End of the planning horizon",
  t.PLAN_START_DATE AS "When the plan run started",
  t.PLAN_COMPLETION_DATE AS "When the plan run completed — the recency check",
  t.DATA_START_DATE AS "Snapshot start",
  t.DATA_COMPLETION_DATE AS "Snapshot completion",
  t.CURR_SCHEDULE_DESIGNATOR AS "The schedule the plan ran against",
  t.DEMAND_TIME_FENCE_FLAG AS "Whether the demand time fence was applied"
FROM <catalog>.<schema>.MSC_PLANS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.PLAN_ID = <PLAN_ID>
  -- AND t.PLAN_COMPLETION_DATE >= DATE '<DATE_FROM>'
  -- AND t.PLAN_COMPLETION_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.PLAN_ID;

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <PLAN_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_SUPPLIESMSC_PLANSforeign key · N:1
    ON MSC_SUPPLIES.PLAN_ID = MSC_PLANS.PLAN_ID AND MSC_SUPPLIES.ORGANIZATION_ID = MSC_PLANS.ORGANIZATION_ID
  • MSC_DEMANDSMSC_PLANSforeign key · N:1
    ON MSC_DEMANDS.PLAN_ID = MSC_PLANS.PLAN_ID AND MSC_DEMANDS.ORGANIZATION_ID = MSC_PLANS.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.