Results for “demand_planner_dimensions”

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

Overview

The view RHX_DP_HIER_LVLS_PUB_V is a public database view shipped within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 footprint under the MRP – Master Scheduling/MRP product family. Despite its assignment to the MRP module, the object belongs to the RHX (Demand Planning / Advanced Planning) schema lineage, which supports the Demand Planner workbench and hierarchy-based demand modeling. The view exposes demand plan hierarchy levels in a flattened, reporting-friendly form, joining hierarchy headers, hierarchy-level assignments, level definitions, parent-level definitions, common lookup meanings for the dimension code, and the owning demand plan.

The metadata notes that this view is "Retrofitted" and "Not implemented in this database," meaning it is delivered as part of the standard patchset or a backported (retrofitted) bundle but is not necessarily created in every environment unless the corresponding Demand Planning features are licensed and configured. Its role is to provide a stable, public-facing (_PUB_V) SQL interface that reporting, extensions, and integrations can query without depending on the private RHX tables directly.

Underlying Base Objects

The ETRM metadata records no documented referenced base objects for this view; however, the view text unambiguously identifies its underlying tables. These are:

• RHX_DP_HIERARCHIES – demand plan hierarchy headers (aliased H), filtered by VALID_FLAG = 1.
• RHX_DP_HIERARCHY_LEVELS – the association of levels to hierarchies (aliased HL), including parent-level linkage and the ATTRIBUTE1–15 flex columns.
• RHX_DP_LEVELS – level master definitions (aliased L and L1), providing level names and parent level names.
• RHX_DP_DEMAND_PLANS – the demand plan header (aliased DP), supplying the plan name.
• FND_COMMON_LOOKUPS – Oracle Application Object Library lookup values (aliased FCL), restricted to LOOKUP_TYPE = 'DEMAND_PLANNER_DIMENSIONS' to translate the dimension code into a meaning.

The view is a compound query: the first branch returns explicit hierarchy-level rows with a defined parent; the second branch (UNION ALL) returns top-of-hierarchy level rows where LEVEL_TYPE_CODE = 1 and where the level's demand plan and dimension match the hierarchy's. This two-branch construction ensures that both child levels and root levels are represented evenly.

Key Columns

• HIERARCHY_ID / HIERARCHY_NAME – identifier and descriptive name of the demand plan hierarchy.
• LEVEL_ID / LEVEL_NAME – identifier and name of the hierarchy level.
• PARENT_LEVEL_ID / PARENT_LEVEL_NAME – the parent level, enabling reconstruction of hierarchy trees; the second UNION ALL branch resolves these to 0 and a placeholder ("BLAH") for root levels.
• DIMENSION_CODE / DIMENSION_NAME – the demand planning dimension, where the code is joined to FND_COMMON_LOOKUPS to yield a user-facing meaning.
• DEMAND_PLAN_ID / DEMAND_PLAN_NAME – the owning demand plan.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield columns carried across from the hierarchy-level record for extensibility.

Common Use Cases and Queries

Typical scenarios include rebuilding a demand hierarchy tree for analysis, validating level configuration for a given plan, or surfacing dimension meanings in integration extracts. It is important to note that a search for an unrelated part number such as "coxreels p-lp-350" will not match this object; that string is an item number and would reside in inventory or item master tables, not a hierarchy-definition view. A representative query is:

• SELECT hierarchy_name, level_name, parent_level_name, dimension_name, demand_plan_name FROM RHX_DP_HIER_LVLS_PUB_V WHERE demand_plan_id = :plan_id ORDER BY hierarchy_id, parent_level_id;
• Reconstructing parent-child relationships: filter on parent_level_id to walk the tree programmatically.
• Reporting on dimension breakdowns: GROUP BY dimension_name to count levels per dimension.

Because the view is public and joins only lookup and RHX definitional tables, it is safe for custom reporting layers and BIPublisher extracts in EBS 12.1.1 and 12.2.2 environments where Demand Planning is implemented.