Search Results act_summary

Overview

APPS.PJI_FM_SUM_EXTR is a PL/SQL package in the Oracle E-Business Suite Projects (PJI) schema that supports the extract, summarization, and aggregation of project financial and resource data for Oracle Project Management and Oracle Project Resource Management reporting. Its primary business function is to consolidate detail-level financial and activity transactions into summary staging tables (the PJI_FM_AGGR_FIN and PJI_FM_AGGR_ACT families) and to load the resource aggregation table PJI_RM_AGGR_RES6, which feeds downstream Project Intelligence and Project Management reporting extracts. The package also manages the lifecycle of batch workers, handles currency conversion for aggregated amounts, identifies and purges "dangling" financial and activity rows, and populates the time dimension used by the extract process.

The package is classified as OTHER (an internal, non-public API). It is not a user-facing API and is intended to be invoked by the surrounding PJI extract framework rather than by external customizations. In the dependency chain, PJI_FM_SUM_EXTR references only SYS.STANDARD directly, while it is referenced by PJI_FM_CMT_EXTR, PJI_FM_EXTR, PJI_FM_SUM_MAIN, and by itself (recursive worker processing). The package is marked VALID in the APPS schema.

Key Procedures and Functions

Twenty-two documented procedures and functions are exposed. They fall into several functional groups:

• Worker orchestration: START_HELPER, WAIT_FOR_WORKER, WORKER_STATUS, FORCE_SUBSEQUENT_RUN, CLEANUP_WORKER, and WRAPUP_FAILURE manage the parallel worker model that drives the extract. START_HELPER spawns worker processes; WAIT_FOR_WORKER and WORKER_STATUS coordinate and monitor them; FORCE_SUBSEQUENT_RUN controls pipeline sequencing; CLEANUP_WORKER and WRAPUP_FAILURE perform teardown and error handling.
• Dimension and conversion support: POPULATE_TIME_DIMENSION loads time-dimension data required for aggregation, and CURR_CONV_TABLE builds the currency conversion table used to translate monetary amounts into reporting currency.
• Dangling-row management: DANGLING_FIN_ROWS and DANGLING_ACT_ROWS identify orphaned financial and activity rows; MOVE_DANGLING_FIN_ROWS and MOVE_DANGLING_ACT_ROWS relocate them; PURGE_DANGLING_FIN_ROWS and PURGE_DANGLING_ACT_ROWS remove them from the staging area.
• Summary and aggregation: FIN_SUMMARY and ACT_SUMMARY produce summarized financial and activity output; AGGREGATE_FIN_SLICES, AGGREGATE_ACT_SLICES, and AGGREGATE_RES_SLICES aggregate data across the defined slices for financial, activity, and resource domains respectively.
• Supporting metadata: ORG_EXTR_INFO_TABLE supplies organizational extract context used during processing.

No parameter signatures are exposed in the metadata, and none are asserted here.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. Aggregation output targets include PJI_FM_AGGR_ACT1, PJI_FM_AGGR_ACT2, PJI_FM_AGGR_FIN1, PJI_FM_AGGR_FIN2, and PJI_RM_AGGR_RES6, which store summarized activity, financial, and resource results respectively. PJI_FM_AGGR_DLY_RATES supplies daily currency conversion rates consumed by the conversion logic. PJI_FM_DNGL_ACT and PJI_FM_DNGL_FIN hold dangling activity and financial rows that are identified, moved, or purged by the corresponding procedures. PJI_FM_PROJ_BATCH_MAP maps projects to batches, supporting worker distribution. PJI_ORG_EXTR_INFO provides organizational extract parameters, PJI_SYSTEM_SETTINGS supplies system-level configuration and control flags, and DUAL is used for single-row procedural evaluations.

Usage Notes

PJI_FM_SUM_EXTR is an internal component of the PJI extract framework and is invoked indirectly rather than through direct user interaction. Its most common entry point is through the parent packages PJI_FM_EXTR and PJI_FM_SUM_MAIN, which orchestrate the overall financial management extract and summary runs, typically launched from Oracle Projects concurrent programs. PJI_FM_CMT_EXTR (the commitment extract) also invokes it, reflecting the shared summarization infrastructure across financial and commitment extracts. Because the package is classified OTHER and is not a published API, custom code should not call its procedures directly; the supported approach is to trigger the associated concurrent programs. Administrators troubleshooting extract performance or dangling-row errors should examine the worker orchestration and dangling-row procedures, and the result tables listed above are the appropriate place to verify extract output.