Search Results shutdown_process




Overview
Explore in AI Chat

Overview

APPS.PJI_RM_SUM_MAIN is the central driver package in the Oracle EBS Project Resource Management (PJI/RM) summarization subsystem. It orchestrates the process that accumulates, aggregates, and validates project and resource data used by Project Management reporting and the resource management summaries. The package encapsulates the full lifecycle of a summarization run — initialization, execution, parallel worker coordination, dangling-data reporting, commit management, and wrap-up or failure handling. Its header declares global constants and control variables that reveal its design intent: a process identifier (g_process), a parallel limit of eight processes (g_parallel_limit, g_parallel_processes), a parallel process delay (g_process_delay), a commit threshold of 10,000 records (g_commit_threshold), and display names for the full, incremental, and partial summarization programs (g_full_disp_name, g_incr_disp_name, g_prtl_disp_name) along with a helper package reference (g_helper_name). It also establishes an extraction date window bounded by PJI_UTILS.GET_EXTRACTION_START_DATE and a far-future maximum date. The package supports both Resource Management (RM) and Financial Management (FM) run modes, evidenced by the dual parameter sets in INIT_PROCESS.

Key Procedures and Functions

  • PRIOR_ITERATION_SUCCESSFUL — Boolean function that reports whether a preceding iteration of the summarization process completed successfully, enabling downstream logic to proceed or abort.
  • INIT_PROCESS — Initializes a summarization run. Accepts the run mode and parameters for both RM (schedule, organization, include-sub-org) and FM (operating unit, project range, plan type).
  • PROCESS_RUNNING — Boolean function that determines whether the process is currently running, supporting concurrency control and wait behavior.
  • RUN_PROCESS — The primary execution entry point that drives the summarization run through its stages.
  • MY_PAD — String utility that pads a value to a specified length with a given character, used for formatted output.
  • GET_MISSING_TIME_HEADER — Returns the header text for the missing-time diagnostic report.
  • GET_MISSING_TIME_TEXT — Returns the missing-time diagnostic text for a given calendar, period type, and date range.
  • DANGLING_REPORT — Produces the dangling-data report identifying orphaned or inconsistent summarization records.
  • WRAPUP_PROCESS — Performs normal completion processing at the end of a successful run.
  • WRAPUP_FAILURE — Performs cleanup and status handling when a run fails.
  • SHUTDOWN_PROCESS — Terminates the process and returns the standard concurrent program errbuf and retcode values.
  • SUMMARIZE — The core summarization routine invoked to aggregate the underlying project and resource data.

Tables Accessed

  • PA_PROJECTS_ALL — The project master table, read to identify projects in scope for summarization and to resolve project-level attributes.
  • PJI_SYSTEM_CONFIG_HIST — System configuration history, consulted to determine active configuration settings for the run.
  • PJI_SYSTEM_SETTINGS — Current system settings controlling summarization behavior and parameters.
  • DUAL — Used for single-row evaluations and date/constant resolution.

Usage Notes

PJI_RM_SUM_MAIN is typically invoked through Oracle Projects concurrent programs, specifically the summarization programs referenced by its full, incremental, and partial display names, and is referenced by two other packages within the PJI subsystem. The parallel parameters (limit, process count, delay) indicate it is designed for parallel worker execution with commit batching. Administrators run it on schedule to keep resource management summaries current; custom code should call it only through its documented entry points (INIT_PROCESS, RUN_PROCESS, SUMMARIZE) rather than manipulating its internal state directly.