Results for “header_ext_number_attribute1”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ZX_PRVDR_HDR_EXTNS_GT is a transient Global Temporary Table (identified by the "_GT" suffix) owned by the ZX schema within the Oracle E-Business Tax (E-Business Tax / ETRM) module. In Oracle EBS 12.1.1 and 12.2.2, this table stores user-extensible attributes that must be passed to a tax partner service at the transaction header level for the purpose of tax processing and reporting. Because the attributes are configurable per implementation, the table provides a generic container of positional VARCHAR, NUMBER, and DATE slots rather than discrete, semantically named columns. The table acts as a staging structure for header-level extensibility data consumed during tax determination invoked through the partner service integration framework.
From a heuristic Data Vault modeling perspective, the documented metadata classifies this object as standalone based on its foreign-key structure. In Data Vault terms, it most closely resembles a satellite-like structure attached to a transaction header hub, since it carries descriptive and attribute payload keyed by business identifiers (application, entity, transaction, provider, and regime) rather than serving as an associative link between multiple business entities. This classification is a modeling suggestion only; the table is physically implemented as a flat, standalone structure with no declared foreign keys.
Key Information Stored
The table is defined with 56 documented columns. The most significant columns fall into three groups: composite business keys, extensible attribute payload, and standard audit columns.
- EVENT_CLASS_CODE — Identifies the event class context for the transaction being taxed.
- APPLICATION_ID — Identifies the source application (for example, Receivables, Payables, or Order Management) supplying the transaction.
- ENTITY_CODE — Denotes the entity type associated with the transaction line context.
- TRX_ID — The unique transaction identifier within the source application.
- PROVIDER_ID — The tax service provider identifier for the partner service call.
- TAX_REGIME_CODE — The tax regime under which the transaction is being evaluated.
- HEADER_EXT_VARCHAR_ATTRIBUTE1 through 30 — Thirty positional ALPHANUMERIC slots holding user-defined header-level attributes.
- HEADER_EXT_NUMBER_ATTRIBUTE1 through 10 — Ten positional numeric slots for user-defined header attributes.
- HEADER_EXT_DATE_ATTRIBUTE1 through 5 — Five positional date slots for user-defined header attributes.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row.
The surrogate primary key is ZX_PRVDR_HDR_EXTNS_GT_PK, composed of (EVENT_CLASS_CODE, APPLICATION_ID, ENTITY_CODE, TRX_ID, PROVIDER_ID, TAX_REGIME_CODE). A separate unique index, ZX_PRVDR_HDR_EXTNS_GT_U1, covers the same six columns in a different ordinal arrangement, confirming that these columns collectively form the business-key candidate that uniquely identifies a header extensibility record.
Common Use Cases and Queries
This table is primarily queried by the tax partner service integration routines during tax calculation. Typical scenarios include retrieving user-defined header attributes for a specific transaction before invoking an external tax provider, and auditing which extensible values were supplied for a given tax regime or provider.
- Retrieving header extensibility attributes for a transaction:
SELECT * FROM zx.zx_prvdr_hdr_extns_gt WHERE trx_id = :p_trx_id AND application_id = :p_app_id; - Filtering by provider and regime to diagnose partner-service behavior:
SELECT provider_id, tax_regime_code, header_ext_varchar_attribute1 FROM zx.zx_prvdr_hdr_extns_gt WHERE provider_id = :p_provider AND tax_regime_code = :p_regime; - Reporting on numeric or date extensible attributes used for tax reporting:
SELECT entity_code, header_ext_number_attribute1, header_ext_date_attribute1 FROM zx.zx_prvdr_hdr_extns_gt WHERE event_class_code = :p_event_class; - Audit tracing, joining the audit columns to identify when and by whom extensibility data was staged:
SELECT trx_id, created_by, creation_date FROM zx.zx_prvdr_hdr_extns_gt ORDER BY creation_date DESC;
Because it is a global temporary table, rows persist only for the duration of a session or transaction, so queries should target the current session context when troubleshooting tax partner service payloads.
Related Objects
The documented metadata records no foreign-key relationships, and the Data Vault classification is standalone. Consequently, related objects are inferred from the shared tax-processing domain rather than enforced referential constraints:
- ZX_PRVDR_HDR_EXTNS_INT — The interface table that commonly accompanies this staging structure for partner header extensibility data.
- ZX_PRVDR_LINE_EXTNS_GT — The line-level counterpart that supplies extensible attributes for transaction lines.
- ZX_LINES / ZX_LINE_DETAILS — Tax lines produced from the determination process that consumes header extensibility data.
- ZX_PARTY_TAX_PROFILE — Stores the partner and provider configuration referenced by PROVIDER_ID and TAX_REGIME_CODE.
- ZX_REGIMES_B — Defines the tax regimes referenced by TAX_REGIME_CODE.
Integration typically occurs through the E-Business Tax service APIs and the partner service callout routines, which populate ZX_PRVDR_HDR_EXTNS_GT from source application transactions before tax determination executes.
-
This table stores the user extensible attributes that need to be passed to the partner service at the transaction level for the purpose of tax processing/reporting.
-
This table stores the user extensible attributes that need to be passed to the partner service at the transaction level for the purpose of tax processing/reporting.
-
This global temporary table is used to cache copy of the transaction lines before user modifies them. This copying is carried only for upgraded tax partner integration.
-
This global temporary table is used to cache copy of the transaction lines before user modifies them. This copying is carried only for upgraded tax partner integration.
-
eTRM - ZX Tables and Views 12.2.2
This global temporary table is used to return validation errors for imported transactions from tax perspective.
-
eTRM - ZX Tables and Views 12.1.1
This global temporary table is used to return validation errors for imported transactions from tax perspective.