Search Results p_organization

Overview

PJI_PMV_AVL is a PL/SQL package that belongs to the Oracle Projects suite of applications (the "PJI" prefix denotes Projects Intelligence/Projects reporting components). Its name reflects its role as a PMV (Page Metadata View) Availability repository — "PMV" is the Oracle Business Intelligence System (BIS) framework that powers Oracle Daily Business Intelligence and embedded analytics pages. The package supplies the SQL definitions and PL/SQL data drivers required to render Availability-related analytics pages within Oracle Projects. The header comment ($Header: PJIRR01S.pls 120.1 2005/05/31 08:18:27 appldev $) indicates the source file is PJIRR01S.pls and that the package has been stable since the 11i/12.0 era, and it is carried forward unchanged into 12.1.1 and 12.2.2.

The package is classified in ETRM as an "OTHER" API, meaning it is not a formal public interface but an internal reporting utility invoked by the BIS/PMV runtime engine. The user search term "media pending anporvool" appears to be a corrupted form of a common reporting query such as "media pending approval," which is one of the availability views the RA-series reports expose.

Key Procedures and Functions

The package exposes two parallel groups of entry points, consistent with the BIS PMV architecture in which each analytics page requires both a SQL generator (Get_SQL) and a PL/SQL data provider (PLSQLDriver).

• Get_SQL_PJI_REP_RA1 through Get_SQL_PJI_REP_RA5 — Five procedures that each build and return the dynamic SQL text for one Availability report page (RA1, RA2, RA3, RA4, RA5). They accept a page parameter table (BIS_PMV_PAGE_PARAMETER_TBL) and return both the SQL string and a query-attribute collection (BIS_QUERY_ATTRIBUTES_TBL) that describes the result columns to the PMV engine.
• PLSQLDriver_RA1 through PLSQLDriver_RA5 — Corresponding functions that execute the report logic and return strongly typed PL/SQL collections (PJI_REP_RA1_TBL ... PJI_REP_RA5_TBL). Their parameters consistently include operating unit, organization, threshold, as-of date, and view-by, with RA1 and RA3/RA4 additionally accepting a period type and RA3 accepting an availability type. These parameters drive the filter criteria and grouping displayed on the Availability dashboard pages.

Together the five report variants cover different views of resource/project availability — for example available capacity, committed versus uncommitted effort, and period-based versus as-of-date snapshots.

Tables Accessed

The ETRM metadata records no directly referenced tables for this package, because the SQL is generated dynamically and the base tables are resolved at runtime through APPS synonyms. Based on the Availability subject area, the underlying queries draw on Oracle Projects and Oracle HRMS objects such as project and resource assignment tables, organization and operating unit definitions, and availability/assignment fact tables. The package itself is a metadata and driver layer and does not own persistent data.

Usage Notes

PJI_PMV_AVL is not intended to be called directly by end users or custom code. It is invoked by the BIS PMV runtime when a user opens an Availability analytics page or a Dashboard region that references reports RA1–RA5. The PMV framework first calls the relevant Get_SQL_* procedure to obtain the page SQL, then calls the matching PLSQLDriver_* function to populate the page. Because the package is designated "OTHER" and is referenced by zero other packages, it should be treated as an internal reporting object. Customizations are discouraged; upgrades from 12.1.1 to 12.2.2 may overwrite the package body.