Search Results wf_notification_attr_resp_v




Overview
Explore in AI Chat

Overview

The WF_NOTIFICATION_ATTR_RESP_V view is an Oracle Application Object Library (FND) reporting object shipped under the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose information for notifications that have been responded to and are closed. The view filters the Oracle Workflow notification store to the subset of notifications whose status equals CLOSED, and joins those notifications to their message attribute definitions restricted to the RESPOND subtype. The practical effect is a flattened, query-friendly projection of the response payload captured when a recipient acts upon a notification. Because it is a view over core Workflow tables rather than a product-specific transactional table, it functions as a cross-module accessibility layer: any application, concurrent program, or external integration can read responded notification metadata without needing to reconstruct the multi-table Workflow schema. This makes it particularly useful for workflow auditing, approval trail reporting, and integration extracts where the response attribute value and the responding recipient role must be retrieved together.

Underlying Base Objects

The view text defines a three-way join across the Workflow notification and attribute stores, with supporting function and lookup calls. The documented base objects are:

  • WF_NOTIFICATIONS (referenced as a synonym) — supplies the notification header, including status, message type, message name, and notification identifier. The predicate WFN.STATUS = 'CLOSED' restricts output to responded and closed notifications.
  • WF_NOTIFICATION_ATTRIBUTES (referenced as a synonym) — supplies the attribute rows linked by NOTIFICATION_ID, providing the attribute name and text value.
  • WF_MESSAGE_ATTRIBUTES_VL (documented as a VIEW) — the message attribute definition view, joined on message type, message name, and attribute name, and filtered by SUBTYPE = 'RESPOND' to isolate response attributes. It also provides the display name.
  • WF_DIRECTORY (documented as a PACKAGE) — invoked as WF_DIRECTORY.GETROLEDISPLAYNAME to translate the recipient role into a human-readable display name.
  • WF_NOTIFICATION (documented as a PACKAGE) — invoked as WF_NOTIFICATION.GETSHORTTEXT to produce the attribute display value from the attribute name and notification identifier.

Both WF_NOTIFICATIONS and WF_NOTIFICATION_ATTRIBUTES are documented as synonyms in the ETRM metadata, resolving to the underlying Workflow base tables.

Key Columns

The view exposes the following documented columns:

  • GROUP_ID — the notification group identifier, used for grouping related notifications.
  • RECIPIENT_ROLE — the role that received and responded to the notification. This is the column most directly associated with the search term recipient_role, and it is the value passed to GETROLEDISPLAYNAME.
  • RECIPIENT_ROLE_DISPLAY_NAME — the resolved display name of the recipient role.
  • ATTRIBUTE_NAME — the internal name of the responded attribute.
  • ATTRIBUTE_DISPLAY_NAME — the display label of the attribute from the message attribute definition.
  • ATTRIBUTE_VALUE — the short-text value returned by GETSHORTTEXT for the attribute.
  • ATTRIBUTE_DISPLAY_VALUE — the attribute display value.
  • MESSAGE_TYPE and MESSAGE_NAME — the workflow message identifying the notification definition.

Common Use Cases and Queries

Typical scenarios include auditing approval responses, reporting responder activity by role, and extracting response values for downstream integration. A common query retrieves all responded attributes for a given message:

  • SELECT recipient_role, recipient_role_display_name, attribute_name, attribute_value FROM wf_notification_attr_resp_v WHERE message_name = :p_message_name ORDER BY recipient_role;
  • Filtering by responder: SELECT ... WHERE recipient_role = :p_role AND message_type = :p_type;
  • Joining back to WF_NOTIFICATIONS on group or notification context to correlate the response with the original notification subject and dates.

Because GETSHORTTEXT and GETROLEDISPLAYNAME are PL/SQL function calls embedded in the view, queries against large notification volumes should be constrained by message type, name, or recipient role to avoid unnecessary function invocation.