Results for “parent_level_value”

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

Overview

RHX_DP_LVLVAL_PUB_V is a public view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It presents level value records for demand planning hierarchies, exposing the structural relationship between each level within a hierarchy and its parent level. The view is identified in the ETRM metadata as "Retrofitted," indicating it was carried forward to maintain compatibility across releases, and it is explicitly documented as not implemented in the current database. Its role is primarily reporting and integration: it provides a denormalized, DISTINCT-filtered projection of level value data that external programs, custom reports, and interface routines can consume without directly accessing the underlying base table.

Because the view carries the _PUB_ naming convention, it is intended as a published interface object — a stable contract exposed to customers and integrators. This is significant in Oracle EBS 12.1.1 and 12.2.2, where the underlying transactional tables may change shape between releases but the published view is expected to remain consistent. The view surfaces both the current level and its parent, which is precisely the context a user searching for "parent_level_value" requires: the parent side of a hierarchy relationship is materialized as first-class columns.

Underlying Base Objects

The documented metadata states that no referenced base objects are recorded and that the view is not implemented in the database. However, the view text unambiguously identifies its source: a single base table, RHX_DP_LEVEL_VALUES. The SELECT is a flattened, DISTINCT projection over the columns of that table, with no joins, unions, or subqueries. Consequently, the cardinality of the view equals the number of distinct level value rows present in RHX_DP_LEVEL_VALUES.

The DISTINCT clause deserves note. Where the base table may contain duplicate combinations — for example, repeated attribute or hierarchy entries — the view collapses them, presenting a clean set of level-to-parent associations. There are no documented additional base objects, and no aggregation or grouping is applied. The relationship is therefore one of pure projection: one row in the view corresponds to one distinct row in RHX_DP_LEVEL_VALUES.

Key Columns

• DIMENSION_CODE / DIMENSION_NAME — identify the planning dimension to which the level value belongs.
• DEMAND_PLAN_ID / DEMAND_PLAN_NAME — the demand plan context for the hierarchy.
• HIERARCHY_ID / HIERARCHY_NAME — the hierarchy containing the level.
• LEVEL_ID / LEVEL_NAME / LEVEL_VALUE — the level itself and the value assigned to it.
• ID_OF_LEVEL_VALUE — the identifier of the current level value.
• PARENT_LEVEL_ID / PARENT_LEVEL_NAME / PARENT_LEVEL_VALUE — the parent level context; these are the columns most relevant to the "parent_level_value" search.
• ID_OF_PARENT_LEVEL_VALUE — the identifier of the parent level value.
• BUCKET_START_DATE — the effective start of the time bucket for the level value.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns for extensibility.

Common Use Cases and Queries

Typical use is traversal of demand plan hierarchies, producing parent-child mappings and validating roll-ups.

• List all parent-child level relationships for a demand plan.
• Find the parent of a specific child level value.
• Extract hierarchy level values with descriptive flexfield attributes for reconciliation.
• Feed external planning or integration processes with a stable published representation.

Sample query:

SELECT DEMAND_PLAN_NAME, HIERARCHY_NAME, LEVEL_NAME, LEVEL_VALUE, PARENT_LEVEL_NAME, PARENT_LEVEL_VALUE FROM RHX_DP_LVLVAL_PUB_V WHERE DEMAND_PLAN_ID = :plan_id ORDER BY HIERARCHY_ID, LEVEL_ID;