Search Results wf_notification_status




Overview
Explore in AI Chat

Overview

APPS.XDP_FMC_V is a reporting and integration view within the Oracle E-Business Suite Workflow schema, exposed under the APPS synonym layer. It presents a denormalized, human-readable projection of the Workflow Notification runtime table, WF_NOTIFICATIONS, by joining each notification row to the WF_LOOKUPS lookup table for the lookup type WF_NOTIFICATION_STATUS. In doing so, the view resolves the internal single-character status code stored on the notification into its descriptive meaning (for example, OPEN, CLOSED, CANCELED, or ERROR), which is otherwise unintelligible without a secondary lookup.

The view is documented for E-Business Suite releases 12.1.1 and 12.2.2 and is referred to by Oracle as an "FMC" (Forms/Message Center) view, reflecting its role in surfacing notification data to notification monitoring tools, the Workflow Administrator responsibility, and custom reports. The object exposes the ROWID of the underlying WF_NOTIFICATIONS row as its first selected column, which is significant for tools that require a unique row identifier for updateable or drill-down cursors. The user search term wf_notification_status maps directly to the lookup type used in this view's WHERE clause, making this object the canonical join point for status-decoded notification reporting.

Underlying Base Objects

The view is defined with a two-object join: WF_NOTIFICATIONS (documented in ETRM as the base object, exposed to APPS as a synonym) and WF_LOOKUPS (documented as a view). WF_NOTIFICATIONS is the transactional store for Workflow notification instances, holding recipient, message, priority, and lifecycle data. WF_LOOKUPS supplies the lookup code-to-meaning mapping maintained by the Workflow lookup type WF_NOTIFICATION_STATUS.

The join predicate is strictly equi-join on L.LOOKUP_CODE = N.STATUS combined with the constant filter L.LOOKUP_TYPE = 'WF_NOTIFICATION_STATUS'. Because WF_LOOKUPS is itself a view over the FND lookup infrastructure, the effective dependency chain is APPS.XDP_FMC_V to WF_LOOKUPS to the underlying FND_LOOKUP_VALUES storage. No outer join is used: notifications whose STATUS value has no matching lookup row are excluded from the result set, a behavior worth noting when auditing data integrity.

Key Columns

  • ROWID — ROWID of the WF_NOTIFICATIONS row; useful as a surrogate key for cursor updates and drill-down.
  • NOTIFICATION_ID — Primary identifier of the notification; the standard join key to WF_NOTIFICATION_ATTRIBUTES and workflow history tables.
  • GROUP_ID — Groups related notifications dispatched together.
  • MESSAGE_TYPE / MESSAGE_NAME — Identifies the workflow item type and message that generated the notification.
  • RECIPIENT_ROLE — The role or user receiving the notification.
  • STATUS — Raw code held in WF_NOTIFICATIONS.
  • MEANING — Decoded status text sourced from WF_LOOKUPS; this is the user-facing value.
  • MAIL_STATUS, PRIORITY, ACCESS_KEY — Delivery state, priority ranking, and secure access token.
  • BEGIN_DATE, END_DATE, DUE_DATE — Lifecycle timestamps for aging and SLA reporting.
  • USER_COMMENT, CALLBACK, CONTEXT — Respondent comment, response callback, and context payload.

Common Use Cases and Queries

The most frequent scenario is status-decoded notification reporting, especially reconciling open versus closed notifications for a recipient or workflow type.

  • List open notifications for a role: SELECT notification_id, message_name, meaning, due_date FROM apps.xdp_fmc_v WHERE recipient_role = :role AND status = 'OPEN' ORDER BY due_date;
  • Status distribution: SELECT meaning, COUNT(*) FROM apps.xdp_fmc_v GROUP BY meaning;
  • Aging analysis using the decoded status: SELECT notification_id, meaning, SYSDATE - begin_date days_open FROM apps.xdp_fmc_v WHERE status = 'OPEN';
  • Joining to attributes for troubleshooting: SELECT v.notification_id, v.meaning, a.name, a.text_value FROM apps.xdp_fmc_v v, wf_notification_attributes a WHERE a.notification_id = v.notification_id;

Because the view filters on the WF_NOTIFICATION_STATUS lookup type, it is the recommended access path whenever notification status must be displayed in its decoded form rather than as a raw code.