Search Results pqh_attribute_ranges




Overview
Explore in AI Chat

Overview

The PQH_ATTRIBUTE_RANGES table is a core data object within the Oracle E-Business Suite (EBS) Public Sector Human Resources (PQH) module. It functions as the central repository for defining conditional routing and authorization rules, often referred to as workflow rules, for various personnel transaction categories. In the context of EBS 12.1.1 and 12.2.2, this table enables the configuration of complex, attribute-based approval hierarchies. Its role is to determine the appropriate approver or routing list for a transaction based on specific attribute values, such as an employee's salary, position, or department, thereby automating and enforcing organizational approval policies within the HRMS system.

Key Information Stored

The table's primary purpose is to link a specific range of values for a transaction attribute to a designated approval path. Key columns include the primary key, ATTRIBUTE_RANGE_ID, which uniquely identifies each rule. The ATTRIBUTE_ID column is a foreign key to PQH_ATTRIBUTES, defining which transaction attribute (e.g., 'Salary Amount', 'Job Grade') the rule evaluates. The ROUTING_CATEGORY_ID foreign key links to PQH_ROUTING_CATEGORIES, specifying the type of transaction (e.g., promotion, hire) to which the rule applies. Crucially, the ROUTING_LIST_MEMBER_ID foreign key points to PQH_ROUTING_LIST_MEMBERS, identifying the specific individual or group responsible for approval when the attribute value falls within the defined range. The table also typically contains columns to store the minimum and maximum values (FROM_VALUE and TO_VALUE) that constitute the applicable range for the specified attribute.

Common Use Cases and Queries

A primary use case is configuring tiered salary approval rules, where transactions exceeding certain monetary thresholds are routed to higher-level executives. For instance, a rule may specify that salary change requests between $50,000 and $100,000 require Director approval, while those over $100,000 require VP approval. Administrators and developers query this table to audit, troubleshoot, or report on existing routing configurations. A common SQL pattern retrieves all rules for a specific routing category:

  • SELECT attr.NAME, ar.FROM_VALUE, ar.TO_VALUE, rlm.NAME FROM pqh_attribute_ranges ar, pqh_attributes attr, pqh_routing_list_members rlm WHERE ar.attribute_id = attr.attribute_id AND ar.routing_list_member_id = rlm.routing_list_member_id AND ar.routing_category_id = <category_id> ORDER BY attr.NAME, ar.FROM_VALUE;

This is essential for validating that business rules are correctly implemented in the system.

Related Objects

PQH_ATTRIBUTE_RANGES is intrinsically linked to several key PQH tables, forming the backbone of the routing engine. As indicated by its foreign keys, it has a direct relationship with PQH_ATTRIBUTES (which defines the evaluable attributes), PQH_ROUTING_CATEGORIES (which defines transaction types), and PQH_ROUTING_LIST_MEMBERS (which defines approvers and approval lists). The table is heavily referenced by the underlying PL/SQL logic of the Public Sector HR workflows. While not a direct API, the business logic governing the creation and validation of these ranges is typically encapsulated within the associated PQH server-side packages, which manage the routing and approval processes for personnel transactions.