Search Results req_line




Overview
Explore in AI Chat

Overview

APPS.RCV_ENTER_RECEIPTS_V is a consolidated, read-only database view that presents the complete set of receipt entry candidates available to the Oracle E-Business Suite Receiving application. It serves as the single reporting and integration surface behind the Enter Receipts form, unifying purchase order receipts, internal requisitions, inventory (inter-org) receipts, RMA returns, and advance ship notice (ASN) sources into one homogeneous row structure. In Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is used both by the Receiving forms UI and by external integrations, reporting tools, and APIs that need to identify pending receipt lines before a receipt is actually created and saved to the RCV_TRANSACTIONS and RCV_SHIPMENT_HEADERS tables.

The view is the primary lookup for the rcv_shipment_header_id value—the surrogate key that identifies the shipment header associated with a receipt row. Because receipt headers are only assigned when a receipt is saved, the view exposes this identifier for rows that already carry an in-transit shipment (typically ASN and pre-generated receipts), while rows awaiting first-time receipt carry a null shipment header id until the transaction is committed.

Underlying Base Objects

The view is defined over a UNION ALL of five constituent views, each of which supplies a distinct receipt source:

Supporting package references documented in the metadata include HR_GENERAL and HR_SECURITY (for operating unit and security profile filtering), OE_SYS_PARAMETERS (for order management profile options), and PO_CLM_INTG_GRP (for procurement contract integration). The union structure explains why the same logical row can carry PO, requisition, or order attributes in different columns; only the subset relevant to the source is populated for any given row.

Key Columns

The most commercially significant columns are the shipment anchors and their linked purchase order context:

Common Use Cases and Queries

Typical usage resolves pending receipts for a PO, traces shipment headers for ASN-based receipts, and feeds downstream integrations. Sample statements:

  • Find receipt-ready lines for a purchase order:
SELECT po_number, po_line_number, item_number, ordered_qty,
       rcv_shipment_header_id, closed_code
  FROM apps.rcv_enter_receipts_v
 WHERE po_number = '12345'
   AND closed_code = 'OPEN';
  • Identify ASN rows that already carry a shipment header:
SELECT rcv_shipment_header_id, rcv_shipment_number,
       asn_type, ship_to_location, ordered_qty
  FROM apps.rcv_enter_receipts_v
 WHERE rcv_shipment_header_id IS NOT NULL
   AND source_type_code = 'ASN';
  • Reconcile requisition and inventory receipts destined to a subinventory:
SELECT req_number, to_organization_id, destination_subinventory,
       item_number, ordered_qty
  FROM apps.rcv_enter_receipts_v
 WHERE req_number IS NOT NULL
   AND destination_subinventory = 'STORES';

Because the view is a union over five source-specific views, queries should filter on ORDER_TYPE_CODE, RECEIPT_SOURCE_CODE, or SOURCE_TYPE_CODE to avoid returning irrelevant rows and to improve execution plans. The rcv_shipment_header_id is generally not unique per row across all sources, so joins should be qualified by shipment line or PO context.