Search Results placed_on_ng_flag




Overview
Explore in AI Chat

Overview

APPS.POR_VIEW_REQS_TO_APPR_V is a Self-Service Web Application view in Oracle E-Business Suite, registered under FND Design Data ICX.POR_VIEW_REQS_TO_APPR_V and owned by the APPS schema. Its documented purpose is to supply data to the "Orders to Approve" query on the Approvals page of the iProcurement/Procurement Self-Service responsibility. In the 12.1.1 and 12.2.2 releases the object carries a VALID status and is implemented as a view, not a table, so it materialises no data of its own and inherits its transactional state entirely from the underlying purchasing and Workflow tables.

The view is structurally a requisition-approval worklist: it joins requisition header data to the Workflow notification that represents the pending approval task, resolves the current approver identity through FND_GLOBAL and WF_USER_ROLES, and exposes a small, display-oriented column set. It is read-only in practice and is referenced by no other database object, which confirms its role as a terminal presentation layer rather than a reusable integration point.

Underlying Base Objects

The ETRM dependency listing shows the view resolving against the following APPS synonyms, views, and packages:

  • PO_REQUISITION_HEADERS — the primary source of requisition identity, number, description, and authorization status.
  • WF_NOTIFICATIONS and WF_NOTIFICATION_ATTRIBUTES — the approval task and its contextual attributes; these supply the notification identifier (NID).
  • WF_USER_ROLES — resolves the role or user holding the notification, restricting rows to the current approver's worklist.
  • FND_GLOBAL (package) — provides session context such as the effective user and responsibility, which is what makes the "Orders to Approve" list user-specific.
  • AP_CARDS — the source of the procurement card number, evidencing that the view supports p-card requisitions.
  • PO_DOCUMENT_TYPES, PO_LOOKUP_CODES, and GL_SETS_OF_BOOKS — supporting reference data for document type, lookup meaning, and ledger context.
  • FINANCIALS_SYSTEM_PARAMETERS and PER_ALL_PEOPLE_F — application-level settings and the person/employee record used for display.
  • POR_VIEW_REQS_PKG (package) — documented dependent code that encapsulates part of the selection or formatting logic.

Key Columns

The view exposes eleven columns, several of which are display strings rather than raw codes:

  • REQ_HEADER_ID (NUMBER) — the unique requisition identifier and the natural join key back to PO_REQUISITION_HEADERS.
  • REQUISITION_NUMBER (VARCHAR2 20) — the user-facing requisition number.
  • DESCRIPTION (VARCHAR2 240) — requisition description.
  • STATUS_CODE (VARCHAR2 25) and STATUS (VARCHAR2 80) — the authorization status code and its translated display value.
  • PCARD_NUMBER (VARCHAR2 80) — the procurement card number, populated from AP_CARDS. This is the column users most frequently search for, because p-card requisitions must be routed to the correct cardholder or approver.
  • CREATION_DATE (DATE) — the standard Who column.
  • PLACED_ON_SO_FLAG (VARCHAR2) and PLACED_ON_NG_FLAG (VARCHAR2 4000) — flags indicating whether the requisition has been placed on a sourcing event or a negotiation; the 4000-character width on the negotiation flag reflects an aggregated or concatenated value.
  • EMERGENCY_PO_NUM (VARCHAR2 20) — the reserved PO number for emergency requisitions.
  • NID (NUMBER) — the Workflow notification identifier, which is the bridge to the approval response forms.

Common Use Cases and Queries

Typical use is troubleshooting or auditing an approver's pending requisition worklist, or locating requisitions tied to a specific procurement card. Because the view is filtered by FND_GLOBAL session context, queries run as a privileged user may return only that session's rows; concurrent-program or SYSADMIN-level queries should therefore be interpreted with care.

  • List an approver's pending items: 
    SELECT requisition_number, description, status, pcard_number, nid
FROM   apps.por_view_reqs_to_appr_v
ORDER  BY creation_date;
  • Find p-card requisitions by card: 
    SELECT requisition_number, pcard_number, status, req_header_id
FROM   apps.por_view_reqs_to_appr_v
WHERE  pcard_number = :pcard_number;
  • Identify emergency requisitions carrying a reserved PO number: 
    SELECT requisition_number, emergency_po_num, status
FROM   apps.por_view_reqs_to_appr_v
WHERE  emergency_po_num IS NOT NULL;

For historical or cross-approver reporting beyond session scope, query PO_REQUISITION_HEADERS and the Workflow notification tables directly, or use the EBS-standard requisition approval reports, rather than relying on this Self-Service view.