Results for “jai_rgm_thresholds”
47 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JAI_RGM_THRESHOLDS is an Oracle E-Business Suite table owned by the JA schema and delivered as part of the Asia/Pacific Localizations (JA) product family. It stores threshold amounts associated with an organization Tax Account Number (TAN), a party Permanent Account Number (PAN), and a financial year. The table functions as the header-level repository for regime-driven threshold configuration, feeding the India localization features that govern withholding, reporting, and tax deduction behavior. Each row represents a distinct threshold definition scoped to a combination of regime, organization, party, and fiscal period.
From a Data Vault modeling perspective, the FK topology suggests a satellite-leaning classification. The table carries a surrogate primary key, descriptive and measure attributes (threshold amounts), and a set of foreign keys that contextualize those attributes against reference dimensions such as HZ_PARTIES, JAI_RGM_DEFINITIONS, and JAI_AP_TDS_THHOLD_SLABS. This structure is characteristic of a satellite attached to a hub or link rather than an independent hub.
Key Information Stored
The table comprises sixteen documented columns at release 12.2.2. The most significant attributes are:
- THRESHOLD_ID — The surrogate primary key, enforced by the JAI_RGM_THRESHOLDS_PK constraint and the JAI_RGM_THRESHOLDS_U1 unique index.
- REGIME_ID — Foreign key to JAI_RGM_DEFINITIONS, identifying the tax regime under which the threshold applies.
- ORG_TAN_NO — The organization-level Tax Account Number tethering the threshold to a reporting entity.
- PARTY_ID — Foreign key to HZ_PARTIES, linking the threshold to a specific trading party or vendor.
- PARTY_TYPE — Classifies the party category to which the threshold definition applies.
- PARTY_PAN_NO — The party Permanent Account Number used for statutory reporting and matching.
- FIN_YEAR — The financial year for which the threshold amount is valid.
- TOTAL_THRESHOLD_AMT — The cumulative threshold amount configured for the regime, organization, and party combination.
- TOTAL_THRESHOLD_BASE_AMT — The corresponding base-currency threshold amount used for comparative evaluation.
- THRESHOLD_SLAB_ID — Foreign key to JAI_AP_TDS_THHOLD_SLABS, associating the threshold with a defined slab structure.
- OBJECT_VERSION_NUMBER — Optimistic locking column maintained by the framework.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
The business key is captured by the JAI_RGM_THRESHOLDS_U2 unique index over (REGIME_ID, ORG_TAN_NO, PARTY_TYPE, PARTY_ID, FIN_YEAR), confirming that a single threshold record exists per regime, organization, party type, party, and fiscal year.
Common Use Cases and Queries
Typical usage involves determining whether cumulative transactions for a party have crossed the configured threshold within a financial year. A representative query retrieves the current threshold for a party and regime:
- SELECT threshold_id, total_threshold_amt, total_threshold_base_amt FROM ja.jai_rgm_thresholds WHERE regime_id = :p_regime AND org_tan_no = :p_tan AND party_type = :p_type AND party_id = :p_party AND fin_year = :p_year;
- Joining to HZ_PARTIES to resolve party names for threshold exception reports.
- Joining to JAI_AP_TDS_THHOLD_SLABS to evaluate slab-based deduction rates.
- Reporting cumulative thresholds by financial year against actual transaction totals for statutory reconciliation.
Reporting scenarios include threshold utilization dashboards, PAN-level compliance extracts, and slab validation audits performed by tax and localization administrators.
Related Objects
The following objects are most significant in relation to JAI_RGM_THRESHOLDS, based on the documented foreign key network:
- JAI_RGM_THRESHOLD_DTLS — Child detail table referencing JAI_RGM_THRESHOLDS.THRESHOLD_ID, storing line-level threshold information.
- HZ_PARTIES — Referenced via PARTY_ID, providing registered party master data.
- JAI_AP_TDS_THHOLD_SLABS — Referenced via THRESHOLD_SLAB_ID, defining TDS threshold slab structures.
- JAI_RGM_DEFINITIONS — Referenced via REGIME_ID, supplying regime configuration metadata.
Together these objects form the threshold configuration and evaluation chain used by the India localization regime management functionality.
-
This table stores threshold amount for ORG_TAN_NUM ,PARTY_PAN_NUM and FIN_YEAR
-
This table stores threshold amount for ORG_TAN_NUM ,PARTY_PAN_NUM and FIN_YEAR
-
TABLE: JA.JAI_RGM_THRESHOLDS 12.1.1
-
TABLE: JA.JAI_RGM_THRESHOLDS 12.2.2
-
VIEW: JA.JAI_RGM_THRESHOLDS# 12.2.2
-
VIEW: JA.JAI_RGM_THRESHOLDS# 12.2.2
-
12.1.1 DBA Data 12.1.1
-
This table stores classification details for each threshold header
-
This table stores classification details for each threshold header
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
PACKAGE: APPS.JAI_CONSTANTS 12.1.1
-
PACKAGE: APPS.JAI_CONSTANTS 12.2.2
-
eTRM - JA Tables and Views 12.1.1
The 'JA_CN_SYSTEM_PARAMETERS_ALL' table stores information defined by 'System Options' form, 'Electronic Accounting Book Export' program will get most data from data in the table. A legal entity can only have one record in the table.
-
eTRM - JA Tables and Views 12.2.2
The 'JA_CN_VOUCHER_NUMBER' table stores the voucher number of GL journal lines.
-
eTRM - JA Tables and Views 12.1.1
The 'JA_CN_SYSTEM_PARAMETERS_ALL' table stores information defined by 'System Options' form, 'Electronic Accounting Book Export' program will get most data from data in the table. A legal entity can only have one record in the table.
-
12.2.2 DBA Data 12.2.2
-
eTRM - JA Tables and Views 12.2.2
The 'JA_CN_VOUCHER_NUMBER' table stores the voucher number of GL journal lines.
-
12.1.1 DBA Data 12.1.1