Search Results debug_exception

Overview

APPS.HR_KPI is a PL/SQL package body that serves a dual purpose within the Oracle E-Business Suite 12.1.1 and 12.2.2 environment. Its primary role is to provide a standardized diagnostic and instrumentation layer built on the Oracle Application Object Library (AOL) FND_LOG and FND_MESSAGE APIs, enabling developers to emit structured trace messages and raise user-friendly errors from PL/SQL routines. In addition to this logging utility, HR_KPI exposes a set of Java-backed entry points surfaced through PL/SQL function wrappers, most notably REQUEST and PARSERESPONSE, which form the interface between the database tier and the Java component referenced in the package header. The package is classified as "OTHER" in the ETRM metadata, meaning it is not modelled as a traditional business API but is instead an internal utility and integration helper. The dominating theme of the source excerpt is the debug_* family of procedures, which includes the debug_end procedure that a user searching for "debug_end" would be directed toward.

Key Procedures and Functions

• DEBUG_START — Marks the beginning of a routine for tracing purposes. Emits a "start" string at the FND_LOG.LEVEL_PROCEDURE level when the current runtime logging level permits it.
• DEBUG_END — The counterpart to DEBUG_START. Emits an "end" string at FND_LOG.LEVEL_PROCEDURE to signal completion of the instrumented routine. This is the procedure most directly relevant to the "debug_end" search term.
• DEBUG_TEXT — Writes a free-form message at FND_LOG.LEVEL_STATEMENT, used for general statement-level tracing.
• DEBUG_EVENT — Writes an event message at FND_LOG.LEVEL_EVENT, used to trace significant business or control-flow events.
• DEBUG_EXCEPTION — Raises a standardized error using the FND_MESSAGE tokens SQL_PLSQL_ERROR, ROUTINE, ERRNO and REASON, and conditionally emits an exception-level log entry. This consolidates error reporting into a single reusable routine.
• REQUEST — A PL/SQL wrapper declared as a Java-language function that passes a context and a cookie (an IN OUT NOCOPY VARCHAR2) to the Java layer, returning a VARCHAR2 result. It serves as the primary outward-facing engine call.
• PARSERESPONSE — Processes or parses the response returned by the Java engine or an external service.
• SAVE_USER_PREFERENCE — Persists a user preference value; details of the underlying storage are not exposed in the excerpt.

Tables Accessed

The ETRM metadata records no table references for APPS.HR_KPI through APPS synonyms. That absence is consistent with the source excerpt, which shows the debug routines relying solely on FND_LOG and FND_MESSAGE — infrastructure APIs rather than application tables. The Java-backed routines (REQUEST, PARSERESPONSE, SAVE_USER_PREFERENCE) may interact with data outside the documented DML surface, but no specific table dependencies are documented.

Usage Notes

HR_KPI is typically invoked from custom PL/SQL code and from other packaged code that follows the EBS logging convention of pairing debug_start and debug_end calls around a routine body. Tracing is controlled by the standard FND_LOG runtime level profile option (FND: Debug Log Level) combined with the logger setting (FND: Debug Log Enabled). When the current runtime level is below the level being emitted, the STRING call is skipped, so the instrumentation is effectively free when logging is disabled. Because the log level procedure check is embedded in each routine, developers can instrument production code with negligible overhead. The package is also referenced by the Java integration layer via the REQUEST function. Developers searching for "debug_end" should note that it is a public procedure in this package body and is normally called immediately before a routine exits so that trace output brackets the routine's execution.