Search Results pa_ppr_concurrent_program




Overview
Explore in AI Chat

Overview

PA_PPR_CONCURRENT_PROGRAM is an Oracle Projects PL/SQL package owned by APPS that supports the Project Performance Reporting (PPR) infrastructure within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to populate and refresh the reporting structures used by Project Performance Reporting, where project data is aggregated against a Reporting Breakdown Structure (RBS) and staged for downstream reporting and analytics. The package is declared AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the definer, which is relevant when the package is called from concurrent programs, forms, or other PL/SQL units operating in the APPS schema context.

The package coordinates a multi-step, batch-driven process. It accepts project and RBS parameters, denormalizes RBS information for performance, maps RBS headers against project versions, generates mapping rules and events, and produces the summarized output that Project Performance Reporting consumes. The header comment and internal declarations indicate it is intended primarily as a concurrent-program entry point rather than a general-purpose API.

Key Procedures and Functions

  • SUMMARIZE — The primary concurrent-program entry point. It returns standard concurrent program errbuf and retcode outputs and drives the summarization run based on a run mode plus optional operating unit, project range, RBS header, and transaction type filters.
  • RUN_PROCESS — The worker procedure invoked per batch to execute the processing cycle for a given worker and calling mode.
  • PROCESS_RBS_DENORM — Denormalizes RBS data, supporting the flattened structure the summarization logic relies upon.
  • POPULATE_FIN8 — Populates the FIN8 financial aggregate structure. This is the procedure most relevant to searches for "populate_fin8," and it is referenced in the ETRM metadata as a documented procedure of the package. It operates on behalf of a worker and project and is controlled by a calling mode.
  • MAP_RBS_HEADERS — Maps RBS headers to project versions and records the mapping, taking a worker, project, RBS version, and event type.
  • CREATE_MAPPING_RULES — Creates the mapping rules that associate projects with their RBS structures. The source notes indicate this API need not be called for every project, so it is typically invoked selectively.
  • PROCESS_RBS_CHANGES — Handles incremental changes to RBS assignments, allowing the reporting structures to stay synchronized without full reprocessing.
  • CREATE_EVENTS — Generates project events used to drive downstream processing and tracking.
  • PPR_LOG — A logging utility that records diagnostic messages during execution.

Tables Accessed

The package reads and writes a defined set of Project Performance Reporting tables through APPS synonyms. Project and configuration data are drawn from PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_PROJ_FP_OPTIONS. Budget and plan information comes from PA_BUDGET_VERSIONS and PA_FIN_PLAN_TYPES_B. The RBS structure is represented by PA_RBS_ELEMENTS, PA_RBS_PRJ_ASSIGNMENTS, and PA_RBS_VERSIONS_B. Change and event tracking uses PA_PJT_EVENTS, PA_PJT_EVENTS_02, PA_PJI_PROJ_EVENTS_LOG, and PA_PJT_PROJ_BATCH. Temporary processing objects are held in PA_PPR_OBJ_TMP and PA_PPR_OBJ_TMP2, and the aggregated financial result set is PJI_FM_AGGR_FIN7 (with FIN8 associated with the POPULATE_FIN8 procedure).

Usage Notes

This package is normally invoked through a concurrent program rather than called directly. The SUMMARIZE procedure exposes the standard errbuf/retcode signature required by concurrent managers, and the internal worker procedures (RUN_PROCESS, POPULATE_FIN8, MAP_RBS_HEADERS, CREATE_EVENTS, and PROCESS_RBS_CHANGES) form the processing chain executed by that request. Parameters such as run mode, operating unit, project range, RBS header, and transaction type allow the run to be scoped to a specific set of projects or a single reporting structure.

Because the package executes as the current user, custom callers must ensure the invoking schema has the necessary grants on the referenced PA and PJI tables. The ETRM metadata indicates the package is referenced by one other package, suggesting some internal dependency within the Project Performance Reporting flow. When troubleshooting, PPR_LOG output and the event/batch tables (PA_PJT_PROJ_BATCH, PA_PJI_PROJ_EVENTS_LOG) provide the primary diagnostic trail. The source header dates the package to release 12.2.0, confirming compatibility with EBS 12.1.1 and 12.2.2 environments.