Search Results metrics_event_int_with_context




Overview

APPS.FND_LOG_REPOSITORY is the low-level repository package behind the Oracle E-Business Suite FND_LOG (AFLOG) logging and metrics infrastructure. It exposes the internal APIs used to persist log messages, exception stacks, transaction context, binary attachments, and performance metrics into the FND_LOG_* tables. Because it is classified as an OTHER API rather than a public interface, it is not intended for direct invocation by customers; instead it is the storage and retrieval layer that the public FND_LOG PL/SQL interface, and the AOL implementations of AFLOG in Java and C, call to flush buffered messages and metrics to the database. The package header carries a $Header of AFUTLGRS.pls 120.3 dated 2006/09/18, indicating it has been a stable component of the technology stack across the 11i and R12 releases, and it remains present in both 12.1.1 and 12.2.2 with the same documented procedure surface.

Key Procedures and Functions

Tables Accessed

The package reads and writes the full FND_LOG family through APPS synonyms: FND_LOG_MESSAGES and FND_LOG_MESSAGES_S for message text and its sequence; FND_LOG_EXCEPTIONS and FND_LOG_UNIQUE_EXCEPTIONS (with their _S sequences) for error stacks and de-duplicated exceptions; FND_LOG_METRICS, FND_LOG_METRICS_S, and FND_METRICS_EVENT_KEY_S for performance metrics; FND_LOG_TRANSACTION_CONTEXT and FND_LOG_TRANSACTION_CTX_ID_S for transaction context; and FND_LOG_ATTACHMENTS for BLOB storage. Supporting lookups include FND_APPLICATION for module and application identification, FND_CONCURRENT_REQUESTS for child context tied to a request, FND_LANGUAGES for translated message text, and FND_NEW_MESSAGES for message registration.

Usage Notes

FND_LOG_REPOSITORY is invoked indirectly. Application code calls FND_LOG.STRING, FND_LOG.TRACE, or the metric APIs, which delegate to the _INTERNAL routines here. Middle-tier components written in Java or C reach the same routines through the AOL AFLOG bridge, which is why several procedures are explicitly documented as callable only from those implementations. Concurrent programs benefit from SET_CHILD_CONTEXT_FOR_CONC_REQ so that logged messages and metrics are attributed to the correct request. Custom code should use the public FND_LOG interface rather than calling this package directly, since the internal contract may change and the unchecked variants bypass level enablement checks. GET_BLOB_INTERNAL is typically reached when a log viewer or diagnostic utility retrieves an attachment stored against a log entry.