Search Results merge_overview_type




Overview
Explore in AI Chat

Overview

PJI_REP_MEASURE_UTIL is a utility package in the Oracle EBS Project Management (PJI) module that supports the reporting layer of Project Performance Reporting and the Measure Tracking framework. Its principal business function is to resolve, format, and return the values of project performance measures — both financial and activity-based — for presentation in reporting tools such as the Project Performance Reporting (PPR) pages and related dashboards. The package serves as the bridge between stored measure definitions (measure codes, sets, and identifiers) and the computed measure values consumed by reporting UIs and concurrent processes.

The package header carries a $Header string of 120.4 dated 2006, indicating it is a long-standing, mature component that has remained largely stable across the 12.1.1 and 12.2.2 releases. Its API classification is UTIL, consistent with its role as a shared technical service invoked by other packages rather than a self-contained business process. The metadata notes that it is referenced by one other package, confirming its utility-call nature.

Key Procedures and Functions

The documented interface exposes eleven procedures and functions:

  • COMPUTE_PROJ_PERF_EXCEPTIONS — Evaluates project performance exceptions, identifying measures that fall outside expected thresholds and returning status and message information to the caller.
  • GET_MEASURE_LABELS — Accepts a collection of measure codes and returns the corresponding display labels, enabling the UI to render human-readable measure names.
  • GET_MEASURE_ATTRIBUTES — Returns the structural attributes of supplied measure codes, including associated measure set codes, time slices, and internal measure IDs.
  • GET_FINANCIAL_MEASURES — Retrieves computed financial measure values for a given project, along with exception indicators, based on measure codes, measure sets, time slices, and measure IDs.
  • GET_FORMATTED_MEASURES — Returns measure values in a formatted, presentation-ready state suitable for direct display.
  • GET_ACTIVITY_MEASURES — Retrieves activity-oriented measure values for a project, following the same parameter pattern as the financial variant.
  • GET_PLAN_TYPE_INFO — Supplies information about financial plan types used in measure calculation.
  • PREPAREDATA — Prepares or stages the data required for measure computation and reporting.
  • RETRIEVEDATA — Reads staged data and returns it to the requesting process.
  • MERGE_OVERVIEW_TYPE — Consolidates or merges overview-type records for reporting aggregation.
  • GET_FINANCIAL_MEASURES_WRP — A wrapper around GET_FINANCIAL_MEASURES, likely providing a simplified or alternate calling convention.

Tables Accessed

The package reads and writes through APPS synonyms. Measure definitions are sourced from PJI_MT_MEASURES_B and PJI_MT_MEASURE_SETS_B. Project context is drawn from PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_BUDGET_VERSIONS, PA_FIN_PLAN_TYPES_B, PA_PERCENT_COMPLETES, PA_PROJ_ELEM_VER_SCHEDULE, and PA_IMPLEMENTATIONS_ALL. Reporting structure and time-slice logic rely on PJI_TIME_RPT_STRUCT and PJI_TIME_CAL_RPT_STRUCT. Temporary and staging objects include PA_PERF_TEMP_OBJ_MEASURE and PJI_REP_XTD_MEASURES_TMP, used to hold intermediate computations and extended measure output. DUAL and PLITBLM are used for scalar evaluation and PL/SQL table operations respectively.

Usage Notes

PJI_REP_MEASURE_UTIL is typically invoked indirectly. The Project Performance Reporting pages in the E-Business Suite call the measure retrieval routines to populate performance tables and graphs, while concurrent programs that precompute project performance data invoke COMPUTE_PROJ_PERF_EXCEPTIONS and the data preparation routines. Because the package exposes collection-based parameters using SYSTEM.PA_*_TBL_TYPE types, custom code integrating with it must declare and populate these standard PA collection types. The presence of NOCOPY OUT parameters indicates the API is designed for performance in high-volume reporting calls. Direct calls are generally reserved for extensions and diagnostics; standard usage flows through Oracle-delivered reporting components.