Search Results po_requisition_headers




Overview
Explore in AI Chat

Overview

POR_RCV_HOME_REQS_V is a view owned by the APPS schema within the Oracle iProcurement (ICX) product family. Its documented purpose is to query requisitions that are surfaced on the receiving home page, presenting a consolidated, denormalized picture of requisition demand that is either expected as an external purchase order shipment or as an internal inventory shipment. In Oracle EBS 12.1.1 and 12.2.2 this view acts primarily as a reporting and UI-support construct rather than a transactional object; no DML is expected against it, and it is consumed by the receiving home page region to show the user the requisition lines awaiting receipt.

The view is relevant to users who search on the term po_requisition_headers because its driving table is PO_REQUISITION_HEADERS (referenced in the metadata as the synonym PO_REQUISITION_HEADERS under the APPS schema). The view resolves requisition header attributes and joins them forward through requisition lines and purchase order or shipment line structures, so it answers the question: which of my requisitions have receipt-qualifying demand remaining?

Underlying Base Objects

Documented referenced base objects include PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, PO_HEADERS_ALL, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_DISTRIBUTIONS_TRX_V, PO_VENDORS, RCV_SHIPMENT_LINES, HR_ALL_ORGANIZATION_UNITS_TL, MTL_SYSTEM_ITEMS, and the packages PO_INQ_SV and PO_CLM_INTG_GRP. The transactional joins map requisition headers to requisition lines, then to line locations and distributions, then to purchase order headers and vendors, filtered by receiving routing.

Structurally the view is a UNION ALL of two branches. The first branch joins PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_LINE_LOCATIONS, PO_HEADERS, PO_DISTRIBUTIONS, and PO_VENDORS, restricting demand to line locations that are approved, not cancelled, not finally closed, of shipment type STANDARD, BLANKET, or SCHEDULED, with a receiving routing identifier of 3, and with a positive open quantity (ordered minus delivered minus cancelled). The second branch covers internal inventory requisitions, joining requisition headers and lines to RCV_SHIPMENT_LINES and HR_ALL_ORGANIZATION_UNITS, with routing header 3 and shipped quantity exceeding received quantity. This union design is what allows a single home page query to blend external purchasing demand with internal inventory replenishment demand.

Key Columns

  • REQUISITION_HEADER_ID — the primary identifier of the requisition header, linking back to PO_REQUISITION_HEADERS.
  • SEGMENT1 — the human-readable requisition number.
  • DESCRIPTION — the requisition header description.
  • PREPARER_ID — the user who prepared the requisition.
  • TO_PERSON_ID — the requisition line requestor/deliver-to person.
  • ORDER_NUM — the purchase order number for externally sourced demand; for inventory-sourced rows this is populated via the PO_INQ_SV.GET_SO_NUMBER call rather than a purchase order.
  • VENDOR — the vendor name for purchase order demand; for inventory demand the organization unit name is returned instead.

Common Use Cases and Queries

The principal use case is the receiving home page listing requisition demand pending receipt. A secondary use is ad hoc reporting on open, receipt-eligible requisition activity across purchasing and inventory sourcing.

SELECT requisition_header_id, segment1, description,
       preparer_id, to_person_id, order_num, vendor
  FROM apps.por_rcv_home_reqs_v
 WHERE segment1 = :requisition_number;

Because the view already filters for open, approved, unclosed, receipt-eligible demand, no additional quantity filtering is normally required. A typical analyst query aggregates by vendor or order number to see outstanding receipt workload:

SELECT vendor, order_num, COUNT(*) req_lines
  FROM apps.por_rcv_home_reqs_v
 GROUP BY vendor, order_num;

Consumers should note that the UNION ALL means a requisition can appear with vendor-populated rows for external PO demand and organization-name rows for inventory demand. Join back to PO_REQUISITION_HEADERS on REQUISITION_HEADER_ID for any header attributes not exposed here.