MSC_PLANS
Schema: MSCcontrolPer inventory orgThe 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
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.
Fields
13 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PLAN_ID | The plan id every plan-output row is scoped by | NUMBER | Key |
| 2 | COMPILE_DESIGNATOR | The plan name users see | VARCHAR2 | |
| 3 | SR_INSTANCE_ID | The collected source instance | NUMBER | |
| 4 | ORGANIZATION_ID | The org that owns the plan | NUMBER | |
| 5 | PLAN_TYPE | MRP, DRP, or MPS plan — numeric, names documented, codes not | NUMBER | |
| 6 | CURR_START_DATE | Start of the planning horizon | DATE | |
| 7 | CURR_CUTOFF_DATE | End of the planning horizon | DATE | |
| 8 | PLAN_START_DATE | When the plan run started | DATE | |
| 9 | PLAN_COMPLETION_DATE | When the plan run completed — the recency check | DATE | Filter date |
| 10 | DATA_START_DATE | Snapshot start | DATE | |
| 11 | DATA_COMPLETION_DATE | Snapshot completion | DATE | |
| 12 | CURR_SCHEDULE_DESIGNATOR | The schedule the plan ran against | VARCHAR2 | |
| 13 | DEMAND_TIME_FENCE_FLAG | Whether the demand time fence was applied | NUMBER |
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.
-- ============================================================
-- 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
ON MSC_SUPPLIES.PLAN_ID = MSC_PLANS.PLAN_ID AND MSC_SUPPLIES.ORGANIZATION_ID = MSC_PLANS.ORGANIZATION_IDON MSC_DEMANDS.PLAN_ID = MSC_PLANS.PLAN_ID AND MSC_DEMANDS.ORGANIZATION_ID = MSC_PLANS.ORGANIZATION_ID