Results for “update_activity_dates_fin”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PJI_FM_SUM_BKLG is a PL/SQL package body belonging to the Oracle EBS Project Intelligence (PJI) product family. Its documented API classification is OTHER, indicating that it is an internal implementation package rather than a published extension API. Consistent with its name, the package supports the summarization of financial backlog data for projects, operating within the batch-oriented processing framework used by Project Intelligence to stage, aggregate, and reconcile financial project data.

The package participates in the worker-based processing architecture that PJI uses to parallelize large data volumes. Procedures accept a worker identifier, register progress and completion through PJI_PROCESS_UTIL, and write results into intermediate and final map tables. The header comment identifies the source file as PJISF12B.pls, with a revision date of November 2005, placing the object within the long-standing PJI summarization code base carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents seven procedures or functions within this package body:

• ROWID_ACTIVITY_DATES_FIN — Computes minimum activity dates and aggregated revenue for financial data. The documented excerpt shows it inserting into PJI_FM_RMAP_FIN using an append hint, joining the project batch map to the PJI_FM_AGGR_FIN9 aggregation table and grouping by row identifier and project identifier. It uses PJI_PROCESS_UTIL.NEED_TO_RUN_STEP to enforce idempotent, restartable execution and REGISTER_STEP_COMPLETION to mark progress, followed by a commit.
• UPDATE_ACTIVITY_DATES_FIN — Applies the computed financial activity dates, updating previously established date values in the target structures.
• ROWID_ACTIVITY_DATES_ACT — The actuals counterpart to the financial routine, deriving minimum activity dates for actual cost transactions and staging them for subsequent update.
• UPDATE_ACTIVITY_DATES_ACT — Applies the computed actual activity dates.
• SCOPE_PROJECTS_BKLG — Determines the set of projects eligible for backlog processing within the current batch, establishing the working scope for downstream summarization steps.
• CLEANUP_INT_TABLE — Removes residual rows from intermediate processing tables, preventing stale data from contaminating subsequent batch runs.
• PROCESS_DRMT_BKLG — Serves as the driver routine for the backlog summarization flow, orchestrating the scoping, date derivation, update, and cleanup steps.

Tables Accessed

The documented reference list identifies PJI_SYSTEM_SETTINGS as a table accessed through APPS synonyms. This table supplies system-level configuration values that govern processing behavior, such as batch sizing and feature enablement. In addition to the documented table, the visible source excerpt confirms operations against PJI_FM_RMAP_FIN (the financial row map target) and PJI_FM_AGGR_FIN9 (the financial aggregation source), joined with the batch map table pji_pji_proj_batch_map. These operations insert and select by worker identifier, reinforcing the parallel worker design.

Usage Notes

This package is not a public API and should not be invoked directly from custom code. It is driven by the PJI summarization concurrent programs and batch framework, which assign worker identifiers and coordinate execution across parallel workers. External integrations with Project Intelligence should use supported public APIs rather than this internal package. Because execution depends on PJI_PROCESS_UTIL step registration, interrupting a run may leave step state that must be cleared before reprocessing; the CLEANUP_INT_TABLE procedure exists to support such recovery. The object is referenced by zero other packages, confirming that it sits at the outer edge of the dependency graph as a driver of backlog summarization rather than a shared utility.