Results for “default_tax_id”

30 results




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

Overview

JAI_AP_TDS_INV_TAXES is an Asia/Pacific Localizations (JA product family) table owned by the JA schema that stores details of all Tax Deducted at Source (TDS) taxes applicable on an Oracle Payables invoice. It sits at the intersection of Oracle Payables invoice processing and the India/APAC TDS withholding framework, capturing the tax determination, threshold evaluation, and calculated amounts for each invoice distribution, invoice line, or invoice-level section that is subject to TDS. Because TDS obligations in India are governed by cumulative and single-transaction thresholds, this table records both the defaulted tax and the actual tax applied after threshold consideration.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying JAI_AP_TDS_INV_TAXES as a link table. Its many outbound foreign keys to invoice, threshold header/group/slab/transaction, and tax definition tables indicate it resolves and associates multiple business keys rather than acting as a standalone hub. Practitioners designing a warehouse layer over Oracle EBS would therefore treat this object as an associative entity connecting invoice distributions to the TDS tax and threshold dimensions.

Key Information Stored

The surrogate primary key is TDS_INV_TAX_ID, enforced through JAI_AP_TDS_INV_TAXES_PK. The documented business-key candidate is JAI_AP_TDS_INV_TAXES_UK1, a unique index over INVOICE_ID, INVOICE_LINE_NUMBER, INVOICE_DISTRIBUTION_ID, SECTION_TYPE, and ACTUAL_TAX_ID, which guarantees that a given tax cannot be recorded twice for the same invoice distribution and section.

The most significant columns include:

Common Use Cases and Queries

Typical scenarios include reconciling TDS deducted against invoice distributions, auditing cases where the defaulted tax differs from the actual tax, and reporting threshold utilisation. A representative query joining to the invoice header might read:

  • SELECT t.INVOICE_ID, t.INVOICE_LINE_NUMBER, t.ACTUAL_TAX_ID, t.CALC_TAX_AMOUNT, t.PROCESS_STATUS FROM JA.JAI_AP_TDS_INV_TAXES t WHERE t.INVOICE_ID = :invoice_id;
  • SELECT t.TDS_INV_TAX_ID, t.DEFAULT_TAX_ID, t.ACTUAL_TAX_ID, t.FUNC_TAX_AMOUNT FROM JA.JAI_AP_TDS_INV_TAXES t WHERE t.USER_DELETED_TAX_FLAG = 'N' AND t.ACTUAL_TAX_ID <> t.DEFAULT_TAX_ID;
  • SELECT t.THRESHOLD_SLAB_ID, SUM(t.TAX_AMOUNT) FROM JA.JAI_AP_TDS_INV_TAXES t GROUP BY t.THRESHOLD_SLAB_ID;

These patterns support supplier TDS return preparation, tax category audit, and diagnostics of threshold-crossing behaviour on specific invoices.

Related Objects

The table participates in a dense relationship graph, and the most significant related objects are:

  • AP_INVOICES_ALL via JAI_AP_TDS_INV_TAXES.INVOICE_ID — the parent invoice header.
  • JAI_CMN_TAXES_ALL via ACTUAL_TAX_ID and DEFAULT_TAX_ID — the tax definitions for defaulted and actual taxes.
  • JAI_AP_TDS_THHOLD_HDRS via THRESHOLD_HDR_ID — the threshold header driving TDS logic.
  • JAI_AP_TDS_THHOLD_GRPS via THRESHOLD_GRP_ID and DEFAULT_THRESHOLD_GRP_ID — threshold grouping used for cumulative aggregation.
  • JAI_AP_TDS_THHOLD_SLABS via THRESHOLD_SLAB_ID, THRESHOLD_SLAB_ID_SINGLE, DEFAULT_CUM_THRESHOLD_SLAB_ID, and DEFAULT_SIN_THRESHOLD_SLAB_ID — slab definitions for cumulative and single-transaction thresholds.
  • JAI_AP_TDS_THHOLD_TRXS via THRESHOLD_TRX_ID — threshold transaction history.

These joins underpin any reporting that traces a deducted TDS amount from invoice back to the tax definition and threshold slab that produced it.