Results for “certificate_line_num”

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

Overview

The JA.JAI_AP_TDS_INV_PAYMENTS table is a core data object within the Oracle E-Business Suite Asia/Pacific Localizations module, specifically supporting Tax Deducted at Source (TDS) processing for India and other regional statutory requirements. The table records the details of all TDS-relevant invoices that have been paid, providing the linkage between Accounts Payable payment transactions and the withholding tax structures required for statutory reporting such as Form 16 and Form 16A. Each record represents a single paid invoice line associated with a TDS tax event, capturing the full financial and tax footprint of that payment. The object is classified as VALID in the ETRM metadata, and its 39 documented columns confirm an operational rather than a setup-oriented role.

From a Data Vault modeling perspective, the heuristic classification is link. This is consistent with the fanned-out foreign key structure of the table: it connects invoices, payments, checks, suppliers, taxes, and Form 16 headers, rather than acting as a hub (which would hold a single business entity) or a satellite (which would hold descriptive attributes for one hub). Modelers should treat this as a transactional intersection that stitches together AP and TDS domains.

Key Information Stored

The surrogate primary key is TDS_PAYMENT_ID, reinforced by the unique index JAI_AP_TDS_INV_PAYMENTS_U1. This column uniquely identifies each TDS payment record and is the most reliable join key. The remaining columns fall into several logical groups:

• Invoice linkage: INVOICE_ID, INVOICE_DATE, PREPAY_INVOICE_ID, and PARENT_INVOICE_ID tie the record to AP_INVOICES_ALL and handle prepayment and cancellation relationships (PARENT_INVOICE_CANCEL_FLAG).
• Payment and check detail: INVOICE_PAYMENT_ID, CHECK_ID, CHECK_DATE, CHECK_AMOUNT, and PAYMENT_AMOUNT capture the disbursement side, referencing AP_INVOICE_PAYMENTS_ALL and AP_CHECKS_ALL.
• Tax computation: TDS_SECTION, TDS_TAX_ID, TDS_TAX_RATE, TAXABLE_BASIS, and TAX_AMOUNT hold the withholding tax basis and computed amounts.
• Supplier and authority: TAX_AUTHORITY_ID, TAX_AUTHORITY_SITE_ID, VENDOR_ID, VENDOR_SITE_ID, and ORG_TAN_NUM identify the deductee and the tax collection authority, including the TAN registration number.
• Statutory posting: FORM16_HDR_ID, CERTIFICATE_NUM, and CERTIFICATE_LINE_NUM link the payment to Form 16 header and certificate records required for annual returns.
• Audit and concurrency: the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE), PROGRAM_ID, REQUEST_ID, and OBJECT_VERSION_NUMBER support traceability and optimistic locking.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include identifying all TDS-bearing payments for a vendor within a financial year, verifying that the TDS deducted matches the tax authority remittance, and generating data for Form 16/16A certificate preparation. A common join pattern links this table to AP_INVOICES_ALL and AP_CHECKS_ALL:

SELECT t.TDS_PAYMENT_ID, t.INVOICE_ID, i.INVOICE_NUM, t.CHECK_ID, t.CHECK_AMOUNT, t.TAX_AMOUNT, t.ORG_TAN_NUM
FROM JA.JAI_AP_TDS_INV_PAYMENTS t
JOIN AP.AP_INVOICES_ALL i ON i.INVOICE_ID = t.INVOICE_ID
WHERE t.FIN_YEAR = :year AND t.VENDOR_ID = :vendor_id;

Other scenarios include threshold-based deduction audits (joining THRESHOLD_TRX_ID to JAI_AP_TDS_THHOLD_TRXS) and tax category analysis via TAX_CATEGORY_ID. Because the table is keyed on the payment, it is the natural driver for any extract of TDS deducted at payment time.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign key relationships:

• AP_INVOICES_ALL — joined on INVOICE_ID; source of invoice header detail.
• AP_INVOICE_PAYMENTS_ALL — joined on INVOICE_PAYMENT_ID; payment-level allocation detail.
• AP_CHECKS_ALL — joined on CHECK_ID; payment instrument and disbursement information.
• JAI_AP_TDS_F16_HDRS_ALL — joined on FORM16_HDR_ID; statutory certificate header data.
• JAI_CMN_TAXES_ALL — joined on TDS_TAX_ID; withholding tax definition and rate setup.
• AP_SUPPLIERS — joined on TAX_AUTHORITY_ID; the tax authority recipient of the deduction.
• JAI_CMN_VENDOR_SITES — joined on VENDOR_ID and VENDOR_SITE_ID; deductee supplier and site context.
• AP_SUPPLIER_SITES_ALL — joined on VENDOR_SITE_ID; alternate supplier site reference.
• JAI_AP_TDS_THHOLD_TRXS — joined on THRESHOLD_TRX_ID; threshold transaction tracking for cumulative deduction logic.

These relationships confirm the table's role as a central transactional link uniting AP payment data with India TDS statutory processing within the JA localization schema.