Search Results g_log_mode

Overview

APPS.INV_MGD_POS_UTIL is a utility package body belonging to the Oracle Inventory module, created to support the Inventory Position View and Export functionality. Its stated purpose, taken directly from the source header, is to provide "Utilities for Inventory Position View and Export." The package encapsulates a lightweight, self-contained logging facility used by the Inventory Management position reporting programs. Rather than relying on a separate diagnostic framework, INV_MGD_POS_UTIL delivers two procedures — Log_Initialize and Log — that together allow a concurrent program or calling routine to conditionally emit trace and diagnostic messages based on the current Applications logging profile settings. The package is classified as a UTIL API in the ETRM metadata, owner APPS, and is referenced by five other packages, confirming its role as a shared, cross-cutting service within the Inventory application family. The original source header (INVUPOSB.pls, version 115.2) dates to December 2002 and lists Paolo Juvara as the original author, with an initial creation date of 09/01/2000.

Key Procedures and Functions

Two public procedures are documented:

• LOG_INITIALIZE — Initializes the log facility and is intended to be called from the top-level procedure of each concurrent program. It reads the profile option AFLOG_LEVEL via FND_PROFILE.Value and converts the result to a numeric log level. When the profile returns NULL, the internal logging mode variable is set to "OFF," effectively suppressing all output. When a level is present, the procedure inspects the CONC_REQUEST_ID profile: if the request ID is non-zero (indicating execution inside a concurrent request), the logging mode is set to "SRS"; otherwise it is set to "SQL." This design allows the same logging calls to route output appropriately depending on whether the code runs under a concurrent manager or in an interactive SQL session.
• LOG — Writes a message to the log. It accepts a message level indicating the priority of the entry and the message text itself. The documented priority values, from highest to lowest severity, are G_LOG_ERROR, G_LOG_EXCEPTION, G_LOG_EVENT, G_LOG_PROCEDURE, and G_LOG_STATEMENT. The globally maintained log level is compared against the requested message level to decide whether the entry is emitted.

Tables Accessed

The ETRM metadata records no direct table references through APPS synonyms for this package. Its only data dependencies are the Oracle Application Object Library profile option infrastructure, accessed through the standard FND_PROFILE.Value call for the AFLOG_LEVEL and CONC_REQUEST_ID profile options. All runtime state is held in package globals: G_PKG_NAME (a constant identifying the package), g_log_level (the numeric threshold), and g_log_mode (OFF, SQL, or SRS). No DML is performed against Inventory or application tables.

Usage Notes

INV_MGD_POS_UTIL is invoked programmatically rather than from a form. The documented convention is that the top-level procedure of each concurrent program calls Log_Initialize once at startup to establish the logging mode and level, after which the program issues Log calls at the appropriate severity throughout its execution. Because the mode is derived from the presence of a concurrent request ID, identical source code behaves correctly whether run in a SQL*Plus test session (SQL mode) or through the concurrent manager (SRS mode). The metadata indicates the package is referenced by five other packages, and its role as a shared utility means customizations extending the Inventory Position View or Export should follow the same pattern: call Log_Initialize from the entry point and use Log for diagnostics, gated by the AFLOG_LEVEL profile option so that logging can be enabled or disabled without code changes.