MRP_SCHEDULE_DESIGNATORS
Schema: MRPcontrolPer inventory orgThe MDS/MPS schedule name master per organization — schedule type, relief behavior, and whether the schedule supplies ATP
MPS_RELIEF governs whether the planning manager relieves (consumes) this schedule as orders execute.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
10 fields · 2 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SCHEDULE_DESIGNATOR | The MDS/MPS schedule name — key together with the organization | VARCHAR2 | Primary-key field |
| 2 | ORGANIZATION_ID | Inventory organization — part of the key | NUMBER | Primary-key field |
| 3 | SCHEDULE_TYPE | MDS vs MPS — numeric, undecoded | NUMBER | |
| 4 | MPS_RELIEF | Whether the planning manager relieves (consumes) the schedule as orders execute | NUMBER | |
| 5 | INVENTORY_ATP_FLAG | Whether the schedule supplies ATP — always no for an MDS | NUMBER | |
| 6 | DESCRIPTION | Schedule description | VARCHAR2 | |
| 7 | DISABLE_DATE | When the schedule was disabled — NULL while active | DATE | |
| 8 | DEMAND_CLASS | Demand class the schedule serves | VARCHAR2 | |
| 9 | ORGANIZATION_SELECTION | Single-org vs multi-org schedule scope | NUMBER | |
| 10 | PRODUCTION | Auto-release flag for the schedule | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading MRP_SCHEDULE_DESIGNATORS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <SCHEDULE_DESIGNATOR>, <watermark>
-- ============================================================
-- Table : MRP_SCHEDULE_DESIGNATORS — The MDS/MPS schedule name master per organization — schedule type, relief behavior, and whether the schedule supplies ATP
-- Purpose: Column-selected read of MRP_SCHEDULE_DESIGNATORS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + SCHEDULE_DESIGNATOR
-- 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.SCHEDULE_DESIGNATOR AS "The MDS/MPS schedule name — key together with the organization",
t.ORGANIZATION_ID AS "Inventory organization — part of the key",
t.SCHEDULE_TYPE AS "MDS vs MPS — numeric, undecoded",
t.MPS_RELIEF AS "Whether the planning manager relieves (consumes) the schedule as orders execute",
t.INVENTORY_ATP_FLAG AS "Whether the schedule supplies ATP — always no for an MDS",
t.DESCRIPTION AS "Schedule description",
t.DISABLE_DATE AS "When the schedule was disabled — NULL while active",
t.DEMAND_CLASS AS "Demand class the schedule serves",
t.ORGANIZATION_SELECTION AS "Single-org vs multi-org schedule scope",
t.PRODUCTION AS "Auto-release flag for the schedule"
FROM <catalog>.<schema>.MRP_SCHEDULE_DESIGNATORS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.SCHEDULE_DESIGNATOR = '<SCHEDULE_DESIGNATOR>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.SCHEDULE_DESIGNATOR;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON MRP_SCHEDULE_DATES.SCHEDULE_DESIGNATOR = MRP_SCHEDULE_DESIGNATORS.SCHEDULE_DESIGNATOR AND MRP_SCHEDULE_DATES.ORGANIZATION_ID = MRP_SCHEDULE_DESIGNATORS.ORGANIZATION_ID
More Planning tables
- MSC_DEMANDSEvery demand row a plan considered — sales orders, forecasts, and the dependent demand exploded from supplies, each with its due date, quantity, and origin
- MSC_PLANSThe 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
- MSC_SUPPLIESEvery supply row in a plan — existing purchase orders, jobs, on-hand, and in-transit alongside the planner's recommended planned orders; the supply side of ASCP plan output
- MSC_SYSTEM_ITEMSThe planning copy of the item master at plan + instance + org + item grain — collected item attributes frozen per plan run, and the bridge column back to the source EBS item
- MRP_FORECAST_DATESThe forecast fact — one row per forecast entry per item, org, forecast name, and date, carrying both the entered quantity and the post-consumption remainder
- MRP_FORECAST_DESIGNATORSThe forecast name and forecast set master per organization — consumption behavior (consume flag, forward/backward time fences, outlier cap) lives at this level