Results for “receipt_uom”

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

Overview

POR_RCV_CONF_ITEMS_V is a view owned by the APPS schema in Oracle E-Business Suite, associated with the ICX (Oracle iProcurement) product family. Its documented purpose is to support the receive items flow by exposing the set of item lines that are presented to the user on the confirmation page once receipts have been entered and confirmed. In practice, the view consolidates header, line, transaction, unit of measure, and organization information so that the confirmation screen can render a single, joined result set without repeatedly querying transactional tables.

Beyond the interactive iProcurement flow, the view is useful in reporting and integration contexts. Because it already joins receipt shipment data with requisition and purchasing data, it provides a convenient, pre-validated source for queries concerning received items, their source and destination organizations, and the originating document (requisition or purchase order). The view is definition-only; it stores no data of its own and instead reflects the current state of the underlying transactional tables at query time.

Underlying Base Objects

The view text reveals two distinct branches combined with a UNION ALL. The first branch joins PO_REQUISITION_LINES and PO_REQUISITION_HEADERS to RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, and RCV_TRANSACTIONS, with HR_ALL_ORGANIZATION_UNITS supplying both the source and destination organization names and MTL_UNITS_OF_MEASURE supplying the unit of measure description. This branch is restricted to transactions of type DELIVER with a source document code of REQ, meaning it covers requisition-sourced receipts.

The second branch shifts the originating document to the purchasing side, joining PO_LINES, and (per the documented ETRM metadata) the transaction views PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, and PO_DISTRIBUTIONS_TRX_V, together with PO_VENDORS and the requisition distribution objects PO_REQ_DISTRIBUTIONS and PO_REQUISITION_HEADERS/PO_REQUISITION_LINES for the segment lookup. The documented referenced-object list also includes PO_CLM_INTG_GRP, a package, and HR_ALL_ORGANIZATION_UNITS_TL, the translation table behind organization names. Together these objects supply receipt, transaction, purchasing, and organization context.

Key Columns

• RECEIPT_NUM — the receipt number from RCV_SHIPMENT_HEADERS.
• TRANSACTION_DATE — the date of the deliver transaction.
• SEGMENT1 — the requisition (or, in the purchasing branch, the derived requisition) number.
• ITEM_DESCRIPTION — the item description, truncated to 240 characters in the purchasing branch.
• UNIT_OF_MEASURE_TL — the translated unit of measure description.
• QUANTITY_RECEIVED — the quantity received on the shipment line.
• WAYBILL_AIRBILL_NUM, PACKING_SLIP — shipping and packing references captured at receipt.
• USSGL_TRANSACTION_CODE, COMMENTS — accounting and free-text comments from line and header.
• SOURCE and DESTINATION_ORGANIZATION — organization names resolved through HR_ALL_ORGANIZATION_UNITS; these are the columns most relevant to destination-organization analysis.
• VENDOR — vendor name in the purchasing branch.
• GROUP_ID — the transaction group identifier.

Common Use Cases and Queries

A typical use is auditing received quantities by destination organization, for example: SELECT receipt_num, transaction_date, destination_organization, item_description, quantity_received FROM apps.por_rcv_conf_items_v WHERE destination_organization = :org ORDER BY transaction_date DESC;

The view also supports reconciliation of receipts against requisitions or purchase orders, locating receipts by packing slip or waybill, and feeding downstream reporting on delivered quantities. Note that the UNION ALL can produce rows with differing source attributes, so filters should account for both requisition-sourced and purchase-order-sourced receipts.