Search Results header_ext_varchar_attribute1




Overview

ZX.ZX_PRVDR_HDR_EXTNS_GT is a global temporary table in the Oracle E-Business Tax (ZX) schema that serves as a staging and interface structure for header-level, third-party tax service provider extensible attributes. It is part of the EBS Tax (ETRM) subsystem introduced with the 12.1.1 release and carried into 12.2.2, where external tax determination engines or partner integrations return provider-specific data alongside a tax calculation result.

The table is defined as a global temporary table. The current session can see data it placed in the table, but other sessions cannot; data is temporary and has a duration of SYS$TRANSACTION, meaning rows are removed at the end of the transaction. This design makes the object suitable for transient, per-transaction population during provider integration processing, typically before the values are consumed by the tax engine and persisted into permanent tax tables.

The ETRM metadata carries a heuristic Data Vault classification of standalone, which is best treated as a modeling suggestion rather than a declared constraint. Because the primary key is a composite of transaction and provider identifiers with no documented foreign key dependencies, the object does not resolve cleanly into a hub, link, or satellite pattern; it is better understood as a transient keyed staging structure.

Key Information Stored

The table contains 56 documented columns. The most significant are the composite business identifiers and the provider extensible attribute groups.

The declared primary key, ZX_PRVDR_HDR_EXTNS_GT_PK, comprises EVENT_CLASS_CODE, APPLICATION_ID, ENTITY_CODE, TRX_ID, PROVIDER_ID, and TAX_REGIME_CODE. The unique index ZX_PRVDR_HDR_EXTNS_GT_U1 mirrors the same business-key columns (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, PROVIDER_ID, TAX_REGIME_CODE), reinforcing that the transaction-to-provider-to-regime combination is the natural business key rather than any single surrogate column.

Common Use Cases and Queries

Typical usage centers on retrieving provider-supplied header attributes for a specific transaction, provider, and tax regime during tax calculation or reconciliation reporting.

SELECT trx_id, provider_id, tax_regime_code,
       header_ext_varchar_attribute1,
       header_ext_number_attribute1
  FROM zx.zx_prvdr_hdr_extns_gt
 WHERE application_id   = :app_id
   AND entity_code      = :entity_code
   AND event_class_code = :event_class
   AND trx_id           = :trx_id;

Because the table is session-private and transaction-scoped, queries are normally issued from within the same session and transaction that populated it. Diagnostic queries for search terms such as header_ext_varchar_attribute1 are commonly used to confirm whether a third-party provider returned a value, to trace tax determination discrepancies, and to map provider output into EBS tax reporting extracts.

Related Objects

The ETRM metadata documents no foreign key relationships for this object, and it is classified as standalone. Direct dependents are therefore driven by the shared ZX transaction identifier and the ZX Tax provider integration interfaces rather than by declared constraints.

  • ZX_PRVDR_HDR_EXTNS_GT_PK — primary key constraint on EVENT_CLASS_CODE, APPLICATION_ID, ENTITY_CODE, TRX_ID, PROVIDER_ID, TAX_REGIME_CODE.
  • ZX_PRVDR_HDR_EXTNS_GT_U1 — unique index on the matching business-key column set.
  • ZX third-party provider integration APIs — the ZX Tax service provider interfaces that populate this global temporary table during tax determination, keyed by APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and TRX_ID.
  • ZX permanent tax header and line tables — the tax repository structures that receive the resolved values after processing, joined on TRX_ID and TAX_REGIME_CODE.