Search Results g_transaction_context_id

Overview

APPS.FND_LOG is the Oracle E-Business Suite logging infrastructure package. It provides a centralized, level-based diagnostic and instrumentation facility used throughout the E-Business Suite to record errors, exceptions, events, procedures, and statements into a persistent log store. The package is part of the Foundation (FND) technology stack and is available in both the 12.1.1 and 12.2.2 releases. Its primary business function is to give developers, support engineers, and system administrators a consistent mechanism for capturing runtime trace information across concurrent programs, forms, service processes, and ICX functions without requiring custom logging code in every component. Because logging is governed by numeric levels, administrators control verbosity at runtime through profile options, and the volume of captured data can be tuned without source changes. The package is referenced by 3237 other packages, reflecting its role as a ubiquitous cross-module dependency.

Key Procedures and Functions

FND_LOG exposes 17 documented procedures and functions. Core lifecycle routines include INIT_TRANSACTION and SET_TRANSACTION, which establish and manage the log transaction context that groups messages belonging to a single component invocation. Message emission is handled by STRING, STRING_WITH_CONTEXT, MESSAGE, MESSAGE_WITH_ATTACHMENT, and MESSAGE_WITH_CONTEXT, each differing in the amount of contextual or attached detail recorded alongside the text. Instrumentation of measurements is provided by WORK_METRIC and WORK_METRICS_EVENT; the latter corresponds directly to the work_metrics_event search term and is used to record structured work-metric events during execution. Utility routines include TEST, GET_TEXT, SET_BUFFERED_MODE, RESET_BUFFERED_MODE, and PROXY_ALERT_FOR_CONC_REQ. Buffered mode allows messages to accumulate in memory before being flushed, reducing I/O overhead during high-volume processing. The package declares six severity constants — LEVEL_UNEXPECTED (6), LEVEL_ERROR (5), LEVEL_EXCEPTION (4), LEVEL_EVENT (3), LEVEL_PROCEDURE (2), and LEVEL_STATEMENT (1) — together with the module-level variable G_TRANSACTION_CONTEXT_ID.

Tables Accessed

The package reads and writes several application tables through APPS synonyms. FND_LOG_MESSAGES is the primary store into which emitted log records are inserted. FND_LOG_TRANSACTION_CONTEXT holds transaction metadata used by INIT_TRANSACTION and SET_TRANSACTION. FND_NEW_MESSAGES supports message lookup and text retrieval operations such as GET_TEXT. DBMS_UTILITY is referenced for supporting Oracle-supplied utility calls, including error stack and call stack retrieval.

Usage Notes

FND_LOG is typically invoked from PL/SQL code executing inside concurrent programs, Oracle Forms, service processes, and ICX functions. INIT_TRANSACTION should be called only after FND_GLOBAL.INITIALIZE, since some transaction context is derived from FND_GLOBAL. Callers pass only the arguments relevant to their environment — for example, a form passes FORM_ID and FORM_APPLICATION_ID while leaving concurrent and service parameters NULL. Because the package is the standard logging entry point across the E-Business Suite, custom code should emit diagnostics through FND_LOG rather than writing directly to FND_LOG_MESSAGES, ensuring consistent level handling, transaction grouping, and administrator-controlled verbosity.