Search Results process_drmt_bklg




Overview
Explore in AI Chat

Overview

PJI_FM_SUM_BKLG is a PL/SQL package owned by the APPS schema in Oracle EBS Applications, classified as an OTHER API within the ETRM registry. Its documented purpose is to initiate and drive the calculation of key project-related backlog metrics for the Oracle Projects (PJI) summarization architecture. Specifically, the package supports the computation of Revenue at Risk, Dormant Backlog, Not Started Backlog, Lost Backlog, and Active Backlog. These figures are essential to project financial management, providing project managers and financial analysts with a categorized view of committed but unrealized revenue and associated risk exposure.

The package header (PJISF12S.pls, version 120.2, dated November 2005) declares an AUTHID CURRENT_USER package, meaning its SQL executes with the privileges of the invoking user rather than the definer. The header is intended to be called by the PJI Summarization Process, which orchestrates the broader population and refresh of project financial fact data. The core engine of the package inserts project day records into the partitioned temporary table PJI_FM_AGGR_ACT, which generates the majority of the required aggregation numbers. Those rows are subsequently merged back into the PJI_AC_PROJ_F fact table, making the results available to downstream reporting and analytics.

Key Procedures and Functions

  • ROWID_ACTIVITY_DATES_FIN — Processes activity date information for finalized (FIN) records using ROWID-based access, preparing the date ranges needed for backlog classification.
  • UPDATE_ACTIVITY_DATES_FIN — Applies updated activity dates to the finalized record set identified by the prior ROWID pass.
  • ROWID_ACTIVITY_DATES_ACT — The active-record analogue of the FIN procedure, identifying active project activity dates via ROWID for subsequent processing.
  • UPDATE_ACTIVITY_DATES_ACT — Updates activity dates for the active record set.
  • SCOPE_PROJECTS_BKLG — Determines the set of projects in scope for the backlog summarization run, establishing the population the remaining steps operate against.
  • CLEANUP_INT_TABLE — Removes intermediate/staging rows after processing, maintaining the integrity and performance of the temporary tables used during the run.
  • PROCESS_DRMT_BKLG — Executes the dormant backlog processing logic, generating the dormant backlog measure that flags projects with no recent activity.

All seven documented subprograms accept a worker ID parameter that supports parallel, multithreaded execution under the PJI Summarization Process.

Tables Accessed

The ETRM metadata documents a reference to PJI_SYSTEM_SETTINGS via an APPS synonym. This table supplies configuration and system-level parameters that govern summarization behavior, such as calendar and threshold settings. The package documentation also explicitly references PJI_FM_AGGR_ACT, the partitioned temporary aggregation table into which project day records are inserted, and PJI_AC_PROJ_F, the project financial fact table into which the aggregated rows are merged. These three objects form the read-and-write backbone of the backlog calculation.

Usage Notes

PJI_FM_SUM_BKLG is not invoked directly by end users. It is called by the PJI Summarization Process, the standard Oracle Projects concurrent program flow that recalculates project financial aggregates. Because the package header is AUTHID CURRENT_USER and the referenced ETRM record shows it is referenced by zero other packages, it is effectively a leaf-level implementation package driven by the summarization orchestrator.

Customizations should avoid direct calls unless mirroring the summarization sequence, since the procedures depend on a specific invocation order (scoping, ROWID processing, updates, processing, cleanup) and on the temporary aggregation table being properly staged. Any integration should respect that lifecycle to avoid corrupting the fact table merge.