MRP_FORECAST_DESIGNATORS
Schema: MRPcontrolPer inventory orgThe forecast name and forecast set master per organization — consumption behavior (consume flag, forward/backward time fences, outlier cap) lives at this level
Forecast sets and the forecasts inside them share the table — a row with a NULL FORECAST_SET is itself a set; filter before counting forecasts.
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
12 fields · 2 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | FORECAST_DESIGNATOR | The forecast (or forecast set) name — key together with the organization | VARCHAR2 | Key |
| 2 | ORGANIZATION_ID | Inventory organization — part of the key | NUMBER | Key |
| 3 | DESCRIPTION | Forecast description | VARCHAR2 | |
| 4 | FORECAST_SET | The parent set — NULL when this row IS a set | VARCHAR2 | |
| 5 | CONSUME_FORECAST | Whether sales orders consume the forecast | NUMBER | |
| 6 | UPDATE_TYPE | Consumption update behavior | NUMBER | |
| 7 | BUCKET_TYPE | Set-level bucket — daily, weekly, or periodic | NUMBER | |
| 8 | FOREWARD_UPDATE_TIME_FENCE | Forward consumption window in days (the column name really is spelled FOREWARD) | NUMBER | |
| 9 | BACKWARD_UPDATE_TIME_FENCE | Backward consumption window in days | NUMBER | |
| 10 | OUTLIER_UPDATE_PERCENTAGE | Cap on how much of the forecast one order may consume | NUMBER | |
| 11 | DEMAND_CLASS | Demand class the forecast serves | VARCHAR2 | |
| 12 | DISABLE_DATE | When the forecast was disabled — NULL while active | DATE |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading MRP_FORECAST_DESIGNATORSon 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 : MRP_FORECAST_DESIGNATORS — The forecast name and forecast set master per organization — consumption behavior (consume flag, forward/backward time fences, outlier cap) lives at this level
-- Purpose: Column-selected read of MRP_FORECAST_DESIGNATORS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + FORECAST_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.FORECAST_DESIGNATOR AS "The forecast (or forecast set) name — key together with the organization",
t.ORGANIZATION_ID AS "Inventory organization — part of the key",
t.DESCRIPTION AS "Forecast description",
t.FORECAST_SET AS "The parent set — NULL when this row IS a set",
t.CONSUME_FORECAST AS "Whether sales orders consume the forecast",
t.UPDATE_TYPE AS "Consumption update behavior",
t.BUCKET_TYPE AS "Set-level bucket — daily, weekly, or periodic",
t.FOREWARD_UPDATE_TIME_FENCE AS "Forward consumption window in days (the column name really is spelled FOREWARD)",
t.BACKWARD_UPDATE_TIME_FENCE AS "Backward consumption window in days",
t.OUTLIER_UPDATE_PERCENTAGE AS "Cap on how much of the forecast one order may consume",
t.DEMAND_CLASS AS "Demand class the forecast serves",
t.DISABLE_DATE AS "When the forecast was disabled — NULL while active"
FROM <catalog>.<schema>.MRP_FORECAST_DESIGNATORS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.FORECAST_DESIGNATOR = '<FORECAST_DESIGNATOR>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.FORECAST_DESIGNATOR;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <FORECAST_DESIGNATOR>, <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 MRP_FORECAST_DATES.FORECAST_DESIGNATOR = MRP_FORECAST_DESIGNATORS.FORECAST_DESIGNATOR AND MRP_FORECAST_DATES.ORGANIZATION_ID = MRP_FORECAST_DESIGNATORS.ORGANIZATION_IDON MRP_FORECAST_DESIGNATORS.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_ID