Results for “wf_message”

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

Overview

WF_MESSAGES_VL is a validated view owned by the APPS schema in Oracle E-Business Suite, registered under the FND — Application Object Library product. It is a translation (VL, or "view language") construct that presents Oracle Workflow message definitions alongside their language-specific, user-facing text. The view joins the base message repository (WF_MESSAGES) to its translations (WF_MESSAGES_TL), resolving the correct translation at runtime through the USERENV('LANG') session parameter. This makes it the canonical access point for message metadata in the session's active language.

Functionally, WF_MESSAGES_VL acts as the read interface for the Oracle Workflow notification and messaging engine, which underlies approvals, notifications, and Business Event messaging across the E-Business Suite. Rather than reading the protected base tables directly, administrators, developers, and reporting tools use this view to inspect message definitions, their default priorities, access roles, and localized subject/body content.

Underlying Base Objects

Per the documented metadata, the view is defined over two base objects referenced as synonyms in the APPS schema: WF_MESSAGES and WF_MESSAGES_TL. The defining SQL aliases WF_MESSAGES as B and WF_MESSAGES_TL as T, joining them on matching TYPE and NAME. A further filter, T.LANGUAGE = USERENV('LANG'), restricts each row to the language of the current session. WF_MESSAGES is the "base" table holding language-independent structural attributes, while WF_MESSAGES_TL is the translation table holding display_name, description, subject, body, and HTML body for each language. Because the view is a simple join, it inherits the security and integrity of both underlying tables.

Key Columns

• ROW_ID — The rowid of the WF_MESSAGES base row; a unique physical identifier.
• TYPE / NAME — The composite logical key identifying a message definition. TYPE and NAME together uniquely identify each message.
• PROTECT_LEVEL — The protection level governing whether the message may be modified (0–1000 scale; 1000 = fully protected, typically seeded).
• CUSTOM_LEVEL — The customization level, indicating the extent to which the definition may be customized.
• DEFAULT_PRIORITY — The default delivery priority assigned to the message, used by the Workflow engine when routing notifications. This is the column most directly relevant to the search term "default_priority."
• READ_ROLE / WRITE_ROLE — The roles permitted to read and to modify the message, supporting access control.
• DISPLAY_NAME / DESCRIPTION — The localized display name and description of the message.
• SUBJECT / BODY / HTML_BODY — The localized notification subject, plain-text body, and HTML-formatted body.

Common Use Cases and Queries

A frequent requirement is auditing message priorities to troubleshoot notification routing or delivery behavior. The DEFAULT_PRIORITY column is commonly queried for exactly this purpose:

• Listing messages with priority 1 or 0 (highest/lowest): SELECT type, name, display_name, default_priority FROM wf_messages_vl WHERE default_priority = 1;
• Auditing customs and protected messages: SELECT name, default_priority, protect_level, custom_level FROM wf_messages_vl WHERE custom_level != 0 ORDER BY name;
• Reviewing access roles: SELECT name, read_role, write_role FROM wf_messages_vl WHERE read_role IS NOT NULL;
• Confirming localized content: SELECT name, display_name, subject FROM wf_messages_vl WHERE name = :message_name;

Because the view automatically filters to the session language, the last query returns the content appropriate to the connected user. When no row appears, the corresponding translation for that language is missing from WF_MESSAGES_TL. As with all VL views in the Application Object Library, WF_MESSAGES_VL should be treated as a read-only reporting interface; modifications to message definitions are performed through the Workflow administrator UI or the Workflow Builder, never by direct DML against the view.