Results for “threshold_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JAI_AP_TDS_THHOLD_TYPES is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product family. It stores the detail-level definitions of Tax Deducted at Source (TDS) threshold types, each tied to a parent TDS threshold header record. In the Oracle EBS 12.1.1 and 12.2.2 releases, this object serves as a child table in the withholding tax threshold configuration hierarchy, allowing multiple threshold types to be grouped under a single threshold header for the purpose of computing cumulative TDS liability across a defined period.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table carries a dedicated surrogate primary key and its row identity is anchored on a single business key candidate (THRESHOLD_TYPE_ID), which is characteristic of an entity hub. Downstream reference tables such as JAI_AP_TDS_THHOLD_SLABS, JAI_AP_TDS_THHOLD_TAXES, JAI_AP_TDS_REPOSITORY, and JAI_AP_TDS_THHOLD_ACCOUNT all point to it, reinforcing this hub role within the localizations data model.

Key Information Stored

The documented schema contains 12 columns. The most significant are summarized below.

• THRESHOLD_TYPE_ID — Surrogate primary key, enforced through the unique index JAI_AP_TDS_THHOLD_TYPES_PK. It uniquely identifies each threshold type row and is the join key used by all dependent tables.
• THRESHOLD_HDR_ID — Foreign key to JAI_AP_TDS_THHOLD_HDRS, linking each detail type to its parent threshold header.
• THRESHOLD_TYPE — Descriptive identifier for the category of threshold being defined.
• FROM_DATE and TO_DATE — Effective-dating columns that bound the validity period during which the threshold type applies.
• DEFAULT_TYPE — Flag indicating whether this threshold type is treated as the default within its header grouping.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard WHO audit columns that track insert and update provenance.

THRESHOLD_TYPE_ID is both the documented unique index and the primary key, making it the sole business-key candidate available in the metadata. THRESHOLD_HDR_ID is not unique and therefore functions as a foreign-key attribute rather than an alternate key.

Common Use Cases and Queries

Typical reporting scenarios resolve the threshold configuration hierarchy or trace tax slabs and tax mappings back to their originating type. A representative join query retrieves all types for a given header:

• SELECT t.threshold_type_id, t.threshold_type, t.from_date, t.to_date FROM ja.jai_ap_tds_thhhold_types t WHERE t.threshold_hdr_id = :p_hdr_id — wait, correct table name is JAI_AP_TDS_THHOLD_TYPES.
• Resolving effective-dated lookups by filtering on SYSDATE BETWEEN FROM_DATE AND TO_DATE.
• Joining to JAI_AP_TDS_THHOLD_SLABS on THRESHOLD_TYPE_ID to reproduce the slab ranges used in TDS computation.
• Joining to JAI_AP_TDS_THHOLD_TAXES on THRESHOLD_TYPE_ID to identify which taxes participate in a threshold group.
• Data migration or extract scripts that pivot the header-to-type relationship for downstream reporting.

Related Objects

• JAI_AP_TDS_THHOLD_HDRS — Parent table; joined via THRESHOLD_HDR_ID.
• JAI_AP_TDS_THHOLD_SLABS — Child table; references THRESHOLD_TYPE_ID.
• JAI_AP_TDS_THHOLD_TAXES — Child table; references THRESHOLD_TYPE_ID.
• JAI_AP_TDS_REPOSITORY — References THRESHOLD_TYPE_ID for repository-level TDS definitions.
• JAI_AP_TDS_THHOLD_ACCOUNT — References THRESHOLD_TYPE_ID for accounting mappings.