Search Results role_extra_info_id




Overview
Explore in AI Chat

Overview

The PQH_ROLE_EXTRA_INFO table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a flexible extension table designed to store supplemental, role-specific information that is not captured in the standard role definition tables. This table enables the system to attach additional attributes and contextual data to roles, which is a common requirement in public sector HR implementations for managing complex position hierarchies, compliance data, or jurisdiction-specific role properties. Its existence underscores the configurability of the PQH module to meet specialized legislative and organizational needs beyond standard HRMS functionality.

Key Information Stored

The table's primary purpose is to hold key-value pairs of extra information linked to a specific role. Based on the provided metadata, the critical columns include:

  • ROLE_EXTRA_INFO_ID: The primary key column, uniquely identifying each record in this table.
  • ROLE_ID: A foreign key column that links the extra information to a specific role defined in the PQH_ROLES table. This is the fundamental relationship that ties the supplemental data to a role entity.
  • INFORMATION_TYPE: A column that categorizes the nature of the extra information stored. This acts as a classifier, allowing different categories of supplemental data (e.g., 'BUDGET_CODE', 'LEGISLATIVE_FLAG') to be associated with a role. The metadata indicates it references another lookup or validation table.
While specific column names for the actual data values are not detailed in the excerpt, a table of this design typically includes columns such as INFORMATION_NUMBER or INFORMATION_CHAR to store the supplemental value corresponding to the INFORMATION_TYPE.

Common Use Cases and Queries

This table is primarily accessed for enhanced role reporting and data validation within public sector processes. A common use case is generating reports that combine standard role descriptions with their extended attributes for audit or funding analysis. For instance, an organization may need to list all roles with a specific legislative classification. A typical query would join this table to PQH_ROLES to retrieve a comprehensive dataset.

Sample SQL Pattern:
SELECT pr.ROLE_NAME, prei.INFORMATION_TYPE, prei.INFORMATION_CHAR
FROM PQH_ROLES pr,
PQH_ROLE_EXTRA_INFO prei
WHERE pr.ROLE_ID = prei.ROLE_ID
AND prei.INFORMATION_TYPE = 'LEGISLATIVE_CODE';
This table is also critical for customizations or integrations where external systems require access to the full set of role attributes. Data from this table may be surfaced through custom forms or API-based interfaces.

Related Objects

The PQH_ROLE_EXTRA_INFO table maintains defined relationships with other key PQH entities, as documented in the metadata:

  • Primary Key: PQH_ROLE_EXTRA_INFO_PK on the ROLE_EXTRA_INFO_ID column.
  • Foreign Key (References PQH_ROLES): The ROLE_ID column is a foreign key to the PQH_ROLES table. This is the principal relationship, ensuring all extra information is attached to a valid, existing role definition.
  • Foreign Key (References Lookup): The INFORMATION_TYPE column references another table (not fully named in the excerpt, indicated by '%'), which is likely a lookup table (such as FND_LOOKUP_VALUES or a module-specific equivalent) that validates and provides meaning for the type codes used.
Consequently, any process or report involving detailed role information will typically involve joining PQH_ROLE_EXTRA_INFO with PQH_ROLES. Developers and DBAs must respect these referential integrity constraints during data loads, updates, or custom program development.