Search Results plc_auth




Overview
Explore in AI Chat

Overview

POR_VIEW_REQS_TO_APPR_V is an Oracle iProcurement (ICX) view owned by the APPS schema that presents the set of purchase requisitions currently awaiting approval by a given user. Its purpose is to drive the "Orders to Approve" region of the iProcurement home page, associating open workflow approval notifications with the underlying requisition header and the authorization status of the document. The view is defined as a UNION ALL query; the documented excerpt covers the first branch, which resolves approvals tied to a user's responsibility (FND_RESP role), while a second branch handles role-based group box users.

The view is read-only and is not a stored table; it reflects the live state of open workflow notifications at query time. Because it depends on FND_GLOBAL.USER_NAME, results are always scoped to the session's currently logged-in user, making it unsuitable for cross-user administrative reporting without session context changes.

Underlying Base Objects

Key Columns

  • REQUISITION_HEADER_ID — surrogate key of the requisition; used for drill-down navigation.
  • SEGMENT1 — the requisition number, also matched against the workflow notification's DOCUMENT_NUMBER attribute.
  • DESCRIPTION — requisition header description.
  • AUTHORIZATION_STATUS and DISPLAYED_FIELD — internal status code and its translated display value.
  • CARD_NUMBER — procurement card number, when applicable.
  • CREATION_DATE — date the requisition was created.
  • TRANSFERRED_TO_OE_FLAG — indicates whether the requisition has been transferred to Order Entry.
  • IS_PLACEDONNG — derived flag from POR_VIEW_REQS_PKG indicating a placed order.
  • EMERGENCY_PO_NUM — emergency purchase order number, if any.
  • NOTIFICATION_ID — the open workflow notification identifier, enabling approve/reject actions.

Common Use Cases and Queries

The principal use case is retrieving all requisitions awaiting the current user's approval. A typical query would be:

  • SELECT segment1, description, displayed_field, creation_date FROM por_view_reqs_to_appr_v ORDER BY creation_date DESC;
  • SELECT requisition_header_id, notification_id, emergency_po_num FROM por_view_reqs_to_appr_v WHERE transferred_to_oe_flag = 'N';

Because PO_DOCUMENT_TYPES constrains the workflow MESSAGE_TYPE, the view only returns documents whose approval item types are defined in that table — reinforcing that "po_document_types" is central to the view's filtering logic. The view is used for approval-list rendering, notification counts, and workflow-driven drill-down rather than for general purchasing analytics.