Results for “node_type”

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

Overview

PQH_DE_CS_GRADES_V is an APPS-owned database view in the Oracle E-Business Suite Public Sector HR (PQH) product family. It exposes a hierarchical, self-referencing structure of generic hierarchy nodes that belong to hierarchy definitions of type REMUNERATION_REGULATION. In practice, the view presents the active remuneration-regulation hierarchy as a flattened but hierarchy-aware result set, returning one row per node together with its parent pointer and the underlying entity identifier. Rather than storing data itself, the view derives its contents from the generic hierarchy framework shared across Oracle HRMS, which allows multiple hierarchy structures (organizations, positions, grades, and remuneration regulations) to be modeled in a common set of tables.

In Oracle EBS 12.1.1 and 12.2.2, this view is primarily consumed by Public Sector HR grade and remuneration configuration screens, concurrent programs, and reporting or integration layers that need to navigate the regulation hierarchy without directly querying the base hierarchy tables. Because it filters on the currently effective hierarchy version, the view provides a date-sensitive snapshot of the regulation structure for the current system date.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

• PER_GEN_HIERARCHY — holds the hierarchy header, including the hierarchy type used to filter for REMUNERATION_REGULATION.
• PER_GEN_HIERARCHY_VERSIONS — holds the dated versions of each hierarchy, linked to the header by HIERARCHY_ID and constrained by DATE_FROM and DATE_TO.
• PER_GEN_HIERARCHY_NODES — holds the individual hierarchy nodes, including NODE_TYPE, HIERARCHY_NODE_ID, PARENT_HIERARCHY_NODE_ID, ENTITY_ID, and HIERARCHY_VERSION_ID.

The view joins the hierarchy header to its versions, restricts to versions effective on TRUNC(SYSDATE), and then performs a hierarchical CONNECT BY traversal over PER_GEN_HIERARCHY_NODES. The traversal starts at the node whose ENTITY_ID equals 'BE' and whose parent node is null, and walks downward using the relationship PARENT_HIERARCHY_NODE_ID = PRIOR HIERARCHY_NODE_ID.

Key Columns

• HIERARCHY_NODE_ID — the unique identifier of each node in the remuneration-regulation hierarchy. This is the column most commonly searched for and is used as the join key between parent and child rows.
• PARENT_HIERARCHY_NODE_ID — the identifier of the node's parent. A null value identifies the root node (ENTITY_ID = 'BE'). This column drives the CONNECT BY relationship.
• NODE_TYPE — indicates the classification of the node, distinguishing, for example, hierarchy levels or entity categories within the regulation structure.
• ENTITY_ID — the identifier of the underlying business entity represented by the node. The literal 'BE' denotes the starting, top-level node from which the hierarchy traversal begins.

Common Use Cases and Queries

Typical scenarios include verifying the active remuneration-regulation hierarchy, resolving parent-child relationships between grades or regulation nodes, and feeding upstream integrations that require node identifiers rather than entity names.

To list the full effective regulation hierarchy:

• SELECT NODE_TYPE, HIERARCHY_NODE_ID, PARENT_HIERARCHY_NODE_ID, ENTITY_ID FROM APPS.PQH_DE_CS_GRADES_V;

To locate a specific node and its parent:

• SELECT HIERARCHY_NODE_ID, PARENT_HIERARCHY_NODE_ID, ENTITY_ID FROM APPS.PQH_DE_CS_GRADES_V WHERE HIERARCHY_NODE_ID = :node_id;

To find all immediate children of a given node:

• SELECT HIERARCHY_NODE_ID, ENTITY_ID FROM APPS.PQH_DE_CS_GRADES_V WHERE PARENT_HIERARCHY_NODE_ID = :parent_node_id;

Because the view depends on TRUNC(SYSDATE), results reflect only the version effective today; historical or future-dated regulation structures must be queried from the base hierarchy tables directly.