Search Results txn_category_attribute_id




Overview
Explore in AI Chat

Overview

The HR.PQH_TXN_CATEGORY_ATTRIBUTES table is a critical intersection entity within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the HRMS module. It functions as a mapping table that defines the relationship between transaction categories and their associated table attributes. Its primary role is to configure and control which data attributes are relevant, visible, or required for specific transaction types within the system. By linking transaction categories (PQH_TRANSACTION_CATEGORIES) to underlying data attributes (PQH_ATTRIBUTES) and their associated tables (PQH_TABLE_ROUTE), it enables the dynamic assembly of data entry forms and security rules based on the business context of a transaction.

Key Information Stored

The table's structure centers on establishing these relationships and defining attribute behavior. The primary key, TXN_CATEGORY_ATTRIBUTE_ID, uniquely identifies each mapping record. The foreign key columns ATTRIBUTE_ID, TRANSACTION_CATEGORY_ID, and TRANSACTION_TABLE_ROUTE_ID form the core links to the related master entities. Control and configuration are managed through several flag columns: SELECT_FLAG indicates if the attribute is active for the category; IDENTIFIER_FLAG, LIST_IDENTIFYING_FLAG, and MEMBER_IDENTIFYING_FLAG determine if and how the attribute can be used to identify entities within workflow or list structures. The FORM_COLUMN_NAME specifies the exact database column or form field where the attribute-level security or rule is applied.

Common Use Cases and Queries

This table is central to transactional setups in HRMS, such as approvals, position management, or workforce transactions. A common use case involves querying all attributes configured for a specific transaction category to validate setup or troubleshoot a form. For example, to find all active attributes for a given transaction category, one might use:

  • SELECT pta.attribute_id, pa.attribute_name, pta.form_column_name FROM hr.pqh_txn_category_attributes pta JOIN hr.pqh_attributes pa ON pta.attribute_id = pa.attribute_id WHERE pta.transaction_category_id = <CATEGORY_ID> AND pta.select_flag = 'Y';

Another critical scenario is identifying the transaction category for a specific attribute mapping, often needed during data audits or when analyzing security rules based on the TXN_CATEGORY_ATTRIBUTE_ID.

Related Objects

HR.PQH_TXN_CATEGORY_ATTRIBUTES sits at the nexus of several key EBS HRMS objects. It is a child table to PQH_ATTRIBUTES, PQH_TRANSACTION_CATEGORIES, and PQH_TABLE_ROUTE, as defined by its foreign key constraints. Conversely, it is a parent table to PQH_COPY_ENTITY_TXNS and PQH_SPECIAL_ATTRIBUTES, which reference its primary key (TXN_CATEGORY_ATTRIBUTE_ID). This relationship hierarchy indicates its data is used to govern transaction copying functionality and the definition of special attribute rules. The associated indexes, such as PQH_TXN_CATEGORY_ATTRIBUTES_PK and the various foreign key indexes, are essential for maintaining performance in these interrelated transactional processes.