Search Results pqh_routing_lists




Overview
Explore in AI Chat

Overview

The PQH_ROUTING_LISTS table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. As indicated by its description, it serves as the master repository for defining routing lists used specifically for position-controlled workflow processes. In the context of Oracle EBS, particularly for public sector implementations, workflows often require approval or notification routing based on organizational hierarchy and position, rather than individual employees. This table provides the structural definition for these reusable routing paths, enabling the automation of business processes such as position management, funding, or transaction approvals according to configured organizational rules.

Key Information Stored

The table stores the fundamental metadata for each unique routing list. The primary identifier is the ROUTING_LIST_ID, a system-generated primary key (PQH_ROUTING_LISTS_PK). A critical business key is the ROUTING_LIST_NAME, which must be unique as enforced by the PQH_ROUTING_LISTS_UK unique key. This name is the user-facing identifier for the list. While the provided ETRM excerpt does not list all columns, typical supporting columns in such a table would include creation date, created by, last update date, last updated by, and potentially attributes for enabling/disabling the list or defining its effective dates. The table's structure is designed to be referenced by child tables that define the list's members and categorization.

Common Use Cases and Queries

The primary use case is the configuration and execution of position-based approval workflows. An administrator defines a routing list by name in this table, then populates its members via the related PQH_ROUTING_LIST_MEMBERS table. During a workflow transaction, the system queries this table to identify the valid routing list and then determines the specific approvers. Common queries include auditing all defined routing lists or troubleshooting workflow issues by examining list definitions. A fundamental sample SQL pattern is:

  • SELECT routing_list_id, routing_list_name, creation_date FROM hr.pqh_routing_lists ORDER BY routing_list_name;
  • SELECT rl.routing_list_name, rm.member_sequence, rm.object_type FROM hr.pqh_routing_lists rl, hr.pqh_routing_list_members rm WHERE rl.routing_list_id = rm.routing_list_id ORDER BY rl.routing_list_name, rm.member_sequence;

Related Objects

As per the documented foreign keys, PQH_ROUTING_LISTS has direct relationships with two key child tables. The PQH_ROUTING_LIST_MEMBERS table holds the sequential members (e.g., specific positions or roles) that constitute the routing list, linked via ROUTING_LIST_ID. The PQH_ROUTING_CATEGORIES table, also linked by ROUTING_LIST_ID, is used to categorize or group routing lists for different business processes or transaction types within the PQH module. This hierarchy allows a single routing list definition to be associated with multiple categories and contain multiple ordered members, forming the backbone of the position-controlled workflow engine.