Results for “tds_cert”

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

Overview

APPS.JAI_AP_TDS_F16_DTLS_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, defined in the APPS schema. It exposes the line-level detail of Indian withholding tax (Tax Deducted at Source, or TDS) records as they are aggregated onto Form 16 certificates. Form 16 is the statutory certificate that a deductor issues to a deductee documenting the tax withheld during a financial year. The view consolidates certificate header attributes, invoice-level TDS payment facts, base invoice organization context, and tax-rate configuration into a single denormalized result set, allowing the ETRM extraction, India localization reporting, and downstream reporting tools to retrieve Form 16 detail without traversing multiple normalized tables.

The object is of particular interest to users searching on the term "tds_payments", since the driving table of the view, JAI_AP_TDS_INV_PAYMENTS, is aliased as TDS_PAYMENTS within the view definition and supplies the majority of the exposed columns.

Underlying Base Objects

The view is defined over four referenced base objects, all resolved in the APPS schema through synonyms:

• JAI_AP_TDS_INV_PAYMENTS (aliased TDS_PAYMENTS) — the primary fact source, holding invoice-payment-level TDS amounts, taxable basis, rates, and the foreign key links to the Form 16 header and the TDS tax.
• JAI_AP_TDS_F16_HDRS_ALL (aliased TDS_CERT) — the Form 16 certificate header, supplying certificate number, financial year, organization TAN, and audit columns.
• AP_INVOICES_ALL (aliased BASE_INVOICES) — the parent payables invoice, used mainly to derive ORG_ID for the operating unit context.
• JAI_CMN_TAXES_ALL (aliased TAX) — the tax configuration, providing the section/form type, surcharge rate, and cess rate applicable to the TDS tax.

Joins are established on TDS_PAYMENTS.FORM16_HDR_ID = TDS_CERT.FORM16_HDR_ID, TDS_PAYMENTS.PARENT_INVOICE_ID = BASE_INVOICES.INVOICE_ID, and TAX.TAX_ID = TDS_PAYMENTS.TDS_TAX_ID.

Key Columns

• FORM16_HDR_ID — identifier of the Form 16 certificate header record.
• CERTIFICATE_NUM and LINE_NUM — the certificate number and its line sequence, together providing the natural line key.
• INVOICE_ID and TDS_INVOICE_ID — the parent payables invoice and the TDS invoice reference respectively.
• INVOICE_AMOUNT and TAXABLE_BASIS — both mapped from TAXABLE_BASIS, representing the amount on which TDS is computed.
• TDS_TAX_RATE and TDS_INVOICE_AMT — the applied withholding rate and the resulting withheld tax amount (TAX_AMOUNT).
• INVOICE_PAYMENT_ID — the payment against which TDS was deducted.
• ORG_ID — operating unit, sourced from the parent invoice.
• IT_CERTIFICATE_NUMBER — mapped from TAX.STFORM_TYPE, the certificate/section type from tax configuration.
• FIN_YR, ORG_TAN_NUM — financial year and deductor TAN on the certificate header.
• SURCHARGE_RATE and CESS_RATE — statutory levies from JAI_CMN_TAXES_ALL.
• TDS_INV_DATE, TAX_AUTHORITY_ID — invoice date and tax authority reference.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the certificate header.

Common Use Cases and Queries

The view is typically queried when reconciling Form 16 certificates to the individual invoices and payments from which TDS was withheld, when building India statutory reports, or when validating that surcharge and cess are correctly applied.

A representative query filtering by certificate and financial year:

• SELECT certificate_num, line_num, tds_inv_date, invoice_amount, tds_tax_rate, tds_invoice_amt, surcharge_rate, cess_rate FROM apps.jai_ap_tds_f16_dtls_v WHERE fin_yr = :p_fin_yr AND org_tan_num = :p_tan ORDER BY certificate_num, line_num;

A second scenario traces a specific payment back to its certificate line:

• SELECT form16_hdr_id, certificate_num, line_num, invoice_id, tds_invoice_id, invoice_amount, tds_invoice_amt FROM apps.jai_ap_tds_f16_dtls_v WHERE invoice_payment_id = :p_payment_id;

Because ORG_ID is exposed, the view also supports operating-unit-scoped extracts, making it suitable for multi-organization reporting and for one-off data verification during TDS configuration changes or period-close activities.