Search Results ap_invoices_all




Overview

The JAI_AP_TDS_F16_DTLS_ALL table resides in the JA schema and belongs to the Asia/Pacific Localizations product family within Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). It stores the detail records of invoices that have been considered against a particular Tax Deducted at Source (TDS) certificate — specifically the Indian Form 16 / Form 16A withholding context. Each row represents a single invoice, or a portion of an invoice, that contributes to the certificate's deducted amount.

The table is most commonly encountered when querying the Payables subledger, because it references AP_INVOICES_ALL twice (the original invoice and its TDS counterpart) and therefore appears in searches originally motivated by the term "ap_invoices_all". Its relationship to Payables is by foreign key, not by inheritance: JAI_AP_TDS_F16_DTLS_ALL augments standard Payables data with localization-specific certification detail.

From a dimensional-modelling perspective, the mined Data Vault classification is link. This reflects the table's role as an associative construct joining an AP invoice, a TDS invoice, and an AP invoice payment across organizational context. Treating it as a link (rather than a hub or satellite) is a heuristic suggestion derived from the foreign-key structure, not a documented Oracle design statement.

Key Information Stored

The table is owned by JA and documents 22 columns. The surrogate primary key is a single column:

The most significant descriptive and foreign-key columns are:

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include verifying which supplier invoices were captured on a Form 16 certificate, reconciling withheld versus remitted TDS, and validating certificate totals against invoice-level detail.

  • Certificate drill-down: join JAI_AP_TDS_F16_DTLS_ALL.INVOICE_ID to AP_INVOICES_ALL.INVOICE_ID to list invoice numbers, vendor, and amounts behind a given CERTIFICATE_NUM.
  • Withheld-to-paid reconciliation: compare TDS_INVOICE_AMT against TDS_INVOICE_AMT_PAID by FIN_YR and ORG_ID to expose remittance shortfalls.
  • Operating unit reporting: aggregate by ORG_ID via HR_ALL_ORGANIZATION_UNITS to produce TDS liability summaries per business unit.
  • Payment traceability: join INVOICE_PAYMENT_ID to AP_INVOICE_PAYMENTS_ALL to identify the checks or payments that triggered withholding.

A representative query pattern filters by financial year and certificate number and joins both AP invoice roles separately for original and TDS invoice context.

Related Objects

The following objects are directly referenced or reference this table through documented keys:

  • AP_INVOICES_ALL — joined twice, on INVOICE_ID and TDS_INVOICE_ID.
  • AP_INVOICE_PAYMENTS_ALL — joined on INVOICE_PAYMENT_ID.
  • HR_ALL_ORGANIZATION_UNITS — joined on ORG_ID.
  • JAI_AP_TDS_F16_ALL / certificate header objects — logical parent supplying CERTIFICATE_NUM context within the localization.
  • JAI_AP_TDS_F16_DTLS_ALL_PK — the unique index enforcing the surrogate key on FORM16_DTL_ID.

Because the table is a localization extension of Payables, direct DML is discouraged; certification data is normally maintained through the JA TDS certificate concurrent programs and forms. Financial-year and TAN columns make it a primary source for Indian statutory withholding returns (Form 26Q/27Q) reconciliation.