Results for “doc_seq_value”

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

Overview

ZX_TRX_HEADERS_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. As its name and documentation indicate, the table exists primarily to pass transaction header information into the tax calculation engine at runtime. When an application such as Receivables, Payables, Order Management, or Purchasing needs tax determined for a document, it populates this GTT with the relevant header attributes, and the E-Business Tax API consumes those rows to drive tax determination, tax line generation, and tax accounting. The table is a transient, session-scoped structure: its contents persist only for the duration of the invoking transaction or session, which is why it is implemented as a GTT rather than a permanent table.

The metadata classifies this object as standalone under a heuristic Data Vault analysis, based primarily on its FK structure. In Data Vault modeling terms, this suggests treating the GTT as neither a conventional hub nor a link, but a transient staging/interface structure — a suggestion rather than a hard designation, appropriate for a table whose lifetime is bounded by a single tax computation call.

Key Information Stored

The table carries 91 documented columns spanning 12.2.2. Its declared business-key candidate is the unique index ZX_TRX_HEADERS_GT_U1, defined on (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID) — the composite that uniquely identifies the transaction being taxed. The GTT has no documented surrogate single-column primary key; the U1 composite effectively serves that identification role.

The most operationally significant columns include:

• APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID — the tax determination context; together they identify the source transaction and its event class.
• EVENT_TYPE_CODE — further qualifies the event driving tax.
• TRX_NUMBER, TRX_DATE, TRX_DESCRIPTION, TRX_DOC_REVISION — human-readable document identity and timing.
• LEDGER_ID, TRX_CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_TYPE, MINIMUM_ACCOUNTABLE_UNIT, PRECISION — currency and rounding parameters used to compute tax amounts.
• LEGAL_ENTITY_ID, ESTABLISHMENT_ID, FIRST_PTY_ORG_ID — legal party context; these carry the foreign-key relationships noted in the metadata.
• TRX_BATCH_ID — links the header to a batch of transactions (FK to CN_TRX_BATCHES_ALL).
• RELATED_DOC_* and APPLIED_TO_TRX_NUMBER — support credit/application relationships between documents.
• DEFAULT_TAXATION_COUNTRY, PORT_OF_ENTRY_CODE, TAX_REPORTING_FLAG, QUOTE_FLAG — reporting and determination controls.

Common Use Cases and Queries

The typical use is to populate the GTT before calling the E-Business Tax calculation API (for example ZX_API_PUB or the ZX_TAX_DETERMINATION routines), then read back the calculated tax lines. Diagnostic queries frequently examine what the calling application actually supplied. Because the table is a GTT, queries only return rows for the current session unless the GTT is defined with ON COMMIT PRESERVE ROWS and populated accordingly.

• Trace a specific transaction's tax call: SELECT trx_id, trx_number, trx_date, default_taxation_country FROM zx.zx_trx_headers_gt WHERE trx_id = :p_trx_id;
• Validate key completeness: check that APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and TRX_ID are non-null and unique per the U1 index before invoking the API.
• Reconcile currency parameters: inspect CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE, and MINIMUM_ACCOUNTABLE_UNIT where tax rounding discrepancies appear.
• Support rollup reporting: stage headers by TRX_BATCH_ID, then aggregate tax results by LEDGER_ID and period.

Related Objects

The FK relationships documented in the metadata identify the principal related objects:

• FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID to resolve the legal entity responsible for the transaction.
• PER_ESTABLISHMENTS — joined on ESTABLISHMENT_ID to supply the establishment tax context.
• CN_TRX_BATCHES_ALL — joined on TRX_BATCH_ID for batch-level grouping.
• FND_SESSION_VALUES — joined on ICX_SESSION_ID, tying the rows to the originating web session.
• ZX_TRX_LINES_GT — the companion GTT holding transaction line details; header and line rows are consumed together by the tax engine.
• ZX_LINES / ZX_LINES_DET_FACTORS — the persistent tax result tables populated by the calculation process.
• ZX_API_PUB / ZX_TAX_DETERMINATION — the PL/SQL packages that read this GTT during tax determination.