Results for “header_ext_varchar_attribute1”

26 results




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

Overview

ZX_PTNR_NEG_LINE_GT is a global temporary table owned by the ZX schema within the E-Business Tax (E-Business Suite 12.1.1 and 12.2.2) module. It serves a narrowly scoped but important purpose: caching a copy of transaction lines before a user modifies them. This copy operation is performed only for upgraded tax partner integration scenarios, meaning the table exists to preserve the pre-modification state of line-level tax data so that the integrated tax partner can correctly reconcile what changed. Because the table is a global temporary table (GTT), its rows are session- or transaction-scoped, and the data is automatically purged based on the GTT definition, preventing long-term accumulation of transient records.

In terms of heuristic Data Vault modeling, the FK relationships show this table references EVENT_CLASS_MAPPING_ID, TRX_LINE_ID, and PRODUCT_ID, yet the table itself is classified as standalone (no other table is documented as referencing it). This suggests the object chiefly functions as a staging or temporary satellite-per-line construct, holding descriptive line snapshots rather than acting as a persistent hub or link. It should be treated as transient working data rather than an authoritative source of record.

Key Information Stored

The table contains 219 documented columns, most of which are repeated geography and descriptive attribute sets (ship-to, ship-from, bill-to, bill-from type/value pairs, and generic EXT attribute columns). The most operationally significant columns include:

The surrogate primary key is not explicitly segregated in the documented metadata; business-key candidates are effectively the combination of TRX_LINE_ID with EVENT_CLASS_MAPPING_ID, which uniquely positions a cached line within its tax computation context.

Common Use Cases and Queries

Typical scenarios for this table revolve around tax partner integration upgrades, reconciliation, and troubleshooting. Because it is a global temporary table, queries only succeed within the session that populated it, so diagnostic queries are usually run immediately after a transaction modification.

  • Reconciling pre- and post-modification lines: Compare cached values with current CN_TRX_LINES_ALL values to identify what changed and drive correct tax recalculation.
  • Verifying exemption handling: Confirm EXEMPT_CERTIFICATE_NUMBER and EXEMPTION_CONTROL_FLAG were captured before edits.
  • Tracing applied and adjusted documents: Use APPLIED_FROM_TRX_ID, APPLIED_FROM_LINE_ID, and the ADJUSTED_DOC_* columns to reconstruct document lineage.

A representative query joins the GTT to its transaction line and event class mapping:

  • SELECT g.TRX_LINE_ID, g.LINE_AMT, g.TAX_REGIME_CODE, c.LINE_AMOUNT, m.EVENT_CLASS_CODE FROM ZX.ZX_PTNR_NEG_LINE_GT g, CN_TRX_LINES_ALL c, ZX_EVNT_CLS_MAPPINGS m WHERE g.TRX_LINE_ID = c.LINE_ID AND g.EVENT_CLASS_MAPPING_ID = m.EVENT_CLASS_MAPPING_ID;

Related Objects

The foreign keys documented for ZX_PTNR_NEG_LINE_GT establish the following significant related objects:

  • CN_TRX_LINES_ALL – joined via TRX_LINE_ID; the authoritative transaction line table.
  • ZX_EVNT_CLS_MAPPINGS – joined via EVENT_CLASS_MAPPING_ID; defines the event class mapping for tax.
  • FND_DM_PRODUCTS – joined via PRODUCT_ID; the product definition used to resolve line product context.

Related E-Business Tax objects typically consulted alongside this table include ZX_LINES, ZX_LINES_DET_FACTORS, and ZX_TRX_LINES for tax line results, plus the tax partner integration APIs that populate and consume the cached negative lines during upgrade processing. Because the table is standalone in the FK graph, dependent objects are generally program units and integration routines rather than other tables referencing it.