Search Results rcv_receipt_confirmation_v




Overview
Explore in AI Chat

Overview

RCV_RECEIPT_CONFIRMATION_V is an APPS-owned reporting view within the Inventory (INV) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents a consolidated, denormalized picture of receiving activity, joining receipt header and line data from the RCV schema with transaction, item, category, vendor, customer, locator, license plate, and unit-of-measure attributes. The view is designed to support receipt confirmation reporting and downstream integration, exposing both the receiving transaction context and the corresponding inventory material transaction. In the ETRM metadata, the object holds a VALID status and belongs to the APPS schema, meaning it is intended for direct querying by concurrent programs, reports, and interfaces rather than as a base table for further DDL. Its DISTINCT select clause indicates that the joins across multiple descriptive flexfield and key flexfield views may otherwise produce duplicate rows, so consumers should expect one row per qualifying transaction combination.

Underlying Base Objects

The documented reference list confirms the view is defined over a substantial set of base tables, synonyms, views, and packages. Receiving is anchored by RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. Inventory detail is drawn from MTL_MATERIAL_TRANSACTIONS, MTL_UNIT_TRANSACTIONS, and MTL_TRANSACTION_LOT_NUMBERS. Item and category information comes from MTL_SYSTEM_ITEMS_B_KFV, MTL_ITEM_CATEGORIES, MTL_CATEGORIES_KFV, MTL_UNITS_OF_MEASURE, and MTL_PARAMETERS. Locators and LPNs are sourced from MTL_ITEM_LOCATIONS_KFV and WMS_LICENSE_PLATE_NUMBERS. Source document context is retrieved via PO_HEADERS_ALL, PO_LINES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL. Party and personnel data come from PO_VENDORS, PO_VENDOR_SITES_ALL, HZ_PARTIES, HZ_CUST_ACCOUNTS, HR_EMPLOYEES, HR_LOCATIONS_ALL, and the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, while FND_GLOBAL and FND_PROFILE supply session and profile context.

Key Columns

The view exposes descriptive identifiers such as WAREHOUSE and TRANSFER_WAREHOUSE from MTL_PARAMETERS organization codes, RECEIPT from RCV_SHIPMENT_HEADERS, SHIPMENT and SHIPMENT_TYPE from shipment lines, and DOCUMENT_TYPE, DOCUMENT_NUMBER, and DOCUMENT_LINE_NUMBER resolved conditionally by source document code (PO, RMA, REQ, or INVENTORY). Item attributes include ITEM, ITEM_ID, ITEM_DESCRIPTION, REVISION, TRANSACTION_UOM, and PRIMARY_UOM, with secondary quantity and UOM populated only when the tracking quantity indicator equals 'PS'. Transaction columns include TRANSACTION_TYPE, TRANSACTION_DATE, CREATION_DATE, TRANSACTION_ID, PARENT_TRANSACTION_ID, and INSPECTION_STATUS. Critically for the searched term, MMT_TRANSACTION_ID maps to INV.TRANSACTION_ID from MTL_MATERIAL_TRANSACTIONS, providing the link between the receiving record and the inventory material transaction. Related inventory columns include SUBINVENTORY, TRANSFER_SUBINVENTORY, LOCATOR, TRANSFER_LOCATOR, LPN, TRANSFER_LPN, PARENT_LPN, TRANSACTION_QUANTITY, and PRIMARY_QUANTITY.

Common Use Cases and Queries

Typical usage includes receipt confirmation reporting, reconciliation between receiving and inventory transactions, and integration extracts that require document, vendor, and item context in a single query. A representative query joining the search term follows:

  • SELECT receipt, document_number, item, transaction_quantity, mmt_transaction_id FROM apps.rcv_receipt_confirmation_v WHERE receipt = :receipt_num;
  • SELECT mmt_transaction_id, transaction_id, transaction_date, subinventory FROM apps.rcv_receipt_confirmation_v WHERE mmt_transaction_id = :mmt_id;
  • SELECT document_type, vendor_name, item, primary_quantity FROM apps.rcv_receipt_confirmation_v WHERE shipped_date BETWEEN :start_date AND :end_date;

Because the view performs DISTINCT processing across numerous key flexfield views, queries filtering on a single indexed column such as MMT_TRANSACTION_ID or RECEIPT_NUM remain the most efficient approach. Reports requiring large date ranges should apply bind variables to SHIPPED_DATE or TRANSACTION_DATE and avoid selecting unused columns.