Results for “jai_ap_tds_th_vsite_v”

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

Overview

JAI_AP_TDS_TH_VSITE_V is an APPS-owned database view within the Oracle E-Business Suite Asia/Pacific Localizations (JA) product family. It is a reporting and resolution layer that joins vendor master, vendor site, Tax Deducted at Source (TDS) vendor header, organization TAN, vendor type, and TDS threshold setup data into a single flattened result set. The view is defined over Oracle Payables vendor entities (PO_VENDORS and PO_VENDOR_SITES_ALL) and several JA TDS localization objects, and it is marked VALID in both 12.1.1 and 12.2.2 reference metadata.

The view's primary role is to resolve which TDS threshold setup applies to a given vendor and vendor site combination for a specific organization TAN. It evaluates the exception configuration flag (EXCEPTION_SETUP_FLAG) on the threshold header and, using correlated subqueries against the JAI_AP_TDS_THHOLD_XCEPS exception table, determines whether a general rule or a vendor-specific exception governs the threshold. This makes it a foundational object for TDS threshold validation, withholding determination, and downstream reporting in Indian localizations.

Underlying Base Objects

The documented base objects include both views and synonyms:

• PO_VENDORS and PO_VENDOR_SITES_ALL (views) — supply VENDOR_ID and VENDOR_SITE_ID.
• JAI_AP_TDS_VENDOR_HDRS (synonym) — supplies PAN_NO at the vendor/site level.
• JAI_AP_TDS_ORG_TAN_V (view) — supplies ORG_TAN_NUM for the operating organization.
• JAI_AP_TDS_VNDR_TYPE_V (view) — supplies TDS_VENDOR_TYPE_LOOKUP_CODE.
• JAI_AP_TDS_THHOLD_HDRS (synonym) — supplies SECTION_CODE, SECTION_TYPE, THRESHOLD_SETUP_NAME, THRESHOLD_HDR_ID, and EXCEPTION_SETUP_FLAG.
• JAI_AP_TDS_THHOLD_XCEPS (synonym) — referenced inside the EXCEPTION_SETUP_FLAG correlated subqueries.
• FND_GLOBAL (package) — the standard Oracle Application Object Library context package, typically invoked to supply organization/user context (e.g., ORG_ID via FND_GLOBAL.ORG_ID) in localization views.

The join logic links A.VENDOR_ID to B.VENDOR_ID, B.VENDOR_ID to C.VENDOR_ID, B.VENDOR_SITE_ID to C.VENDOR_SITE_ID, B.ORG_ID to D.ORGANIZATION_ID, and A.VENDOR_ID to E.VENDOR_ID, with the vendor type lookup code equated to the threshold header's VENDOR_TYPE_LOOKUP_CODE. The exception branch filters threshold headers by matching SECTION_CODE, VENDOR_TYPE_LOOKUP_CODE, ORG_TAN, and VENDOR_PAN.

Key Columns

• VENDOR_ID / VENDOR_SITE_ID — identifiers for the supplier and supplier site.
• TDS_VENDOR_TYPE_LOOKUP_CODE — classification of the vendor for TDS purposes (e.g., company, individual, non-resident).
• PAN_NO — Permanent Account Number of the vendor from the TDS vendor header.
• TAN_NO — Tax Deduction Account Number of the deductor organization.
• SECTION_CODE / SECTION_TYPE — the Income Tax Act section and type driving the threshold.
• THRESHOLD_SETUP_NAME / THRESHOLD_HDR_ID — the named threshold setup and its header identifier.
• EXCEPTION_SETUP_FLAG — indicates whether a general threshold rule ('N') or an explicit vendor exception ('Y') applies.

Common Use Cases and Queries

Typical scenarios include auditing which threshold setup resolves for a supplier site, diagnosing missing or conflicting TDS configuration, and supplying data to withholding reports and reconciliations. A representative query follows:

SELECT vendor_id, vendor_site_id, pan_no, tan_no,
       section_code, threshold_setup_name, exception_setup_flag
FROM   apps.jai_ap_tds_th_vsite_v
WHERE  vendor_id = :p_vendor_id
AND    vendor_site_id = :p_vendor_site_id;

Because the view is defined over intersections of vendor, site, TAN, and threshold data, joins that return no rows generally indicate a configuration gap — such as a missing TAN for the organization or an unmatched vendor type — rather than a data error.