Search Results jai_mtl_match_receipts




Overview
Explore in AI Chat

Overview

The JAI_MTL_MATCH_RECEIPTS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is designed to support specific statutory requirements for tax accounting in certain regional implementations, particularly India. The table's primary role is to track and store transactional data for receipts that have been matched to shipments, specifically for the purpose of claiming excise duty and Value-Added Tax (VAT) on capital goods during inter-organization transfers. This functionality is critical for compliance with local tax laws that govern the movement and receipt of capital assets between different legal or business entities within an organization.

Key Information Stored

While the provided metadata does not list all columns, the structure and relationships indicate the table stores key identifiers that link receipt matching events to broader inventory and purchasing transactions. The primary key, MATCH_RECEIPT_ID, uniquely identifies each matched receipt record. Two critical foreign key columns establish the necessary links: SHIPMENT_LINE_ID connects to the RCV_SHIPMENT_LINES table, anchoring the record to a specific received shipment line, and INVENTORY_ITEM_ID paired with ORGANIZATION_ID links to the MTL_SYSTEM_ITEMS_B table, identifying the specific item and its organizational context. This structure ensures each record in JAI_MTL_MATCH_RECEIPTS is tied to a tangible receipt and a master inventory item, forming the basis for subsequent tax determination and claim processes.

Common Use Cases and Queries

The primary use case for this table is generating reports and supporting processes for tax recovery on capital goods. Finance and tax teams use the data to substantiate excise and VAT input credit claims during audits. A common reporting query would join this table to shipment and item master data to list all matched receipts eligible for tax claims within a period. For example:

  • Identifying matched receipts for a specific item or organization to reconcile tax records.
  • Supporting month-end or quarter-end tax reporting by summarizing matched receipt data.
  • Troubleshooting issues in the tax claim process by verifying that receipts for inter-organization transfers have been correctly recorded in this register.

A sample SQL pattern would involve selecting from JAI_MTL_MATCH_RECEIPTS and joining to RCV_SHIPMENT_LINES for receipt details and MTL_SYSTEM_ITEMS_B for item descriptions.

Related Objects

JAI_MTL_MATCH_RECEIPTS is centrally linked to two fundamental EBS tables, as documented by its foreign key relationships:

  • RCV_SHIPMENT_LINES: Joined via the SHIPMENT_LINE_ID column. This relationship provides access to detailed information about the received shipment, including quantities, dates, and associated purchase order details.
  • MTL_SYSTEM_ITEMS_B: Joined via the INVENTORY_ITEM_ID and ORGANIZATION_ID columns. This link provides master data about the capital good itself, such as its description, item category, and other defining attributes necessary for accurate tax classification.

These relationships are essential for any query or report that needs to present a complete picture of the matched receipt, combining transactional data from Receiving with master data from Inventory.