Results for “pqh_attribute_ranges_v3”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PQH_ATTRIBUTE_RANGES_V3 is an APPS-owned view within the Public Sector HR (PQH) product family of Oracle E-Business Suite. It exposes attribute range definitions that control routing and approval behavior for HR transactions, and it is designed primarily for consumption by the Oracle Approvals Management / routing engine rather than by end users. The view presents a denormalized, presentation-ready projection of routing membership: instead of forcing a caller to resolve whether a routing target is a routing list member, a position, or an assignment, the view collapses these alternatives into a single routing member identifier and a corresponding display name.
The view is documented as VALID and is referenced in the 12.1.1 and 12.2.2 ETRM repository under the APPS schema. Its naming convention is significant: the V3 suffix indicates a versioned interface, meaning prior versions (V1, V2) may still exist for backward compatibility with existing personalizations, concurrent programs, or custom code. Developers migrating code across releases should confirm which version a given integration was originally built against before substituting V3.
Underlying Base Objects
PQH_ATTRIBUTE_RANGES_V3 is defined over two principal row sources joined in the view text:
- PQH_ATTRIBUTE_RANGES (referenced via synonym as RNG) — the driving table holding each attribute range record, including its range name, approver and enablement flags, and the alternative routing targets (routing list member, position, or assignment).
- PQH_ROUTING_LIST_MEMBERS_V (referenced as RLM) — a view supplying the resolved routing list member, including user and role names, joined with an outer join on ROUTING_LIST_MEMBER_ID.
Supporting objects called from the SELECT list include the HR_GENERAL package (specifically HR_GENERAL.DECODE_POSITION), which resolves a position identifier into a display name, and PQH_UTILITY, which resolves an assignment identifier through DECODE_ASSIGNMENT_NAME. The documented base object list also cites PQH_TCT_WIZARD_PKG, which participates in the broader attribute range and routing configuration flow. Because the view invokes package functions in its projection, queries against it can carry PL/SQL context-switch overhead; this is a material performance consideration for high-volume reports.
Key Columns
- ATTRIBUTE_RANGE_ID — the primary identifier of the attribute range record; this is the column most commonly supplied as a bind variable or join predicate.
- ROUTING_CATEGORY_ID — identifies the routing category to which the range belongs, linking the range to a routing configuration.
- ATTRIBUTE_ID — the attribute the range qualifies. The view predicate restricts output to rows where ATTRIBUTE_ID IS NULL, so only non-attribute-specific ranges are surfaced by this version.
- ROUTING_MEMBER_ID — a derived, coalesced identifier. It returns the routing list member when present; otherwise the position identifier, otherwise the assignment identifier.
- ROUTING_MEMBER_NAME — the human-readable counterpart, built from role name, role-and-user concatenation, position decode, or assignment decode as appropriate.
- RANGE_NAME — the descriptive name assigned to the range.
- APPROVER_FLAG and ENABLE_FLAG — control flags indicating whether the range acts as an approver and whether it is active.
- OBJECT_VERSION_NUMBER — the optimistic locking column carried through from the base table.
Common Use Cases and Queries
Typical uses include validating routing configuration prior to go-live, auditing which ranges are enabled, and resolving a routing member name for a given range in reports and interfaces. Because the view filters out rows with a non-null ATTRIBUTE_ID, it is the correct source when only assignment-, position-, or list-based ranges are relevant.
To retrieve all enabled approver ranges:
SELECT attribute_range_id, routing_category_id, range_name,
routing_member_id, routing_member_name
FROM apps.pqh_attribute_ranges_v3
WHERE enable_flag = 'Y'
AND approver_flag = 'Y';
To resolve a specific range by its searched identifier:
SELECT attribute_range_id, range_name, routing_member_name FROM apps.pqh_attribute_ranges_v3 WHERE attribute_range_id = :p_attribute_range_id;
When joining to other routing configuration tables, drive from ATTRIBUTE_RANGE_ID and always filter on ENABLE_FLAG to avoid surfacing obsolete ranges. Given the package calls in the projection, avoid selecting unnecessary columns in bulk extracts.
-
Attribute Ranges View
APPS.PQH_ATTRIBUTE_RANGES_V3·↳ HR_GENERAL·↳ PQH_ATTRIBUTE_RANGES·↳ PQH_ROUTING_LIST_MEMBERS_V·Explore PQH module →
-
Attribute Ranges View
APPS.PQH_ATTRIBUTE_RANGES_V3·↳ HR_GENERAL·↳ PQH_ATTRIBUTE_RANGES·↳ PQH_ROUTING_LIST_MEMBERS_V·Explore PQH module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - PQH Tables and Views 12.1.1
This is a Copy of PQH_WORKSHEET_PERIODS table populated by EFC (Euro as functinoal currency) process.
-
eTRM - PQH Tables and Views 12.2.2
This is a Copy of PQH_WORKSHEET_PERIODS table populated by EFC (Euro as functinoal currency) process.
-
eTRM - PQH Tables and Views 12.1.1
This is a Copy of PQH_WORKSHEET_PERIODS table populated by EFC (Euro as functinoal currency) process.
-
12.2.2 DBA Data 12.2.2
-
eTRM - PQH Tables and Views 12.2.2
This is a Copy of PQH_WORKSHEET_PERIODS table populated by EFC (Euro as functinoal currency) process.
-
12.1.1 DBA Data 12.1.1