Results for “rhx_dp_dimensions_v”

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

Overview

RHX_DP_DIMENSIONS_V is a reporting view belonging to the MRP (Master Scheduling/MRP) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified in the ETRM repository as a retrofitted object, indicating that it was introduced or reworked during the upgrade and consolidation effort that carried forward legacy demand planning functionality into the current EBS schema. The view exposes the intersection between demand plans and the descriptive flexfield-style lookup values that define the dimensions available to those plans, giving report writers and integrators a single denormalized source for plan-level metadata.

Functionally, the view serves as a reference layer for demand planning analytics. Rather than requiring report authors to join the demand plan header table to the common lookups table manually, RHX_DP_DIMENSIONS_V presents the plan identity alongside the dimension code, display name, and longer description for every dimension associated with a given plan. Its most frequently referenced column, DIMENSION_DESCRIPTION, supplies the human-readable text that appears in dimension pickers, analysis dashboards, and extract files. In the documented 12.2.2 metadata the view is listed with no documented base objects and is marked "Not implemented in this database," which is typical of ETRM entries generated from source definitions rather than a live instance.

Underlying Base Objects

The view text defines two source objects. The first is RHX_DP_DEMAND_PLANS, referenced with the alias RDP, which supplies the demand plan identifier, plan name, and plan description. The second is FND_COMMON_LOOKUPS, aliased FCU, which supplies the lookup-derived dimension attributes. The join between the two tables is not restricted by a foreign key column in the documented SQL; instead, the result set is constrained by a filter on FCU.LOOKUP_TYPE equal to 'DEMAND_PLANNER_DIMENSIONS'. This means every row in RHX_DP_DEMAND_PLANS is effectively cross-joined to the set of active demand planner dimension lookup values, producing one output row per plan-dimension combination.

Readers should note that FND_COMMON_LOOKUPS is the standard EBS lookup repository and that its LOOKUP_CODE, MEANING, and DESCRIPTION columns map directly to the view's DIMENSION_CODE, DIMENSION_NAME, and DIMENSION_DESCRIPTION columns respectively. The absence of documented base objects in the ETRM metadata means dependency analysis should be performed against the underlying tables directly.

Key Columns

• DEMAND_PLAN_ID — Numeric identifier of the demand plan, carried from the RHX_DP_DEMAND_PLANS header.
• DEMAND_PLAN_NAME — The user-assigned name of the demand plan.
• DEMAND_PLAN_DESCRIPTION — Free-text description of the plan.
• DIMENSION_CODE — The lookup code from FND_COMMON_LOOKUPS identifying the dimension.
• DIMENSION_NAME — The lookup meaning, representing the display label of the dimension.
• DIMENSION_DESCRIPTION — The lookup description, providing the full descriptive text most often used for on-screen labels and report headings.

Common Use Cases and Queries

The view is typically used to populate dimension selection lists, to enrich demand planning extracts with descriptive labels, and to validate that expected dimension lookup values are configured. A representative query retrieving the descriptive metadata for a specific plan is:

SELECT demand_plan_id,
       demand_plan_name,
       dimension_code,
       dimension_name,
       dimension_description
  FROM rhx_dp_dimensions_v
 WHERE demand_plan_id = :plan_id
 ORDER BY dimension_code;

To inventory all dimension descriptions configured across the instance, without filtering by plan:

SELECT DISTINCT dimension_code,
                dimension_name,
                dimension_description
  FROM rhx_dp_dimensions_v
 ORDER BY dimension_name;

Because the view is documented as not implemented in the reference database, availability should be confirmed in the target environment before it is referenced by concurrent programs or BI Publisher data models. Where the view is absent, equivalent results can be produced by joining RHX_DP_DEMAND_PLANS to FND_COMMON_LOOKUPS on LOOKUP_TYPE = 'DEMAND_PLANNER_DIMENSIONS'.