Results for “mrp_forecast_designators”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRP.MRP_FORECAST_DESIGNATORS is the forecast designator master table in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. A forecast designator is the named identifier that logically groups a set of forecast entries for a given organization; it acts as the header-level authority that defines how forecast consumption, forecast spreading, and forecast set membership are governed. Every forecast row written to the MRP forecast tables is validated against a designator recorded here, making this object the controlling reference for forecasting, master scheduling, and demand planning activities in Release 12.1.1 and 12.2.2.
The table is owned by the MRP schema and is flagged VALID in the ETRM object registry, with 42 documented columns in Release 12.2.2. Mining of the foreign-key structure yields a heuristic Data Vault classification of hub-leaning: the designator (in combination with organization) is a stable, non-volatile business key that many dependent tables reference. From a dimensional modeling perspective, this table is best treated as a hub (or, in a star schema, a conformed dimension) rather than as a transactional satellite.
Key Information Stored
The physical primary key is MRP_FORECAST_DESIGNATORS_PK, a composite of FORECAST_DESIGNATOR and ORGANIZATION_ID. A separate unique index, MRP_FORECAST_DESIGNATORS_U1, declares the same two columns as the business-key candidate, confirming that a forecast designator is unique only within an organization.
FORECAST_DESIGNATOR— the named identifier of the forecast; the principal business key element used by nearly all dependent tables.ORGANIZATION_ID— the inventory organization owning the designator; the second half of the primary key and the primary partitioning/routing attribute.DESCRIPTION— free-text description of the forecast designator.FORECAST_SET— self-referencing attribute that groups designators into a forecast set; also resolves back to this same table.CONSUME_FORECAST— controls whether forecast entries are consumed by actual sales orders during planning.UPDATE_TYPE— determines how forecast values are updated when overlapping demand is encountered.DISABLE_DATE— the date after which the designator is no longer active for planning.FOREWARD_UPDATE_TIME_FENCEandBACKWARD_UPDATE_TIME_FENCE— boundaries that restrict how far forward and backward forecast consumption or updates may propagate.OUTLIER_UPDATE_PERCENTAGE— tolerance percentage used to suppress outlier demand during forecast updates.CUSTOMER_ID,SHIP_ID, andBILL_ID— demand-scoping attributes allowing a designator to be constrained to a specific customer, ship-to, or bill-to (the latter referencingIGS_FI_BILL_ALL).DEMAND_CLASSandBUCKET_TYPE— demand classification and bucket granularity used in consumption logic.APS_COLLECTION_FLAG— indicates whether the designator participates in Advanced Planning/collections processing.- Standard audit columns (
LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY,LAST_UPDATE_LOGIN) and theDDF_CONTEXT/ATTRIBUTE_CATEGORY/ATTRIBUTE1-15descriptive-flexfield block.
Common Use Cases and Queries
The most common reporting need is to enumerate active forecast designators for a given organization alongside their set membership and disable dates:
SELECT FORECAST_DESIGNATOR, DESCRIPTION, FORECAST_SET, DISABLE_DATE FROM MRP.MRP_FORECAST_DESIGNATORS WHERE ORGANIZATION_ID = :org_id AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE);- Tracing which designators feed Kanban or load parameters, or identifying consumption configuration before a planning run: filter on
CONSUME_FORECASTandUPDATE_TYPE. - Auditing changes: join to related MRP tables on
FORECAST_DESIGNATORandORGANIZATION_IDto reconcile forecast entries, dates, and interface staging rows. - Cross-module reporting with manufacturing or safety-stock data, since
MTL_SAFETY_STOCKSandMTL_ABC_COMPILE_HEADERScarry forecast designator references.
Related Objects
The following objects depend on or reference MRP_FORECAST_DESIGNATORS, joined on FORECAST_DESIGNATOR plus ORGANIZATION_ID unless noted:
MRP_FORECAST_DATES— forecast bucket rows keyed bySOURCE_FORECAST_DESIGNATORandSOURCE_ORGANIZATION_ID.MRP_FORECAST_ITEMS— item-level forecast entries referencingFORECAST_DESIGNATORandORGANIZATION_ID.MRP_FORECAST_INTERFACE— inbound forecast staging table keyed by the same designator/organization pair.MRP_LOAD_PARAMETERS— planning load configuration referencing bothFORECAST_DESIGNATORandSOURCE_FORECAST_DESIGNATOR.MRP_SCHEDULE_DATES— master schedule rows referencing the source designator.MRP_KANBAN_PLANS— Kanban input driven byINPUT_DESIGNATOR.MTL_SAFETY_STOCKS— safety-stock definitions scoped to a forecast designator.MTL_ABC_COMPILE_HEADERS— ABC compile requests referencingMRP_FORECAST_NAME.MRP_PARAMETERSandMRP_FORECAST_DESIGNATORS.FORECAST_SET(self-join) — organizational planning parameters and set grouping.IGS_FI_BILL_ALL— referenced through theBILL_IDforeign key.
-
Forecast names and sets
-
Forecast names and sets
-
View: MRP_FORECASTS_LOV_V 12.2.2
Forecast designators and forecast sets list of values view
APPS.MRP_FORECASTS_LOV_V·↳ MRP_FORECAST_DESIGNATORS·Explore MRP module →
-
View: MRP_FORECASTS_LOV_V 12.1.1
Forecast designators and forecast sets list of values view
APPS.MRP_FORECASTS_LOV_V·↳ MRP_FORECAST_DESIGNATORS·Explore MRP module →
-
View: EDW_FORECAST_FKV 12.1.1
This view can be used by fact views to derive Forecast dimension foreign keys
APPS.EDW_FORECAST_FKV·↳ EDW_LOCAL_INSTANCE·↳ MRP_FORECAST_DESIGNATORS·↳ MTL_PARAMETERS·Explore ISC module →