Search Results fnd_log_transaction_ctx_id_s

Overview

FND_LOG_REPOSITORY is the internal PL/SQL engine that underpins the Oracle EBS logging infrastructure. It is a PACKAGE BODY owned by the APPS schema, with a status of VALID, and belongs to the broader FND_LOG family of logging and diagnostics components shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. Its business function is to provide the runtime implementation that records, buffers, formats, and persists log messages, metrics, exceptions, and transaction context for concurrent programs, forms, and other EBS runtime components. The package is classified under the ETRM as API classification OTHER, meaning it is an internal implementation package rather than a documented public API. It exposes eighteen documented program units and is referenced by twenty-seven other packages, making it a heavily reused, foundational logging service.

Key Procedures and Functions

The package provides a layered set of internal entry points for writing log data. Message emission is handled by STRING_UNCHECKED_INTERNAL, STRING_UNCHECKED_TO_CONTEXT, and STR_UNCHKED_INT_WITH_CONTEXT, which record free-text log strings, including variants that associate the message with a transaction context. Metric capture is handled by METRIC_INTERNAL_WITH_CONTEXT and METRICS_EVENT_INT_WITH_CONTEXT, which persist numeric metric values alongside their context. Context management is provided by INIT and INIT_TRANS_INT_WITH_CONTEXT, which initialize logging state, and by SET_CHILD_CONTEXT_FOR_CONC_REQ and CLEAR_CHILD_CONTEXT, which establish and tear down a child logging context tied to a concurrent request. Buffered mode, used to reduce logging overhead during high-volume execution, is controlled by SET_BUFFERED_MODE and RESET_BUFFERED_MODE. Retrieval and conversion utilities include GET_BULK_CONTEXT_PVT, BULK_INSERT_PVT, GET_BLOB_INTERNAL, INSERT_BLOB for large object log payloads, METRIC_STRING_TO_DATE for metric timestamp parsing, and CHECK_ACCESS_INTERNAL for access validation.

Tables Accessed

The package reads and writes through APPS synonyms against the core logging tables. FND_LOG_MESSAGES and FND_LOG_MESSAGES_S store log message text and its sequence-generated identifiers. FND_LOG_METRICS and FND_LOG_METRICS_S hold captured metric values and their sequence numbers, while FND_METRICS_EVENT_KEY_S supplies metric event key identifiers. FND_LOG_TRANSACTION_CONTEXT together with FND_LOG_TRANSACTION_CTX_ID_S maintains the transaction context and its identifier sequence — the object referenced by the search term fnd_log_transaction_ctx_id_s. Exception data is stored in FND_LOG_EXCEPTIONS and FND_LOG_UNIQUE_EXCEPTIONS with the FND_LOG_UNIQUE_EXCEPTION_S sequence. FND_LOG_ATTACHMENTS supports attached log content, and FND_NEW_MESSAGES holds message definitions. Auxiliary tables include FND_APPLICATION, FND_CONCURRENT_REQUESTS, and FND_LANGUAGES.

Usage Notes

FND_LOG_REPOSITORY is primarily invoked indirectly. Forms, concurrent programs, and the FND_LOG wrapper API call into it through packages such as FND_LOG and FND_LOG_METRICS, rather than by direct invocation. Custom code that uses the supported FND_LOG API automatically exercises this package. Because FND_LOG_TRANSACTION_CTX_ID_S is a sequence referenced internally for transaction context identifiers, it should not be manipulated directly. Administrators indirectly affect behavior through FND profile options governing logging levels and buffered mode. Direct calls are not recommended in customizations, as the package is an internal repository whose interface may change between releases.