Search Results base_summary

Overview

The APPS.PJI_FM_SUM_ACT package belongs to the Oracle Projects family of PL/SQL utilities that support the Project Financial Management (PJI) summarization and aggregation architecture. Its principal business purpose is to build and maintain the summarized actual cost and financial balances used by Oracle Projects reporting, inquiries, and downstream integrations. In Oracle E-Business Suite 12.1.1 and 12.2.2, Project Management and Project Costing rely on aggregated tables rather than querying raw transaction and expenditure extracts directly, because the volume of source data (expenditures, supplier invoices, requisitions, funding records) is far too large for interactive querying.

The package carries the AUTHID CURRENT_USER directive, meaning it executes with the privileges of the invoking schema rather than the definer. Its header stamp ($Header: PJISF08S.pls 120.1 ...) indicates it originated as a Projects summarization script and was formally packaged. ETRM classifies the API as OTHER, distinguishing it from a public, externally supported API. The package is not intended for direct customer invocation.

Key Procedures and Functions

ETRM documents exactly two procedures in the package specification:

• BASE_SUMMARY — The core worker routine. It performs the base-level summarization of actual project transactions, consolidating detail rows from the extract and aggregation tables into summarized actual balances. It accepts a worker identifier parameter that lets the summarization framework isolate concurrent batch runs and tag the rows it processes.
• CLEANUP — The companion housekeeping routine. It removes residual or staging data associated with a completed summarization run, using the same worker identifier to identify the rows that belong to that run. It is normally called after BASE_SUMMARY has finished.

No public functions are declared; the specification exposes only these two procedures. Neither is documented with an argument list in the ETRM excerpt beyond the worker identifier, and no parameter details should be assumed beyond that.

Tables Accessed

The package operates against seven documented tables accessed by APPS synonyms:

• Aggregation targets: PJI_FM_AGGR_ACT1 and PJI_FM_AGGR_FIN1 store the summarized actual and financial aggregate results produced by the summarization process.
• Extract sources: PJI_FM_EXTR_ARINV (Oracle Receivables invoices), PJI_FM_EXTR_DINVC and PJI_FM_EXTR_DINVCITM (distributed supplier invoice headers and lines), PJI_FM_EXTR_DREVN (revenue extracts), and PJI_FM_EXTR_FUNDG (funding extracts).

These PJI_FM_EXTR_* tables represent the staged, pre-processed view of external subledger data that Projects reads when computing actual cost and revenue. BASE_SUMMARY reads them to populate the aggregate tables; CLEANUP deletes staging rows keyed by the worker identifier.

Usage Notes

PJI_FM_SUM_ACT is an internal engine component. It is not exposed in Oracle Projects forms for direct user execution and is not documented as a supported extension point. Typical invocation is indirect, through the Projects concurrent programs and internal orchestrators that perform financial summarization for a project or set of projects, or through wrapper packages — ETRM records that this package is referenced by one other package. Because BASE_SUMMARY and CLEANUP operate on shared staging and aggregate tables, they must be run in the correct sequence for the same worker identifier and must not be launched concurrently for overlapping data sets. Custom code should call the supported Projects summarization entry points rather than invoking these procedures directly, since the package is AUTHID CURRENT_USER and depends on APPS synonyms being visible to the calling schema.