Search Results wf_notification_attributes

Overview

The WF_NOTIFICATION_ATTRIBUTES table is a core data object within the Oracle E-Business Suite (EBS) Workflow technology stack. Owned by the APPLSYS schema and part of the Application Object Library (FND) module, this table serves as the persistent store for all attribute data associated with workflow notifications. Its primary role is to hold the specific runtime values for attributes defined in a notification message template at the moment a notification is sent. This enables the dynamic, personalized content within notifications, such as item numbers, dates, or approval comments, to be stored, retrieved, and displayed to the end-user within the Workflow Notification Mailer or the EBS user interface.

Key Information Stored

The table's structure is designed to associate dynamic attribute values with a specific notification instance. The primary key, WF_NOTIFICATIONS_ATTR_PK, is a composite key on NOTIFICATION_ID and NAME, ensuring unique attribute storage per notification. The NOTIFICATION_ID column is a foreign key that links the attribute data to its parent notification record in the WF_NOTIFICATIONS table. The NAME column stores the internal name of the workflow attribute as defined in the workflow process. The VALUE column, while not explicitly listed in the provided metadata but standard in this table, is the most critical, as it holds the actual runtime data for the attribute. Other typical columns include TYPE for the attribute datatype and TEXT_VALUE for longer text data, facilitating the storage of diverse information types required by business processes.

Common Use Cases and Queries

A primary use case is troubleshooting or auditing notification content. For instance, to retrieve all attribute data for a specific notification to verify what information was sent, a developer or administrator might execute a query joining to WF_NOTIFICATIONS. Another common scenario is generating custom reports on workflow history, extracting specific attribute values like purchase order numbers or approval statuses from past notifications. A sample query pattern is:

• SELECT wna.notification_id, wna.name, wna.value FROM apps.wf_notification_attributes wna WHERE wna.notification_id = &NOTIFICATION_ID;

This table is also central when the Workflow Notification Mailer processes and assembles notifications for delivery, reading the stored attributes to populate the final message body.

Related Objects

The WF_NOTIFICATION_ATTRIBUTES table has a direct and documented foreign key relationship with the WF_NOTIFICATIONS table, which is its central parent object. The relationship is defined as follows:

• Foreign Key from WF_NOTIFICATION_ATTRIBUTES to WF_NOTIFICATIONS: The NOTIFICATION_ID column in WF_NOTIFICATION_ATTRIBUTES references the NOTIFICATION_ID column in WF_NOTIFICATIONS. This ensures every attribute record is linked to a valid notification instance. Deletion of a notification typically cascades to delete its associated attribute records.

This table is also intrinsically linked to the underlying workflow engine tables (WF_ITEMS, WF_PROCESS_ACTIVITIES) and is commonly accessed via the public Workflow APIs, such as those in the WF_NOTIFICATION package, which provide a supported interface for reading and manipulating this data.