Results for “hdr_trx_user_key1”

50+ results




Overview
Explore in AI Chat

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

Overview

ZX_TRX_TAX_LINK_GT is a global temporary table (GTT) owned by the ZX schema within the Oracle E-Business Tax (E-Business Tax / ETRM) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to pass information about the allocation of imported tax lines to transaction lines during tax processing for imported transactions. In practice, it acts as a transient staging structure: rows are populated for the duration of a session or transaction, consumed by the tax engine, and then released according to the GTT's ON COMMIT DELETE ROWS or ON COMMIT PRESERVE ROWS semantics.

The table is central to the interface import flow, where externally sourced tax lines must be reconciled against the transaction lines they apply to before E-Business Tax finalizes tax determination and tax line records. The documented physical schema shows 24 columns and one unique index, ZX_TRX_TAX_LINK_GT_U1, spanning APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, and SUMMARY_TAX_LINE_NUMBER.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it does not fit a hub, link, or satellite pattern cleanly. It is better understood as a process-scoped staging table whose composite unique key behaves like a business key candidate for the import session rather than as a durable warehouse link entity.

Key Information Stored

The most significant columns fall into three groups. The first group establishes the transaction context: APPLICATION_ID identifies the owning application, ENTITY_CODE identifies the transaction entity, EVENT_CLASS_CODE identifies the event class, and TRX_ID identifies the transaction header. The second group identifies the specific line being linked: TRX_LINE_ID references the transaction line (documented as a foreign key to CN_TRX_LINES_ALL), and TRX_LEVEL_TYPE distinguishes whether the row applies at header or line level.

The third group carries the imported tax line references: SUMMARY_TAX_LINE_NUMBER, INTERFACE_LINE_ENTITY_CODE, INTERFACE_LINE_ID, INTERFACE_TAX_ENTITY_CODE, INTERFACE_TAX_LINE_ID, and LINE_AMT. Descriptive user-key columns — HDR_TRX_USER_KEY1 through HDR_TRX_USER_KEY6 and LINE_TRX_USER_KEY1 through LINE_TRX_USER_KEY6 — provide flexible external identifiers for the header and line respectively.

The surrogate identifier is the composite unique index ZX_TRX_TAX_LINK_GT_U1 (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, SUMMARY_TAX_LINE_NUMBER), which serves as the business-key candidate for the allocations held in this GTT.

Common Use Cases and Queries

Typical usage occurs during imported transaction tax processing, where a caller inserts allocation rows, the tax engine reads them to associate interface tax lines with transaction lines, and results are written back to the interface tables. Debugging and reconciliation queries are the most common inspection pattern:

  • Session tracing: query by TRX_ID and APPLICATION_ID to view all allocations for a given transaction during an active import session.
  • Line-level verification: join TRX_LINE_ID to CN_TRX_LINES_ALL to confirm which transaction lines received imported tax amounts.
  • Amount reconciliation: sum LINE_AMT by SUMMARY_TAX_LINE_NUMBER to compare against interface totals.
  • Error diagnosis: examine INTERFACE_TAX_LINE_ID and INTERFACE_LINE_ID when interface import failures are reported.

Because the table is a GTT, queries only return rows visible to the current session; other sessions' data is isolated by design. This makes it unsuitable for persistent reporting and appropriate only for in-flight diagnostics.

Related Objects

The documented foreign key associates this table with CN_TRX_LINES_ALL via TRX_LINE_ID, linking allocations to transaction lines. Broader E-Business Tax dependencies include the interface staging tables referenced by INTERFACE_LINE_ID and INTERFACE_TAX_LINE_ID, the transaction header structures implied by TRX_ID, and the tax line repository represented by SUMMARY_TAX_LINE_NUMBER. The ZX_TRX_TAX_LINES and ZX_LINES_DET_FACTORS structures participate in the same processing flow, along with the E-Business Tax engine APIs that consume these allocations. Analysts working with imported tax transactions should treat ZX_TRX_TAX_LINK_GT as a transient bridge between interface data and finalized tax lines rather than as a source of historical reporting data.