Search Results bucket_set_code

Overview

PJI_AVL_DAYS_V is a lightweight internal summarization view within the Oracle E-Business Suite Project Intelligence (PJI) module. Project Intelligence was Oracle's earlier analytical and reporting layer for project data, and much of its functionality was subsequently folded into later project reporting and analytics tools. In the ETRM reference for 12.1.1 and 12.2.2, this view is explicitly marked as obsolete and, more importantly, is documented as not implemented in this database. The view therefore carries no runtime footprint in a standard EBS instance; it exists only as documentation of a historical code artifact.

Functionally, the view provides a code/value lookup list describing availability-day buckets. The name "AVL_DAYS" indicates that the rows represent categories of resource availability expressed in days, and the view exposes them in a two-column ID/VALUE shape suitable for list-of-values rendering, flexfield validation, or join lookups within PJI reporting logic. It does not aggregate transactional data despite being described as a summarization view; the summarization is conceptual, collapsing a configured bucket set into a simple picklist.

Underlying Base Objects

The view text is a single-table selection over PJI_MT_BUCKETS, the PJI bucket-set maintenance table. The definition filters that table to a single bucket set:

• Base table: PJI_MT_BUCKETS — stores bucket definitions grouped by bucket set code.
• Filter predicate: BUCKET_SET_CODE = 'PJI_RES_AVL_DAYS' — restricts output to the resource availability-days bucket set.
• Column mapping: SEQ is aliased as ID, and NAME is aliased as VALUE, normalizing the output to a conventional key/description pair.

No views, synonyms, or external tables are referenced. The ETRM 12.2.2 metadata lists no owner and no referenced base objects, consistent with the view being non-implemented. For a browser-specific query, the user searching on bucket_set_code should understand that the string literal 'PJI_RES_AVL_DAYS' is hard-coded here, and that the logical key of interest in the base table is the BUCKET_SET_CODE column rather than a column surfaced by the view itself. Selecting from the view does not expose BUCKET_SET_CODE.

Key Columns

• ID — Derived from PJI_MT_BUCKETS.SEQ. A numeric sequence value identifying the bucket position or ordering of the availability-days bucket.
• VALUE — Derived from PJI_MT_BUCKETS.NAME. The display name or label of the bucket, for example a descriptive availability-days range.

The view deliberately hides the bucket set code and other administrative columns such as creation and update audit fields, presenting only the minimal key/value contract expected by lookup consumers.

Common Use Cases and Queries

Because the view is obsolete and not implemented, it should not be referenced in new customizations or extensions on 12.1.1 or 12.2.2. The recommended substitute is a direct query against the base table, which also permits inspection of the bucket set code that the original view suppressed. A representative query is:

SELECT seq, name, bucket_set_code FROM pji_mt_buckets WHERE bucket_set_code = 'PJI_RES_AVL_DAYS' ORDER BY seq;

Where legacy code still references the view, a functionally equivalent reconstruction is:

SELECT seq AS id, name AS value FROM pji_mt_buckets WHERE bucket_set_code = 'PJI_RES_AVL_DAYS' ORDER BY seq;

Typical historical uses included populating a bucket picklist in a PJI availability report, driving LOV validation for a parameter, and joining bucket identifiers to project resource availability facts. In all of these scenarios the modern approach is to resolve the bucket set through PJI_MT_BUCKETS directly, filter on BUCKET_SET_CODE in a WHERE clause so the predicate remains tunable, and avoid depending on an obsolete PJI view that no longer exists in supported EBS environments. Any conversion effort should also confirm whether the equivalent data has migrated to a successor project analytics schema.