Results for “audit_indicator”

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

Overview

XTR_TAX_CATEGORIES is a Treasury (XTR) module reference table within Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It defines the tax categories used to group calculation methods and rates applied to treasury transactions and counterparties. Rather than storing rates or formulas directly, the table acts as a classification layer: each category serves as an organizing key that downstream tax setup consumes when determining how withholding or transaction tax is calculated for a given party.

The ETRM metadata classifies this object heuristically as hub-leaning under a Data Vault modeling convention. In practice this means XTR_TAX_CATEGORIES behaves as a stable, low-volatility reference hub: it holds a compact set of unique business keys that are referenced by other tables, with minimal descriptive payload. It is not a transactional or link table, and its row count is expected to remain small and slowly changing.

Key Information Stored

The documented physical schema under the XTR owner contains three columns. Only these should be treated as authoritative:

• TAX_CATEGORY — The primary key column and the single business-key candidate. It is enforced both by the primary key constraint XTR_TAX_CATEGORIES_PK and by the unique index XTR_TAX_CATEGORIES_U1. This column carries the user-defined category code that other treasury tables reference.
• DESCRIPTION — The descriptive name or explanation associated with the category, used for display in setup forms and reports.
• AUDIT_INDICATOR — A flag controlling or recording audit behavior for the category row.

Notably, XTR_TAX_CATEGORIES employs a natural business key (TAX_CATEGORY) as its primary key rather than a system-generated surrogate. There is no separate numeric ID column in the documented schema, which reinforces its hub classification: the business key itself is the identity. Because only three columns are present, any additional descriptive attributes observed at a customer site are likely the product of a customization or an extension table.

Common Use Cases and Queries

Typical uses center on validating tax category setup during implementation, auditing which categories are assigned to parties, and driving lookup lists in treasury tax configuration. A simple validation query lists all defined categories:

• SELECT tax_category, description FROM xtr.xtr_tax_categories ORDER BY tax_category;

To find parties assigned to each category, join against the referencing tables on the shared TAX_CATEGORY column:

• SELECT c.tax_category, c.description, p.party_id FROM xtr.xtr_tax_categories c JOIN xtr.xtr_party_info p ON p.tax_category = c.tax_category;

Referential integrity is a recurring concern: because two tables depend on this key, deletions or renames of a TAX_CATEGORY value must respect those foreign keys. A common audit pattern identifies orphaned or unassigned categories using an outer join and a null test on the referencing side.

Related Objects

The ETRM metadata documents two foreign keys that reference XTR_TAX_CATEGORIES through the TAX_CATEGORY column:

• XTR_PARTY_INFO.TAX_CATEGORY → XTR_TAX_CATEGORIES.TAX_CATEGORY — assigns a tax category to a treasury party record.
• XTR_PARTY_DEFAULTS.TAX_CATEGORY → XTR_TAX_CATEGORIES.TAX_CATEGORY — establishes a default tax category for a party.

Because the documented schema exposes no child tables of its own, XTR_TAX_CATEGORIES is a pure parent. Any calculation methods and rates that the description alludes to are grouped conceptually by this category value but are held in separate rate and method setup objects rather than within this table. Implementers should therefore treat XTR_TAX_CATEGORIES strictly as the shared lookup that anchors party-level tax configuration, and should verify its values exist before inserting into the two referencing tables.