Search Results jai_cmn_match_taxes_uk1




Overview
Explore in AI Chat

Overview

The table JAI_CMN_MATCH_TAXES is a core transactional data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It is designed to support localized excise tax accounting, specifically for jurisdictions like India. Its primary role is to store the results of a critical tax recomputation process. This process occurs when goods received into inventory are matched against specific sales shipments, enabling the system to calculate the precise excise duty liability based on the actual goods sold, as required by regional excise laws. The table acts as a repository for these recalculated tax amounts, ensuring accurate financial reporting and compliance with statutory ledger postings.

Key Information Stored

The table's structure is centered on linking procurement and sales transactions for tax determination. Its primary key (MATCH_TAX_ID) ensures each record is unique. A significant unique key constraint combines several foreign key columns to enforce business logic: REF_LINE_ID (likely referencing the sales order line), ORDER_INVOICE, RECEIPT_ID, and TAX_LINE_NO. This combination prevents duplicate tax calculations for the same matched transaction. Key data columns include TAX_ID, which links to the master tax definition in JAI_CMN_TAXES_ALL, and RECEIPT_ID, which links to the receipt transaction in JAI_CMN_RG_23D_TRXS—a table typically associated with excise duty registers. The table stores the recomputed tax amounts, quantities, and other attributes necessary for generating compliant excise documentation.

Common Use Cases and Queries

The primary use case is the generation of excise duty reports, such as the RG 23D register in the Indian context, which mandates tracking duty based on the clearance of goods. Finance and tax teams query this table to audit the excise liability calculated post-receipt matching. A common reporting pattern involves joining to related shipment and receipt tables to reconcile tax figures. For troubleshooting, a query might isolate records for a specific sales order or receipt to verify the matching logic and resulting tax amounts. Sample SQL to analyze matched taxes for a period would typically join JAI_CMN_MATCH_TAXES with JAI_CMN_RG_23D_TRXS and JAI_CMN_TAXES_ALL.

Related Objects

  • JAI_CMN_TAXES_ALL: A master table providing the tax rate and rules applied via the foreign key on TAX_ID.
  • JAI_CMN_RG_23D_TRXS: Directly related through the RECEIPT_ID foreign key, this table stores detailed excise register entries for receipts, forming one side of the match.
  • Primary Key Constraint (JAI_CMN_MATCH_TAXES_PK): On MATCH_TAX_ID, ensuring record uniqueness.
  • Unique Key Constraint (JAI_CMN_MATCH_TAXES_UK1): On the combination of REF_LINE_ID, ORDER_INVOICE, RECEIPT_ID, and TAX_LINE_NO, enforcing the business rule for the matching process.