Results for “enable_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQH_ROUTING_LISTS is a transactional configuration table owned by the HR schema within the Public Sector HR (PQH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores routing lists that drive position-controlled workflow, a mechanism used primarily by public sector and federal implementations to direct approval, notification, or review routing based on the hierarchical position structure of the organization rather than on the standard Oracle HR supervisory hierarchy. A routing list defined in this table acts as a reusable container that determines which approvers, reviewers, or recipients participate in a given workflow event initiated against a position.

From a dimensional modeling perspective, the ETRM-provided heuristic classifies this object as hub-leaning within a Data Vault construct. This reflects the fact that PQH_ROUTING_LISTS carries its own unique business key — ROUTING_LIST_NAME — and serves as the central reference point into which dependent satellite and link-style detail (categories and members) resolve. Practically, this means the table can be modeled as a stable business entity, with its mutable descriptive attributes and its member/category associations separated into downstream constructs.

Key Information Stored

The table consists of nine documented columns and supports two key structures. The surrogate primary key is ROUTING_LIST_ID, enforced by the PQH_ROUTING_LISTS_PK constraint. A second unique index, PQH_ROUTING_LISTS_UK, is defined on ROUTING_LIST_NAME, establishing that column as the business-key candidate — the human-readable identifier by which administrators and end users recognize a given routing configuration.

Among the remaining columns, ENABLE_FLAG governs whether the routing list is active and eligible for use in workflow resolution; disabled lists remain intact but are ignored by the routing engine. The standard audit and concurrency columns are present: OBJECT_VERSION_NUMBER provides optimistic locking for the Oracle Application Framework, while CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture the full who-and-when lineage required for compliance reporting and data reconciliation. Collectively, these attributes make the table both a functional configuration store and an auditable master record.

Common Use Cases and Queries

The most frequent scenario is identifying which routing lists exist, which are currently enabled, and how each is composed. A baseline reporting query returns the active lists:

• SELECT routing_list_id, routing_list_name, enable_flag, last_update_date FROM hr.pqh_routing_lists WHERE enable_flag = 'Y' ORDER BY routing_list_name;
• Joining to PQH_ROUTING_LIST_MEMBERS on ROUTING_LIST_ID to enumerate the approvers or recipients attached to each list.
• Joining to PQH_ROUTING_CATEGORIES on ROUTING_LIST_ID to determine which workflow categories a list is bound to, supporting impact analysis before disabling or renaming a list.
• Audit-style queries filtering on CREATED_BY or LAST_UPDATED_BY to trace configuration changes made during a given period.

Typical reporting use cases include documenting approval hierarchies for audit, validating that every active workflow category references an enabled routing list, and generating configuration baselines when migrating between 12.1.1 and 12.2.2 environments.

Related Objects

Two documented foreign-key relationships anchor this table to the rest of the position-controlled workflow model:

• PQH_ROUTING_CATEGORIES — references PQH_ROUTING_LISTS via PQH_ROUTING_CATEGORIES.ROUTING_LIST_ID, associating each category with the routing list that governs it.
• PQH_ROUTING_LIST_MEMBERS — references PQH_ROUTING_LISTS via PQH_ROUTING_LIST_MEMBERS.ROUTING_LIST_ID, defining the individual members (approvers or recipients) belonging to each list.

Together with the parent PQH_ROUTING_LISTS record, these two dependent tables form the complete routing-list configuration set. Any modification to a routing list, particularly disabling it or altering its members, should be evaluated against both referencing tables to ensure workflow continuity in a position-controlled environment.