Search Results adjusted_doc_entity_code




Overview
Explore in AI Chat

Overview

ZX_USER_PROC_LINE_INPUT_V is an APPS-owned database view in Oracle E-Business Suite, classified under the FND – Application Object Library product. It is a tax determination interface view used by the E-Business Tax (EBTax) engine, exposing the line-level input structure that feeds the tax determination and tax processing pipeline. The view presents the row-level "input" that the tax engine uses to determine applicable taxes for a document line, and the name "USER_PROC_LINE_INPUT" reflects that it exposes the user-processed transaction line attributes consumed during tax determination.

The view is particularly relevant to the column alias TRX_LINE_TYPE, which is mapped from the underlying column ZX_DET_FACT.TRX_LEVEL_TYPE. This alias is the field that applications and reports reference to determine whether a tax line is processed at the document header level or at the line level. The view plays a role both in EBTax internal processing and in reporting/integration scenarios where tax-relevant line attributes must be surfaced for a transaction.

Underlying Base Objects

The view is defined over two documented base objects:

  • ZX_LINES_DET_FACTORS (referenced as the synonym ZX_DET_FACT within the view text) — the primary source of tax determination factors at line level. It supplies transaction identity, party/location tax profiles, exemption data, product attributes, and adjusted-document references.
  • ZX_TRX_PRE_PROC_OPTIONS_GT (referenced as ZX_PRE_REC_OPT) — a global temporary table holding pre-processing options, including the tax provider, tax regime, and related configuration that govern how tax is determined for the transaction.

The join between these objects supplies both the transaction line facts and the applicable tax options/regime context, producing a consolidated row per transaction line for tax determination input.

Key Columns

Common Use Cases and Queries

The view is commonly used to inspect the tax-relevant line input for a transaction, to diagnose why a particular tax was or was not determined, and to verify line-level versus header-level processing (via TRX_LINE_TYPE). A representative query to retrieve the key line type for a given transaction is:

  • SELECT trx_id, trx_line_id, trx_line_type, tax_regime_code, tax_provider_id FROM zx_user_proc_line_input_v WHERE trx_id = :p_trx_id;
  • To filter to line-level rows: SELECT * FROM zx_user_proc_line_input_v WHERE trx_line_type = 'LINE';
  • To review exemption context for a transaction's lines: SELECT trx_line_id, exempt_certificate_number, exempt_reason_code, exemption_control_flag FROM zx_user_proc_line_input_v WHERE trx_id = :p_trx_id;

Because it consolidates determination factors with pre-processing options, the view is useful in EBTax troubleshooting and audit reporting rather than as a high-volume transactional source.