Results for “hri_primary_hrchys”

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

Overview

HRI_PRIMARY_HRCHYS is a table owned by the HRI schema, the database schema associated with Oracle Human Resources Intelligence (HRI), a module within Oracle E-Business Suite (EBS) that supports HR analytics and organizational reporting. The table stores the primary hierarchy definitions used by HR Intelligence to represent organizational structures across an enterprise. In Oracle EBS 12.1.1 and 12.2.2, this table functions as a foundational reference for organizational hierarchy traversal, capturing the relationship between an organization, its parent organization, and the versioned organization structure to which it belongs.

The heuristic Data Vault classification mined from the foreign-key structure identifies HRI_PRIMARY_HRCHYS as a standalone object. In Data Vault modeling terms, this suggests the table behaves most like a hub or reference structure rather than a transactional link or satellite, since no direct foreign-key dependencies to other tables were documented. Practitioners designing downstream models should treat this as a modeling suggestion rather than a hard constraint, as the true relationship topology may involve soft joins through business keys such as ORGANIZATION_ID and BUSINESS_GROUP_ID.

Key Information Stored

The table contains 12 documented columns. The composite primary key, enforced by the constraint HRI_PRIMARY_HRCHYS_PK, comprises three columns: ORGANIZATION_ID, ORGANIZATION_STRUCTURE_ID, and ORG_STRUCTURE_VERSION_ID. These three columns together form the surrogate primary key for the record and, in most implementations, also serve as the primary business-key candidate because the hierarchy row is uniquely identified by the combination of the organization, the structure it belongs to, and the version of that structure.

• ORGANIZATION_ID — Identifies the organization recorded in the hierarchy. Part of the composite primary key.
• ORGANIZATION_STRUCTURE_ID — Identifies the organizational structure (for example, a business group hierarchy or reporting hierarchy) to which the record belongs. Part of the composite primary key.
• ORG_STRUCTURE_VERSION_ID — Identifies the version of the organization structure, enabling historical tracking of hierarchy changes over time. Part of the composite primary key.
• PARENT_ORGANIZATION_ID — The parent organization to which the current organization rolls up, defining the hierarchy edge.
• ORGANIZATION_LEVEL — The depth or level of the organization within the hierarchy, useful for level-based reporting.
• BUSINESS_GROUP_ID — The business group context for the organization, supporting multi-tenant and multi-entity reporting.
• ORG_LAST_UPDATED — The date the underlying organization record was last updated, distinct from the table row audit timestamp.
• LAST_UPDATE_DATE — Standard EBS audit column capturing the last modification timestamp of the row.
• LAST_UPDATED_BY — The user ID that last modified the row.
• LAST_UPDATE_LOGIN — The login ID associated with the last update, used for audit trails.
• CREATED_BY — The user ID that created the row.
• CREATION_DATE — The timestamp when the row was created.

The standard EBS "who columns" (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) indicate that the table is maintained by concurrent programs or PL/SQL packages within the HRI module rather than by direct user data entry.

Common Use Cases and Queries

Typical use cases center on organizational reporting, hierarchy flattening, and historical analysis of structure changes. A common query pattern joins the table to itself on PARENT_ORGANIZATION_ID to reconstruct the hierarchy edges, then filters by ORGANIZATION_STRUCTURE_ID and ORG_STRUCTURE_VERSION_ID to obtain a point-in-time view.

• Point-in-time hierarchy extraction: SELECT ORGANIZATION_ID, PARENT_ORGANIZATION_ID, ORGANIZATION_LEVEL FROM HRI.HRI_PRIMARY_HRCHYS WHERE ORGANIZATION_STRUCTURE_ID = :p_structure AND ORG_STRUCTURE_VERSION_ID = :p_version;
• Version comparison: Compare two ORG_STRUCTURE_VERSION_ID values for the same ORGANIZATION_STRUCTURE_ID to detect reorganizations.
• Business group roll-up reporting: Group by BUSINESS_GROUP_ID to aggregate headcount or cost across organizations.
• Level-based analytics: Use ORGANIZATION_LEVEL to identify top-level or leaf organizations for dashboard filters.

HRI tables are frequently consumed by Oracle HRMS Intelligence reports and by custom BI Publisher or OBIA extracts. Because the primary key is composite and version-aware, extract queries should always include the structure and version predicates to avoid duplicating organizations across versions.

Related Objects

The following objects are most significant in relation to HRI_PRIMARY_HRCHYS. Because the Data Vault classification is standalone, no formal foreign keys are documented; joins are made through shared business keys.

• HR_ALL_ORGANIZATION_UNITS — Joined on ORGANIZATION_ID to resolve organization names and attributes.
• HR_ORGANIZATION_INFORMATION — Joined on ORGANIZATION_ID for organization classifications and descriptive flexfields.
• HR_ORG_STRUCTURE_ELEMENTS — Provides the structure element definitions referenced by ORGANIZATION_STRUCTURE_ID.
• HR_ORG_STRUCTURE_VERSIONS — Joined on ORG_STRUCTURE_VERSION_ID to resolve version dates and status.
• HR_ORG_STRUCTURE_ELEMENT_VERSIONS — Links structure elements to versions consumed by this table.
• PER_BUSINESS_GROUPS — Joined on BUSINESS_GROUP_ID to enforce the operating unit or business group context.
• HRI_PRIMARY_HRCHYS_PK — The primary key constraint enforcing uniqueness on ORGANIZATION_ID, ORGANIZATION_STRUCTURE_ID, and ORG_STRUCTURE_VERSION_ID.
• HR_ORGANIZATION_UNITS — The underlying organization definition table from which ORGANIZATION_ID values are drawn.

Together these objects support end-to-end organizational hierarchy reporting within the Human Resources Intelligence module and its downstream analytics consumers.