Results for “to_number”

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

Overview

PQH_ATTRIBUTE_RANGES is a table in the HR schema belonging to the Public Sector HR (PQH) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata describes its purpose succinctly: it stores routing and authorization rules for transaction categories. In operational terms, the table defines the boundaries or ranges that govern how a given transaction is routed through a routing list and which approvers or members are involved at each step. Each row binds an attribute definition, a routing category, and a routing list member together with range criteria, allowing the routing engine to determine the appropriate disposition of a transaction based on values supplied during processing.

From a heuristic Data Vault modeling perspective, this object is classified as a link. The classification is mined from its foreign key structure: the table does not hold a descriptive master record of its own, but instead associates three parent entities — PQH_ATTRIBUTES, PQH_ROUTING_LIST_MEMBERS, and PQH_ROUTING_CATEGORIES — through surrogate foreign keys. This link recommendation reflects the fact that the row represents a relationship (a routing rule) rather than an independent business entity. The core business key is defined by the unique index PQH_ATTRIBUTE_RANGES_PK, which spans ATTRIBUTE_RANGE_ID and ZD_EDITION_NAME, confirming that the table participates in the Oracle 12.2.2 edition-based redefinition model.

Key Information Stored

The 23 documented columns resolve into several functional groups. The most significant are:

• ATTRIBUTE_RANGE_ID — the surrogate primary key, generated for each range definition and used as the target of downstream references.
• ATTRIBUTE_ID — foreign key to PQH_ATTRIBUTES, identifying which attribute the range applies to.
• ROUTING_CATEGORY_ID — foreign key to PQH_ROUTING_CATEGORIES, defining the transaction category being routed.
• ROUTING_LIST_MEMBER_ID — foreign key to PQH_ROUTING_LIST_MEMBERS, identifying the specific approver or member associated with the range.
• ASSIGNMENT_ID and POSITION_ID — contextual identifiers tying the rule to a specific assignment or position where the range applies.
• RANGE_NAME — the human-readable label for the range definition.
• APPROVER_FLAG — indicates whether the associated member acts as an approver for the transaction.
• FROM_CHAR, TO_CHAR, FROM_DATE, TO_DATE, FROM_NUMBER, TO_NUMBER — the typed boundary values that define the range itself across character, date, and numeric data types.
• ENABLE_FLAG and DELETE_FLAG — status controls determining whether the rule is active or logically deleted.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and concurrency columns.
• ZD_EDITION_NAME — the edition identifier supporting the 12.2.2 editioning architecture, and part of the primary key.

The business-key candidate is the composite of ATTRIBUTE_RANGE_ID with ZD_EDITION_NAME as captured in the unique index; the surrogate identifier remains ATTRIBUTE_RANGE_ID.

Common Use Cases and Queries

Typical usage centers on evaluating which approvers a transaction should reach. A common query joins the range table to its parents to resolve complete routing rules:

• Listing all ranges for a routing category: SELECT RANGE_NAME, ATTRIBUTE_ID, FROM_NUMBER, TO_NUMBER FROM HR.PQH_ATTRIBUTE_RANGES WHERE ROUTING_CATEGORY_ID = :cat AND ENABLE_FLAG = 'Y';
• Determining approvers by joining to PQH_ROUTING_LIST_MEMBERS on ROUTING_LIST_MEMBER_ID and filtering on APPROVER_FLAG = 'Y'.
• Auditing configuration changes by filtering LAST_UPDATE_DATE within a reporting period.
• Range evaluation logic: comparing a transaction amount against FROM_NUMBER and TO_NUMBER, or a date against FROM_DATE and TO_DATE.

Reports frequently exclude logically deleted rows with DELETE_FLAG = 'N' and restrict to the current edition via ZD_EDITION_NAME.

Related Objects

• PQH_ATTRIBUTES — joined on ATTRIBUTE_ID; supplies the attribute definition the range constrains.
• PQH_ROUTING_LIST_MEMBERS — joined on ROUTING_LIST_MEMBER_ID; identifies the member or approver.
• PQH_ROUTING_CATEGORIES — joined on ROUTING_CATEGORY_ID; defines the transaction category.
• PQH_ROUTING_LISTS — parent of routing list members, providing the routing list context.
• HR_ALL_ORGANIZATION_UNITS and PER_ALL_ASSIGNMENTS_F — referenced indirectly through ASSIGNMENT_ID and POSITION_ID for assignment and position context.