Search Results oe_order_headers_u2




Overview
Explore in AI Chat

Overview

APPS.POR_RCV_REQS_ORDER_V is an Oracle E-Business Suite purchasing and receiving view that consolidates requisition-driven demand against two distinct fulfillment sources: purchase order shipments and internal sales order demand. Its logical name indicates its intended role as a receiving-oriented requisition-to-order reconciliation view, presenting each requisition line alongside the corresponding external purchase order or internal order reference. The view is defined by a UNION ALL of two queries joined through the requisition distribution chain, and is owned by the APPS schema in both 12.1.1 and 12.2.2.

The first branch resolves requisition distributions to purchase order distributions, returning open and approved purchase order shipments that are accruing receipts. The second branch resolves requisition lines with a source type of INVENTORY to internal sales order headers, where the originating system document reference matches the requisition segment. This structure allows receiving and procurement users to reconcile outstanding requisition demand across both external and internal supply channels from a single source. The view is read-only and intended for reporting rather than transactional processing.

Underlying Base Objects

The view is documented as being defined over eleven base objects: HR_ALL_ORGANIZATION_UNITS_TL, OE_ORDER_HEADERS, PO_DISTRIBUTIONS, PO_HEADERS, PO_LINE_LOCATIONS, PO_RELEASES, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, PO_SYSTEM_PARAMETERS, PO_VENDORS, and RCV_SHIPMENT_LINES. With the exception of PO_VENDORS, which is itself a view, all are exposed as synonyms.

The principal join path for the purchase order branch flows from PO_REQUISITION_HEADERS to PO_REQUISITION_LINES to PO_REQ_DISTRIBUTIONS, then to PO_DISTRIBUTIONS, PO_LINE_LOCATIONS, PO_HEADERS, PO_RELEASES, and PO_VENDORS. The internal order branch joins PO_REQUISITION_LINES to OE_ORDER_HEADERS via ORIG_SYS_DOCUMENT_REF and to PO_SYSTEM_PARAMETERS for the internal order source identifier, with HR_ALL_ORGANIZATION_UNITS_TL supplying the source organization name. RCV_SHIPMENT_LINES is referenced for receiving-context correlation.

Key Columns

  • REQUISITION_HEADER_ID / SEGMENT1 / DESCRIPTION — Identifier, document number, and description of the sourcing requisition header.
  • PREPARER_ID — The requisition preparer.
  • TO_PERSON_ID — The requestor or deliver-to person on the requisition line.
  • ORDER_NUM_REL_NUM — In the PO branch, the concatenation of PO number and release number; in the internal order branch, the internal order number as character.
  • PO_NUMBER / ORDER_NUMBER — Mutually exclusive: the PO branch populates PO_NUMBER and returns NULL for ORDER_NUMBER, while the internal branch does the reverse.
  • PO_RELEASE_NUMBER — Populated only for released purchase orders; NULL for the internal order branch.
  • VENDOR — Vendor name for purchase orders or the source organization name for internal orders.
  • CREATION_DATE — Requisition header creation date, common to both branches.

Common Use Cases and Queries

The view supports requisition-to-receipt reconciliation, open purchase order shipment reporting, and internal order sourcing analysis. The second branch carries an optimizer hint, /*+ INDEX(OSH OE_ORDER_HEADERS_U2) */, which is directly relevant to the query term oe_order_headers_u2; this index is the unique key on order number used to drive the internal order lookup efficiently.

Typical usage:

  • SELECT segment1, order_num_rel_num, po_number, order_number, vendor FROM apps.por_rcv_reqs_order_v WHERE creation_date >= :p_from_date;
  • Filter on po_number IS NULL to isolate internal order demand, or on order_number IS NULL to isolate purchase order demand.
  • Join to RCV_SHIPMENT_LINES or receiving tables on the order references to compare ordered versus received quantities.
  • Group by vendor to summarize outstanding requisition commitment by supplier or source organization.