Search Results po_notifications_sv3




Overview
Explore in AI Chat

Overview

APPS.PO_WF_NOTIFICATIONS_V is a Purchasing-family reporting view that consolidates Oracle Workflow notification data with purchasing document header information. It exists to answer a specific operational question: which workflow notifications are outstanding, or have been actioned, against a given purchasing document, and who is the recipient, what is the document worth, and what is its approval state. The view joins the Workflow notification tables to PO_HEADERS and PO_ACTION_HISTORY, so each row represents a notification tied to a purchasing document at a particular point in its approval path.

Because the object is a view and not a table, it carries no storage of its own. All values are resolved at query time, and several columns are computed by calling PL/SQL functions from the PO_NOTIFICATIONS_SV3 package and the WF_NOTIFICATION and WF_DIRECTORY packages. This makes the view convenient for ad hoc querying and for forms or concurrent programs that need a flattened notification-plus-document record, but it also means query performance is sensitive to the underlying function calls and to the selectivity of the driving Workflow tables.

Use of the view is confined to the APPS schema context. It is not intended to be updated, and it should be treated strictly as a read-only reporting and diagnostic object.

Underlying Base Objects

The view is defined over synonyms and package objects rather than directly over tables. The documented base objects are WF_NOTIFICATIONS, WF_ITEM_ACTIVITY_STATUSES, WF_USERS, WF_NOTIFICATION (package), WF_DIRECTORY (package), PO_HEADERS, PO_HEADERS_ALL, PO_ACTION_HISTORY, PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_NOTIFICATIONS_SV3 (package), PO_CORE_S2 (package), PO_RELEASES and PO_REQUISITION_HEADERS.

Structurally, WF_NOTIFICATIONS is the master table for individual notifications, and WF_ITEM_ACTIVITY_STATUSES links a notification to the workflow item and activity that produced it. WF_USERS supplies the originating system identifier. PO_HEADERS provides the purchasing document attributes — segment1, agent, currency, type lookup code, authorization status and the workflow item key and type used to correlate to Workflow. PO_ACTION_HISTORY carries the approval path, request, program and revision information. PO_DOCUMENT_TYPES_ALL_B and _TL provide the security and access level codes and the translated document type name.

The join predicates restrict results to document types 'PO' and 'PA', to action history rows where ACTION_CODE is null, and to activity statuses of 'NOTIFIED'. The correlation between Workflow and Purchasing is performed on WF_ITEM_TYPE and WF_ITEM_KEY against the PO_HEADERS workflow item columns.

Key Columns

Identification columns include NOTIFICATION_ID, GROUP_ID, MESSAGE_TYPE and MESSAGE_NAME from WF_NOTIFICATIONS, plus PO_HEADER_ID, SEGMENT1 and WF_ITEM_KEY from PO_HEADERS. Recipient information is exposed through RECIPIENT_ROLE and its display name, with ORIGINAL_RECIPIENT resolved via PO_NOTIFICATIONS_SV3.GET_WF_ROLE_ID into FROM_ID and FROM_EMPLOYEE_NAME.

Common Use Cases and Queries

Typical uses include open-notification reporting for a buyer or operating unit, auditing approval routing and revision history, and diagnosing stalled document approvals.

SELECT notification_id, segment1, recipient_role_name,
       subject, doc_status_dsp, due_date
FROM   apps.po_wf_notifications_v
WHERE  org_id = :p_org_id
AND    status = 'OPEN'
ORDER BY due_date;

SELECT segment1, type_name, amount, currency_code,
       doc_owner, approval_path_id, sequence_num
FROM   apps.po_wf_notifications_v
WHERE  po_header_id = :p_po_header_id
ORDER BY sequence_num;

Because SUBJECT, MESSAGE, AMOUNT and the display-name columns invoke package functions per row, queries should always filter on indexed columns such as PO_HEADER_ID, NOTIFICATION_ID or ORG_ID before projecting those computed columns. Broad unfiltered scans over the view are discouraged.