Results for “routing_member_name”

24 results




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

Overview

PQH_ATTRIBUTE_RANGES_V4 is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PQH – Public Sector HR product family. In ETRM 12.1.1 and 12.2.2 it carries a VALID status and is described simply as an "Attribute Ranges View." Its purpose is to resolve the low-level routing configuration stored in PQH_ATTRIBUTE_RANGES into human-readable routing members, so that approvers, routing lists, and attribute ranges can be reported on without the consumer needing to join multiple decode packages by hand.

The view consolidates routing category, routing member, and routing member name into a single flattened result set. Rather than each row representing a raw foreign key, the view applies DECODE logic to determine whether a routing entry points to a routing list member, a position, or an assignment, and then resolves the appropriate display name. This makes it a convenient reporting surface for routing configuration reporting, approval matrix audits, and integration extracts where a descriptive identifier is required.

Underlying Base Objects

The documented base objects referenced by the view are PQH_ATTRIBUTE_RANGES (accessed through a synonym), PQH_ROUTING_LIST_MEMBERS_V (a view), HR_GENERAL (a package), and PQH_TCT_WIZARD_PKG (a package).

  • PQH_ATTRIBUTE_RANGES – The primary driver table, aliased RNG in the view text. It holds the attribute range definitions and the routing pointers (ROUTING_CATEGORY_ID, ROUTING_LIST_MEMBER_ID, POSITION_ID, ASSIGNMENT_ID).
  • PQH_ROUTING_LIST_MEMBERS_V – Aliased RLM, joined with an outer join on ROUTING_LIST_MEMBER_ID. It supplies role and user names for routing list members.
  • PQH_UTILITY – Supplies DECODE_ASSIGNMENT_NAME, used to resolve an assignment identifier into a display name.
  • HR_GENERAL – Supplies DECODE_POSITION, used to resolve a position identifier into a display name.
  • PQH_TCT_WIZARD_PKG – Documented as a referenced base object, associated with the attribute range wizard functionality that populates and maintains these ranges.

Because the view depends on these packages, its output reflects the current naming conventions and decode logic in the HR and PQH schemas at runtime.

Key Columns

  • ROUTING_CATEGORY_ID – Taken directly from RNG.ROUTING_CATEGORY_ID. Identifies the routing category the attribute range belongs to.
  • ROUTING_MEMBER_ID – A computed identifier. If ROUTING_LIST_MEMBER_ID is not null it returns that value; otherwise it falls back to POSITION_ID, and failing that to ASSIGNMENT_ID. It therefore presents a single, uniform member key regardless of member type.
  • ROUTING_MEMBER_NAME – A descriptive label corresponding to ROUTING_MEMBER_ID. For routing list members it concatenates ROLE_NAME and USER_NAME (for example, "Role - User"); for positions and assignments it returns the decoded position or assignment name.

Filtering in the view text excludes rows where ATTRIBUTE_ID is null and rows where the routing list member, position, and assignment identifiers are all null, ensuring only meaningful routing rows are exposed. DISTINCT is applied to suppress duplicates.

Common Use Cases and Queries

Typical uses include auditing which routing members are configured against attribute ranges, reconciling approval hierarchies, and feeding downstream reports or interfaces that require readable names rather than raw IDs.

  • Auditing routing categories and their members for a specific configuration.
  • Extracting routing member lists for approval workflow documentation.
  • Validating that positions and assignments resolve to valid decoded names.

Representative query:

SELECT routing_category_id, routing_member_id, routing_member_name FROM apps.pqh_attribute_ranges_v4 WHERE routing_category_id = :p_category_id ORDER BY routing_member_name;

To enumerate distinct members across all categories:

SELECT DISTINCT routing_member_id, routing_member_name FROM apps.pqh_attribute_ranges_v4 WHERE routing_member_name IS NOT NULL ORDER BY 2;

Because membership is derived at runtime through PQH_UTILITY and HR_GENERAL, name values reflect current position and assignment definitions, so results should be re-queried rather than cached when naming changes are possible.