Results for “threshold_type_id”

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

Overview

JAI_AP_TDS_THHOLD_LE_V is a database view owned by the APPS schema within the JA (Asia/Pacific Localizations) product family of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its documented purpose is to obtain the legal entity associated with withholding tax threshold configuration used by the India Localizations' Tax Deducted at Source (TDS) functionality. Functionally, the view provides a de-duplicated projection of legal entity, threshold header, and threshold type identifiers drawn from the threshold account mapping table.

The view plays a supporting role rather than a transactional one. It does not store data; it exposes a distinct set of threshold-to-legal-entity relationships that downstream reporting, validation logic, and localization integrations consume when determining which thresholds apply to which legal entity. Because the same threshold header may be mapped across multiple accounts, the DISTINCT operator is significant: consumers of this view receive one row per unique combination of legal entity, threshold header, and threshold type, which is precisely the grain required for legal-entity-level assignment and lookup.

Underlying Base Objects

The view is defined over a single documented base object, referenced in ETRM as the synonym JAI_AP_TDS_THHOLD_ACCOUNT (alias MAP in the view text). The complete view definition is:

• SELECT DISTINCT MAP.LEGAL_ENTITY_ID, MAP.THRESHOLD_HDR_ID, MAP.THRESHOLD_TYPE_ID FROM JAI_AP_TDS_THHOLD_ACCOUNT MAP

In practice, the synonym resolves to the underlying threshold account mapping table maintained by the JA localization. This table associates legal entities with threshold headers and threshold types for TDS processing, and it therefore carries the raw mappings that the view distills. The view introduces no joins, filters, or calculations — it is a pure de-duplication and projection layer. This design keeps the view lightweight and makes it a stable interface for concurrent programs, forms, and custom reports that require the unique legal entity / threshold relationships without traversing the full mapping table.

Key Columns

The view exposes exactly three columns, each of which is central to threshold resolution:

• LEGAL_ENTITY_ID — The identifier of the legal entity (registered legal organization) to which the threshold mapping applies. This drives legal-entity-level tax determination and reporting.
• THRESHOLD_HDR_ID — The identifier of the threshold header record, linking the mapping to the configured TDS threshold definition (for example, cumulative or per-transaction thresholds).
• THRESHOLD_TYPE_ID — The identifier of the threshold type, classifying the nature of the threshold being applied. This column is the key term associated with the common search for "threshold_type_id" and is typically joined to the threshold type setup entity to resolve descriptive attributes such as threshold category and applicability.

The combination of these three columns forms the logical key of the view's result set, reflecting the DISTINCT projection over the mapping table.

Common Use Cases and Queries

The view is most frequently used to enumerate which thresholds are configured for a given legal entity, or, conversely, to determine which legal entities share a threshold configuration. Typical consumers include custom India TDS reports, reconciliation extracts, and validation queries executed during localization setup. Sample SQL:

• SELECT LEGAL_ENTITY_ID, THRESHOLD_HDR_ID, THRESHOLD_TYPE_ID FROM APPS.JAI_AP_TDS_THHOLD_LE_V WHERE LEGAL_ENTITY_ID = :p_legal_entity_id; — Retrieve threshold assignments for a specific legal entity.
• SELECT THRESHOLD_TYPE_ID, COUNT(DISTINCT LEGAL_ENTITY_ID) FROM APPS.JAI_AP_TDS_THHOLD_LE_V GROUP BY THRESHOLD_TYPE_ID; — Summarize legal entity coverage per threshold type.
• SELECT DISTINCT LEGAL_ENTITY_ID FROM APPS.JAI_AP_TDS_THHOLD_LE_V WHERE THRESHOLD_HDR_ID = :p_threshold_hdr_id; — Identify all legal entities mapped to a given threshold header.

Because the view performs no filtering beyond DISTINCT, callers should apply their own legal entity, threshold header, or threshold type predicates and, where descriptive text is required, join THRESHOLD_TYPE_ID to the corresponding threshold type setup table. Standard APPS schema grants govern access.