Search Results transaction_category_id

Overview

The HR.PQH_TRANSACTION_CATEGORIES table is a core setup table within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically for the Position Hierarchy (PQH) functionality. Its primary role, as indicated by the metadata, is to provide "Setup information to allow selective routing of transactions." This table defines distinct categories or types of HR transactions, enabling the system to apply specific business rules, workflows, and routing paths based on the transaction type. It is a seed data table, residing in the APPS_TS_SEED tablespace, and is fundamental to configuring and controlling the behavior of HR position management processes in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on the unique identification and definition of each transaction category. The most critical column is TRANSACTION_CATEGORY_ID, which serves as the primary key (PQH_TRANSACTION_CATEGORIES_PK). Another uniquely constrained combination is SHORT_NAME and BUSINESS_GROUP_ID (PQH_TRANSACTION_CATEGORIES_UK), ensuring a unique, business group-specific identifier for each category. Key foreign key columns link to routing configuration: CONSOLIDATED_TABLE_ROUTE_ID and MASTER_TABLE_ROUTE_ID both reference the PQH_TABLE_ROUTE table, determining the approval routing rules for consolidated and master data scenarios, respectively. The FORM_NAME column is also indexed, suggesting its use in associating transaction categories with specific application forms or interfaces.

Common Use Cases and Queries

This table is primarily referenced during the setup and execution of HR position transactions. Administrators use it to define and maintain the list of valid transaction types, such as creation, update, or deletion of positions, and to assign appropriate workflow routes. Common technical queries involve joining this table to transactional data to retrieve category descriptions or enforce routing logic. For example, to list all transaction categories with their associated routing rule IDs for a specific business group:

• SELECT transaction_category_id, short_name, consolidated_table_route_id, master_table_route_id FROM hr.pqh_transaction_categories WHERE business_group_id = &bg_id;

Another frequent use case is resolving the transaction category for a given transaction record, often for reporting or debugging workflow issues:

• SELECT pt.*, cat.short_name FROM pqh_position_transactions pt, pqh_transaction_categories cat WHERE pt.wf_transaction_category_id = cat.transaction_category_id;

Related Objects

As per the foreign key dependencies, PQH_TRANSACTION_CATEGORIES is a central reference point for numerous transactional and setup tables. Key dependent objects include PQH_POSITION_TRANSACTIONS (which stores the actual transaction records), PQH_TEMPLATES, and PQH_TRANSACTION_TEMPLATES. It is also referenced by configuration tables like PQH_ROUTING_CATEGORIES, PQH_ROLE_TEMPLATES, and PQH_TXN_CATEGORY_ATTRIBUTES. The table has a direct relationship with PQH_TABLE_ROUTE via its two foreign key columns, forming the core of the transaction routing mechanism. This extensive web of dependencies underscores its critical role as a control table for the Position Hierarchy module.