Results for “precedence_1”

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

Overview

JAI_CMN_TAX_CTG_LINES is a table in the JA (Asia/Pacific Localizations) product schema that stores the individual tax lines associated with defined tax categories. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the bridge between a tax category header and the individual tax components that make up that category. It allows multiple taxes to be grouped under a single tax category and applied in a defined precedence order, which is essential for jurisdictions that levy compound or stacked taxes — a common requirement in Asia/Pacific localization scenarios such as India, Thailand, and other regions where multiple indirect taxes cascade.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as a link. This is consistent with its structure: the table primarily exists to resolve a many-to-many relationship between tax categories and taxes, with its composite primary key formed from two foreign key columns. Treating it as a link table is a reasonable modeling suggestion.

Key Information Stored

The table comprises 19 documented columns. The most significant are:

• TAX_CATEGORY_ID — Foreign key to JAI_CMN_TAX_CTGS_ALL. Identifies the owning tax category. Part of the composite primary key.
• TAX_ID — Foreign key to JAI_CMN_TAXES_ALL. Identifies the individual tax attached to the category. Part of the composite primary key.
• LINE_NO — Sequencing value that controls the order in which tax lines appear within the category.
• PRECEDENCE_1 through PRECEDENCE_10 — Ten precedence columns that define the calculation and application order of taxes within the category. These support complex multi-tier tax scenarios where the result of one tax feeds into the next.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking record creation and modification.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent update control, relevant in 12.2.x.

The surrogate primary key is JAI_CMN_TAX_CTG_LINES_PK, defined over (TAX_CATEGORY_ID, TAX_ID). Because the PK is composed of the two foreign keys, it also serves as the natural business-key candidate: the combination of category and tax uniquely identifies a line and prevents duplicate tax attachments.

Common Use Cases and Queries

Typical usage includes retrieving all taxes for a category, resolving precedence for compound tax calculations, and reporting on category composition.

List all taxes in a category:

• SELECT l.TAX_ID, t.TAX_NAME, l.LINE_NO FROM JAI_CMN_TAX_CTG_LINES l, JAI_CMN_TAXES_ALL t WHERE l.TAX_ID = t.TAX_ID AND l.TAX_CATEGORY_ID = :cat_id ORDER BY l.LINE_NO;

Determine precedence ordering for a category:

• SELECT TAX_ID, PRECEDENCE_1, PRECEDENCE_2, PRECEDENCE_3 FROM JAI_CMN_TAX_CTG_LINES WHERE TAX_CATEGORY_ID = :cat_id;

Reporting scenarios commonly join this table to JAI_CMN_TAX_CTGS_ALL for category-level summaries and to JAI_CMN_TAXES_ALL to obtain tax rates and names. Audit queries leverage the CREATED_BY and LAST_UPDATE_DATE columns to trace configuration changes.

Related Objects

The following objects are most significant in relation to this table:

• JAI_CMN_TAX_CTGS_ALL — Parent of the category side; joined on TAX_CATEGORY_ID.
• JAI_CMN_TAXES_ALL — Parent of the tax side; joined on TAX_ID, supplying tax names and rates.
• JAI_CMN_TAX_CTG_LINES_PK — Composite primary key index over (TAX_CATEGORY_ID, TAX_ID).

Together these objects form the core configuration model for category-based tax determination within the Asia/Pacific Localizations module, and downstream tax calculation routines depend on the precedence data held here to compute compound tax amounts correctly.