Results for “delete_flag”

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

Overview

PQH_ATTRIBUTE_RANGES_V1 is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PQH (Public Sector HR) product family. Its documented description is simply "Attribute Ranges View." In practice, the view exposes the set of routing category attribute ranges defined for routing lists, filtered to only those range definitions that are global rather than tied to a specific routing list member, position, or assignment.

The view is defined with a WHERE clause that excludes any row where ROUTING_LIST_MEMBER_ID, POSITION_ID, or ASSIGNMENT_ID is populated. This means PQH_ATTRIBUTE_RANGES_V1 surfaces only the "header-level" or category-level attribute ranges — the reusable range definitions keyed by routing category and range name — while the context-specific ranges associated with individual members, positions, or assignments remain in the base table. For reporting and integration purposes, the view therefore acts as a clean, de-duplicated lookup of routing category ranges, isolating the range_name and enable/delete status attributes that functional users and downstream processes rely on. It is one of several attribute-range views in the PQH schema, each scoped to a different level of the routing hierarchy.

Underlying Base Objects

The view is defined over a single documented base object: the synonym PQH_ATTRIBUTE_RANGES, which resolves to the underlying APPS table of the same name. No joins to other tables are present; the view text is a simple filtered projection:

• PQH_ATTRIBUTE_RANGES (SYNONYM) — the physical base table holding attribute range definitions, including routing category, range name, and the routing list member, position, and assignment discriminators.

Because the view references the synonym rather than the fully qualified base table and performs no join, its dependency chain is shallow and stable across releases. The distinctive behavior of the view is entirely driven by its WHERE predicate: only rows with NULL ROUTING_LIST_MEMBER_ID, POSITION_ID, and ASSIGNMENT_ID qualify. A DISTINCT keyword further eliminates duplicate combinations of the projected columns, ensuring each routing category/range name pairing appears once.

Key Columns

The view exposes four columns, drawn directly from the base table:

• ROUTING_CATEGORY_ID — Identifier of the routing category to which the range definition belongs. This is the primary grouping key and the column most commonly used to join the view to routing category definitions.
• RANGE_NAME — The user-defined name of the attribute range. This is the column most frequently queried and displayed, and matches the "range_name" search term by which this object is typically located.
• ENABLE_FLAG — Indicates whether the range definition is currently active (enabled) or inactive.
• DELETE_FLAG — Deletion indicator, exposed through an NVL expression that substitutes 'N' when the underlying value is NULL, so the view always returns a non-null, single-character flag.

The DELETE_FLAG column is the only one subject to transformation in the view text; the remaining three columns are passed through unchanged.

Common Use Cases and Queries

Typical uses include validating routing category configuration, populating LOVs or parameter lists for range_name, and auditing which ranges are enabled versus soft-deleted. Because the view excludes member-, position-, and assignment-specific rows, queries against it return the global range definitions only — ideal when a report or interface needs the category-level template rather than every contextual instance.

To list all active range names for a routing category:

• SELECT routing_category_id, range_name FROM apps.pqh_attribute_ranges_v1 WHERE enable_flag = 'Y' AND delete_flag = 'N' AND routing_category_id = :p_category_id ORDER BY range_name;

To search for a specific range by name, the pattern most relevant to a range_name lookup:

• SELECT routing_category_id, range_name, enable_flag FROM apps.pqh_attribute_ranges_v1 WHERE UPPER(range_name) LIKE UPPER('%' || :p_range_name || '%');

To audit disabled or soft-deleted ranges:

• SELECT routing_category_id, range_name, enable_flag, delete_flag FROM apps.pqh_attribute_ranges_v1 WHERE enable_flag = 'N' OR delete_flag = 'Y';

Because the view is owned by APPS and built on a synonym, it must be accessed with the APPS schema prefix or through a synonym granted to the calling schema. As a view, it cannot be used as a DML target; all maintenance of attribute ranges must be performed against the base table PQH_ATTRIBUTE_RANGES.