Search Results pqh_txn_category_attributes_pk




Overview
Explore in AI Chat

Overview

The PQH_TXN_CATEGORY_ATTRIBUTES table is a core intersection entity within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a critical junction table that establishes and manages the many-to-many relationships between transaction categories and their associated table attributes. In the context of Oracle EBS 12.1.1 and 12.2.2, this table is essential for configuring and controlling the specific data elements (attributes) that are relevant, required, or available for different types of HR transactions. By linking a transaction category to one or more attributes, it defines the data model and validation rules for transaction processing, enabling flexible and rule-based data capture within the complex workflows of public sector HR operations.

Key Information Stored

The table's primary purpose is to store relationship records, with its key columns serving as foreign keys to other master tables. The central identifier is the TXN_CATEGORY_ATTRIBUTE_ID, which is the primary key for each unique relationship record. The three principal foreign key columns define the relationship: TRANSACTION_CATEGORY_ID links to PQH_TRANSACTION_CATEGORIES, ATTRIBUTE_ID links to PQH_ATTRIBUTES, and TRANSACTION_TABLE_ROUTE_ID links to PQH_TABLE_ROUTE. This structure allows the system to answer which attributes are applicable for a given transaction category and, through the table route, understand the context or step in a process where that attribute is used. The intersection record itself may also store configuration flags controlling attribute behavior, such as whether it is mandatory, display-only, or hidden for that specific transaction context.

Common Use Cases and Queries

A primary use case is the dynamic generation of data entry screens or approval forms within a transaction workflow. The system queries this table to determine the list of attributes to display for a user performing a specific transaction type. For example, a "Promotion" transaction category may be linked to attributes like "New Grade" and "New Salary," while a "Transfer" may be linked to "New Department" and "New Location." Common queries include retrieving all attributes for a category or checking if a specific attribute is enabled for a given transaction. Sample SQL patterns include:

  • SELECT a.ATTRIBUTE_NAME FROM pqh_attributes a, pqh_txn_category_attributes tca WHERE tca.transaction_category_id = :p_category_id AND tca.attribute_id = a.attribute_id;
  • Investigating configuration issues by joining to all related master tables: PQH_TRANSACTION_CATEGORIES, PQH_ATTRIBUTES, and PQH_TABLE_ROUTE.

Related Objects

As an intersection table, PQH_TXN_CATEGORY_ATTRIBUTES has extensive relationships within the PQH schema. It is directly referenced by foreign keys from PQH_COPY_ENTITY_TXNS and PQH_SPECIAL_ATTRIBUTES, indicating its role in transaction copying and special attribute rule processing. Its existence is fundamentally dependent on three primary master tables: PQH_TRANSACTION_CATEGORIES (defining types of HR actions), PQH_ATTRIBUTES (defining the individual data fields available), and PQH_TABLE_ROUTE (defining process steps or contexts). Any customization, data fix, or report concerning the configuration of transaction data fields will likely involve joining to this central intersection entity to resolve the relationships between these key components.