Search Results jai_ap_tds_thhold_trxs




Overview
Explore in AI Chat

Overview

The JAI_AP_TDS_THHOLD_TRXS table is a core transactional repository within the Oracle E-Business Suite Asia/Pacific Localizations module (JA). It is designed specifically for India's Tax Deducted at Source (TDS) compliance. The table's primary function is to store a detailed record of every transaction for which a TDS invoice has been generated. This serves as the central link between the standard Oracle Payables invoice (AP_INVOICES_ALL) and the localized TDS processing logic. Each record represents a unique TDS assessment event, tracking the associated vendor, tax authority, tax rate, invoice details, and its grouping for threshold calculations, forming the auditable backbone of the TDS invoice lifecycle.

Key Information Stored

The table's structure is defined by its extensive foreign key relationships, which indicate the critical data points it stores. The primary key, THRESHOLD_TRX_ID, is a unique system-generated identifier for each TDS transaction record. Other pivotal columns include THRESHOLD_HDR_ID and THRESHOLD_GRP_ID, which link the transaction to its parent threshold calculation header and grouping. The table stores key entity identifiers: VENDOR_ID and VENDOR_SITE_ID for the supplier, INVOICE_TO_VENDOR_ID for the invoicing party, and TDS_AUTHORITY_VENDOR_ID and TDS_AUTHORITY_VENDOR_SITE_ID for the tax-deducting authority. The INVOICE_ID column directly references the source payables invoice in AP_INVOICES_ALL, while TAX_ID points to the applicable TDS tax definition in JAI_CMN_TAXES_ALL. Collectively, these columns provide a complete snapshot of the who, what, and how much for each TDS deduction event.

Common Use Cases and Queries

This table is essential for troubleshooting, auditing, and generating TDS-specific reports. A common use case is tracing the TDS history of a specific supplier invoice or investigating discrepancies in TDS amounts. Developers and support consultants frequently query this table to understand the flow of a TDS transaction through the system. Sample SQL patterns include joining to payables and supplier tables to list all TDS invoices for a vendor, or joining to the related tax lines and cancellation tables to assess the current status of TDS liabilities. For instance, a basic query to retrieve TDS transaction details for an invoice would be:

  • SELECT t.*, a.invoice_num, p.party_name vendor_name FROM jai_ap_tds_thhold_trxs t, ap_invoices_all a, hz_parties p WHERE t.invoice_id = a.invoice_id AND t.vendor_id = p.party_id AND a.invoice_num = '<INVOICE_NUMBER>';

Reporting use cases center on reconciliation between TDS deductions claimed and the underlying invoice payments, as well as generating statutory forms.

Related Objects

JAI_AP_TDS_THHOLD_TRXS is a central hub with numerous documented relationships. It references these key objects:

  • JAI_AP_TDS_THHOLD_HDRS / JAI_AP_TDS_THHOLD_GRPS: Via THRESHOLD_HDR_ID and THRESHOLD_GRP_ID for threshold calculation context.
  • AP_INVOICES_ALL: Via INVOICE_ID for the source invoice.
  • HZ_PARTIES / HZ_PARTY_SITES: For Vendor, Invoice-To Vendor, and TDS Authority party and site details.
  • JAI_CMN_TAXES_ALL: Via TAX_ID for the specific TDS tax rate and rule.

Conversely, it is referenced by these transactional child tables: