Search Results jai_cmn_tax_types_all

Overview

JAI_CMN_TAX_TYPES_ALL is a transactional and configuration table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, and it is a core component of the India Localization (and broader Asia/Pacific GST) tax engine. Its stated purpose is to store the tax type definition for GST, meaning each row represents a distinct tax type — such as Central GST, State GST, Integrated GST, cess, or withholding style tax types — that the localization engine applies during transaction processing and tax computation.

In the EBS architecture, the table acts as a master reference for tax determination. It is consumed by tax calculation and reporting routines used across Order Management, Purchasing, Payables, Receivables, and the India GST reports. Because the table name carries the _ALL suffix, it follows the EBS multi-org convention that permits assignment across operating units through an associated org-assignment mapping, while the definitions themselves remain centralized.

Within a heuristic Data Vault classification mined from the foreign key structure, this object is described as standalone. In Data Vault modeling terms, it is therefore best represented as a hub (or a small hub-with-satellite construct) anchored on the TAX_TYPE_ID business key, rather than as a link that bridges two unrelated business keys. Modelers should treat TAX_TYPE_ID as the durable business key of the hub and place descriptive and range attributes in a satellite.

Key Information Stored

The documented physical schema records 15 columns. The most significant are:

• TAX_TYPE_ID — Surrogate primary key of the table; the unique internal identifier for each tax type definition.
• TAX_TYPE_CODE — The user-facing business key / short code used to identify the tax type in setups and lookups.
• REGIME_ID — Foreign key to JAI_RGM_DEFINITIONS, tying the tax type to the tax regime under which it is levied.
• REGIME_CODE — Denormalized regime code, provided for ease of reporting and joins.
• DESCRIPTION — Free-text description of the tax type as displayed in the localization setup forms.
• OFF_SET_TYPE — Indicates the offsetting/accounting treatment applied when the tax type posts to the ledger.
• ROUNDING_FACTOR — Defines rounding behavior applied to computed tax amounts for this tax type.
• START_DATE and END_DATE — Effective dating range governing when the tax type is valid and usable in transactions.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OA Framework to manage concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit (WHO) columns recording who created and last modified the record and when.

The surrogate key (TAX_TYPE_ID) is distinct from the business-key candidate TAX_TYPE_CODE, which is the value users recognize and search for. The effective-dating columns (START_DATE, END_DATE) further qualify uniqueness, since a tax type code may be reused across validity periods.

Common Use Cases and Queries

Typical scenarios include validating tax type configuration, building tax determination reports, and troubleshooting GST calculations that fail to find an applicable tax type for a given regime and date.

A common lookup query retrieves active tax types for a regime:

• Select TAX_TYPE_CODE, DESCRIPTION, OFF_SET_TYPE, ROUNDING_FACTOR FROM JAI_CMN_TAX_TYPES_ALL WHERE REGIME_CODE = :regime AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE + 1);
• Join to JAI_RGM_DEFINITIONS on REGIME_ID to enrich reporting with the regime name and description.
• Filter by TAX_TYPE_CODE to confirm a specific tax type is configured and not end-dated before a transaction date.

Reporting use cases include reconciling the number of defined GST tax types per regime, auditing effective-dating gaps or overlaps, and exporting configuration to data warehouses for downstream tax analytics. When investigating a missing-tax-type error, comparing the transaction date against START_DATE/END_DATE in this table is a standard first diagnostic step.

Related Objects

• PAY_US_TAX_TYPES — Referenced via TAX_TYPE_ID; the base tax type table on which the localization definition depends.
• JAI_RGM_DEFINITIONS — Referenced via REGIME_ID; defines the tax regime to which each tax type belongs.
• JAI_CMN_TAX_RATES_ALL — Companion setup table holding the rates applied to these tax types.
• JAI_CMN_TAX_VALUES and associated GST transaction/registers tables — depend on the tax type definitions for computation and reporting.
• AP/AR/OM/PO transaction tables with India localization attributes — indirectly depend on tax type codes resolved from this table during tax determination.

Because the table is flagged standalone in the relationship data, joins are predominantly driven from the two documented foreign keys (TAX_TYPE_ID and REGIME_ID), which should be treated as the primary integration points when building custom queries or extensions.