Search Results forecast_set_designator

Overview

APPS.MRP_FORECASTS_LOV_V is a read-only database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It exposes forecast designator information sourced from the Oracle Advanced Supply Chain Planning / Material Requirements Planning (MRP) forecast tables. The view is purpose-built as a List of Values (LOV) source, meaning its structure is optimized to feed Oracle Forms and OAF-based LOV windows that allow users to select a forecast set and its associated forecast designator in forecast-related functionality.

The view flattens the hierarchical relationship between forecast sets and forecast designators into a single denormalized result set. Rather than requiring the caller to navigate the parent-child structure of MRP_FORECAST_DESIGNATORS through self-joins, MRP_FORECASTS_LOV_V performs that join internally and returns both the set-level and designator-level attributes side by side. For the user searching on forecast_designator, this view is the primary documented object through which designator-valued LOV lookups are populated in EBS MRP and forecasting modules.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, the sole referenced base object is MRP_FORECAST_DESIGNATORS (accessed via an APPS synonym). The view text aliases this table twice, as MRFDE1 and MRFDE2, to model the self-referencing relationship between forecast sets and their child designators:

• MRFDE1 represents the parent record — the forecast set — identified where a designator's FORECAST_SET is NULL (i.e., it is not itself a child of another designator).
• MRFDE2 represents the child record — the individual forecast designator — whose FORECAST_SET column points back to the parent's FORECAST_DESIGNATOR within the same ORGANIZATION_ID.

The first branch of the UNION ALL returns the joined set/designator combinations. The second branch returns forecast sets that have no associated child designator, emitting a single-space placeholder (' ' FORECAST_DESIGNATOR) and NULL forecast-level description/disable date columns. This guarantees that every forecast set appears in the LOV at least once, even when no child designators are defined.

Key Columns

• FORECAST_SET_DESIGNATOR — the designator value of the parent forecast set (from MRFDE1 or, in the second branch, from MRFDE).
• FORECAST_SET_DESCRIPTION — the descriptive text of the forecast set.
• FORECAST_SET_DISABLE_DATE — the date the forecast set becomes inactive.
• FORECAST_SET_BUCKET_TYPE — the bucket type governing how the forecast set's time buckets are defined.
• FORECAST_DESIGNATOR — the child designator value (from MRFDE2); a single space when no child exists.
• FORECAST_DESCRIPTION — the descriptive text of the individual forecast designator (NULL in the second branch).
• FORECAST_DISABLE_DATE — the disable date of the individual designator (NULL in the second branch).
• ORGANIZATION_ID — the inventory organization that owns both the set and its designators; the join is scoped on this column to prevent cross-organization matches.

Common Use Cases and Queries

The view is most commonly referenced when building or troubleshooting LOV behavior for forecast selection. A typical lookup retrieves all active forecasts for a given organization:

• Validate designator membership: SELECT forecast_set_designator, forecast_designator FROM apps.mrp_forecasts_lov_v WHERE organization_id = :org_id;
• Filter by disable status: add WHERE forecast_disable_date IS NULL OR forecast_disable_date > SYSDATE to surface only active designators.
• Populate Forms LOVs: the paired set/designator naming convention allows a single LOV record to carry both values for downstream defaulting.

Because MRP_FORECAST_DESIGNATORS is the only base object, the view performs no cross-module joins and remains lightweight for interactive querying. As with all APPS-schema views, it should be queried rather than modified, and any client extension should treat it as a stable LOV interface.