Search Results ap_receipt_corrections_v




Overview
Explore in AI Chat

Overview

AP_RECEIPT_CORRECTIONS_V is a Payables (AP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents receipt correction transactions originating from Oracle Purchasing and Receiving, enriched with the associated Payables, purchasing, supplier, and inventory context. The view is designed to expose receiving corrections — quantity or amount adjustments applied to goods receipts — in a structure suitable for inquiry, reconciliation, and integration with Payables invoice matching processes. Because it is a view rather than a base table, it holds no data of its own; all content is derived at runtime from the Receiving, Purchasing, and Payables tables listed below. In ETRM 12.2.2 the object is documented as VALID under the AP - Payables product.

Underlying Base Objects

The view draws on a broad set of referenced base objects across several modules. Receiving data comes from RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES. Purchasing attributes are supplied by PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_LINE_TYPES, PO_LOOKUP_CODES, PO_VENDORS, and PO_VENDOR_SITES_ALL. Supplier and location details are resolved through PO_VENDORS, PO_VENDOR_SITES_ALL, HR_LOCATIONS_ALL_TL, and ORG_ORGANIZATION_DEFINITIONS. Payables-specific attributes are joined from AP_INVOICES, AP_INVOICE_LINES_ALL, AP_LOOKUP_CODES, and AP_TERMS. Additional naming and security derivations use the FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, with buyer names resolved via PER_PEOPLE_F. The join structure links each RCV_TRANSACTIONS correction to its shipment header and line, its purchase order line and shipment, and the corresponding vendor and site.

Key Columns

Common Use Cases and Queries

This view is typically used to review receipt corrections that affect invoice matching, to reconcile accrued receipts against corrected quantities, and to feed downstream reporting or integration extracts. A representative query follows:

SELECT receipt_number, rcv_transaction_date, rcv_transaction_quantity, rcv_transaction_amount, po_number, vendor_name, item_description FROM apps.ap_receipt_corrections_v WHERE rcv_transaction_date >= :start_date AND rcv_transaction_date < :end_date ORDER BY rcv_transaction_date;

Because all joins are embedded, callers need only filter on the exposed columns and apply operating unit or organization security through ORG_ID where required.