Results for “line_ext_date_attribute1”

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

Overview

ZX_PRVDR_LINE_EXTNS_GT is a table owned by the ZX (E-Business Tax) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the extensible attributes required to be passed to the partner service at the line level for the purposes of tax processing and tax reporting. In other words, when E-Business Tax delegates tax determination or reporting to an external tax partner service, this table carries the transaction-line-level descriptive flexfield style extension values that the partner service needs in order to compute or document tax correctly.

The table is a global temporary (GT) structure, indicated by the "_GT" suffix, meaning it is populated transiently during a tax processing call, read by the partner service integration layer, and then cleared. It is a processing staging area rather than a permanent transactional record store. From a Data Vault modeling perspective, the metadata classifies this object as standalone, meaning it has no foreign key dependencies to other tables in the schema. This suggests it functions as a satellite-style attribute store keyed by a composite business key assembled from transaction context and provider information, rather than participating as a hub or link in a normalized reference model.

Key Information Stored

The table contains 58 documented columns organized into a composite business key plus three families of generic extensible attributes.

• Composite business key — The primary key ZX_PRVDR_LINE_EXTNS_GT_PK and the unique index ZX_PRVDR_LINE_EXTNS_GT_U1 both cover the same eight columns: APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, PROVIDER_ID, and TAX_REGIME_CODE. Together these identify the exact line, provider, and tax regime context of the extensible payload.
• Transaction identity columns — APPLICATION_ID identifies the owning application; ENTITY_CODE and EVENT_CLASS_CODE denote the event classification driving tax processing; TRX_ID and TRX_LINE_ID link the record to the transaction header and line respectively.
• Provider and regime columns — PROVIDER_ID identifies the partner tax service being called, and TAX_REGIME_CODE identifies the tax regime under which the line is being evaluated.
• VARCHAR extensible attributes — LINE_EXT_VARCHAR_ATTRIBUTE1 through LINE_EXT_VARCHAR_ATTRIBUTE30 hold text-form extension values passed to the partner service.
• NUMBER extensible attributes — LINE_EXT_NUMBER_ATTRIBUTE1 through LINE_EXT_NUMBER_ATTRIBUTE10 hold numeric extension values.
• DATE extensible attributes — LINE_EXT_DATE_ATTRIBUTE1 through LINE_EXT_DATE_ATTRIBUTE5 hold date-form extension values.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard concurrency and audit tracking.

The composite primary key is the surrogate identifier at the database level, while the unique index columns constitute the business-key candidate that enforces one row per line-provider-regime combination.

Common Use Cases and Queries

Development and support teams inspect this table when diagnosing partner tax service calls, verifying that line-level extension values are populated before a tax determination request is issued.

• Verifying payload population for a transaction line — Query by TRX_ID and TRX_LINE_ID to confirm what extensible values were staged for a specific line before the provider call.
• Provider-specific diagnostics — Filter by PROVIDER_ID and TAX_REGIME_CODE to isolate records for one tax partner and regime.
• Attribute usage audit — Aggregate over the LINE_EXT_VARCHAR, LINE_EXT_NUMBER, and LINE_EXT_DATE attributes to determine which of the extension slots are actually being consumed by the integration.
• Staging troubleshooting — Because the table is transient, unexpected row counts or stale CREATION_DATE values often indicate a failed or incomplete cleanup after a partner service invocation.

Typical filter patterns combine the business key columns; selecting on TRX_ID, TRX_LINE_ID, PROVIDER_ID, or TAX_REGIME_CODE yields precise payload rows. Reporting queries often join the staged extension values back to the source transaction line for reconciliation of tax partner results.

Related Objects

Given the standalone Data Vault classification, this table has no declared foreign keys to other objects. It is nevertheless functionally coupled to the following E-Business Tax integration components, joined through the shared key columns.

• ZX_PRVDR_LINE_EXTNS_GT_PK / ZX_PRVDR_LINE_EXTNS_GT_U1 — The primary key constraint and unique index enforcing uniqueness across APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, PROVIDER_ID, and TAX_REGIME_CODE.
• ZX_LINES / ZX_LINE_DETAILS — Tax lines and their details, related via TRX_ID and TRX_LINE_ID for reconciling staged extension values against computed tax results.
• ZX_PARTY_TAX_PROFILE and provider configuration tables in ZX — Resolve PROVIDER_ID to the partner service definition.
• ZX_REGIMES / TAX_REGIME_CODE reference data — Supplies the TAX_REGIME_CODE context used in the business key.
• Source transaction tables referenced by ENTITY_CODE and APPLICATION_ID — For example, order or invoice line tables, supplying the TRX_ID and TRX_LINE_ID values staged here.
• E-Business Tax partner service integration APIs — The callers that read from this table to assemble the outbound payload to the external tax provider.