Search Results jai_ap_tds_thhold_types




Overview
Explore in AI Chat

Overview

The JAI_AP_TDS_THHOLD_TYPES table is a core data object within the JA (Asia/Pacific Localizations) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is specifically designed to support the configuration and management of Tax Deducted at Source (TDS) functionality for compliant regions. The table's primary role is to store the detailed threshold types defined under a TDS threshold header. Each record represents a distinct category or rule (e.g., based on vendor type, transaction nature, or income category) for which specific TDS deduction thresholds and rates are established. It acts as a critical intermediary, linking high-level threshold headers to the granular slabs and tax rates that govern actual TDS calculations.

Key Information Stored

While the full column list is not detailed in the provided metadata, the documented relationships and keys reveal its essential structure. The primary identifier is the THRESHOLD_TYPE_ID column, which uniquely defines each threshold type record. A crucial foreign key column is THRESHOLD_HDR_ID, which links each type to its parent definition in the JAI_AP_TDS_THHOLD_HDRS table. This establishes the header-type hierarchy. It is logical to infer the table also contains descriptive columns for the threshold type (e.g., name, code) and configuration flags controlling its applicability, effective dates, and status. The data stored here fundamentally dictates which set of rules (slabs and taxes) is applied during TDS processing for a given transaction.

Common Use Cases and Queries

This table is central to setup, inquiry, and troubleshooting of TDS thresholds. A common operational use case is verifying all active threshold types configured for a specific header, often during period-end closing or audit. Support personnel may query this table to diagnose why a particular TDS rate was not applied, by tracing from the transaction back to the applicable threshold type. A typical analytical query would join this table to its header and child slabs to report the complete TDS rule structure.

  • Sample Query (List Types for a Header): SELECT threshold_type_id, <descriptive_columns> FROM jai_ap_tds_thhold_types WHERE threshold_hdr_id = <header_id>;
  • Sample Query (Full Rule Hierarchy): SELECT hdr.header_name, type.threshold_type_id, slab.slab_details FROM jai_ap_tds_thhold_hdrs hdr JOIN jai_ap_tds_thhold_types type ON hdr.threshold_hdr_id = type.threshold_hdr_id JOIN jai_ap_tds_thhold_slabs slab ON type.threshold_type_id = slab.threshold_type_id ORDER BY 1, 2;

Related Objects

The JAI_AP_TDS_THHOLD_TYPES table is a nexus within the TDS threshold schema, with defined relationships to three key tables.

  • Parent Table (Foreign Key Reference): It references JAI_AP_TDS_THHOLD_HDRS via the column JAI_AP_TDS_THHOLD_TYPES.THRESHOLD_HDR_ID. This defines the header under which the type is categorized.
  • Child Tables (Referenced by Foreign Keys):
    • JAI_AP_TDS_THHOLD_SLABS references it using JAI_AP_TDS_THHOLD_SLABS.THRESHOLD_TYPE_ID. This links the threshold type to its applicable income or value slabs.
    • JAI_AP_TDS_THHOLD_TAXES references it using JAI_AP_TDS_THHOLD_TAXES.THRESHOLD_TYPE_ID. This links the threshold type to the specific TDS tax rates to be applied.

This structure confirms that a single threshold header (JAI_AP_TDS_THHOLD_HDRS) can have multiple types, and each type can have multiple associated slabs and tax rates, enabling a highly granular TDS rule engine.