Results for “html_body”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WF_MESSAGES_TL is the translation table for the Oracle Workflow message repository in Oracle E-Business Suite, owned by the APPLSYS schema and delivered under the FND — Application Object Library product. Every workflow notification, message attribute, and token-substitution definition stored in the base WF_MESSAGES table has one or more corresponding rows in WF_MESSAGES_TL, one per installed language, holding the user-visible subject line, message body, and display name. This architecture allows a single logical message definition to be presented in the language of the recipient rather than the language in which the workflow was authored.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: WF_MESSAGES_TL hangs off the WF_MESSAGES business key and carries descriptive, language-dependent attributes rather than acting as an independent hub or an associative link. This classification is a heuristic recommendation only and should be validated against the broader Workflow entity-relationship model before being adopted in a Data Vault design.

Key Information Stored

The table's unique index, WF_MESSAGES_TL_PK, is defined over TYPE, NAME, LANGUAGE, and ZD_EDITION_NAME. Note that ZD_EDITION_NAME references the editioning mechanism used in 12.2 online patching; in a 12.1.1 environment this column is not part of the operational key. The first two columns, TYPE and NAME, form the foreign key back to WF_MESSAGES and together constitute the business-key candidate for the parent message. LANGUAGE isolates the translation.

• TYPE — message type classification (for example, a notification or token category); part of the primary key and the FK to WF_MESSAGES.
• NAME — the internal message name; part of the primary key and the FK to WF_MESSAGES.
• LANGUAGE — the NLS language code identifying this translation row.
• DISPLAY_NAME — the translated, user-facing name of the message.
• SUBJECT — the translated subject line used for notifications.
• BODY — the translated plain-text message body, including substitution tokens.
• HTML_BODY — the HTML-formatted variant of the message body used for rich notification delivery.
• DESCRIPTION — a translated description of the message's purpose.
• SOURCE_LANG — the language in which the message was originally authored, used by the translation/MLS framework.
• PROTECT_LEVEL and CUSTOM_LEVEL — Oracle-standard protection and customization levels governing whether the row may be modified or upgraded.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, scoping the row for multi-tenant or data-group access.

There is no single surrogate column beyond the composite primary key; the primary key itself is the concatenation of TYPE, NAME, and LANGUAGE.

Common Use Cases and Queries

The most frequent requirement is retrieving the translated subject and body for a given message in a specific language, either for reporting on notification content or for verifying that a translation was seeded correctly during patching.

• Join WF_MESSAGES_TL to WF_MESSAGES on TYPE and NAME to compare the base definition against its translations.
• Filter by LANGUAGE to audit which languages are populated for a message, using a query such as SELECT t.name, t.language, t.subject FROM wf_messages_tl t WHERE t.type = :type AND t.name = :name.
• Locate untranslated messages by outer-joining WF_MESSAGES to WF_MESSAGES_TL and filtering where the translation row is null for a target language.
• Report on missing HTML_BODY values for messages where rich notifications are expected.

Because the body columns contain substitution tokens, any content audit should account for token placeholders rather than expecting literal text.

Related Objects

• WF_MESSAGES — the parent table; joined on WF_MESSAGES_TL.TYPE = WF_MESSAGES.TYPE and WF_MESSAGES_TL.NAME = WF_MESSAGES.NAME, and the FK source for this table.
• FND_SECURITY_GROUPS — referenced via WF_MESSAGES_TL.SECURITY_GROUP_ID, providing the security-group scoping of translated rows.
• WF_NOTIFICATIONS — stores runtime notification instances that resolve their subject and body through the message definition and its translation.
• WF_MESSAGE_ATTRIBUTES — defines the tokens available within the message body that appear in the BODY and HTML_BODY columns.
• FND_LANGUAGES — provides the valid LANGUAGE values and their installed status.
• WF_NOTIFICATION_ATTRIBUTES — holds per-instance attribute values substituted into the translated body at delivery time.
• WF_LOCAL_ROLES / FND_USER — supply the recipient's language preference used to select the correct translation row.

Direct DML against WF_MESSAGES_TL is generally discouraged; message and translation definitions should be maintained through the Workflow Builder or the supported loader utilities so that the MLS framework and protection levels remain consistent.