Results for “exception_setup_flag”

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

Overview

JAI_AP_TDS_SITE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JA (Asia/Pacific Localizations) product family. It exposes Tax Deducted at Source (TDS) configuration at the vendor site level, consolidating withholding tax attributes that Oracle Payables and the India localizations use to determine how tax should be deducted on invoices and payments. The view is documented as VALID in ETRM for releases 12.1.1 and 12.2.2 and is defined with a UNION ALL of two underlying threshold views, which allows it to present both site-specific threshold assignments and records where no site-level threshold has been configured.

The view is primarily informational and integration-oriented. Rather than storing data, it provides a stable, denormalized projection of TDS vendor and site attributes—including PAN and TAN numbers, section codes, and threshold setup names—so that reports, concurrent programs, and custom extensions can query withholding tax setup without navigating the more granular threshold tables directly.

Underlying Base Objects

The documented base objects referenced by JAI_AP_TDS_SITE_V are:

• JAI_AP_TDS_TH_VSITE_V (VIEW) — the vendor-site threshold view, supplying records where a site-level TDS threshold setup exists.
• JAI_AP_TDS_NULLSITE_THHOLD_V (VIEW) — supplies records for vendor sites where no site-specific threshold is defined, ensuring such vendors remain visible.
• FND_GLOBAL (PACKAGE) — the standard EBS package used for session context such as responsibilities, users, and organization identifiers; it is referenced for security and context resolution within the localization logic.

The view unions the two threshold views column-for-column, so every row carries the same ten attributes regardless of whether it originated from the site-specific or the null-site branch. The UNION ALL preserves duplicates and avoids the sort overhead of a plain UNION, which is appropriate for a read-only reporting view.

Key Columns

• VENDOR_ID — supplier identifier linking the row to the AP supplier record.
• TDS_VENDOR_TYPE_LOOKUP_CODE — lookup classifying the vendor type for TDS purposes.
• VENDOR_SITE_ID — the specific supplier site to which the TDS configuration applies.
• PAN_NO — Permanent Account Number of the vendor, a statutory Indian tax identifier.
• TAN_NO — Tax Deduction and Collection Account Number, the identifier the deductor reports against; this is the column most directly associated with the "tan_no" search.
• SECTION_CODE — the income tax section under which deduction is made (for example, the applicable TDS section).
• SECTION_TYPE — categorizes the section, distinguishing how the rate or threshold is applied.
• THRESHOLD_SETUP_NAME — the named threshold configuration governing exemption limits.
• THRESHOLD_HDR_ID — surrogate key to the threshold setup header.
• EXCEPTION_SETUP_FLAG — indicates whether an exception to the standard threshold applies.

Common Use Cases and Queries

Typical uses include validating that supplier sites have TAN and PAN data captured, reconciling threshold setups against withholding tax definitions, and feeding downstream India TDS returns. A simple lookup by tax account number is shown below:

• SELECT vendor_id, vendor_site_id, pan_no, tan_no, section_code FROM apps.jai_ap_tds_site_v WHERE tan_no = :tan_no;
• SELECT vendor_site_id, threshold_setup_name, exception_setup_flag FROM apps.jai_ap_tds_site_v WHERE vendor_id = :vendor_id ORDER BY vendor_site_id;
• SELECT section_code, section_type, COUNT(*) FROM apps.jai_ap_tds_site_v WHERE tan_no IS NULL GROUP BY section_code, section_type;

Because the view is a UNION ALL over two threshold views, queries should filter on VENDOR_SITE_ID or TAN_NO to limit result sets. Joins to PO_VENDORS and PO_VENDOR_SITES on VENDOR_ID and VENDOR_SITE_ID respectively are common when the objective is a full supplier report.