Search Results pay_on_code




Overview
Explore in AI Chat

Overview

The PO_AP_RECEIPT_MATCH_V view, owned by the APPS schema, is a pre-built reporting object within the Oracle E-Business Suite Payables (AP) module. It presents a consolidated, denormalized projection of receipt, purchase order, and supplier data, purpose-built to support the three-way and four-way matching processes that are central to Payables invoice validation. Rather than requiring developers and analysts to join dozens of Purchasing, Receiving, and Payables tables manually, this view exposes a single SQL source that brings together receipt transactions, shipment details, purchase order headers, lines, line locations, releases, supplier information, tax codes, payment terms, and inventory organization data in one result set.

The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Note that the view text carries an inline reference to BUG 4158565, indicating that the ITEM_ID column was added or modified to resolve a specific defect; this is common in Oracle seeded objects and signals that the view has been patched over time. Because the object resides in the APPS schema and is defined over multiple synonym and view references, it inherits Oracle's standard multi-org and security behavior through FND_GLOBAL and HR_SECURITY package calls at runtime.

Underlying Base Objects

The ETRM metadata documents a broad dependency list. Core Receiving objects include RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES, which provide the receipt transaction ID, transaction date, quantity, receipt number, line number, and container data. Purchasing objects include PO_HEADERS, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL, supplying PO number, line number, shipment number, unit price (via NVL of price override and unit price), release number, and terms.

Supplier and reference data are drawn from AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, AP_TERMS, AP_TAX_CODES_ALL, AP_LOOKUP_CODES, and PO_LOOKUP_CODES. Location and organizational context come from HR_LOCATIONS_ALL_TL, ORG_ORGANIZATION_DEFINITIONS, and PER_PEOPLE_F (buyer name via HR_PERSON_NAME). Security and multi-org filtering are applied through the FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages, which enforce operating unit and organization access at query time.

Key Columns

Common Use Cases and Queries

The view is most frequently used to reconcile received quantities against invoiced quantities, to investigate receipt accrual balances, and to build custom matching reports. A typical query filters by PO number and vendor:

  • Receipt-to-invoice reconciliation: SELECT receipt_number, po_number, rcv_transaction_quantity, po_unit_price FROM po_ap_receipt_match_v WHERE po_number = :po_num AND org_id = :org_id;
  • Uninvoiced receipts by vendor: SELECT vendor_name, receipt_number, rcv_transaction_date FROM po_ap_receipt_match_v WHERE vendor_id = :vendor_id ORDER BY rcv_transaction_date;
  • Tax and terms lookup for matching: selecting tax_name, po_payment_terms, accrue_on_receipt_flag to validate accrual logic.

Because the view applies FND_GLOBAL and HR_SECURITY at runtime, queries automatically respect the caller's operating unit unless the session context is adjusted. Developers should be aware that, as with most APPS seeded views, performance depends on the underlying base tables and that direct DML is not supported.