Search Results notification_status

Overview

APPS.PO_WF_NOTIFICATIONS_V is a Purchasing (PO) module reporting view that consolidates Oracle Workflow notification data with Purchasing document context. Its stated purpose is to surface "information about purchase orders, releases and requisitions that have outstanding notifications." In practice, the view joins the Workflow notification layer (WF_NOTIFICATIONS, WF_ITEM_ACTIVITY_STATUSES, and Workflow PL/SQL APIs) to the Purchasing document layer (PO_HEADERS, PO_ACTION_HISTORY, and PO_DOCUMENT_TYPES_ALL_TL). This makes it a convenient single source for identifying documents stuck in an approval or notification cycle, rather than querying Workflow and Purchasing tables separately.

The view is owned by the APPS schema and is marked VALID in the ETRM dictionary for 12.1.1 and 12.2.2. Because it exposes workflow notification identifiers alongside PO header identifiers, it is frequently used in reporting, dashboards, and integration scripts that monitor outstanding approvals and notification backlog.

Underlying Base Objects

The documented base objects include WF_NOTIFICATIONS, WF_ITEM_ACTIVITY_STATUSES, PO_HEADERS, PO_HEADERS_ALL, PO_ACTION_HISTORY, PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_RELEASES, PO_REQUISITION_HEADERS, and WF_USERS. Supporting PL/SQL packages referenced in the view text are PO_NOTIFICATIONS_SV3, PO_CORE_S2, WF_NOTIFICATION, and WF_DIRECTORY.

The central join links PO_HEADERS.PO_HEADER_ID to PO_ACTION_HISTORY.OBJECT_ID where the action code is null, and connects the workflow item (WF_ITEM_TYPE/WF_ITEM_KEY) to the matching WF_ITEM_ACTIVITY_STATUSES row with an activity status of NOTIFIED. Document type descriptions are resolved through PO_DOCUMENT_TYPES_ALL_TL, restricted to document type codes of PO and PA.

Key Columns

• NOTIFICATION_ID, GROUP_ID, MESSAGE_TYPE, MESSAGE_NAME — Workflow notification identity.
• RECIPIENT_ROLE, RECIPIENT_ROLE_NAME — the role/user notified; resolved via WF_DIRECTORY.GETROLEDISPLAYNAME.
• SUBJECT and MESSAGE — derived through WF_NOTIFICATION.GETSUBJECT and GETSHORTBODY.
• STATUS, MAIL_STATUS, BEGIN_DATE, END_DATE, DUE_DATE — notification state and timing.
• PO_HEADER_ID, SEGMENT1 — PO document number and internal identifier.
• AMOUNT, CURRENCY_CODE — document value and its currency. Note this view exposes CURRENCY_CODE directly from PO_HEADERS; there is no GET_BASE_CURRENCY column here. Base currency conversion requires joining to PO_CURRENCIES or calling currency APIs separately.
• TYPE_NAME, TYPE_LOOKUP_CODE, AUTHORIZATION_STATUS — document classification and approval state.
• WF_ITEM_KEY, WF_ITEM_TYPE — workflow correlation keys.
• OBJECT_TYPE_CODE, OBJECT_SUB_TYPE_CODE, APPROVAL_PATH_ID, ORG_ID — routing and multi-org context.

Common Use Cases and Queries

A typical query lists outstanding notifications for purchase orders and releases:

SELECT notification_id, segment1, type_name, authorization_status,
       currency_code, amount, recipient_role_name, due_date
FROM   apps.po_wf_notifications_v
WHERE  org_id = :p_org_id
AND    status = 'OPEN'
ORDER BY due_date;

Because the view carries no base-currency column, users searching for get_base_currency should join PO_HEADERS currency data or use the standard currency conversion APIs. The view is best suited for notification monitoring, approval aging reports, and integration polling for stuck documents.