Search Results pji_resource_availability

Overview

APPS.PJI_AVL_THRESHOLDS_V is a lightweight reporting view in Oracle EBS that exposes the numeric threshold boundaries used by the Project Resource Availability (PJI) subsystem. The view is defined entirely over the bucket configuration table PJI_MT_BUCKETS, filtering that table to a single bucket set identified by the code PJI_RESOURCE_AVAILABILITY. Its purpose is to present the upper boundary values that delimit availability buckets so that reports, concurrent programs, and integration layers can classify resource availability into discrete ranges without hard-coding limits.

In Oracle EBS reporting and integration, this view acts as a stable, read-only abstraction over what is otherwise a generic multi-purpose bucket table. Because PJI_MT_BUCKETS stores bucket definitions for several subsystems, exposing only the resource availability bucket set simplifies application access and insulates consuming code from changes to storage or from other bucket sets. This is consistent with the broader Oracle Applications pattern of providing narrow views that present a curated subset of a shared configuration table.

Underlying Base Objects

The view is defined with the following query text:

• SELECT seq, to_value FROM pji_mt_buckets WHERE bucket_set_code = 'PJI_RESOURCE_AVAILABILITY'

Accordingly, the single underlying base object is PJI_MT_BUCKETS, the bucket maintenance table that stores bucket set definitions, sequence numbers, and boundary values. The view performs a simple projection and filter: it selects the sequence and upper boundary columns while restricting rows to the resource availability bucket set. No joins, aggregations, or functions are applied, so the view is a direct, non-materialized window onto the base table.

No direct reference to a pji_resource_availability object is documented, but the search term aligns with the bucket set code value, indicating that users seeking resource availability configuration are routed to this view rather than to the base table. The ETRM metadata documents no additional referenced base objects, reinforcing that PJI_MT_BUCKETS is the sole data source.

Key Columns

• SEQ — The sequence number of the bucket within the PJI_RESOURCE_AVAILABILITY bucket set. It establishes the ordering of buckets and typically corresponds to ascending availability ranges.
• TO_VALUE — The upper boundary (threshold) value for the bucket. It defines where one availability bucket ends and the next begins, enabling classification of a measured availability percentage or quantity into the correct bucket.

Because the view exposes only these two columns, consumers rely on SEQ for ordering and TO_VALUE for range limits. The bucket set code itself is fixed by the view's WHERE clause and is therefore not projected.

Common Use Cases and Queries

The view is commonly queried to retrieve the ordered set of availability thresholds for display, validation, or downstream calculation. A typical retrieval is:

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

Typical scenarios include:

• Populating a lookup or list of values that offers resource availability bucket ranges in a user interface.
• Validating that configured thresholds are monotonic and free of gaps before availability processing runs.
• Feeding availability classification logic in custom reports that map a computed availability value to a bucket label using SEQ and TO_VALUE.
• Comparing configuration across environments by extracting the bucket definitions for audit or migration purposes.

Since the view is read-only and based on a single configuration table, it is safe for reporting use. Any change to thresholds must be made in the base table PJI_MT_BUCKETS; the view reflects those changes immediately without further maintenance.