Search Results wf_messages_tl




Overview
Explore in AI Chat

Overview

The WF_MESSAGES_TL table is a core translation table within the Oracle E-Business Suite (EBS) Application Object Library (FND) product. It is owned by the APPLSYS schema and is integral to the Oracle Workflow (WF) technology stack. Its primary role is to store translated text for the message definitions maintained in the base table, WF_MESSAGES. This table enables the multilingual support (NLS) of workflow notifications, error messages, and other user-facing text within the Workflow engine, allowing the system to display content in a user's preferred language. Its existence is critical for global deployments of EBS 12.1.1 and 12.2.2, ensuring that workflow processes adhere to local language requirements.

Key Information Stored

The table stores translated versions of the data held in the WF_MESSAGES table. Its structure is typical of an EBS translation table, containing a unique key composed of the original record's identifier columns plus a language column. Based on standard translation table patterns and the provided metadata, the key columns are:

  • TYPE and NAME: These columns, along with LANGUAGE, form the primary key (WF_MESSAGES_TL_PK). They constitute a foreign key reference to the WF_MESSAGES table, uniquely identifying the source message for which a translation exists.
  • LANGUAGE: The language code (e.g., 'US' for American English, 'KO' for Korean) for the translated row.
  • PROTECT_LEVEL and CUSTOM_LEVEL: Standard Oracle Application Object Library columns that manage the customization and protection level of the translated data.
  • DISPLAY_NAME and other text columns: These columns hold the actual translated text. While the specific column names are not detailed in the provided excerpt, translation tables typically include columns like DISPLAY_NAME, DESCRIPTION, or the specific text columns from the base table that require translation.

Common Use Cases and Queries

The primary use case is retrieving workflow message text in a user's session language. This is handled automatically by the Workflow engine and underlying FND APIs, which query this table based on the session language set in FND_GLOBAL.APPS_INITIALIZE. Common manual queries include auditing translations or troubleshooting missing text. A sample query to retrieve a specific message in all available languages would be:

SELECT tl.language, tl.display_name
FROM apps.wf_messages_tl tl
WHERE tl.type = '<MESSAGE_TYPE>'
AND tl.name = '<MESSAGE_NAME>'
ORDER BY tl.language;

Another frequent scenario is identifying messages that lack a translation for a critical language, which can be accomplished via an outer join between WF_MESSAGES and WF_MESSAGES_TL filtered for a specific LANGUAGE code.

Related Objects

WF_MESSAGES_TL has a direct and dependent relationship with its base table, as documented in the provided foreign key metadata.

  • WF_MESSAGES: This is the primary related table. The foreign key relationship is defined on the columns WF_MESSAGES_TL.TYPE and WF_MESSAGES_TL.NAME referencing the corresponding columns in WF_MESSAGES. Every record in WF_MESSAGES_TL must have a corresponding parent record in WF_MESSAGES. Standard joins use: WHERE wm.type = tl.type AND wm.name = tl.name.
  • FND_LANGUAGES: While not listed in the provided constraints, translation tables are conceptually related to FND_LANGUAGES, which defines the valid LANGUAGE values available in the system.
  • Workflow Engine APIs: The table is accessed internally by Oracle Workflow APIs and views that serve translated message content to runtime processes and notification mailers.