Search Results po_num_rel_num




Overview
Explore in AI Chat

Overview

The APPS.POR_RCV_ORD_REQUESTER_V view is a reporting construct within the Oracle iProcurement (ICX) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents purchase order shipment and distribution data filtered to those distributions that carry a deliver-to person, effectively exposing receiving-oriented purchasing information organized by requester. The view is designed to support the iProcurement receiving pages and related inquiries, allowing a requester to see the purchase order lines and shipments for which they are the designated recipient, along with the associated quantities already delivered and the remaining expected receipt quantity.

Because the object is a view and not a base table, it holds no data of its own. It derives its rows dynamically from the purchasing, receiving, and human resources tables that constitute the procure-to-pay data model. This makes it suitable for reporting and integration scenarios where requester-centric receipt information is required without duplicating transactional data.

Underlying Base Objects

The view joins several documented base objects. Purchase order data is sourced from PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_DISTRIBUTIONS, and PO_RELEASES, with PO_VENDORS and PO_VENDOR_SITES supplying supplier information. Requester identity is resolved through PER_PEOPLE_F, with additional supporting references to HR_ general-purpose packages and HR security constructs. Unit of measure conversion relies on MTL_UNITS_OF_MEASURE. The view also references RCV_SHIPMENT_LINES, PO_REQUISITION_LINES, and the POR_RCV_TRANSACTION_SV and PO_INQ_SV packages, which provide shipment number derivation and inquiry support logic. Platform utilities such as FND_GLOBAL and HR_GENERAL supply environment and naming context.

The joins are anchored on PO_DISTRIBUTIONS, which acts as the driving table. Each distribution is linked to its line, line location, header, and release, producing one row per distribution with a valid deliver-to person. The PER_PEOPLE_F effective-dated view is constrained to the maximum effective end date per person, ensuring only the current person record is used.

Key Columns

Notable columns include PO_HEADER_ID, PO_LINE_ID, and PO_LINE_LOCATION_ID as primary keys; PO_NUMBER (POH.SEGMENT1), PO_RELEASE_NUMBER, PO_LINE_NUMBER, and PO_SHIPMENT_NUMBER for document identification; and PO_NUM_REL_NUM, which concatenates the PO number and release number with a dash separator, supporting the common "po_num_rel_num" lookup pattern. REQUESTOR_ID and REQUESTOR expose the deliver-to person, while QUANTITY_ORDERED, QUANTITY_DELIVERED, and EXPECTED_RECEIPT_QTY (derived as ordered minus cancelled minus delivered) express receipt status.

Date fields include NEED_BY_DATE, PROMISED_DATE, and EXPECTED_RECEIPT_DATE (coalesce of promised and need-by). Supplier columns SOURCE and SUPPLIER_SITE identify the vendor. TO_ORGANIZATION_ID, SHIP_TO_LOCATION_ID, ITEM_ID, and ITEM_DESCRIPTION support logistics and item reporting. A constant 'PO' literal and a derived shipment number complete the record.

Common Use Cases and Queries

A frequent scenario is retrieving the concatenated PO and release identifier for receipt processing. For example:

  • SELECT PO_NUM_REL_NUM, PO_LINE_NUMBER, REQUESTOR, EXPECTED_RECEIPT_QTY FROM APPS.POR_RCV_ORD_REQUESTER_V WHERE REQUESTOR_ID = :p_requestor_id;

  • SELECT PO_NUM_REL_NUM, PO_NUMBER, PO_RELEASE_NUMBER, QUANTITY_ORDERED, QUANTITY_DELIVERED FROM APPS.POR_RCV_ORD_REQUESTER_V WHERE PO_HEADER_ID = :p_po_header_id AND PO_LINE_LOCATION_ID = :p_shipment_id;

  • SELECT PO_NUM_REL_NUM, ITEM_DESCRIPTION, EXPECTED_RECEIPT_QTY, EXPECTED_RECEIPT_DATE FROM APPS.POR_RCV_ORD_REQUESTER_V WHERE EXPECTED_RECEIPT_QTY > 0 ORDER BY EXPECTED_RECEIPT_DATE;

These queries serve receiving worklists, open-receipt reports, and integration extracts that require requester-scoped PO and release identification.