Results for “quantity_received”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

POR_RECEIPTS_SUMMARY_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and classified under the ICX product family, which corresponds to Oracle iProcurement. The view presents a consolidated, denormalized summary of goods receipts that have been created against purchase requisition lines. Within the EBS architecture, it functions as a read-only presentation layer that joins requisition line data to the corresponding receiving transactions, allowing iProcurement and downstream reporting components to display receipt confirmation details to requisitioners without querying the receiving tables directly.

The view is particularly significant in that it exposes the WAYBILL_NUMBER column, sourced from the RCV_SHIPMENT_HEADERS table's WAYBILL_AIRBILL_NUM column. Users searching for "waybill_number" in the context of Oracle iProcurement typically arrive at this view because it is the documented, supported interface through which the receiving carrier's waybill or airbill number is surfaced alongside requisition and receipt information. This makes the view the canonical reference point for tracking shipment documentation numbers tied to requisitions, a common requirement in inbound logistics, freight reconciliation, and supplier performance reporting.

Underlying Base Objects

According to the documented view text, POR_RECEIPTS_SUMMARY_V is defined over three base tables joined through two equality conditions:

• PO_REQUISITION_LINES (SYNONYM) — aliased as PRL; the driving table supplying REQUISITION_LINE_ID and LINE_LOCATION_ID.
• RCV_SHIPMENT_HEADERS (SYNONYM) — aliased as RSH; supplies receipt number, creation date, freight carrier code, and waybill/airbill number.
• RCV_SHIPMENT_LINES (SYNONYM) — aliased as RSL; supplies packing slip, quantity received, unit of measure, and comments.
• FND_PROFILE (PACKAGE) — referenced in the SELECT list through FND_PROFILE.VALUE_WNPS to resolve the ICX_DATE_FORMAT_MASK profile option at runtime.

The join logic is: PRL.REQUISITION_LINE_ID = RSL.REQUISITION_LINE_ID and RSH.SHIPMENT_HEADER_ID = RSL.SHIPMENT_HEADER_ID. Because RCV_SHIPMENT_LINES is the intersection point, only requisition lines that have generated a receipt shipment line will appear in the result set. The view therefore behaves as an inner-join projection; requisition lines without receipts are excluded. The inclusion of the profile-driven date format means output presentation is session- and site-dependent.

Key Columns

• REQUISITION_LINE_ID — Primary key of the requisition line; the principal correlation key back to PO_REQUISITION_LINES.
• LINE_LOCATION_ID — Identifies the specific shipment or location schedule on the requisition line.
• RECEIPT_NUM — The receipt number from the shipment header, used as the user-facing receipt identifier.
• RECEIPT_DATE — The shipment header creation date, formatted using the ICX_DATE_FORMAT_MASK profile value.
• CARRIER — The freight carrier code recorded on the shipment header.
• PACKING_SLIP — Packing slip reference captured on the shipment line.
• WAYBILL_NUMBER — The waybill or airbill number from the shipment header; the column most commonly targeted by searches for "waybill_number."
• QUANTITY_RECEIVED and UNIT_OF_MEASURE — The received quantity and its UOM, used for reconciliation and discrepancy analysis.
• ITEM_COMMENTS — Free-text comments recorded at the shipment line level.

Common Use Cases and Queries

Typical scenarios include reporting receipt details for a requisition, tracing a waybill number to the originating requisition, and validating received quantities against ordered quantities. The following sample returns all receipts for a given requisition line:

SELECT receipt_num, receipt_date, waybill_number, carrier, quantity_received, unit_of_measure FROM apps.por_receipts_summary_v WHERE requisition_line_id = :p_line_id;

To locate the requisition behind a waybill, query by the waybill column:

SELECT requisition_line_id, line_location_id, receipt_num, receipt_date, packing_slip FROM apps.por_receipts_summary_v WHERE waybill_number = :p_waybill;

For freight or carrier volume analysis, aggregate on carrier:

SELECT carrier, COUNT(*) receipt_count, SUM(quantity_received) total_qty FROM apps.por_receipts_summary_v WHERE receipt_date >= :p_from_date GROUP BY carrier;

Because the view is APPS-owned and read-only, queries should be executed with appropriate MO or responsibility contexts and must not be used for transactional writes. As with all EBS views, validation on the target release (12.1.1 or 12.2.2) is recommended before production dependency.