Search Results item_to_receipt

Overview

The APPS.JAI_AP_MATCH_INV_TAX_V view is a tax reconciliation view within the Oracle E-Business Suite financials module, specifically part of the India Localization (JAI) tax solution set. It consolidates tax line information arising from two distinct procurement matching flows: item-to-PO matching and item-to-receipt matching. This view serves as a unified reporting and integration layer over India-specific tax tables, allowing tax amounts to be reported against the appropriate invoice and transaction context regardless of whether the underlying match originated at the purchase order or at the receipt stage.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2 environments where the India Localization tax engine is installed. Its principal role is to present a normalized, aggregated tax picture per invoice line, joining self-assessed and vendor tax records to their originating procurement transactions. Because it exposes a virtual column named match_type with values ITEM_TO_PO or ITEM_TO_RECEIPT, it enables downstream reports and interfaces to distinguish the two match paths without needing to query the base tables directly.

Underlying Base Objects

Per the documented ETRM metadata, JAI_AP_MATCH_INV_TAX_V is defined over the following base objects, all exposed through APPS synonyms:

• JAI_AP_MATCH_INV_TAXES — the central table holding invoice-level tax match records, including tax_id, line_location_id, rcv_transaction_id, invoice_id, parent_invoice_line_number, and TAX_AMOUNT.
• JAI_PO_TAXES — the purchase-order tax detail table, joined on tax_id and line_location_id for the ITEM_TO_PO branch.
• JAI_RCV_LINE_TAXES — the receipt line tax table, joined on tax_id and shipment_line_id for the ITEM_TO_RECEIPT branch.
• RCV_TRANSACTIONS — the standard receiving transactions table, used to link the receipt tax line to its transaction_id.

The view is constructed as a UNION ALL of two selectivity branches. The ITEM_TO_PO branch joins JAI_PO_TAXES to JAI_AP_MATCH_INV_TAXES where rcv_transaction_id is null, meaning the tax was matched against a PO and not a receipt. The ITEM_TO_RECEIPT branch joins JAI_RCV_LINE_TAXES, JAI_AP_MATCH_INV_TAXES, and RCV_TRANSACTIONS where rcv_transaction_id is not null, linking shipment_line_id to the receiving transaction. Both branches are then wrapped in an outer aggregation that groups by match_type and the remaining descriptive columns while summing TAX_AMOUNT.

Key Columns

• MATCH_TYPE — literal discriminator returning 'ITEM_TO_PO' or 'ITEM_TO_RECEIPT'; identifies the matching path.
• INVOICE_ID and PARENT_INVOICE_LINE_NUMBER — the AP invoice header and parent line to which the tax relates.
• TRANSACTION_ID — for PO matches this is the line_location_id; for receipt matches it is the receiving transaction_id.
• TAX_LINE_NO, TAX_ID, TAX_TYPE — identification of the specific tax line and tax regime.
• PRECEDENCE_1 through PRECEDENCE_10 — tax precedence configuration columns used by the India tax engine for computation ordering.
• CURRENCY, TAX_RATE, QTY_RATE, UOM — monetary and unit-of-measure attributes for the tax line.
• TAX_AMOUNT — aggregated tax amount (SUM of NVL to zero), one row per grouped tax line.
• VENDOR_ID and VENDOR_SITE_ID — supplier identity; VENDOR_SITE_ID is NULL for the PO branch.
• MODVAT_FLAG — indicates whether the tax is modvat-eligible.

Common Use Cases and Queries

Typical usage includes reconciling India withholding and excise taxes between invoices and their PO or receipt origins, validating that the correct match path was applied, and feeding tax extracts to statutory reporting interfaces. A representative query isolates receipt-based tax lines for a given invoice:

• SELECT invoice_id, parent_invoice_line_number, tax_type, tax_amount FROM apps.jai_ap_match_inv_tax_v WHERE match_type = 'ITEM_TO_RECEIPT' AND invoice_id = :p_invoice_id;
• SELECT match_type, SUM(tax_amount) FROM apps.jai_ap_match_inv_tax_v GROUP BY match_type;
• SELECT tax_id, tax_rate, currency, vendor_id FROM apps.jai_ap_match_inv_tax_v WHERE invoice_id = :p_invoice_id AND modvat_flag = 'Y';

Because the view performs aggregation, filtering on TAX_AMOUNT should be done on the grouped result. Direct DML against the view is not supported; inserts and updates must target the underlying base tables.