Search Results jai_retro_tax_changes




Overview
Explore in AI Chat

Overview

The JAI_RETRO_TAX_CHANGES table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the JA - Asia/Pacific Localizations product. Its primary function is to serve as an audit and processing ledger for retroactive tax modifications applied to transactional documents. In jurisdictions with complex tax regulations, tax rates or rules can change with retroactive effect, requiring the system to recalculate and adjust taxes on historical invoices, purchase orders, or other documents after their original posting. This table systematically captures the details of each individual tax line adjustment resulting from such retroactive recalculations, ensuring a complete audit trail and supporting subsequent financial reconciliation and reporting.

Key Information Stored

While the full column list is not detailed in the provided metadata, the defined relationships and primary key indicate the critical data elements. The table's primary key, TAX_CHANGE_ID, uniquely identifies each retroactive tax change record. A fundamental foreign key, LINE_CHANGE_ID, links each tax change to its parent retroactive line adjustment in the JAI_RETRO_LINE_CHANGES table, establishing the document context. Another essential foreign key, TAX_ID, references the JAI_CMN_TAXES_ALL table to identify the specific tax type (e.g., GST, VAT, CENVAT) that was recalculated. Typical data stored would include the original tax amount, the recalculated tax amount, the difference (delta), the effective date of the retroactive change, and identifiers for the impacted transaction line and document.

Common Use Cases and Queries

This table is central to processes involving retroactive tax compliance. A common use case is generating an audit report of all tax adjustments within a specific period for regulatory review. Support personnel may query it to investigate the tax impact on a particular invoice after a retroactive change has been run. Sample SQL patterns often involve joining to related tables to provide context.

  • Querying adjustments for a specific document: SELECT rtc.* FROM jai_retro_tax_changes rtc, jai_retro_line_changes rlc WHERE rtc.line_change_id = rlc.line_change_id AND rlc.source_doc_id = :p_invoice_id;
  • Summarizing tax impact by tax type: SELECT cta.tax_name, SUM(rtc.tax_amount_difference) FROM jai_retro_tax_changes rtc, jai_cmn_taxes_all cta WHERE rtc.tax_id = cta.tax_id GROUP BY cta.tax_name;

Related Objects

The JAI_RETRO_TAX_CHANGES table exists within a defined hierarchy of retroactive change tables, as evidenced by its foreign key relationships.

  • JAI_RETRO_LINE_CHANGES: This is the direct parent table. The foreign key JAI_RETRO_TAX_CHANGES.LINE_CHANGE_ID references JAI_RETRO_LINE_CHANGES. Each tax change is a child of a more general line-level adjustment.
  • JAI_CMN_TAXES_ALL: This master tax definition table is referenced via the foreign key JAI_RETRO_TAX_CHANGES.TAX_ID. This relationship provides the descriptive details (name, rate, regime) of the tax that was changed.
  • JAI_RETRO_TAX_CHANGES_PK: The primary key constraint on the TAX_CHANGE_ID column ensures the uniqueness of each record.