Search Results prg_change




Overview
Explore in AI Chat

Overview

APPS.PJI_PJP_EXTRACTION_UTILS is a PL/SQL package body that supports the Project Intelligence (PJI) extraction and summarization infrastructure within Oracle E-Business Suite, specifically for the Project Portfolio Analysis and Project Performance (PJP) summarization engine. In the 12.1.1 and 12.2.2 releases, this package provides a collection of utility routines used by the parallel PJP summarization process to manage worker context, record extraction scope across projects, seed and analyze statistics on the PJP fact tables, and purge transient staging data. The package is classified as OTHER in the ETRM registry and is referenced by ten other packages, indicating that it functions as a shared low-level service rather than a user-facing API. Its source header ($Header: PJIUT06B.pls 120.9 ... ship $) confirms it was first created in 2004 and has been maintained through the EBS 12.x line.

Key Procedures and Functions

The package exposes nine documented procedures and functions:

  • SET_WORKER_ID — Internal API that validates and stores the partitioning worker identifier used by the parallel summarization process. It raises an error if the supplied identifier is non-numeric, less than one, or exceeds the parallel process count defined in PJI_PJP_SUM_MAIN.
  • GET_WORKER_ID — External API that returns the current worker identifier stored in the package global, raising an error if no worker context exists.
  • UPDATE_EXTR_SCOPE — Records the extraction scope (the set of projects to be summarized) together with the standard Who columns derived from FND_GLOBAL (user ID and login ID).
  • POPULATE_ORG_EXTR_INFO — Populates the organization-level extraction information used to drive the summarization run.
  • UPDATE_ORG_EXTR_INFO — Updates previously populated organization extraction information.
  • SEED_PJI_PJP_STATS — Initializes statistical records for the PJP extraction process.
  • ANALYZE_PJP_FACTS — Performs statistics gathering on the PJP fact tables to support query performance.
  • TRUNCATE_PJP_TABLES — Clears transient PJP staging tables as part of the extraction lifecycle.
  • LAST_PJP_EXTR_DATE — Returns the date of the most recent PJP extraction, used to determine incremental processing windows.

The search term "prg_change" does not correspond to a procedure here; it relates to system-parameter change history captured through the referenced PJI_SYSTEM_CONFIG_HIST and PJI_SYSTEM_PRC_STATUS tables.

Tables Accessed

The package reads and writes through APPS synonyms. Project metadata is drawn from PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL and PA_XBS_DENORM, while project event logging uses the PA_PJI_PROJ_EVENTS_LOG and its sequence. Extraction control data resides in PJI_PJP_PROJ_EXTR_STATUS and PJI_PROJ_EXTR_STATUS. System-level configuration and processing state are held in PJI_SYSTEM_PARAMETERS, PJI_SYSTEM_CONFIG_HIST and PJI_SYSTEM_PRC_STATUS. Workflow step tracking uses PJI_MT_PRC_STEPS, profiling uses FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES, and catalog and instance inspection use DUAL and V$PARAMETER.

Usage Notes

This package is typically invoked indirectly by the PJP summarization concurrent programs and by the ten dependent packages that rely on its worker-ID, scope, statistics and truncation services. It is not intended for direct end-user execution; customizations should call the documented public routines (GET_WORKER_ID, LAST_PJP_EXTR_DATE and the org extraction procedures) rather than manipulating the underlying staging tables. Because the routines depend on FND_GLOBAL context and on V$PARAMETER, they must be run from a session with a valid EBS login and sufficient privileges on the referenced views.