Results for “rhx_dp_forecast_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RHX_DP_FORECAST_V is a reporting view in the Oracle E-Business Suite Master Scheduling/MRP product family. Its description in the ETRM repository is annotated as "Retrofitted," and the implementation metadata explicitly records it as "Not implemented in this database," meaning the view is documented for reference but is not instantiated in every environment. The view consolidates exploded forecast demand data into an aggregated, denormalized result set suitable for downstream reporting, analytics, and integration with external planning or data-warehouse systems.

The view presents forecast demand at the intersection of a forecast designator, a demand time bucket expressed as WEEK, an item or product, an inventory organization, and the associated ship-to and bill-to party dimensions. Because the underlying source is a temporary explosion table, the view functions as a curated, grouped snapshot rather than a transactional store. In Oracle EBS 12.1.1 and 12.2.2 environments where it exists, it is typically consumed by custom reports, BI Publisher extracts, or interface programs that require forecast quantities already summed across the exploded detail.

Underlying Base Objects

The documented base object is RHX_DP_FCST_EXPLODE_TEMP, a temporary table holding exploded forecast records. The view is defined as a GROUP BY query over that single source, with no additional documented base tables or joins. All costing, item, and party attributes are carried through as columns rather than resolved through lookups, so the view depends entirely on the quality and completeness of the temporary explosion data.

Because the source is designated as a temporary object, the view is not intended to be a persistent system-of-record source. Materialized results persist only while the explosion process populates the temporary table. Any consumer should treat the view as a transient read layer generated during forecast explosion or planning runs, and should not assume historical retention.

Key Columns

• DATA_ELEMENT_ID — Identifier for the data element driving the exploded forecast record.
• FORECAST_DESIGNATOR — The forecast set or designator under which demand was generated.
• SHIP_TO / SHIP_TO_TERRITORY — Ship-to party and its associated territory, used for geographic demand analysis.
• BILL_TO / BILL_TO_TERRITORY — Bill-to party and territory. The bill-to columns frequently appear in search criteria such as "bill_to" because they isolate demand attributable to the invoicing party rather than the receiving location.
• WEEK — The time bucket into which quantity is aggregated.
• PRODUCT / INVENTORY_ITEM_ID — Item description and internal item identifier.
• ORGANIZATION_ID — Inventory organization owning the forecast.
• QUANTITY — Summed demand quantity for the grouping combination.
• DEMAND_CLASS — Classification of the demand (for example forecast versus other categories).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments carried through the explosion, enabling custom dimension reporting.

Common Use Cases and Queries

A frequent requirement is to report forecast demand by billing party across weekly buckets. The following query aggregates quantity by bill-to and week for a given forecast designator:

• SELECT bill_to, week, SUM(quantity) FROM rhx_dp_forecast_v WHERE forecast_designator = :designator GROUP BY bill_to, week ORDER BY bill_to, week;

Analysts searching on "bill_to" commonly require a filtered extract joining ship-to and bill-to territory context, or a comparison of demand split between ship-to and bill-to parties. Because the view already performs SUM and GROUP BY, consumers should avoid redundant aggregation and instead apply filters on designator, organization, or week to limit the scan.

Typical integration scenarios include loading forecast quantities into a data warehouse, feeding territory-level demand dashboards, and reconciling exploded forecast totals against planning output. Given the "Not implemented" annotation, developers should verify view existence in the target instance before deploying dependent code and provide a fallback query against RHX_DP_FCST_EXPLODE_TEMP where the view is absent.