Search Results rbs_push




Overview
Explore in AI Chat

Overview

PA_PPR_CONCURRENT_PROGRAM is an Oracle Projects package body in the APPS schema that supports the Project Performance Reporting (PPR) and Resource Breakdown Structure (RBS) processing framework within Oracle E-Business Suite. Its primary business function is to stage, transform, and publish project performance data so that summary amounts and RBS-based dimensional attributes are available to the Project Performance Reporting and related Project Intelligence reporting layers. The package orchestrates concurrent-style batch processing that aggregates financial transaction amounts, denormalizes RBS assignments and versions, and generates project events that downstream reporting and event-handling mechanisms consume. The "RBS push" search frequently associated with this object refers to the logic that pushes RBS header and version information into staging and aggregation structures via the PROCESS_RBS_DENORM, MAP_RBS_HEADERS, and PROCESS_RBS_CHANGES routines. The header comment identifies the source file as PAPPR01B.pls, with a version string referencing the 120.0.12020000.2 release line, consistent with Oracle EBS 12.1.1 and 12.2.2 deployments.

Key Procedures and Functions

The package exposes nine documented procedures that together form the PPR batch pipeline:

  • SUMMARIZE — Drives the summarization of project performance data, consolidating transactional detail into summary-level records used for reporting.
  • RUN_PROCESS — Acts as the main entry point that sequences the PPR processing steps for a given run.
  • PROCESS_RBS_DENORM — Denormalizes RBS data, flattening RBS element and version relationships so that reporting queries do not require repeated hierarchical joins.
  • POPULATE_FIN8 — Populates the FIN8 aggregation structures used as the source for performance data.
  • MAP_RBS_HEADERS — Establishes the mapping between RBS headers and the project or reporting keys they apply to.
  • CREATE_MAPPING_RULES — Generates mapping rules that govern how RBS values translate into reporting dimensions.
  • PROCESS_RBS_CHANGES — Detects and applies changes to RBS assignments and versions so that downstream data remains synchronized with the current RBS configuration.
  • CREATE_EVENTS — Creates project events that signal downstream consumers of PPR and RBS state changes.
  • PPR_LOG — Provides an internal logging hook; in the documented body the routine is effectively a no-op that performs no database writes.

Tables Accessed

The package reads and writes a set of Project Costing, Project Foundation, and RBS tables through APPS synonyms. PA_PROJECTS_ALL and PA_PROJECT_TYPES_ALL supply project and project-type context. PA_RBS_ELEMENTS, PA_RBS_PRJ_ASSIGNMENTS, and PA_RBS_VERSIONS_B hold the RBS definitions, project-to-RBS assignments, and RBS versions that the denormalization and mapping routines process. PA_PROJ_FP_OPTIONS, PA_FIN_PLAN_TYPES_B, and PA_BUDGET_VERSIONS provide financial plan and budget-version configuration. PJI_FM_AGGR_FIN7 is the aggregation source used by the merge logic (for example, merge_into_fp_txn_accum) to feed PJI_FP_TXN_ACCUM. PA_PJT_PROJ_BATCH, PA_PJT_EVENTS, PA_PJT_EVENTS_02, and PA_PJI_PROJ_EVENTS_LOG support batch and event processing. PA_PPR_OBJ_TMP and PA_PPR_OBJ_TMP2 serve as temporary staging objects for PPR processing.

Usage Notes

PA_PPR_CONCURRENT_PROGRAM is normally invoked from concurrent programs and batch jobs registered in Oracle Projects, and it is referenced by one other package in the environment. Administrators typically schedule it as part of the Project Performance Reporting and RBS maintenance cycle, particularly when RBS assignments or versions change and the denormalized reporting structures must be refreshed. Because several routines rely on staging tables and event creation, the package should be run in a controlled batch window. Custom code that calls RUN_PROCESS or the RBS-specific procedures must account for the sequencing requirements, as POPULATE_FIN8 and MAP_RBS_HEADERS are expected to precede the denormalization and change-processing steps. The disabled PPR_LOG implementation means that diagnostic output is not persisted by default, so DBMS_OUTPUT or external logging should be used for troubleshooting in either 12.1.1 or 12.2.2.