Search Results inl_logging_pvt




Overview
Explore in AI Chat

Overview

INL_LOGGING_PVT is a private PL/SQL package body owned by the APPS schema that provides the centralized diagnostic logging and instrumentation framework used throughout the Oracle E-Business Suite logistics and inventory application modules. Its object name carries the _PVT suffix, which under Oracle EBS naming conventions designates a private implementation package rather than a public API. Consequently, INL_LOGGING_PVT is not itself referenced by any other database object; instead, it is consumed internally by the thirteen packages that depend upon it. The package abstracts the lower-level logging primitives supplied by FND_LOG and the text output facilities of FND_FILE, presenting a uniform set of entry points for recording statements, variable values, procedure boundaries, API invocations, events, and exceptions. This abstraction produces consistent, structured log output across concurrent programs, forms, and server-side PL/SQL routines, and it respects the FND_PROFILE-driven debug and logging levels that administrators configure in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

  • LOG_STATEMENT — Writes an arbitrary informational message to the log at the caller-designated level.
  • LOG_VARIABLE — Records the name and current value of a PL/SQL variable for diagnostic tracing.
  • LOG_BEGINPROC — Marks entry into a procedure or function, typically emitting the routine name and entry-level context.
  • LOG_ENDPROC — Marks normal exit from a procedure or function, bracketing the routine with its begin counterpart.
  • LOG_APICALLIN — Logs the inbound invocation of a public API, capturing that the API was entered by an external or sibling caller.
  • LOG_APICALLOUT — Logs an outbound call from the current package into another API.
  • LOG_EVENT — Records a significant business or processing event within the running program.
  • LOG_EXCEPTION — Captures exception details, including the error message, for the exception handler in scope.
  • LOG_EXPECERROR — Records an expected (handled) application error condition.
  • LOG_UNEXPECERROR — Records an unexpected (unhandled) error condition for later diagnosis.

Tables Accessed

The package body does not read or write any application tables directly. Its dependencies are confined to the EBS technology stack: FND_LOG for writing entries into the FND_LOG_MESSAGES logging repository, FND_FILE for emitting buffered output to concurrent program log and output files, and FND_PROFILE for retrieving the runtime logging and debug level settings that determine whether a given message is actually recorded. The SYS.STANDARD package supplies the built-in PL/SQL types and exceptions referenced in the code. No base or interface tables are touched, so invoking this package carries no transactional or data-integrity consequences.

Usage Notes

INL_LOGGING_PVT is invoked from within PL/SQL code rather than directly by end users. Developers place its routines at key points in concurrent programs, public APIs, and forms-based server logic to trace execution, capture variable state, and report exceptions. Because the interface is private, callers should invoke it only from the logistics packages that depend upon it; customizations that need comparable functionality should call the underlying FND_LOG and FND_FILE APIs directly. Log output is governed by profile options, so effective verbosity is controlled by the FND: Debug Level and related logging profiles. When investigating EBS 12.1.1 or 12.2.2 issues, administrators enable the appropriate debug level, reproduce the transaction, and then query FND_LOG_MESSAGES or inspect the concurrent request log to review the entries this package has written.