Search Results fnd_message_cache




Overview
Explore in AI Chat

Overview

FND_MESSAGE_CACHE is a PL/SQL package body owned by the APPS schema that provides the runtime message-handling foundation for Oracle E-Business Suite. It is a core component of the Oracle Application Object Library (FND) messaging infrastructure, working in tandem with the FND_MESSAGE package. The package serves as the cached access layer through which application code and concurrent programs retrieve translated error, warning, and informational messages stored in the EBS message repository. By caching message text, tokens, and encoded string representations, it minimizes repeated lookups against the message dictionary during a session, improving performance for forms, OAF pages, and PL/SQL APIs that raise or display messages.

Although documented as an "OTHER" API classification, FND_MESSAGE_CACHE is a heavily reused internal utility. The ETRM metadata records that it is referenced by 8 other database objects (packages), confirming its role as a dependency for higher-level messaging packages. Its status is VALID, and it is supported in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

ETRM documents 14 procedures and functions. Their purposes are:

  • SET_NAME — establishes the active message name for the cache context, identifying which message is being loaded or resolved.
  • SET_TOKEN — assigns a token value to be substituted into the cached message text at runtime.
  • SET_TOKEN_SQL — assigns a token whose value is derived from SQL, supporting dynamic substitution.
  • RETRIEVE — returns the cached message string for the current context.
  • CLEAR — resets/empties the message cache, releasing tokens and buffered text.
  • GET_STRING — retrieves the message text as a string value.
  • FETCH_SQL_TOKEN — fetches the value associated with a SQL-based token.
  • GET_NUMBER — returns a message or token interpreted as a numeric value.
  • GET — general accessor for the cached message content.
  • GET_ENCODED — returns the encoded representation of the message, used for transmission or logging.
  • PARSE_ENCODED — parses an encoded message string back into its component parts.
  • SET_ENCODED — stores an encoded message into the cache.
  • RAISE_ERROR — raises a formatted application error using the cached message and its tokens.
  • GET_TOKEN — returns the value currently bound to a named token.

These routines collectively manage the lifecycle of a message: naming, token binding, encoding/decoding, retrieval, and error raising.

Tables Accessed

The ETRM record lists no direct base-table references for FND_MESSAGE_CACHE; its only documented dependency is the APPS.FND_MESSAGE package, plus the SYS STANDARD package. This indicates that the cache package does not itself query the message repository tables (such as FND_NEW_MESSAGES or FND_MESSAGES) directly, but instead delegates message lookup and localization to FND_MESSAGE. Therefore, table access for message text flows through FND_MESSAGE, while FND_MESSAGE_CACHE holds the in-memory buffered values for the duration of the session or call.

Usage Notes

FND_MESSAGE_CACHE is not typically invoked directly by end users. It is called by Oracle Forms, Oracle Applications Framework (OAF) pages, concurrent programs, and other FND packages that need to display, log, or raise messages. Its RAISE_ERROR routine is the mechanism by which application errors are surfaced to the user interface, while SET_TOKEN and SET_TOKEN_SQL support dynamic, parameterized message text.

Custom code that must emit EBS-standard messages should use FND_MESSAGE rather than calling FND_MESSAGE_CACHE directly, because the cache layer is an internal implementation detail whose behavior (and encoded formats) may change across releases. Because ETRM confirms it is referenced by 8 packages but references no other database objects, it should be treated as a shared internal utility supporting the broader messaging stack in both 12.1.1 and 12.2.2.