Search Results jai_ap_tds_thhold_grps_uk1

Overview

The table JAI_AP_TDS_THHOLD_GRPS is a core data structure within the Oracle E-Business Suite Asia/Pacific Localizations module (Product JA). It is specifically designed to support Tax Deducted at Source (TDS) compliance for regions like India. The table's primary function is to store and manage the current threshold position for a defined threshold group. A threshold group is a logical aggregation of transactions for a specific vendor, tax section, and financial year, used to track cumulative taxable amounts against progressive tax slabs. This tracking is essential for determining the correct TDS deduction rate as a vendor's total payments cross predefined monetary thresholds during a fiscal period. Its role is central to the automated TDS calculation engine within Oracle Payables.

Key Information Stored

The table stores the identifying attributes of a threshold group and its current state. The primary key is a system-generated THRESHOLD_GRP_ID. A unique key constraint (JAI_AP_TDS_THHOLD_GRPS_UK1) enforces business rule integrity on the combination of VENDOR_ID, ORG_TAN_NUM (the organization's Tax Deduction and Collection Account Number), VENDOR_PAN_NUM (the vendor's Permanent Account Number), SECTION_TYPE, SECTION_CODE, and FIN_YEAR. This ensures only one active threshold group exists for that specific vendor-tax-financial year context. A critical column is CURRENT_THRESHOLD_SLAB_ID, a foreign key to JAI_AP_TDS_THHOLD_SLABS, which points to the specific tax slab the group's cumulative amount has currently reached. Other columns typically include cumulative amounts and status flags, though they are not explicitly listed in the provided metadata.

Common Use Cases and Queries

The primary use case is the real-time evaluation of TDS liability during invoice validation or payment processing. The system queries this table to find the existing threshold group for a transaction's vendor and tax line, retrieves the current slab, and applies the corresponding tax rate. Common reporting and audit queries involve analyzing threshold consumption. A sample SQL pattern to find the current slab for a vendor would be:

• SELECT grp.THRESHOLD_GRP_ID, slab.* FROM JAI_AP_TDS_THHOLD_GRPS grp, JAI_AP_TDS_THHOLD_SLABS slab WHERE grp.VENDOR_ID = :p_vendor_id AND grp.SECTION_CODE = :p_section_code AND grp.FIN_YEAR = :p_year AND grp.CURRENT_THRESHOLD_SLAB_ID = slab.THRESHOLD_SLAB_ID;

Another critical operational query is checking for the existence of a group before creating a new transaction line to determine if a new group record must be instantiated or an existing one updated.

Related Objects

JAI_AP_TDS_THHOLD_GRPS has integral relationships with several other localization tables, as documented by its foreign key constraints.

• References To (Parent Tables): It draws master data from HZ_PARTIES via VENDOR_ID and from JAI_AP_TDS_THHOLD_SLABS via CURRENT_THRESHOLD_SLAB_ID.
• Referenced By (Child Tables): Its THRESHOLD_GRP_ID is a key foreign key in multiple transactional and audit tables:
  • JAI_AP_TDS_INV_CANCELS (THRESHOLD_GRP_ID)
  • JAI_AP_TDS_INV_TAXES (DEFAULT_THRESHOLD_GRP_ID, THRESHOLD_GRP_ID)
  • JAI_AP_TDS_PREPAYMENTS (TDS_TAX_ID_PREPAY)
  • JAI_AP_TDS_THGRP_AUDITS (THRESHOLD_GRP_ID)
  • JAI_AP_TDS_THHOLD_TRXS (THRESHOLD_GRP_ID)
  These relationships show the table is central to TDS invoice taxes, prepayments, cancellation tracking, audit trails, and the individual transactions that roll up into the group's cumulative total.