Results for “parent_level_id”

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

Overview

The view EDW_PVT_LEVEL_RELATION_MD_V is a public interface object owned by the APPS schema in Oracle E-Business Suite, shipped under the BIS – Applications BIS product family. In ETRM 12.1.1 and 12.2.2 it carries a VALID status, confirming that it is a compiled, deployable database object rather than a stub or deprecated artifact. Its name follows the Enterprise Data Warehouse (EDW) private-view naming convention, indicating that it functions as a lightweight metadata abstraction layer over the underlying hierarchy structures used by Oracle's Business Intelligence and Daily Business Intelligence (DBI) components.

The view presents parent–child relationships between analytic levels within a defined hierarchy. Rather than exposing the full detail of the source hierarchy model, it reduces the relationship to three surrogate identifiers, making it suitable for consumption by ETL processes, warehouse staging routines, and reporting layers that require a normalized level structure without accessing the full underlying hierarchy definition. Consultants searching for parent_level_id encounter this object because that column is one of the three identifiers the view publishes.

Underlying Base Objects

The documented view text defines the object with a single SELECT over CMPLEVELRELATIONSHIP_V:

• CMPLEVELRELATIONSHIP_V — the sole referenced source object. It is a view in the same BIS/CMP family that describes level-to-level relationships within a hierarchy.
• No additional base tables are documented in the ETRM metadata; the view contains no joins, filters, or aggregation, so it is a direct projection of the underlying relationship view.

Because the source is itself a view, the effective dependency chain continues into the CMP hierarchy tables (commonly the CMP_HIERARCHY and level definition tables) that populate CMPLEVELRELATIONSHIP_V. This layering is deliberate: EDW_PVT_LEVEL_RELATION_MD_V isolates downstream consumers from changes to the physical hierarchy schema, since only the column aliases need to remain stable.

Key Columns

The view exposes exactly three columns, all alias mappings from the source:

• HIERARCHY_ID — aliased from HIERARCHY. The surrogate identifier of the hierarchy to which the level relationship belongs. It scopes every parent/child pair to a single hierarchy definition.
• PARENT_LEVEL_ID — aliased from PARENTLEVEL. The identifier of the higher (parent) level in the relationship, typically the more aggregated level in the analytic rollup.
• CHILD_LEVEL_ID — aliased from CHILDLEVEL. The identifier of the lower (child) level, typically the more detailed level nested beneath the parent.

The triple (HIERARCHY_ID, PARENT_LEVEL_ID, CHILD_LEVEL_ID) forms the natural composite key describing an edge in the hierarchy's level graph. This mirrors the pattern of CMP_LEVEL_RELATIONSHIP-style tables and allows relationship chains to be reconstructed by self-join traversal.

Common Use Cases and Queries

Typical applications include validating hierarchy rollups, driving level-aware drill paths in DBI dashboards, and populating warehouse dimension keys. A minimal extraction query is:

• SELECT hierarchy_id, parent_level_id, child_level_id FROM apps.edw_pvt_level_relation_md_v;
• SELECT ... WHERE hierarchy_id = :p_hierarchy_id; to isolate a single hierarchy.
• SELECT parent_level_id, COUNT(*) FROM apps.edw_pvt_level_relation_md_v GROUP BY parent_level_id; to count children per parent level.

Because the object is a view, it must be accessed through a synonym or fully qualified schema reference, and it inherits the security of the APPS schema. Users troubleshooting parent_level_id should confirm the associated hierarchy_id and validate that the referenced level definitions exist in the corresponding CMP level metadata.