Search Results pji_pjp_sum_main




Overview
Explore in AI Chat

Overview

PJI_PJP_SUM_MAIN is a core PL/SQL package in the Oracle EBS Project Intelligence (PJI) / Project Performance (PJP) subsystem, owned by the APPS schema and classified as OTHER in the documented API taxonomy. Its business purpose is to orchestrate the summarization and rollup of project performance data — accumulated cost, budget, and earned-value facts — that drive the Project Performance reporting structures in Oracle Projects. The package acts as the main entry point for the summarization engine: it manages process initialization, dispatches worker logic over the set of projects, tracks execution status, and handles wrap-up and failure recovery for both successful and failed concurrent runs. In effect, it coordinates the transformation of granular project transactions and budgets into the denormalized summary tables consumed by Project Intelligence dashboards and performance reporting.

Key Procedures and Functions

The package exposes seven documented procedures and functions. Each has a distinct role in the summarization lifecycle:

  • INIT_PROCESS — Initializes the summarization run, establishing the process context and allocating the working state required before project-level processing begins.
  • RUN_PROCESS — Main driver that executes the summarization logic across the qualifying project set.
  • WORKER_STATUS — Reports or tracks the status of parallel worker execution, enabling the driver to monitor progress across concurrent workers.
  • OUTPUT_FAILED_RUNS — Emits or records information about failed summarization runs for diagnostics and reprocessing.
  • WRAPUP_PROCESS — Performs normal end-of-run processing, committing the results of a successful summarization cycle.
  • WRAPUP_FAILURE — Handles cleanup and error-state resolution when a run terminates abnormally.
  • SUMMARIZE — Encapsulates the core summarization operation itself, invoked within the processing flow.

Tables Accessed

The package reads and writes documented tables via APPS synonyms, spanning concurrent manager, project setup, and summary structures. FND_APPLICATION, FND_CONCURRENT_PROGRAMS, and FND_CONCURRENT_REQUESTS are consulted to identify the concurrent program and its request context, supporting status reporting and failed-run output. Project definition data comes from PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_PROJECT_TYPES_ALL, and PA_BUDGET_VERSIONS, used to select which projects and budget versions qualify for summarization. Versioned project element data is read from PA_PROJ_ELEMENT_VERSIONS and PA_PROJ_ELEM_VER_STRUCTURE, while PA_PROJ_FP_OPTIONS and PA_PROJ_WORKPLAN_ATTR supply forecast/plan options and workplan attributes. Reporting structures come from PA_RBS_PRJ_ASSIGNMENTS and PA_RBS_VERSIONS_B. The event log PA_PJI_PROJ_EVENTS_LOG records processing events, and PA_XBS_DENORM holds the denormalized summary results that this package populates.

Usage Notes

PJI_PJP_SUM_MAIN is referenced by fourteen packages, including PA_RBS_MAPPING, PA_RLMI_RBS_MAP_PUB, PJI_FM_PLAN_MAINT and its private variant, PJI_FM_SUM_PSI, PJI_FM_XBS_ACCUM_UTILS, PJI_PJP_EXTRACTION_UTILS, PJI_PJP_SUM_CUST, PJI_PJP_SUM_DENORM, PJI_PJP_SUM_MAIN itself, PJI_PJP_SUM_ROLLUP, and PJI_PROCESS_UTIL, indicating it sits centrally in the PJI summarization dependency graph. It is typically invoked through the Project Performance / Project Intelligence concurrent programs rather than directly from a form. In both EBS 12.1.1 and 12.2.2 the object is VALID in APPS. Administration involves diagnosing failures through OUTPUT_FAILED_RUNS and WORKER_STATUS, then resubmitting the concurrent program. Custom code should not call this package directly; extensions should be implemented through the documented customer-facing hooks such as PJI_PJP_SUM_CUST to preserve upgrade safety.