Search Results set_logging_options




Overview
Explore in AI Chat

Overview

APPS.PO_R12_CAT_UPG_DEBUG is a PL/SQL package body in the Oracle E-Business Suite APPS schema that provides diagnostic logging services for the Purchasing R12 catalog upgrade process. Its name reflects its role: it is the debugging and logging utility supporting the R12 catalogue upgrade (PO_R12_CAT_UPG) that migrates purchasing catalogue data to the Release 12 data model. Rather than performing any business transformation itself, the package centralises the emission of trace and diagnostic messages so that upgrade routines, concurrent programs, and dependent packages can uniformly record their progress, decision points, and error conditions.

The package is classified under the ETRM metadata as API classification OTHER, indicating that it is an internal utility rather than a public business API. In EBS 12.1.1 and 12.2.2 it retains the VALID status and is installed as part of the Oracle Purchasing schema, making it available to any upgrading component executing within the APPS environment.

Key Procedures and Functions

The documented interface of PO_R12_CAT_UPG_DEBUG consists of four program units:

  • LOG — the principal message-emitting routine. It records a diagnostic message at the appropriate severity so that upgrade activity can be traced during execution and reviewed after the fact.
  • LOG_STMT — writes a constructed statement or textual fragment to the logging destination, allowing upgrade code to capture dynamically assembled SQL or procedural text for diagnostic purposes.
  • SET_LOGGING_OPTIONS — establishes the logging configuration for the session, determining the level of granularity and destination used by the other routines.
  • IS_LOGGING_ENABLED — a Boolean-style check that reports whether logging is currently active, enabling callers to avoid the overhead of building log messages when diagnostics are switched off.

The presence of IS_LOGGING_ENABLED alongside SET_LOGGING_OPTIONS demonstrates a deliberate design in which logging is conditional, controlled at run time, and guarded at the call site to minimise performance impact during large catalogue upgrades. No parameter lists are documented in the ETRM metadata and none should be assumed.

Tables Accessed

The ETRM metadata records no application tables referenced through APPS synonyms. Instead, the package's dependencies are on infrastructure components: FND_LOG for the Oracle EBS logging framework, FND_PROFILE for profile-option retrieval, and the STANDARD package supplied by SYS. It also depends upon its own specification, PO_R12_CAT_UPG_DEBUG. Log output therefore flows to the standard EBS logging facility rather than to a dedicated upgrade table, and configuration is obtained through the profile layer — a pattern consistent with other Release 12 upgrade utilities.

Usage Notes

PO_R12_CAT_UPG_DEBUG is not referenced by any other database object according to its dependency listing, yet the documented metadata records it as being referenced by seven other packages. This apparent discrepancy reflects the distinction between the package body (invoked at run time, not resolved as a compile-time dependency) and the package specification through which callers bind. In practice the utility is invoked by the catalogue upgrade driver and its supporting packages during upgrade execution, typically under a concurrent program in a patching or upgrade session.

Because logging behaviour is governed by profile options and the SET_LOGGING_OPTIONS routine, administrators and support engineers enable verbose output only when diagnosing a failed or unexpectedly slow catalogue upgrade. Custom code should not depend on this package as a supported API; it is an internal diagnostic aid whose interface may change between releases. In both 12.1.1 and 12.2.2 it remains a valid, installed component of the APPS schema.