Results for “wf_notifications”

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

Overview

WF_NOTIFICATIONS is the core runtime table in the Oracle EBS Workflow (WF) schema that stores every notification sent by the Workflow Engine. Owned by APPLSYS and classified under the FND — Application Object Library product, it acts as the transactional record of messages dispatched to users, roles, or groups as part of a workflow process. Each row represents a single notification instance, capturing its recipient, associated workflow item, message definition, delivery status, response data, and any attribute values passed through the notification's message template.

Because notifications drive human interaction with Oracle Workflow — approvals, FYI messages, and response-required actions — this table is central to Workflow monitoring, approval-chain diagnostics, and notification reconciliation. Under a Data Vault heuristic classification, WF_NOTIFICATIONS leans toward a hub role: its primary key, NOTIFICATION_ID, is a surrogate identifier that anchors linkages from multiple dependent and status-tracking tables, including WF_NOTIFICATION_ATTRIBUTES and the activity status tables. Practitioners modeling this data should treat NOTIFICATION_ID as the stable hub key, with descriptors and status transitions modeled as dependent detail.

Key Information Stored

The table contains 87 documented columns. The surrogate primary key is NOTIFICATION_ID, enforced by the unique index WF_NOTIFICATIONS_PK. Among the most significant columns are:

• NOTIFICATION_ID — surrogate primary key uniquely identifying each notification.
• GROUP_ID — groups related notifications emanating from a single workflow event.
• MESSAGE_TYPE and MESSAGE_NAME — identify the message template definition; these also form the foreign key to WF_MESSAGES.
• RECIPIENT_ROLE and ORIGINAL_RECIPIENT — the resolved recipient of the notification.
• STATUS — the current lifecycle state (Open, Closed, Cancelled, etc.).
• MAIL_STATUS — delivery state of the emailed copy.
• ACCESS_KEY — token used to authenticate the recipient's response.
• BEGIN_DATE, END_DATE, DUE_DATE, SENT_DATE — key temporal markers governing notification validity and delivery.
• RESPONDER, USER_COMMENT, and CALLBACK — capture the response and any processing callback.
• FROM_USER, TO_USER, and SUBJECT — presentation-level addressing content.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling visibility.
• ITEM_KEY and USER_KEY — correlate the notification to its workflow item instance.
• The TEXT_ATTRIBUTE1-10, NUMBER_ATTRIBUTE1-5, DATE_ATTRIBUTE1-5, URL_ATTRIBUTE1-5, and FORM_ATTRIBUTE1-5 columns carry the message's runtime substitution values; the parallel PROTECTED_* columns hold their encrypted counterparts.

Common Use Cases and Queries

WF_NOTIFICATIONS supports notification monitoring, approval audit, and system performance analysis. Common reporting scenarios include identifying stalled open notifications, reconciling email delivery failures, and auditing approver responses.

Typical query pattern for open notifications by recipient:

SELECT n.notification_id, n.recipient_role, n.subject, n.begin_date
FROM   apps.wf_notifications n
WHERE  n.status = 'OPEN'
AND    n.recipient_role = :user_name;

To trace all notifications tied to a workflow item:

SELECT notification_id, message_name, status, sent_date
FROM   apps.wf_notifications
WHERE  item_key = :item_key
ORDER BY sent_date;

Reporting often joins WF_NOTIFICATIONS to WF_NOTIFICATION_ATTRIBUTES to extract business context (for example, PO numbers or amounts embedded in text attributes), and to WF_ITEM_ACTIVITY_STATUSES for approval-step context.

Related Objects

• WF_MESSAGES — referenced via WF_NOTIFICATIONS.MESSAGE_TYPE and MESSAGE_NAME; defines the notification template.
• FND_SECURITY_GROUPS — referenced via WF_NOTIFICATIONS.SECURITY_GROUP_ID.
• WF_NOTIFICATION_ATTRIBUTES — child table joined on NOTIFICATION_ID, storing per-notification attribute values.
• WF_ITEM_ACTIVITY_STATUSES — references WF_NOTIFICATIONS.NOTIFICATION_ID, linking notifications to activity steps.
• WF_ITEM_ACTIVITY_STATUSES_H — the history counterpart, also keyed on NOTIFICATION_ID.
• Workflow Notification APIs (WF_NOTIFICATION package) — programmatic creation, query, and closure of notifications in this table.