Search Results pji_fm_debug




Overview
Explore in AI Chat

Overview

APPS.PJI_FM_DEBUG is a utility package in the Oracle E-Business Suite Applications schema that supports the PJI (Projects Intelligence) forecasting and summarization subsystem. Its name and dependency footprint indicate that it functions as a debugging and diagnostic helper rather than a business-logic engine. In Oracle EBS 12.1.1 and 12.2.2, the PJI modules form the extract, transform, and load layer that populates project forecasting summary tables from transactional project data. PJI_FM_DEBUG sits alongside that pipeline, providing instrumentation that developers and support engineers can enable when diagnosing issues in the forecast summarization programs.

The package is owned by APPS and is documented as VALID in ETRM. Its only external dependency is the SYS.STANDARD package, which is the implicit base package present in every PL/SQL program unit. This minimal dependency profile confirms that PJI_FM_DEBUG does not itself query or manipulate application tables; instead it offers reusable debug routines that other packages call. The ETRM classification for the package is OTHER, meaning it is not a published public API and Oracle does not guarantee interface stability.

Key Procedures and Functions

ETRM documents two callable units within PJI_FM_DEBUG:

  • CONC_REQUEST_HOOK — A hook routine associated with concurrent request processing. It allows debug or trace behavior to be activated or logged in the context of a running concurrent program, typically keyed to the request that invoked the PJI summarization job.
  • CLEANUP_HOOK — A companion routine that performs end-of-run housekeeping, clearing the diagnostic state or temporary artifacts established by CONC_REQUEST_HOOK so that subsequent executions start from a clean slate.

The ETRM metadata does not publish parameter lists for these units, and no parameter signatures should be assumed. They are intended for internal use by the PJI package family.

Tables Accessed

No application tables are documented as referenced by APPS.PJI_FM_DEBUG through APPS synonyms. Its dependency list contains only SYS and STANDARD. Any diagnostic output therefore relies on database facilities such as DBMS_OUTPUT, the FND log tables accessed indirectly through called utilities, or file-based logging, rather than on direct DML against project tables. The absence of table dependencies is consistent with a debug utility whose sole role is instrumentation.

Usage Notes

PJI_FM_DEBUG is referenced by several packages in the PJI forecast summarization chain: PJI_FM_SUM_BKLG, PJI_FM_SUM_EXTR, PJI_FM_SUM_MAIN, and PJI_RM_SUM_MAIN, and it also references itself (recursive or overloaded use). These packages perform backlog summarization, extraction, and the main forecast summarization respectively. PJI_FM_DEBUG is therefore invoked from within those programs rather than directly by end users.

Typical invocation is indirect: a concurrent program such as the PJI forecast summarization request runs, the calling package invokes CONC_REQUEST_HOOK at start-up to establish diagnostic context, and CLEANUP_HOOK at completion. Because the package is classified as OTHER and is not a public API, customizations should not call it directly. It is most useful during troubleshooting, where a developer temporarily enables the debug path to capture trace information about a failed or slow summarization run. In patched environments (12.1.1 or 12.2.2), its behavior and existence should be verified against the installed ETRM record, as internal debug packages may change between releases without notice.