Results for “allow_tax_calculation_flag”

34 results




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

Overview

ZX_TRX_LINE_APP_REGIMES is a transaction-level table in the Oracle E-Business Tax (ZX) module. It stores the applicable tax regimes determined for transactions. Each row represents one applicable regime for a specific transaction line, capturing the outcome of tax regime determination performed by the E-Business Tax engine. When a transaction is processed — whether it originates in Order Management, Receivables, Payables, or another source application — the tax engine evaluates configuration and party tax profiles to decide which regime governs the line. Those decisions are persisted here, making this table a foundational record of regime applicability at the document line level.

From a Data Vault modeling perspective, the heuristic classification for this table is a link. This is consistent with its structure: it resolves relationships between a transaction line, a tax regime, and a tax provider (party tax profile), rather than acting as a standalone hub or a descriptive satellite. The composite primary key reinforces this interpretation, since the key is assembled entirely from references to other business entities plus the event context.

Key Information Stored

The table's identity is defined by the primary key ZX_TRX_LINE_APP_REGIMES_PK, which comprises EVENT_CLASS_CODE, APPLICATION_ID, ENTITY_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, and TAX_REGIME_CODE. A unique index, ZX_TRX_LINE_APP_REGIMES_U1, mirrors this key composition (ordered as APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, TAX_REGIME_CODE), confirming these columns as the business-key candidates. There is no separate single-column surrogate key; identity is fully composite.

The most significant columns include:

Common Use Cases and Queries

Typical usage centers on diagnosing tax determination and reconciling tax results for a transaction. Support and implementation teams frequently query this table to confirm which regime the engine selected for a given line and why. A representative query joins the regime definition:

  • SELECT a.TRX_ID, a.TRX_LINE_ID, a.TAX_REGIME_CODE, r.TAX_REGIME_NAME, a.ALLOW_TAX_CALCULATION_FLAG FROM ZX_TRX_LINE_APP_REGIMES a, ZX_REGIMES_B r WHERE a.TAX_REGIME_CODE = r.TAX_REGIME_CODE AND a.TRX_ID = :trx_id;
  • Filtering by TAX_PROVIDER_ID to review decisions tied to a specific party tax profile.
  • Reporting on lines where ALLOW_TAX_CALCULATION_FLAG or PSEUDO_TAX_ONLY_LINE_FLAG indicates special handling.
  • Tracking records flagged by UPDATE_FLAG for reprocessing after configuration changes.

Related Objects

The most significant related objects, based on documented foreign keys and key structure, are:

  • ZX_REGIMES_B — joined on TAX_REGIME_CODE; provides the regime definition and name.
  • ZX_PARTY_TAX_PROFILE — joined on TAX_PROVIDER_ID; supplies party tax profile context.
  • ZX_TRX_LINES and related ZX transaction tables — share TRX_ID/TRX_LINE_ID linkage for line-level tax data.
  • ZX_LINES / ZX_TRX_HEADERS — provide header and line context for the same transaction.
  • ZX_TAX_DETERMINATIONS and applicable regime result tables — downstream consumers of regime determination.