Search Results receipt_uom_lookup_code




Overview
Explore in AI Chat

Overview

APPS.AP_RECEIPT_CORRECTIONS_V is a read-only database view in the Oracle E-Business Suite Applications (APPS) schema, registered against FND Design Data as SQLAP.AP_RECEIPT_CORRECTIONS_V. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view consolidates receiving transaction information with the corresponding purchasing and supplier data, presenting a single query surface for receipt correction activity. In practice it is used to identify receiving transactions — particularly corrections and adjustments — that impact invoice matching and accrual accounting, and to reconcile receipts against purchase orders and invoices.

The view is flagged Oracle Internal Use Only in the ETRM metadata. Oracle does not support direct data access through this object except from standard Oracle Applications programs. Consequently, it should be treated as a diagnostic and reporting aid rather than a supported integration interface. Any custom code referencing it must be validated before upgrade, since internal views may change between releases.

Underlying Base Objects

The documented dependency list for 12.2.2 includes the following referenced objects: AP_INVOICES, AP_INVOICE_LINES_ALL, AP_LOOKUP_CODES, AP_TERMS, FND_GLOBAL, HR_GENERAL, HR_LOCATIONS_ALL_TL, HR_PERSON_NAME, HR_SECURITY, ORG_ORGANIZATION_DEFINITIONS, PER_PEOPLE_F, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LINE_TYPES, PO_LOOKUP_CODES, PO_RELEASES_ALL, PO_VENDORS, PO_VENDOR_SITES_ALL, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS.

The core driving object is RCV_TRANSACTIONS, which supplies the transaction identifier, date, quantity, and service amount. RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES provide the receipt number, shipment line number, and shipment identifiers. PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL supply the purchase order header, line, and shipment attributes, with PO_RELEASES_ALL contributing release-specific information. Supplier details come from PO_VENDORS and PO_VENDOR_SITES_ALL. Invoice-side data is sourced from AP_INVOICES and AP_INVOICE_LINES_ALL, while AP_LOOKUP_CODES, AP_TERMS, PO_LOOKUP_CODES, and ORG_ORGANIZATION_DEFINITIONS resolve descriptive lookups. HR_GENERAL, HR_LOCATIONS_ALL_TL, HR_PERSON_NAME, HR_SECURITY, and PER_PEOPLE_F resolve buyer and ship-to personnel or location names, and FND_GLOBAL supplies the runtime organization and user context.

Key Columns

The column set is grouped by functional area. Receiving transaction attributes include RCV_TRANSACTION_ID, RCV_TRANSACTION_DATE, RCV_TRANSACTION_QUANTITY, and RCV_TRANSACTION_AMOUNT (the latter specifically documented as the amount for services). Receipt identifiers include RCV_SHIPMENT_HEADER_ID, RECEIPT_NUMBER, RCV_SHIPMENT_LINE_ID, and RCV_SHIPMENT_LINE_NUMBER.

Purchasing attributes include PO_HEADER_ID, PO_NUMBER (combined with type_lookup_code and org_id to form a unique key), PO_LINE_ID, PO_LINE_NUMBER, PO_LINE_LOCATION_ID, PO_LINE_LOCATION_NUMBER, PO_UNIT_PRICE, PO_RELEASE_ID, and PO_RELEASE_NUM. Unit of measure is carried on two columns: PO_UOM_LOOKUP_CODE and RECEIPT_UOM_LOOKUP_CODE, both VARCHAR2(25). The latter — the column surfaced by the search term "receipt_uom_lookup_code" — holds the unit of measure recorded on the receiving transaction, which may differ from the ordered PO unit of measure and is therefore essential when validating quantity discrepancies during receipt correction.

Item and supplier attributes include ITEM_ID, ITEM_DESCRIPTION, CATEGORY_ID, SUPPLIER_ITEM_NUMBER, SHIP_TO_LOCATION_ID, SHIP_TO_LOCATION, BUYER_ID, BUYER, VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_NAME, CURRENCY_CODE, INVENTORY_ORGANIZATION_ID, and INVENTORY_ORGANIZATION_CODE. Commercial terms include PO_FREIGHT_TERMS, PO_PAYMENT_TERMS, BILL_OF_LADING, PACKING_SLIP, PO_APPROVED_FLAG, and PO_APPROVED_DATE.

Common Use Cases and Queries

  • Identifying receipts where the receipt unit of measure differs from the purchase order unit of measure, a frequent root cause of quantity and matching discrepancies.
  • Reconciling receiving transactions to purchase order shipments and invoice lines for accrual and period-end close analysis.
  • Locating service receipts by amount where quantity-based reconciliation is not applicable.
  • Reporting receipt corrections by buyer, supplier, ship-to location, or inventory organization.

Typical queries select the receipt and purchase order identifiers alongside the unit of measure columns:

SELECT receipt_number, rcv_transaction_date, rcv_transaction_quantity, po_number, po_line_number, po_uom_lookup_code, receipt_uom_lookup_code, item_description, vendor_name, currency_code FROM apps.ap_receipt_corrections_v WHERE receipt_uom_lookup_code <> po_uom_lookup_code AND rcv_transaction_date >= :p_start_date;

A supplementary query isolating service receipts by amount: SELECT receipt_number, rcv_transaction_amount, po_number, vendor_name FROM apps.ap_receipt_corrections_v WHERE rcv_transaction_amount IS NOT NULL ORDER BY rcv_transaction_date;

Because the view joins a large number of base objects, queries should be constrained by date, organization, or supplier to avoid full scans across RCV_TRANSACTIONS and PO_LINES_ALL. Given its internal-use designation, output should be used for investigation and reconciliation rather than as a system of record.