Search Results opl_pk

Overview

HRI_ORG_PARAM_LIST is a table owned by the HRI schema (Human Resources Intelligence) in Oracle E-Business Suite 12.1.1 and 12.2.2. The documented description identifies it as the "BIS Organization Parameters List," indicating its role within the Business Intelligence System layer that supports HR analytics and reporting. The table associates organization parameter definitions with specific organizations, acting as an intersection between parameter metadata and the organizational hierarchy that the HR Intelligence module reports against.

In Data Vault modeling terms, the metadata's heuristic classification for this object is link. This is a modeling suggestion rather than an enforced designation: the table resolves relationships between two or more business concepts via foreign key references, which is the classic pattern of a link entity. Its structure is consistent with that interpretation, connecting organization identifiers to parameter records rather than storing a single descriptive entity on its own.

Key Information Stored

The documented physical schema for HRI_ORG_PARAM_LIST contains eight columns. The most significant are the three key components that participate in the primary key constraints, plus the standard EBS audit columns.

• ORG_PARAM_ID — Identifier for the organization parameter; participates in the HRI_ORG_PARAM_LIST_PK primary key and carries a foreign key to HRI_ORG_PARAMS.
• ORGANIZATION_ID_GROUP — Organization group identifier; part of both the primary key and the business-key candidate.
• ORGANIZATION_ID_CHILD — The child organization identifier; the column the user searched for. It is part of the composite primary key and the unique index, and it denotes the descendant organization covered by the parameter entry.
• LAST_UPDATE_DATE — Timestamp of the most recent change to the row.
• LAST_UPDATED_BY — User who performed the last update.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update session.
• CREATED_BY — User who created the row.
• CREATION_DATE — Timestamp when the row was created.

Two unique constraints are documented: HRI_ORG_PARAM_LIST_PK (ORG_PARAM_ID, ORGANIZATION_ID_GROUP, ORGANIZATION_ID_CHILD) and OPL_PK, which covers the same three columns in the order ORGANIZATION_ID_CHILD, ORG_PARAM_ID, ORGANIZATION_ID_GROUP. These represent the business-key candidates; no separate single-column surrogate key is documented, so the composite of parameter and organization identifiers serves as the effective identity of each row.

Common Use Cases and Queries

Because ORGANIZATION_ID_CHILD is a key column, queries that drill into descendant organizations are the most frequent access pattern. A typical reporting query joins the list back to the parameter definition to return organization-specific parameter values:

• Resolving which parameters apply to a given child organization: SELECT * FROM hri.hri_org_param_list WHERE organization_id_child = :org_id;
• Listing all organizations sharing a parameter: SELECT organization_id_child FROM hri.hri_org_param_list WHERE org_param_id = :param_id;
• Traversing group membership by filtering on organization_id_group to return every child organization under a reporting group.
• Audit and incremental extract patterns filtering on LAST_UPDATE_DATE for downstream HR warehouse loads.

HR Intelligence dashboards, organizational hierarchy reports, and parameter-driven analytics commonly read this table to determine scope — which organizations a parameter set influences — before aggregating headcount or cost metrics.

Related Objects

• HRI_ORG_PARAMS — Referenced by the ORG_PARAM_ID foreign key; provides the parameter definitions associated with each list entry. Join on HRI_ORG_PARAM_LIST.ORG_PARAM_ID = HRI_ORG_PARAMS.ORG_PARAM_ID.
• HRI_ORG_PARAM_LIST_PK — The primary key constraint enforcing uniqueness across ORG_PARAM_ID, ORGANIZATION_ID_GROUP, and ORGANIZATION_ID_CHILD.
• OPL_PK — The secondary unique constraint over the same key columns.
• Organization hierarchy tables (HR_ALL_ORGANIZATION_UNITS and related) — Provide the parent/child organization context referenced by ORGANIZATION_ID_GROUP and ORGANIZATION_ID_CHILD, as implied by the naming of those columns.

The FK metadata documents two references from ORG_PARAM_ID to HRI_ORG_PARAMS, which reflects repeated or overlapping constraint definitions rather than two distinct parent tables.