Search Results stage1_extr

Overview

PJI_PROCESS_UTIL is a utility package owned by APPS and classified in Oracle ETRM as a UTIL API. It provides the shared control infrastructure used by the Oracle Project Intelligence (PJI) summarization and rollup processes. Its central responsibility is orchestration bookkeeping: determining whether a given processing step has run and succeeded, recording step completion, maintaining process parameters, and cleaning up transient tables once a process finishes successfully. The package is the internal engine behind the "wrapup_process" search term — the WRAPUP_PROCESS procedure is the routine that finalizes a summarization run by clearing the process log table of step status records after successful completion.

The package is heavily reused: ETRM records that it is referenced by 24 other packages. Rather than duplicating restart logic, retry logic, and batch cleanup in each PJI worker program, those programs delegate to PJI_PROCESS_UTIL. It is also the layer that abstracts concurrent request dependencies, allowing summarization and rollup steps to launch and wait on other concurrent programs.

Key Procedures and Functions

• SUMMARIZATION_STARTED — Returns a status value indicating whether summarization has already been initiated for a given stage (defaulting to the STAGE1_EXTR stage).
• NEED_TO_RUN_STEP — Returns FALSE when a process step did not previously run or failed during a prior process iteration, enabling idempotent and restartable execution.
• REGISTER_STEP_COMPLETION — Called by individual processing steps to update the process log table with a successful completion status for the given process and step.
• CHECK_STEP — Debugging utility. When not set to 'Y', steps can be executed without consulting PJI_SYSTEM_PRC_STATUS to determine whether they have already run.
• WRAPUP_PROCESS — Finalizes a process; if the process completed successfully, it cleans the step status records out of the process log table.
• ADD_STEPS, PRIOR_ITERATION_SUCCESSFUL, REFRESH_STEP_TABLE — Support the step table lifecycle, adding step definitions, evaluating the previous iteration outcome, and refreshing the working step table.
• GET_PROCESS_PARAMETER, SET_PROCESS_PARAMETER — Persist and retrieve process-level parameters across steps and runs.
• SLEEP, WAIT_FOR_STEP, WAIT_FOR_REQUEST, REQUEST_STATUS — Synchronization helpers used to poll concurrent request state and wait on dependent steps or requests.
• TRUNC_INT_TABLE, CLEAN_HELPER_BATCH_TABLE — Housekeeping routines that truncate internal tables and clear helper batch data.
• EXECUTE_ROLLUP_FPR_WBS, EXECUTE_ROLLUP_ACR_WBS, EXECUTE_ROLLUP_FPR_PRG, EXECUTE_ROLLUP_ACR_PRG — Execute financial and actual rollups at WBS and program level respectively.

Tables Accessed

The package reads and writes the PJI process and staging tables. PJI_MT_PRC_STEPS is the central step-definition and status table; PJI_BATCH_STATUS_420 holds batch progress. Aggregation and accumulation results are held in PJI_AC_AGGR_PJP1, PJI_FP_AGGR_PJP1, PJI_AC_XBS_ACCUM_F, and PJI_FP_XBS_ACCUM_F. Helper and mapping data is stored in PJI_HELPER_420, PJI_HELPER_BATCH_MAP, and PJI_PA_PROJ_EVENTS_LOG. The denormalized structures PJI_PA_XBS_DENORM_T, PA_XBS_DENORM, PA_PROJ_ELEMENTS, PA_PROJ_ELEM_VER_STRUCTURE, and PA_PROJ_WORKPLAN_ATTR supply project/WBS hierarchy and attribute context. FND_CONCURRENT_REQUESTS is queried to determine concurrent request status for the WAIT_FOR_REQUEST and REQUEST_STATUS routines.

Usage Notes

PJI_PROCESS_UTIL is an internal package rather than a public API; it is invoked from PJI concurrent programs and from the 24 dependent packages that perform summarization and rollup work. Typical lifecycle: a driver process calls SUMMARIZATION_STARTED, evaluates NEED_TO_RUN_STEP before each unit of work, registers success through REGISTER_STEP_COMPLETION, and finally calls WRAPUP_PROCESS to purge the step log. Steps that depend on other concurrent programs use WAIT_FOR_REQUEST or WAIT_FOR_STEP. Because signatures are not exposed in the ETRM metadata, custom code should call this package cautiously and only where the documented procedures are already used by Oracle's own PJI programs.