Results for “sub_entity_id”

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

Overview

The HRI.HRI_GEN_HRCHY_SUMMARY table is a core object within the Human Resources Intelligence (HRI) product family of Oracle E-Business Suite, maintained in both 12.1.1 and 12.2.2. It stores a Generic Hierarchy Summary — a flattened, denormalized representation of hierarchical relationships between entities (typically HR organizations, positions, supervisors, or other classification structures) and their sub-entities. In the Oracle EBS architecture, HRI objects support HR analytics, workforce intelligence dashboards, and Oracle Daily Business Intelligence (DBI) reporting, and this table serves as the pre-aggregated backbone that allows hierarchical roll-up queries to execute efficiently at report time.

The documented physical schema for release 12.2.2 contains 17 columns in the HRI schema. From a Data Vault modeling perspective (a heuristic derived from the mined foreign-key structure), this object is classified as standalone. Because it is not linked by explicit foreign keys to parent hubs, it is best treated as a self-contained reference or denormalized summary structure rather than a strict hub, link, or satellite. Where a Data Vault design were imposed, the composite of the hierarchy identifiers would behave most like a link, with the descriptive and audit attributes acting as satellite content.

Key Information Stored

The table is uniquely identified by the composite primary key HRI_GEN_HRCHY_SUMMARY_PK, which comprises four columns:

• HIERARCHY_ID — Identifies the generic hierarchy instance (for example, an organization hierarchy or a supervisor hierarchy).
• HIERARCHY_VERSION_ID — Distinguishes dated or versioned instances of the same hierarchy, enabling as-of and historical reporting.
• HIERARCHY_NODE_ID — The parent/superior node within the hierarchy.
• SUB_HIERARCHY_NODE_ID — The descendant/subordinate node; together with the parent node this defines each edge or roll-up pair in the summary.

These four columns form the natural business key and, being the primary key, are the only documented unique identifier. Representative descriptive attributes include:

• BUSINESS_GROUP_ID — The operating business group (multi-organization context), a standard discriminator in HR tables.
• ENTITY_ID and ENTITY_LEVEL — The parent entity's identifier and its depth/level in the hierarchy.
• NODE_TYPE — The classification of the hierarchy node (such as organization or position).
• SUB_ENTITY_BG_ID, SUB_ENTITY_ID, and SUB_ENTITY_LEVEL — The corresponding business group, identifier, and level for the subordinate entity.
• SUB_NODE_TYPE — The node classification of the subordinate.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns identifying who created and last modified each row.

Common Use Cases and Queries

The table is most often consumed in HR analytics and reporting solutions that must traverse hierarchies without recursive joins against operational tables at run time. Typical scenarios include workforce headcount roll-ups by management level, span-of-control and depth-of-hierarchy analysis, and organizational comparison reports.

A representative query to retrieve all direct descendants of a node might be:

• SELECT hierarchy_node_id, sub_hierarchy_node_id, sub_entity_level FROM hri_gen_hrchy_summary WHERE hierarchy_id = :p_id AND hierarchy_version_id = :v_id AND hierarchy_node_id = :n_id AND business_group_id = :bg_id;
• Level-based roll-up: filter on entity_level or sub_entity_level to produce reports at a consistent depth.
• Version comparison: join or filter across hierarchy_version_id values to compare prior and current structures.

Related Objects

The mined relationship data indicates no enforced foreign keys (standalone classification), so dependency is largely logical rather than referential. The most relevant associated objects are:

• HRI_HIERARCHY_NODES (or the corresponding hierarchy definition table in HRI) — joined on HIERARCHY_NODE_ID and HIERARCHY_ID to obtain node names and types.
• HRI_HIERARCHIES — provides hierarchy metadata, joined on HIERARCHY_ID.
• PER_ALL_ORGANIZATION_UNITS — joined on ENTITY_ID / SUB_ENTITY_ID where nodes represent organizations.
• HR_ALL_ORGANIZATION_UNITS — the HR organization definition used in the joined business group context.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for audit reporting.
• HRI_GEN_HRCHY_SUMMARY consumers such as DBI/HR analytics views and Oracle BI Publisher report datasets that source hierarchy metrics directly.

Because the object is standalone, referential integrity is enforced by the HRI collection programs that populate and refresh the summary, making this table a reliable derivation of the underlying hierarchy definitions.