Results for “shutdown_process”

8 results




Overview
Explore in AI Chat

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

Overview

APPS.PJI_RM_SUM_MAIN is the controlling package body behind the Project Intelligence (PJI) resource management summarization and data extraction process in Oracle E-Business Suite. Its header identifies revision 120.15 (PJISR01B.pls, dated 2006/03/23), and it is classified in ETRM as an OTHER-type API owned by APPS. The package orchestrates the extraction and summarization of project resource information, exposing its main entry point through the SUMMARIZE procedure, which is invoked from a concurrent program.

Functionally, the package implements a resumable, multi-step batch pipeline. Extraction is decomposed into discrete steps that are coded as individual program units; RUN_PROCESS invokes these steps in the required order, while INIT_PROCESS initializes the run and WRAPUP_PROCESS resets process status after a successful completion. Because each processing step executes as a separate database transaction, the process supports error recovery: if a run fails, the next execution resumes from the same step rather than restarting from the beginning. Process state and parameters (such as the batch identifier being processed) are persisted through the status tables PJI_SYSTEM_PROCESS_STATUS and PJI_SYSTEM_PARAMETERS, accessed via the API package PJI_PROCESS_UTIL. The scope of extraction is defined by PJI_ORG_EXTR_STATUS, with a snapshot held in PJI_RM_ORG_BATCH_MAP to isolate a given run from concurrent extraction programs and to partition the scope into batches.

Key Procedures and Functions

The documented program units serve the following purposes:

  • SUMMARIZE — the main procedure; called by the concurrent program and serves as the external entry point that drives the summarization run.
  • INIT_PROCESS — initializes the process before RUN_PROCESS is called.
  • RUN_PROCESS — invokes the individual processing steps in the appropriate sequence; each step is a separate transaction.
  • PROCESS_RUNNING — checks or reports whether the extraction/summarization process is currently running, supporting the determination of process state.
  • PRIOR_ITERATION_SUCCESSFUL — evaluates whether the preceding iteration completed successfully, enabling restart and error-recovery logic.
  • WRAPUP_PROCESS — resets process status after a process completes successfully.
  • WRAPUP_FAILURE — handles the wrap-up path when the process fails, recording or resetting status accordingly.
  • SHUTDOWN_PROCESS — performs shutdown and cleanup logic for the process (allowing an orderly stop).
  • GET_MISSING_TIME_HEADER — retrieval of missing time header information used during summarization.
  • GET_MISSING_TIME_TEXT — retrieval of the corresponding missing time text information.
  • DANGLING_REPORT — generates or manages reporting for dangling (unmatched) records identified during processing.
  • MY_PAD — a utility/helper function used internally for formatting or padding values.

Tables Accessed

The package references the following tables through APPS synonyms:

  • PA_PROJECTS_ALL — the base project definition table, read to obtain project information relevant to resource extraction.
  • PJI_SYSTEM_CONFIG_HIST — configuration history used to determine applicable settings for the extraction.
  • PJI_SYSTEM_SETTINGS — active system settings controlling process behavior and parameters.
  • DUAL — the standard single-row utility table, used for lightweight checks and expressions.

In addition, the documentation excerpt explicitly names the status and scope tables PJI_SYSTEM_PROCESS_STATUS, PJI_SYSTEM_PARAMETERS, PJI_ORG_EXTR_STATUS, and PJI_RM_ORG_BATCH_MAP, which are accessed (directly or via PJI_PROCESS_UTIL) to persist process state, store parameters such as batch ID, define organization scope, and snapshotted batching.

Usage Notes

This package is not intended for direct interactive use and has no form-level UI; it is driven by a concurrent program, with SUMMARIZE as the executable entry point. It is referenced by two other packages, indicating its role within a broader Project Intelligence extraction framework. The process is designed to be restartable: runs must tolerate prior partial execution, which is why status tables rather than dynamic scope are used and why concurrent extraction runs are isolated via PJI_RM_ORG_BATCH_MAP. Because multiple Project Intelligence data extraction processes may execute in parallel and PJI_ORG_EXTR_STATUS can be updated concurrently, the batch-map snapshot is essential for consistency. Custom code should not invoke internal steps such as RUN_PROCESS or the wrap-up procedures independently; instead, standard invocation through the concurrent program and the package's process-control routines preserves error recovery and correct status bookkeeping.