Search Results recipient_role_name

Overview

The APPS.WF_NOTIFICATIONS_VIEW object is a documented database view in Oracle E-Business Suite, owned by the APPS schema and catalogued under the FND – Application Object Library product. According to the ETRM metadata (validated against 12.1.1 and 12.2.2), its description is "All notification information." The view consolidates the core workflow notification record with derived, human-readable attributes, exposing both the raw Workflow notification data and decoded values such as the notification subject, message body, recipient role display name, and status meaning.

Its primary role is to serve as a single, query-friendly source for Oracle Workflow notification data used in reporting, operational monitoring, and integration. Rather than joining multiple Workflow tables and packages manually, consumers query WF_NOTIFICATIONS_VIEW to obtain notification identifiers, routing information, status codes and their meanings, dates, and rendered message content in one place. The user's search term, status_name, corresponds directly to one of the view's exposed columns, which translates the internal STATUS code into a descriptive lookup meaning.

Underlying Base Objects

The documented implementation text defines the view as a two-table join against WF_NOTIFICATIONS (referenced as a synonym) and WF_LOOKUPS (a view), augmented by packaged function calls. The base and referenced objects are:

• WF_NOTIFICATIONS (SYNONYM) – the primary source of notification rows, aliased as N.
• WF_LOOKUPS (VIEW) – aliased as L; joined on LOOKUP_TYPE = 'WF_NOTIFICATION_STATUS' and LOOKUP_CODE = N.STATUS to derive STATUS_NAME.
• WF_NOTIFICATION (PACKAGE) – supplies GETSUBJECT and GETSHORTBODY for the SUBJECT and MESSAGE columns.
• WF_DIRECTORY (PACKAGE) – supplies GETROLEDISPLAYNAME for the RECIPIENT_ROLE_NAME column.

The join ensures each notification row is enriched: the lookup join resolves the status code to its display meaning, while the package functions resolve role names and render notification text. Because the view depends on PL/SQL package functions, its rows are computed at query time.

Key Columns

The view exposes twenty columns. The most significant include:

• ROW_ID – the ROWID of the underlying WF_NOTIFICATIONS row.
• NOTIFICATION_ID – unique identifier of the notification.
• GROUP_ID – grouping identifier for related notifications.
• MESSAGE_TYPE / MESSAGE_NAME – the message definition driving the notification.
• RECIPIENT_ROLE – the role receiving the notification.
• STATUS – the internal notification status code (e.g., OPEN, CLOSED).
• STATUS_NAME – the decoded meaning of STATUS via WF_LOOKUPS; this is the column matching the "status_name" search.
• MAIL_STATUS / PRIORITY – delivery and priority attributes.
• BEGIN_DATE, END_DATE, DUE_DATE – lifecycle and due-date timestamps.
• SUBJECT – rendered notification subject (WF_NOTIFICATION.GETSUBJECT).
• MESSAGE – short notification body (WF_NOTIFICATION.GETSHORTBODY).
• RECIPIENT_ROLE_NAME – display name for the recipient role (WF_DIRECTORY.GETROLEDISPLAYNAME).

Common Use Cases and Queries

Typical scenarios include monitoring open notifications, reporting by status, and auditing notification volume per recipient. A representative query filters on the decoded status name, which is exactly what the "status_name" search implies:

• Open notification listing: SELECT NOTIFICATION_ID, SUBJECT, RECIPIENT_ROLE_NAME, STATUS_NAME FROM APPS.WF_NOTIFICATIONS_VIEW WHERE STATUS_NAME = 'Open';
• Per-recipient workload: SELECT RECIPIENT_ROLE_NAME, COUNT(*) FROM APPS.WF_NOTIFICATIONS_VIEW GROUP BY RECIPIENT_ROLE_NAME;
• Due-date analysis: SELECT NOTIFICATION_ID, DUE_DATE, STATUS_NAME FROM APPS.WF_NOTIFICATIONS_VIEW WHERE DUE_DATE < SYSDATE AND STATUS_NAME = 'Open';

Because STATUS_NAME and SUBJECT/MESSAGE rely on lookups and package calls, queries should account for the associated execution cost and follow standard APPS-schema access and security conventions.