Search Results jai_ap_tds_thgrp_audits




Overview
Explore in AI Chat

Overview

The JAI_AP_TDS_THGRP_AUDITS table is a core audit trail object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its primary function is to log and track all modifications made to the TDS (Tax Deducted at Source) threshold group assignments for supplier invoices. Specifically, it records the history of changes occurring in the JAI_AP_TDS_THHOLD_GRPS table, which manages the association between invoices and applicable TDS threshold groups. This audit mechanism is critical for compliance, troubleshooting, and historical reporting in regions with complex TDS regulations, providing a transparent and immutable record of tax determination logic changes throughout the invoice lifecycle.

Key Information Stored

While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly define several critical data points stored in this audit table. Each record captures a specific change event. The central column is THRESHOLD_GRP_AUDIT_ID, which serves as the unique primary key for each audit entry. The table stores identifiers that link to the changed entity and document the modification: THRESHOLD_GRP_ID references the specific threshold group record that was altered; INVOICE_ID links to the AP_INVOICES_ALL record impacted by the change. Crucially, the table stores slab identifiers that capture the state of the TDS calculation before and after the change: OLD_THRESHOLD_SLAB_ID, NEW_THRESHOLD_SLAB_ID, and TRX_THRESHOLD_SLAB_ID. These columns are foreign keys to the JAI_AP_TDS_THHOLD_SLABS table, documenting the precise TDS rate slab transitions that occurred.

Common Use Cases and Queries

The primary use case is forensic analysis and compliance reporting for TDS calculations. Auditors or functional consultants can query this table to understand why a particular invoice had its TDS amount recalculated or to verify the sequence of tax determinations. A common query pattern involves joining to the invoice and threshold slabs tables to produce a human-readable audit trail. For example, to trace all TDS group changes for a specific invoice, one might use a SQL pattern such as:

  • SELECT aud.*, inv.invoice_num, old_slab.rate_code as old_rate, new_slab.rate_code as new_rate
  • FROM jai_ap_tds_thgrp_audits aud,
  • ap_invoices_all inv,
  • jai_ap_tds_thhold_slabs old_slab,
  • jai_ap_tds_thhold_slabs new_slab
  • WHERE aud.invoice_id = inv.invoice_id
  • AND aud.old_threshold_slab_id = old_slab.threshold_slab_id(+)
  • AND aud.new_threshold_slab_id = new_slab.threshold_slab_id(+)
  • AND inv.invoice_num = '<INVOICE_NUMBER>'
  • ORDER BY aud.creation_date;

This is essential for month-end close support, resolving tax discrepancies, and generating audit reports for tax authorities.

Related Objects

The JAI_AP_TDS_THGRP_AUDITS table is centrally connected to several key TDS and Payables tables via foreign key constraints, as documented in the ETRM metadata.

  • JAI_AP_TDS_THHOLD_GRPS: Linked via JAI_AP_TDS_THGRP_AUDITS.THRESHOLD_GRP_ID. This is the primary table whose changes are being audited.
  • AP_INVOICES_ALL: Linked via JAI_AP_TDS_THGRP_AUDITS.INVOICE_ID. This ties each audit record to the specific supplier invoice document affected.
  • JAI_AP_TDS_THHOLD_SLABS: Linked via three separate foreign key columns:
    • TRX_THRESHOLD_SLAB_ID
    • NEW_THRESHOLD_SLAB_ID
    • OLD_THRESHOLD_SLAB_ID
    These relationships are vital for understanding the exact TDS rate slab before (OLD), after (NEW), and potentially the transaction slab (TRX) involved in the change.