Results for “wf_messages”

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

Overview

WF_MESSAGES is the Oracle Workflow message-definition table residing in the APPLSYS schema and registered under the FND – Application Object Library product. It stores the master definitions of workflow messages, which are the reusable notification bodies, subjects, and attribute containers that Oracle Workflow delivers through subscriptions, activities, notifications, and routing rules. Every message that an Oracle E-Business Suite user receives as a notification, or that the workflow engine raises programmatically, must first be defined as a row in WF_MESSAGES, keyed by the composite identifier of message TYPE and NAME.

Within a data-vault-style modeling view, the table behaves as a hub. It anchors a stable business key—the type/name pair—and serves as the reference point to which translation, attribute, notification, activity, and routing-rule satellites and links attach. Treated as a heuristic classification rather than a mandated design, this hub characterization reflects the table's role as the canonical registry of message identity within the Workflow schema.

Key Information Stored

The primary key is WF_MESSAGES_PK, defined on the composite business key (TYPE, NAME); the documented physical schema lists a unique index of (TYPE, NAME, ZD_EDITION_NAME) reflecting the editioning column present in 12.2.x. The most significant columns are:

• TYPE — the owning workflow item type; also a foreign key to WF_ITEM_TYPES and part of the primary key.
• NAME — the internal message name, unique within a type and part of the primary key.
• PROTECT_LEVEL — the customization protection level controlling who may modify the definition.
• CUSTOM_LEVEL — the customization level applied to the message.
• DEFAULT_PRIORITY — the standard priority assigned to notifications raised from this message.
• READ_ROLE — the role or privilege required to read the message.
• WRITE_ROLE — the role or privilege required to modify the message.
• SECURITY_GROUP_ID — the security group to which the definition belongs, referencing FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the editioning identifier used in the 12.2.x schema.

The translatable text—subject, body, and description—is not held here; it is stored in WF_MESSAGES_TL, joined on (TYPE, NAME).

Common Use Cases and Queries

Typical diagnostic and reporting scenarios include locating all messages under a given item type, identifying a message's default priority for notification tuning, and auditing customization levels before applying patches.

• Listing messages for an item type: SELECT TYPE, NAME, DEFAULT_PRIORITY FROM WF_MESSAGES WHERE TYPE = :item_type ORDER BY NAME;
• Resolving display text: join WF_MESSAGES to WF_MESSAGES_TL on TYPE and NAME, filtering by a specific LANGUAGE, to report message subject and body.
• Identifying heavily used messages: aggregate WF_NOTIFICATIONS by MESSAGE_TYPE and MESSAGE_NAME to rank notification volume.
• Diagnosing notification delivery failures by combining message definitions with routing rules and notification status.

These queries are common in upgrade readiness checks and workflow troubleshooting in both 12.1.1 and 12.2.2 environments.

Related Objects

• WF_ITEM_TYPES — parent of TYPE; establishes the owning workflow process.
• WF_MESSAGES_TL — translation table holding subject, body, and description text.
• WF_MESSAGE_ATTRIBUTES — defines the attribute structure of each message (MESSAGE_TYPE, MESSAGE_NAME).
• WF_NOTIFICATIONS — the runtime notifications generated from messages (MESSAGE_TYPE, MESSAGE_NAME).
• WF_ROUTING_RULES — routing definitions that reference messages (MESSAGE_TYPE, MESSAGE_NAME).
• WF_ACTIVITIES — activities that emit messages (ITEM_TYPE, MESSAGE).
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID.

Together these objects form the workflow messaging backbone that drives notification content and delivery across Oracle EBS.