Search Results expected_receipt_date




Overview
Explore in AI Chat

Overview

POR_RCV_HOME_V is a database view shipped with Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 under the ICX — Oracle iProcurement product. Its documented purpose is to support "querying most recent items to receive." In practice, the view exposes a consolidated list of open purchase order shipments that are eligible for receiving, resolving the expected receipt date for each shipment. It is the data source behind the iProcurement "Home" page receiving region, where the requester sees recently ordered items awaiting receipt.

The view is significant because it is one of the few iProcurement objects that surfaces the EXPECTED_RECEIPT_DATE column directly. Users searching on expected_receipt_date in ETRM are directed here because the view defines that column via an NVL expression rather than exposing a physical column from a base table.

Underlying Base Objects

The view is defined over five base tables, joined through standard purchasing keys:

The ETRM metadata for 12.2.2 documents no listed base objects and no owner, and records the object as "Not implemented in this database." Accordingly, the underlying structure must be read from the view text itself, which reveals the five tables above. The body is a UNION ALL of two branches that differ only in how the requestor is derived: the first uses POD.DELIVER_TO_PERSON_ID as REQUESTOR_ID, the second substitutes POH.AGENT_ID with a PO_HEADERS_N3 index hint.

Key Columns

  • REQUESTOR_ID — the person to whom the receipt responsibility applies; either the distribution deliver-to person or, in the second branch, the buyer/agent.
  • AGENT_ID — the purchasing agent (buyer) on the PO header.
  • PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — primary keys enabling drill-down to the PO and to the receiving transaction.
  • PO_NUMBER — the human-readable PO SEGMENT1.
  • ITEM_DESCRIPTION — the PO line description, truncated to 240 characters via SUBSTR.
  • EXPECTED_RECEIPT_DATE — the central column, computed as NVL(POLL.PROMISED_DATE, POLL.NEED_BY_DATE). The promised date takes precedence; the need-by date is the fallback.
  • NULL and 'PO' — literal placeholders used to align the union branches and identify the source document type.

Common Use Cases and Queries

The primary use case is populating the iProcurement home receiving list for a given requestor. Filtering logic ensures only actionable shipments appear: outstanding quantity greater than zero, approved and uncancelled shipments, closed codes other than FINALLY CLOSED, CLOSED, CLOSED FOR RECEIVING, and CANCELLED, shipment types of STANDARD, BLANKET, or SCHEDULED, and RECEIVING_ROUTING_ID = 3 (receiving required).

A typical query retrieving open receipts for a requestor, ordered by the expected date, is:

  • SELECT po_number, item_description, expected_receipt_date
  • FROM por_rcv_home_v
  • WHERE requestor_id = :p_requestor_id
  • ORDER BY expected_receipt_date;

Because EXPECTED_RECEIPT_DATE is derived, users should not expect a corresponding base-table column; querying this view is the supported approach. Performance-conscious implementations may also index or hint against PO_HEADERS_N3, as the definition itself does.