Search Results jai_rgm_thresholds




Overview
Explore in AI Chat

Overview

The JAI_RGM_THRESHOLDS table is a core data object within the Asia/Pacific Localizations (product JA) of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a master repository for defining and storing financial thresholds associated with specific tax regimes and entities. Its primary role is to support localized tax compliance and reporting requirements, particularly for regions like India, by maintaining the ceiling amounts that trigger specific tax deduction or collection obligations. The table enables the system to evaluate transactions against predefined limits based on the combination of an organization's Tax Deduction and Collection Account Number (TAN), a party's Permanent Account Number (PAN), and the financial year.

Key Information Stored

The table's structure is designed to link threshold definitions to specific entities and time periods. While the full column list is not detailed in the provided metadata, the description and foreign key relationships indicate critical data points. The primary identifier is the THRESHOLD_ID. The table stores the ORG_TAN_NUM and PARTY_PAN_NUM, which are key tax identifiers for the organization and the trading party, respectively. The FIN_YEAR column anchors the threshold to a specific financial period. Crucially, it stores the THRESHOLD_AMOUNT. The table establishes relationships via foreign key columns: REGIME_ID links to JAI_RGM_DEFINITIONS to identify the applicable tax regime, PARTY_ID references HZ_PARTIES to identify the customer or supplier, and THRESHOLD_SLAB_ID connects to JAI_AP_TDS_THHOLD_SLABS for detailed slab-based calculations.

Common Use Cases and Queries

The primary use case is the automated determination of Tax Deducted at Source (TDS) or Tax Collected at Source (TCS) applicability during transaction processing, such as invoice creation or payment. The system queries this table to compare cumulative transaction values against the stored threshold for a given PAN, TAN, regime, and financial year. Common reporting and validation queries include identifying active thresholds for a party or verifying setup completeness. A typical SQL pattern would be:

  • SELECT threshold_amount FROM jai_rgm_thresholds WHERE org_tan_num = :p_tan AND party_id = :p_party_id AND fin_year = :p_year AND regime_id = :p_regime_id;
  • SELECT * FROM jai_rgm_thresholds thr, hz_parties hp WHERE thr.party_id = hp.party_id AND hp.party_name LIKE :p_name;

Related Objects

JAI_RGM_THRESHOLDS is central to a network of related localization objects. It is the parent table for JAI_RGM_THRESHOLD_DTLS, which holds additional threshold details. Its definitions are governed by JAI_RGM_DEFINITIONS (for the regime) and JAI_AP_TDS_THHOLD_SLABS (for slab rates). The link to HZ_PARTIES integrates it with the Trading Community Architecture, ensuring thresholds are tied to standardized party records. Applications and reports within the JA localization modules, particularly those handling TDS/TCS calculations and statutory reporting, will heavily reference this table to enforce compliance logic.