Search Results zx_validation_errors_gt_n1

Overview

ZX.ZX_VALIDATION_ERRORS_GT is a global temporary table in the Oracle E-Business Suite Tax (ZX) schema. It serves as a transient staging area for validation error messages generated during tax transaction import and validation processing. Because it is defined as a global temporary table with a data duration of SYS$TRANSACTION, rows inserted by a session are visible only to that session and are automatically purged when the transaction commits or the session terminates. This makes the table unsuitable for permanent audit storage, but ideal for short-lived error accumulation during a single import or validation run.

The table captures mismatches, missing references, and rule failures encountered when tax lines, transaction lines, and interface records are validated. Each row describes a single validation failure tied to a specific transaction, entity, event class, and line, allowing the validation engine to report actionable errors back to the caller or user.

The ETRM metadata classifies this object heuristically as standalone from a Data Vault modeling perspective. This suggests it does not participate in a hub/link/satellite hierarchy and carries no persistent foreign key dependencies. It is best modeled as an operational or transient logging structure rather than a durable Data Vault entity.

Key Information Stored

The table contains 17 documented columns. The most significant include:

• APPLICATION_ID — Identifies the application owning the transaction being validated.
• ENTITY_CODE — Business entity code of the transaction.
• EVENT_CLASS_CODE — Event class code associated with the transaction; central to tax event processing.
• TRX_ID — Identifier of the tax transaction.
• TRX_LINE_ID — Identifier of the transaction line; this column references CN_TRX_LINES_ALL, establishing the primary documented FK.
• TRX_LEVEL_TYPE — Indicates whether the line ID refers to a LINE, SHIPMENT, or FREIGHT level.
• MESSAGE_NAME — Standard (untranslated) message name for the validation error, useful for programmatic handling.
• MESSAGE_TEXT — Translated, human-readable error message text (up to 2000 characters).
• SUMMARY_TAX_LINE_NUMBER — Summary tax line number for imported tax lines.
• INTERFACE_LINE_ENTITY_CODE, INTERFACE_LINE_ID, INTERFACE_TAX_LINE_ID, INTERFACE_TAX_ENTITY_CODE — Temporary identifiers linking errors to Receivables interface records during import.
• OTHER_DOC_APPLICATION_ID, OTHER_DOC_ENTITY_CODE, OTHER_DOC_EVENT_CLASS_CODE, OTHER_DOC_TRX_ID — Columns capturing the counterpart document’s application, entity, event class, and transaction identifiers when the validation error involves a related or offsetting document.

No explicit primary key is documented. The non-unique index ZX_VALIDATION_ERRORS_GT_N1 covers APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, and SUMMARY_TAX_LINE_NUMBER, effectively serving as the business-key access path for error retrieval. The column OTHER_DOC_EVENT_CLASS_CODE, which the user searched, belongs to this counterpart-document grouping and identifies the event class of a related tax document involved in the failure.

Common Use Cases and Queries

Typical usage involves importing tax lines (for example from Receivables or Payables interfaces) and then querying this table to surface validation failures. A common pattern selects all errors for a given transaction:

• SELECT TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, MESSAGE_NAME, MESSAGE_TEXT FROM ZX.ZX_VALIDATION_ERRORS_GT WHERE APPLICATION_ID = :p_app AND ENTITY_CODE = :p_entity AND EVENT_CLASS_CODE = :p_event AND TRX_ID = :p_trx;
• Filtering by MESSAGE_NAME to identify systemic issues across many transactions during a batch import.
• Joining back to CN_TRX_LINES_ALL on TRX_LINE_ID to correlate errors with the offending line.
• Querying on OTHER_DOC_EVENT_CLASS_CODE to trace errors that involve cross-document tax relationships.

Because the table is session-scoped and transaction-duration, queries must be executed within the same session and before commit; after commit the rows are discarded. Reporting use cases therefore focus on real-time validation feedback rather than historical analysis.

Related Objects

The most significant related objects include:

• CN_TRX_LINES_ALL — Referenced via TRX_LINE_ID; provides the transaction line details for any error.
• ZX_LINES and ZX_LINES_DET_FACTORS — Store the tax lines being validated.
• ZX_INTERFACE_LINES / Receivables interface tables — Correlated through INTERFACE_LINE_ID and INTERFACE_TAX_LINE_ID.
• RA_INTERFACE_LINES_ALL — Source of imported transaction lines during Receivables import.
• ZX_VALIDATION_ERRORS (if present in the instance) — Persistent counterpart for retained errors.
• ZX_EVENTS — Supplies event class and entity context matching EVENT_CLASS_CODE and ENTITY_CODE.

These relationships allow the validation engine and DBAs to reconcile transient error output with the underlying transactional and tax structures.