Search Results jai_cmn_document_taxes

Overview

The JAI_CMN_DOCUMENT_TAXES table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the JA (Asia/Pacific Localizations) product module. Its primary function is to store detailed tax information for transactions processed under the India Localization framework. This table acts as a central ledger for tax line items, enabling the system to calculate, record, and report on various statutory taxes applicable to business documents such as invoices and receipts within the Indian regulatory context. Its existence is critical for ensuring tax compliance and accurate financial reporting for organizations operating under this localization.

Key Information Stored

The table's structure is designed to capture the relationship between a transaction document and its associated tax calculations. While the full column list is not detailed in the provided metadata, the documented foreign key relationships reveal its most critical data points. The primary key, DOC_TAX_ID, uniquely identifies each tax record. Essential foreign key columns include TAX_ID, which links to the master tax definition in JAI_CMN_TAXES_ALL, and TAX_CATEGORY_ID, which references the tax category in JAI_CMN_TAX_CTGS_ALL. The SOURCE_DOC_ID column links the tax line to its originating financial document, such as a cash receipt in AR_CASH_RECEIPTS_ALL. Furthermore, the VENDOR_ID column establishes a relationship with the trading party in HZ_PARTIES, crucial for determining tax applicability based on the supplier or customer. Collectively, these columns store the who, what, and how much of transactional tax data.

Common Use Cases and Queries

This table is fundamental for tax reporting, audit trails, and reconciliation processes. A common operational use case is tracing all tax calculations for a specific invoice or receipt to verify accuracy before submission to tax authorities. For reporting, it is frequently joined to document and party tables to generate tax registers or statutory forms like India's GST returns. A typical analytical query might involve summarizing tax amounts by vendor or tax type over a period.

Sample Query Pattern:
SELECT dct.source_doc_id,
ht.party_name vendor_name,
jt.tax_code,
dct.tax_amount
FROM jai_cmn_document_taxes dct,
jai_cmn_taxes_all jt,
hz_parties ht
WHERE dct.tax_id = jt.tax_id
AND dct.vendor_id = ht.party_id
AND dct.creation_date BETWEEN :p_start_date AND :p_end_date;
This pattern extracts a basic tax ledger by joining to the tax master and party tables.

Related Objects

The JAI_CMN_DOCUMENT_TAXES table is integral to a network of related objects, primarily defined by its foreign key constraints. It is a child table that references several key master and transaction tables:

• JAI_CMN_TAX_CTGS_ALL: Joined via TAX_CATEGORY_ID. This provides the tax category (e.g., Input Tax, Output Tax) for the document tax line.
• JAI_CMN_TAXES_ALL: Joined via TAX_ID. This links to the master definition of the tax rate, type, and code.
• AR_CASH_RECEIPTS_ALL: Joined via SOURCE_DOC_ID. This connects the tax record to its source cash receipt transaction.
• HZ_PARTIES: Joined via VENDOR_ID. This provides detailed information about the supplier or customer associated with the taxable transaction.

These relationships position JAI_CMN_DOCUMENT_TAXES as a central hub for querying comprehensive tax data that bridges master definitions, transactional documents, and trading partners.