Skip to content
EBS Reference

MRP_FORECAST_DESIGNATORS

Schema: MRPcontrolPer inventory org

The forecast name and forecast set master per organization — consumption behavior (consume flag, forward/backward time fences, outlier cap) lives at this level

Module: PlanningInventory-org partitioned (ORGANIZATION_ID)
Notes

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.
In field listings, K marks a primary-key field.

Fields

12 fields · 2 key

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1FORECAST_DESIGNATORThe forecast (or forecast set) name — key together with the organizationVARCHAR2
Key
2ORGANIZATION_IDInventory organization — part of the keyNUMBER
Key
3DESCRIPTIONForecast descriptionVARCHAR2
4FORECAST_SETThe parent set — NULL when this row IS a setVARCHAR2
5CONSUME_FORECASTWhether sales orders consume the forecastNUMBER
6UPDATE_TYPEConsumption update behaviorNUMBER
7BUCKET_TYPESet-level bucket — daily, weekly, or periodicNUMBER
8FOREWARD_UPDATE_TIME_FENCEForward consumption window in days (the column name really is spelled FOREWARD)NUMBER
9BACKWARD_UPDATE_TIME_FENCEBackward consumption window in daysNUMBER
10OUTLIER_UPDATE_PERCENTAGECap on how much of the forecast one order may consumeNUMBER
11DEMAND_CLASSDemand class the forecast servesVARCHAR2
12DISABLE_DATEWhen the forecast was disabled — NULL while activeDATE

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.

Query parameters
-- ============================================================
-- 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

  • MRP_FORECAST_DATESMRP_FORECAST_DESIGNATORSforeign key · N:1
    ON MRP_FORECAST_DATES.FORECAST_DESIGNATOR = MRP_FORECAST_DESIGNATORS.FORECAST_DESIGNATOR AND MRP_FORECAST_DATES.ORGANIZATION_ID = MRP_FORECAST_DESIGNATORS.ORGANIZATION_ID
  • MRP_FORECAST_DESIGNATORSMTL_PARAMETERSforeign key · N:1
    ON MRP_FORECAST_DESIGNATORS.ORGANIZATION_ID = MTL_PARAMETERS.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.