Search Results transaction_level_type

Overview

APPS.ZX_IMPORT_TAX_LINES_INPUT_V is a reporting and integration view within the Oracle E-Business Suite (EBS) E-Business Tax (EBTax / ETRM) module. It is defined in the APPS schema and exposes tax line detail that has been staged during the tax import or tax pre-processing flow. The view is not a standalone data store; rather, it is a join driven by Global Temporary Tables (GTTs) that hold tax results and transaction pre-processing options during the course of a tax determination or import run.

The defining characteristic of this view is its use of an explicit optimizer hint, /*+ leading (ztppo) index(zdtl ZX_DETAIL_TAX_LINES_GT_U1) */. This hint forces the ZX_TRX_PRE_PROC_OPTIONS_GT table (alias ztppo) to be the leading table and directs the optimizer to access ZX_DETAIL_TAX_LINES_GT (alias zdtl) through the unique index ZX_DETAIL_TAX_LINES_GT_U1. The presence of this hint indicates the view was specifically tuned for performance on large tax import volumes, where the pre-processing options table is expected to be the smaller driving set.

Underlying Base Objects

The view is defined over two documented base objects, both resolved via synonyms in the APPS schema:

• ZX_DETAIL_TAX_LINES_GT — the detail tax lines global temporary table that stores calculated or imported tax line records, including tax amounts, rates, regime, jurisdiction, and flags.
• ZX_TRX_PRE_PROC_OPTIONS_GT — the transaction pre-processing options global temporary table that controls which records are eligible for partner-level or quote-level processing.

The two objects are joined on a composite key comprising application_id, entity_code, event_class_code, trx_id, tax_regime_code, and tax_provider_id. This composite join ensures each tax detail line is correlated to its correct pre-processing context. Two filters restrict the result set: ztppo.record_for_partners_flag = 'Y' and ztppo.quote_flag = 'N', so only partner-recordable, non-quote records are returned.

Key Columns

The view exposes the full tax line payload together with the event class mapping identifier from the pre-processing options table. Principal columns include:

• evnt_cls_mapping_id — sourced from ztppo; identifies the event class mapping associated with the tax line.
• trx_id / trx_line_id / trx_level_type — transaction and line identifiers plus the level (header or line) at which tax was determined.
• tax_regime_code, tax, tax_jurisdiction_code, place_of_supply_type_code — the tax regime, tax name, jurisdiction, and place of supply.
• tax_rate, taxable_amt, tax_amt, tax_amt_tax_curr, tax_currency_code — rate and monetary amounts, with the tax amount also expressed in tax currency.
• exempt_rate_modifier, exempt_reason — exemptions applied to the line.
• tax_only_line_flag, tax_amt_included_flag, self_assessed_flag, overridden_flag — behavioral flags reflecting how the tax was applied.
• manually_entered_flag, last_manual_entry, tax_registration_number — audit and registration attributes for manual or overridden entries.

Common Use Cases and Queries

Because the view depends on GTT contents, it can only return meaningful rows within the session or processing context that populated those GTTs. It is typically used during tax import diagnostics, partner tax recording, and verification of tax determination output before data is written to permanent ETRM tables.

A typical query filters by transaction to inspect staged tax lines:

• SELECT trx_id, trx_line_id, tax_regime_code, tax, tax_rate, tax_amt
• FROM apps.zx_import_tax_lines_input_v
• WHERE trx_id = :p_trx_id;

Aggregation queries are also common, for example summing tax_amt by tax_regime_code and tax_jurisdiction_code to reconcile tax import results. For performance troubleshooting, the embedded hint should be reviewed, since its fixed leading and index directive may not suit every data distribution; the ZX_DETAIL_TAX_LINES_GT_U1 index is the intended access path on the detail table.