Search Results wrapup_setup

Overview

PJI_FM_SUM_MAIN is a PL/SQL package owned by the APPS schema that forms part of the Oracle Project Portfolio Management (PPM) forecasting and summarization infrastructure. In Oracle EBS 12.1.1 and 12.2.2, this package is a core control module within the Project Intelligence and forecasting engine. It is responsible for orchestrating the summarization and extraction of project forecast data — reconciling forecast records, monitoring batch processing state, and deriving summary tables used by downstream reporting and analysis. Its classification as an "OTHER" API indicates that it is not a published public interface but an internal engine package called by other PJI packages rather than by external custom code.

The package's role places it at the centre of a dependency cluster. It is referenced by nine sibling packages — including PJI_EXTRACTION_UTIL, PJI_FM_EXTR, PJI_FM_SUM_ACT, PJI_FM_SUM_EXTR, PJI_FM_SUM_PSI, PJI_FM_CMT_EXTR, PJI_PJI_EXTRACTION_UTILS, PJI_PROCESS_UTIL, and PJI_FM_DEBUG — and it in turn depends on SYS.STANDARD only at the SQL level. This confirms it as a coordinator rather than an isolated utility.

Key Procedures and Functions

The ETRM metadata documents 13 procedures and functions, described below.

• RUN_SETUP — Establishes the setup context required before a summarization run begins, initialising control records and run state.
• INIT_PROCESS — Initialises an individual processing iteration within the summarization cycle.
• RUN_PROCESS — Executes the main processing logic for the current run.
• PRIOR_ITERATION_SUCCESSFUL — Evaluates whether the preceding iteration completed successfully, guarding against resuming from an inconsistent state.
• PROCESS_RUNNING — Determines whether a processing run is currently active, preventing concurrent execution conflicts.
• SUMMARIZE — Performs the core summarization of forecast data, aggregating detail into summary form.
• MY_PAD — A utility routine, typically used to pad or format values during processing.
• GET_MISSING_TIME_HEADER and GET_MISSING_TIME_TEXT — Retrieve header and textual diagnostic information for missing time-related data detected during summarization.
• DANGLING_REPORT — Produces a report of dangling (orphaned) financial or forecast records identified during processing.
• WRAPUP_SETUP, WRAPUP_PROCESS, and WRAPUP_FAILURE — Close out a run, performing normal completion (setup and process) or failure handling respectively.

Tables Accessed

The package reads and writes a broad set of application tables via APPS synonyms.

• PJI_FM_SUM_MAIN-related staging and control: PJI_FM_PROJ_BATCH_MAP, PJI_PROJ_EXTR_STATUS, PJI_SYSTEM_CONFIG_HIST, PJI_SYSTEM_SETTINGS, PJI_ORG_EXTR_INFO, and PJI_XBS_DENORM — used to track batch mappings, extraction status, configuration, and denormalized extraction data.
• Dangling diagnostics: PJI_FM_DNGL_ACT and PJI_FM_DNGL_FIN — populated or read by DANGLING_REPORT.
• Project reference data: PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_TIME_CAL_NAME, and PA_XBS_DENORM — supplying project, status, element, and calendar context.
• Calendar setup: GL_PERIOD_TYPES — used to resolve period definitions during time-based summarization.

Usage Notes

PJI_FM_SUM_MAIN is an internal engine package invoked by the Project Intelligence forecast extraction and summarization processes, generally through concurrent programs rather than directly from Oracle Forms. Administrators trigger it indirectly by running forecast summarization and extraction concurrent requests; the procedures RUN_SETUP, RUN_PROCESS, SUMMARIZE, and WRAPUP_PROCESS form the expected call sequence. Because the procedures are undocumented as public APIs, custom code should avoid calling this package directly and should instead use the supported concurrent program or the higher-level PJI_PROCESS_UTIL interface.