Search Results set_worker_id

Overview

APPS.PJI_PJP_EXTRACTION_UTILS is a PL/SQL utility package within the Oracle EBS Project Intelligence (PJI) application, responsible for orchestrating the extraction of project performance data into the PJI fact tables used by Project Portfolio Analysis and related reporting engines. The package coordinates worker identification, extraction scope management, organizational extraction metadata, and the maintenance of staging and status tables that track the lifecycle of a PJP (Project Performance) extraction run. Its header revision ($Header: PJIUT06S.pls 120.1 2006/11/10) indicates an established, low-churn internal utility that has remained stable across the 12.1.1 and 12.2.2 code lines. A distinctive aspect of this package is its use of a session-scoped worker identifier, managed through a setter/getter pair, which allows extraction processes to attribute work, statistics, and status records to a specific concurrent worker.

Key Procedures and Functions

• SET_WORKER_ID — Stores the current worker identifier for the session, establishing the context under which subsequent extraction operations execute.
• GET_WORKER_ID — Returns the worker identifier previously set for the session. This is the object referenced by the get_worker_id search term and is the canonical accessor for the session's worker context.
• UPDATE_EXTR_SCOPE — Recomputes or refreshes the extraction scope, determining which projects are eligible for PJP extraction in the current run.
• POPULATE_ORG_EXTR_INFO — Inserts organizational-level extraction information records required for downstream processing.
• UPDATE_ORG_EXTR_INFO — Maintains and updates existing organizational extraction information records.
• SEED_PJI_PJP_STATS — Seeds statistics rows for the PJP extraction, keyed by the supplied worker identifier.
• ANALYZE_PJP_FACTS — Gathers optimizer statistics on the PJP fact tables to sustain query performance.
• TRUNCATE_PJP_TABLES — Clears PJP staging/fact tables. Its parameters include error and return buffers plus flags for check, FPM upgrade, and recovery modes, supporting controlled re-runs and upgrade scenarios.
• LAST_PJP_EXTR_DATE — Returns the date of the last PJP extraction, optionally scoped to a specific project.

Tables Accessed

• PJI_PJP_PROJ_EXTR_STATUS, PJI_PROJ_EXTR_STATUS — Track per-project extraction status across runs.
• PJI_SYSTEM_PARAMETERS, PJI_SYSTEM_CONFIG_HIST, PJI_SYSTEM_PRC_STATUS, PJI_MT_PRC_STEPS — Configuration, history, and process-step control for the PJI extraction engine.
• PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_XBS_DENORM — Provide project master and denormalized attribute data used to determine extraction scope.
• PA_PJI_PROJ_EVENTS_LOG, PA_PJI_PROJ_EVENTS_LOG_S — Event logging for project extraction activity.
• FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES — Resolve profile option settings that govern extraction behavior.
• DUAL, V$PARAMETER — Utility access for single-row queries and database parameter inspection.

Usage Notes

The package is invoked from concurrent programs and internal PJI processing routines rather than from end-user forms directly. The typical sequence is to call SET_WORKER_ID to bind the session context, invoke the scope and organization-info procedures to prepare extraction metadata, run the extraction, and then use the status, statistics, and truncate procedures to finalize or recover the run. The TRUNCATE_PJP_TABLES contract (errbuf, retcode) makes it suitable for direct use as a concurrent program body. Because it is referenced by approximately ten other packages, customizations that modify its behavior should be approached cautiously; extensions should prefer wrapping the documented API rather than altering its internal logic. Its stable, long-lived header indicates the interface has been effectively frozen, so custom code may depend on the current procedure signatures with reasonable confidence.