Search Results pji_avl_thresholds_v

Overview

The view APPS.PJI_AVL_THRESHOLDS_V is a database object within the Oracle E-Business Suite Project Intelligence (PJI) module. As documented in the ETRM metadata, it is classified as an internal summarization view whose status is VALID. Its principal function is to expose the threshold definitions used by the resource availability summarization logic in Project Intelligence. In Oracle EBS 12.1.1 and 12.2.2, PJI provides analytical and reporting capabilities over project and resource data, and this view supports the bucketing mechanism that interprets availability measurements against configured thresholds.

The view does not present transactional project data. Instead, it delivers a compact, query-friendly projection of the threshold setup, allowing reporting components and internal summarization routines to retrieve threshold boundaries without parsing the complete bucket-set configuration. Because it is described as internal, it is primarily intended for consumption by seeded PJI code rather than as an end-user reporting surface, though it remains queryable by developers and administrators for diagnostic purposes.

Underlying Base Objects

The view is defined over a single base table, PJI_MT_BUCKETS. The defining SQL is minimal and is preserved verbatim in the ETRM metadata: the view selects SEQ and TO_VALUE from PJI_MT_BUCKETS and restricts the result set with the predicate WHERE BUCKET_SET_CODE = 'PJI_RESOURCE_AVAILABILITY'. The base table name, PJI_MT_BUCKETS, reflects its role as a multi-threshold bucket definition table, where threshold ranges are stored as ordered bucket entries identified by a bucket set code.

The ETRM metadata documents no additional referenced base objects, and the view text confirms that no joins, unions, or aggregation are applied. The view therefore acts as a filtered projection: it isolates the resource-availability bucket set from all other threshold sets that share the same underlying table. Because the filtering condition is hard-coded, the view always returns only those rows belonging to the PJI_RESOURCE_AVAILABILITY bucket set.

Key Columns

The view exposes a deliberately narrow column list, as documented under the ETRM columns section:

• SEQ — The sequence number of the threshold bucket within the resource-availability bucket set. It establishes the ordered position of each threshold boundary, which is essential for correctly interpreting the range into which a given availability value falls.
• TO_VALUE — The upper boundary value for the bucket identified by SEQ. Values below this boundary map into that bucket; the sequence of TO_VALUE entries defines the successive threshold intervals applied to availability measurements.

The ETRM metadata additionally lists the column names ID and VALUE in its columns section. These represent the documented column labels associated with the view metadata, while the view text itself confirms the exposed projection columns are SEQ and TO_VALUE. When querying, the columns returned are determined by the view definition text, which selects SEQ and TO_VALUE.

Common Use Cases and Queries

The dominant use case is retrieval of the ordered threshold buckets that govern resource availability summarization. PJI summarization logic consumes these boundaries to classify availability results, and reporting extensions may join them to availability measures to produce readable threshold labels or trend bands. A basic query to inspect the configuration is:

• SELECT seq, to_value FROM apps.pji_avl_thresholds_v ORDER BY seq;

A typical integration pattern joins the view to a resource-availability result set on a ranged condition, assigning each measurement to the bucket whose TO_VALUE first exceeds it:

• SELECT a.resource_id, a.availability_value, t.seq AS bucket_seq, t.to_value FROM pji_availability_result a, apps.pji_avl_thresholds_v t WHERE a.availability_value <= t.to_value ORDER BY a.resource_id, t.seq;

Administrators may also use the view during validation to confirm that the resource-availability bucket set is populated and correctly ordered. Because the view is internal and filters on a fixed bucket set code, it is not intended as a generic threshold browser; other bucket-set codes must be queried directly from PJI_MT_BUCKETS. In both 12.1.1 and 12.2.2 the definition and usage remain consistent, as the ETRM 12.2.2 metadata documents no divergence from the view text.