Search Results hri_org_params_pk

Overview

HRI_ORG_PARAMS is a table owned by the HRI schema (Human Resources Intelligence), the business intelligence layer that underpins Oracle HRMS reporting, Oracle HRMSi dashboards, and the BIS (Business Intelligence System) collection programs. The table is documented in ETRM with the description "BIS Organization Parameters Header," which identifies its role as the header or driver record for the organizational parameter sets that control how HR intelligence extracts, aggregates, and presents organization-level data. Each row defines a combination of an organization, an organization structure, and an organizational process, establishing the context in which downstream parameter values are evaluated.

The 12.2.2 physical schema documents nine columns and three constraints: the surrogate primary key HRI_ORG_PARAMS_PK on ORG_PARAM_ID, a business-key unique index HRI_ORG_PARAMS_UK1 on (ORGANIZATION_PROCESS, ORGANIZATION_ID, ORGANIZATION_STRUCTURE_ID), and an additional PK/UK pair named ORP_PK / ORP_UK carrying the same column sets. Based on the mined foreign-key structure, the table is best modeled as a hub-leaning entity in Data Vault terms: it holds the durable business key and serves as the anchor to which descriptive detail tables attach.

Key Information Stored

The most significant columns fall into three groups: surrogate identity, business key, and audit metadata.

• ORG_PARAM_ID — the surrogate primary key (HRI_ORG_PARAMS_PK, also ORP_PK); a system-generated identifier for each parameter header record.
• ORGANIZATION_PROCESS — the organizational process the parameter set applies to; part of the HRI_ORG_PARAMS_UK1 / ORP_UK business key.
• ORGANIZATION_ID — identifies the organization within the HRMS organization model; part of the business key.
• ORGANIZATION_STRUCTURE_ID — references PER_ORGANIZATION_STRUCTURES, qualifying which hierarchy (for example, a business group, organization hierarchy, or position hierarchy) the parameter applies to; part of the business key.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — the standard WHO audit columns that record insert and update provenance.

The unique index on (ORGANIZATION_PROCESS, ORGANIZATION_ID, ORGANIZATION_STRUCTURE_ID) is the natural business key and prevents duplicate parameter headers for the same organization, structure, and process combination.

Common Use Cases and Queries

The table is most often queried to resolve which parameter set governs a given organization context, and then to join to HRI_ORG_PARAM_LIST for the individual parameter values.

• Resolve a parameter header for a known organization:

SELECT p.org_param_id, p.organization_id, p.organization_structure_id,
       p.organization_process
  FROM hri_org_params p
 WHERE p.organization_id = :org_id
   AND p.organization_structure_id = :org_structure_id;

• Retrieve parameter values for a header:

SELECT l.org_param_id, l.*
  FROM hri_org_param_list l
 WHERE l.org_param_id = :org_param_id;

• Report organization coverage: count of configured processes per organization or per organization structure, useful for auditing which organizations have HR intelligence parameters defined.
• Change tracking: filter on LAST_UPDATE_DATE to identify recently modified parameter headers.

Related Objects

• HRI_ORG_PARAM_LIST — child detail table; joins on HRI_ORG_PARAM_LIST.ORG_PARAM_ID = HRI_ORG_PARAMS.ORG_PARAM_ID. This is the primary dependent object.
• PER_ORGANIZATION_STRUCTURES — referenced via HRI_ORG_PARAMS.ORGANIZATION_STRUCTURE_ID; provides the hierarchy definition used to qualify the parameter header.
• PER_ORGANIZATION_UNITS / HR_ALL_ORGANIZATION_UNITS — typically joined on ORGANIZATION_ID to resolve organization names and business group context.
• BIS / HRMSi concurrent programs and collection routines in the HRI schema that read HRI_ORG_PARAMS and HRI_ORG_PARAM_LIST to drive HR intelligence extracts.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for audit reporting.

Because the table sits at the top of the HRI organization parameter hierarchy, any customization or data fix should preserve the uniqueness enforced by HRI_ORG_PARAMS_UK1 and maintain referential integrity with HRI_ORG_PARAM_LIST.