Search Results transaction_template_id




Overview
Explore in AI Chat

Overview

The PQH_TRANSACTION_TEMPLATES table is a core data object within the Oracle E-Business Suite Public Sector HR (PQH) module. It functions as a junction table that establishes a critical relationship between task templates and specific HR transactions. Its primary role is to define and enforce the type and security model applicable to a given transaction by linking it to a predefined template. This linkage is essential for governing the workflow, approval routing, and data access controls for personnel actions in a public sector context, ensuring transactions adhere to configured business rules and security policies.

Key Information Stored

The table stores the associative entities that bind templates to transactions. The key columns include:

  • TRANSACTION_TEMPLATE_ID: The primary surrogate key for the table, uniquely identifying each template-transaction association.
  • TEMPLATE_ID: A foreign key referencing the PQH_TEMPLATES table. This identifies the specific task template governing the transaction's process.
  • TRANSACTION_ID: This column identifies the specific HR transaction type being controlled. The exact source of this identifier depends on the transaction's origin within the HRMS suite.
  • TRANSACTION_CATEGORY_ID: A foreign key referencing the PQH_TRANSACTION_CATEGORIES table. This classifies the transaction into a broader category for grouping and management purposes.
The table enforces uniqueness through a separate unique key constraint (PQH_TRANSACTION_TEMPLATE_UK) on the combination of TEMPLATE_ID, TRANSACTION_ID, and TRANSACTION_CATEGORY_ID.

Common Use Cases and Queries

This table is central to configuring and auditing the security framework for HR transactions. A common use case involves identifying all transaction types governed by a particular template for security analysis or template modification impact assessment. For example, to list all transactions linked to a specific template name:

SELECT tt.transaction_id, tt.transaction_category_id, t.template_name
FROM pqh_transaction_templates tt,
     pqh_templates t
WHERE tt.template_id = t.template_id
  AND t.template_name = '&TEMPLATE_NAME';

Another critical reporting use case is verifying the complete security setup for a transaction category, which is essential for compliance audits:

SELECT cat.name category_name,
       t.template_name,
       tt.transaction_id
FROM pqh_transaction_templates tt,
     pqh_transaction_categories cat,
     pqh_templates t
WHERE tt.transaction_category_id = cat.transaction_category_id
  AND tt.template_id = t.template_id
ORDER BY cat.name, t.template_name;

Related Objects

The PQH_TRANSACTION_TEMPLATES table is intrinsically linked to other key PQH structures. It has defined foreign key relationships to two primary tables:

  • PQH_TRANSACTION_CATEGORIES: Via the TRANSACTION_CATEGORY_ID column, linking the template association to a defined transaction category.
  • PQH_TEMPLATES: Via the TEMPLATE_ID column, linking to the master definition of the task template that controls security and process flow.
This table is a foundational component for the Public Sector HR security model, and its data is likely referenced by various internal APIs, workflows, and user interfaces within the PQH module to determine the appropriate processing rules for any given HR transaction.