Search Results pqh_routing_hist_attribs




Overview
Explore in AI Chat

Overview

The PQH_ROUTING_HIST_ATTRIBS table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a detailed audit and tracking mechanism for workflow routing processes. Specifically, this table stores the attribute values captured at each step of a routing history instance. Its primary role is to persist the contextual data associated with each action or approval step in a workflow, enabling comprehensive audit trails, historical reporting, and process analysis for HR transactions within the public sector context of Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to link routing history steps with their specific data points. The primary key, ROUTING_HIST_ATTRIB_ID, uniquely identifies each stored attribute value. Two critical foreign keys define the table's relationships: ROUTING_HISTORY_ID links to the PQH_ROUTING_HISTORY table, anchoring the data to a specific workflow step, and ATTRIBUTE_ID links to the PQH_ATTRIBUTES table, defining the type of data being stored (e.g., approver comments, action dates, specific decision codes). The table would typically contain columns to hold the actual attribute value (e.g., VALUE_DATE, VALUE_NUMBER, VALUE_CHAR) and potentially context information, forming a complete record of the data in play at each routing milestone.

Common Use Cases and Queries

This table is essential for generating detailed audit reports on HR workflow approvals. A common use case involves tracing the complete decision-making history for a specific transaction, such as a position management change or a special salary authorization. Analysts can query this table to determine what information was presented to each approver and what values they recorded. A sample query pattern would join PQH_ROUTING_HIST_ATTRIBS to PQH_ROUTING_HISTORY and PQH_ATTRIBUTES to produce a human-readable audit trail.

  • Sample SQL Pattern: SELECT rh.process_name, rh.step_name, a.attribute_name, rha.value_char FROM pqh_routing_hist_attribs rha JOIN pqh_routing_history rh ON rha.routing_history_id = rh.routing_history_id JOIN pqh_attributes a ON rha.attribute_id = a.attribute_id WHERE rh.entity_key = :transaction_id ORDER BY rh.creation_date;
  • Reporting Use Case: Creating a report that shows all comments (a specific attribute) made by approvers at each step for a batch of personnel actions, used for compliance reviews or process optimization.

Related Objects

PQH_ROUTING_HIST_ATTRIBS is centrally connected to several key PQH tables. Its existence is dependent on the PQH_ROUTING_HISTORY table, which records the sequence of workflow steps, as enforced by the foreign key on ROUTING_HISTORY_ID. The definition of what attributes can be stored is governed by the PQH_ATTRIBUTES table, referenced via the ATTRIBUTE_ID foreign key. This table is part of a larger data model that likely includes PQH_ROUTING_CATEGORIES and transaction-specific header tables (e.g., PQH_POSITIONS, PQH_BUDGETS), with routing history linking to those entities. Direct manipulation of data in this table is typically performed by the application's underlying PL/SQL APIs rather than through manual DML.