Search Results fun_rich_messages_b

Overview

FUN_RICH_MESSAGES_VL is a VALID database view owned by the APPS schema in Oracle E-Business Suite. It is registered under the FND — Application Object Library product family, although its underlying tables are associated with the FUN (Financials Common) module naming convention, which is why users searching for the base object "fun_rich_messages_b" are typically routed to this view. The suffix "_VL" identifies it as a "view with language" — a standard EBS naming convention denoting a view that joins a base (_B) table to its translation (_TL) table so that the meaning-bearing text column is returned in the session's current language.

The view is primarily consumed for reporting and integration purposes rather than transactional processing. It exposes the stored definition of rich-format messages — messages that may include embedded formatting or markup — together with their multilingual text, providing a single queryable object that resolves the correct language row automatically. The view text selects FROM FUN_RICH_MESSAGES_B and FUN_RICH_MESSAGES_TL, joining on APPLICATION_ID and MESSAGE_NAME, filtered by T.LANGUAGE = USERENV('LANG').

Underlying Base Objects

The documented referenced base objects are two synonyms resolving to the underlying FUN tables:

• FUN_RICH_MESSAGES_B — the base (non-translatable) table holding the message identifier, application context, object version number, and standard WHO audit columns.
• FUN_RICH_MESSAGES_TL — the translation table holding the MESSAGE_TEXT in each installed language.

The join is defined as B.APPLICATION_ID = T.APPLICATION_ID AND B.MESSAGE_NAME = T.MESSAGE_NAME, with the translation side restricted to the language returned by USERENV('LANG'). This means the view returns exactly one MESSAGE_TEXT per message per session language, assuming a complete translation exists.

Key Columns

• ROW_ID — the ROWID of the base (FUN_RICH_MESSAGES_B) row, aliased as ROW_ID.
• APPLICATION_ID — the application context alongside MESSAGE_NAME; the pair forms the effective message key.
• MESSAGE_NAME — the developer-facing name of the rich message.
• MESSAGE_TEXT — the translated rich message content, resolved for the session language.
• OBJECT_VERSION_NUMBER — optimistic locking / versioning column.
• CREATED_BY_MODULE — the module that created the message record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include retrieving the text of a rich message for display or debugging in a specific language, validating that translations exist for all installed languages, and extracting message content for external integration or documentation purposes. Because the view masks the _B/_TL split, a query against it is considerably simpler than one against the base tables.

Sample query for a specific message:

• SELECT APPLICATION_ID, MESSAGE_NAME, MESSAGE_TEXT FROM FUN_RICH_MESSAGES_VL WHERE MESSAGE_NAME = :p_message_name;

Sample query listing rich messages for an application:

• SELECT MESSAGE_NAME, MESSAGE_TEXT FROM FUN_RICH_MESSAGES_VL WHERE APPLICATION_ID = :p_app_id ORDER BY MESSAGE_NAME;

To audit translation coverage, query FUN_RICH_MESSAGES_TL directly, since the VL view shows only the current session language. Note that the view text was not truncated in the documented set and matches the 12.1.1 and 12.2.2 repository definitions.