Search Results pqh_attributes

Overview

The PQH_ATTRIBUTES table is a core data definition table within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It serves as the master repository for defining and managing custom attributes that extend the standard transaction data model. In the context of complex public sector HR processes, organizations often require additional, jurisdiction-specific data points to be captured during transactions. This table provides the structural metadata for these user-defined attributes, enabling the configuration of flexible data collection without direct modification of core application tables. Its role is central to the customization and legislative compliance features of the PQH product, acting as a reference point for attribute definitions used across various transaction workflows, document generation, and approval routing processes.

Key Information Stored

The table stores metadata that defines each attribute's characteristics and context. The primary identifier is the ATTRIBUTE_ID. A unique key constraint ensures the combination of MASTER_TABLE_ROUTE_ID, COLUMN_NAME, and LEGISLATION_CODE is unique, which defines where and under what legislative rule the attribute is applied. The MASTER_TABLE_ROUTE_ID foreign key links to PQH_TABLE_ROUTE, identifying the master transaction table or entity to which this attribute belongs. The COLUMN_NAME holds the logical name of the attribute as used within the system. The LEGISLATION_CODE allows for legislative-specific variations of attributes. The MASTER_ATTRIBUTE_ID column supports hierarchical attribute definitions by creating a self-referential relationship within the same table, pointing to a parent attribute definition.

Common Use Cases and Queries

A primary use case is the administrative setup and audit of custom attributes for transactions. System administrators query this table to review or modify the landscape of configured attributes. Common reporting needs include listing all attributes for a specific transaction table or legislation. For example, to find all attributes defined for a specific master table route under US legislation, one might use:

• SELECT attribute_id, column_name FROM pqh_attributes WHERE master_table_route_id = <route_id> AND legislation_code = 'US';

Another critical scenario is during transaction processing, where the application references PQH_ATTRIBUTES to determine which custom fields to render and validate. Integration or data migration scripts may also query this table to understand the target structure for custom data elements before populating related transactional child tables that store the actual attribute values.

Related Objects

As indicated by its foreign key relationships, PQH_ATTRIBUTES is a central hub referenced by numerous transactional and configuration tables. Key dependent objects include:

• PQH_TABLE_ROUTE: The master table referenced via MASTER_TABLE_ROUTE_ID.
• PQH_ATTRIBUTE_RANGES: Stores valid value ranges for attributes defined here.
• PQH_DOCUMENT_ATTRIBUTES_F & PQH_TEMPLATE_ATTRIBUTES: Link attributes to document templates and generation.
• PQH_ROUTING_HIST_ATTRIBS: Tracks attribute values within approval routing history.
• PQH_TXN_CATEGORY_ATTRIBUTES: Associates attributes with specific transaction categories.

The self-referencing foreign key on MASTER_ATTRIBUTE_ID also indicates a hierarchical relationship within the table itself, allowing for complex attribute structures.