Search Results dimension_code




Overview
Explore in AI Chat

Overview

The view RHX_DP_HIER_LEVELS_V belongs to the Oracle MRP (Master Scheduling/MRP) product family and is documented in Oracle E-Business Suite releases 12.1.1 and 12.2.2 through the ETRM repository. It exposes the hierarchical level definitions that belong to Demand Planning hierarchies. In the Oracle Demand Planning (formerly part of the Advanced Planning suite and integrated with MRP/MPS), hierarchies are used to organize dimension members — such as products, customers, or organizations — into parent-child rollup structures that support aggregation, forecasting, and dimensional analysis. Each hierarchy is composed of one or more levels (for example, a product hierarchy might have "Category," "Family," and "Item" levels). This view assembles those levels together with their parent relationship, the physical tables and columns that define the join between levels, and the full set of descriptive and audit attributes.

The object is labeled as "Retrofitted" and "Not implemented in this database," meaning it is a legacy or migrated definition that may not exist in every environment. It is intended primarily for reporting and integration purposes, bridging the Demand Planning hierarchy metadata stored in the underlying RHX_DP_* tables.

Underlying Base Objects

The view text joins four base tables, all in the RHX_DP_ namespace associated with Demand Planning:

  • RHX_DP_HIERARCHY_LEVELS (alias RHL) — the primary driver table, supplying the level records, their seed flag, program/request audit columns, and the descriptive flexfield attributes.
  • RHX_DP_HIERARCHIES (alias RDH) — supplies the hierarchy name and dimension code, joined on HIERARCHY_ID.
  • RHX_DP_LEVELS (alias RDL1) — supplies the level name for the current level, joined on demand plan, dimension code, and level ID.
  • RHX_DP_LEVELS (alias RDL2) — a self-join on the same table to resolve the parent level name via PARENT_LEVEL_ID.

The join is anchored on RDH.HIERARCHY_ID = RHL.HIERARCHY_ID, with the level tables filtered by matching DEMAND_PLAN_ID and DIMENSION_CODE.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing hierarchy structure, verifying level configuration before a planning run, and driving integration extracts. A representative query filters by dimension:

  • SELECT hierarchy_name, level_name, parent_level_name FROM rhx_dp_hier_levels_v WHERE dimension_code = :p_dimension ORDER BY hierarchy_id, level_id;
  • SELECT dimension_code, COUNT(*) FROM rhx_dp_hier_levels_v GROUP BY dimension_code;
  • SELECT * FROM rhx_dp_hier_levels_v WHERE seed_flag = 'Y';

Because the view is documented as not implemented in some databases, availability should be confirmed before relying on it in concurrent programs or custom reports.