Search Results jai_ap_tds_f16_hdrs_all




Overview
Explore in AI Chat

Overview

The table JAI_AP_TDS_F16_HDRS_ALL is a core data object within the Oracle E-Business Suite Asia/Pacific Localizations module (product JA). It serves as the master repository for header-level information pertaining to Tax Deducted at Source (TDS) certificates, specifically those related to Form 16, a common statutory form in jurisdictions like India. This table functions as the central parent record for TDS certificate generation and tracking, linking vendor information, tax authorities, and organizational data to subsequent certificate lines and payment details. Its role is critical for statutory compliance reporting and reconciliation within the localized financial and payables processes of Oracle EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores the defining attributes of a TDS certificate. While the full column list is not provided in the metadata, the documented foreign key relationships and primary key indicate its critical data elements. The primary key, FORM16_HDR_ID, uniquely identifies each certificate header. Essential foreign key columns include VENDOR_ID and VENDOR_SITE_ID, which link to the supplier and site in HZ_PARTIES and HZ_PARTY_SITES, respectively. The TDS_TAX_ID links to the specific tax rate definition in JAI_CMN_TAXES_ALL. The ORG_ID associates the certificate with an operating unit in HR_ALL_ORGANIZATION_UNITS, enforcing multi-org security. Finally, TAX_AUTHORITY_ID links to the relevant tax authority party record. Collectively, these columns establish the who (vendor), what (tax type), where (organization), and under which authority the TDS certificate was issued.

Common Use Cases and Queries

This table is primarily accessed for statutory reporting, audit inquiries, and payment reconciliation. A common operational use case is generating or reviewing a TDS certificate for a specific vendor and financial period. For reporting, analysts often join this header data with related transaction lines to summarize total TDS deducted by vendor or tax authority. A typical query pattern would retrieve certificate headers for a given operating unit and date range:

  • SELECT hdr.form16_hdr_id, hz.party_name vendor_name, tax.tax_name, hdr.certificate_number FROM jai_ap_tds_f16_hdrs_all hdr, hz_parties hz, jai_cmn_taxes_all tax WHERE hdr.vendor_id = hz.party_id AND hdr.tds_tax_id = tax.tax_id AND hdr.org_id = :p_org_id AND hdr.certificate_date BETWEEN :p_date_from AND :p_date_to;

Another critical use case involves tracing payments linked to a certificate by joining to the JAI_AP_TDS_INV_PAYMENTS or JAI_AP_TDS_PAYMENTS tables via the FORM16_HDR_ID.

Related Objects

The table maintains defined relationships with several key EBS objects, as per the provided foreign key metadata. It is a parent table to transaction detail tables and a child to master data tables.

  • Parent Tables (Referenced by JAI_AP_TDS_F16_HDRS_ALL):
    • HZ_PARTIES (on VENDOR_ID and TAX_AUTHORITY_ID)
    • HZ_PARTY_SITES (on VENDOR_SITE_ID)
    • JAI_CMN_TAXES_ALL (on TDS_TAX_ID)
    • HR_ALL_ORGANIZATION_UNITS (on ORG_ID)
  • Child Tables (Referencing JAI_AP_TDS_F16_HDRS_ALL):
    • JAI_AP_TDS_INV_PAYMENTS (on FORM16_HDR_ID)
    • JAI_AP_TDS_PAYMENTS (on FORM16_HDR_ID)

These relationships form the integrity backbone for the TDS certificate lifecycle, ensuring that all transactions are tied to a valid header record which itself is linked to approved master data.