Results for “tax_only_line_flag”

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

Overview

ZX_IMPORT_TAX_LINES_INPUT_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, documented under the FND – Application Object Library product module. It is part of the E-Business Tax (ZX) schema objects surfaced through the ETRM documentation set. The view exposes a flattened, pre-joined projection of tax line detail records coupled with transaction pre-processing options, allowing downstream processes and external systems to read calculated tax lines without directly addressing the underlying global temporary tables.

The user search term "zx_detail_tax_lines_gt" points directly at the principal base object referenced by this view. ZX_DETAIL_TAX_LINES_GT is a global temporary table that holds tax line detail rows during tax calculation and import processing. Because global temporary tables are session-scoped, direct querying is fragile; this view provides a stable, join-qualified access path that filters rows to those flagged for partner recording and excludes quotation transactions. The view is valid in both EBS 12.1.1 and 12.2.2, though the documented metadata is drawn from ETRM 12.2.2.

Underlying Base Objects

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

• ZX_DETAIL_TAX_LINES_GT (SYNONYM) — aliased as ZDTL; the primary source of tax line attributes including transaction identifiers, regime, tax, jurisdiction, amounts, rates, and flags.
• ZX_TRX_PRE_PROC_OPTIONS_GT (SYNONYM) — aliased as ZTPPO; supplies transaction pre-processing options such as the event class mapping identifier and the partner/quote control flags.

The two objects are joined on a composite key of APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TAX_REGIME_CODE, and TAX_PROVIDER_ID. Because both are global temporary tables, the view only returns rows visible within the current session's populated data. Two additional predicates restrict the result set: ZTPPO.RECORD_FOR_PARTNERS_FLAG must equal 'Y', and ZTPPO.QUOTE_FLAG must equal 'N'. Quotation or non-partner-recording lines are therefore excluded from the view by design.

Key Columns

The view exposes a focused set of tax and transaction identifiers plus calculation attributes:

• EVNT_CLS_MAPPING_ID — event class mapping identifier sourced from the pre-processing options table, linking the line to its classification mapping.
• TRX_ID / TRX_LINE_ID — transaction and transaction line identifiers, enabling correlation back to the source document.
• TRX_LEVEL_TYPE — indicates whether the tax line applies at header, line, or other transaction level.
• TAX_REGIME_CODE, TAX, TAX_JURISDICTION_CODE, PLACE_OF_SUPPLY_TYPE_CODE — tax determination attributes describing the regime, tax, jurisdiction, and place of supply.
• TAX_AMT, TAX_AMT_TAX_CURR, TAXABLE_AMT, TAX_RATE — monetary and rate results, provided in both functional (TAX_AMT) and tax currency (TAX_AMT_TAX_CURR) amounts.
• TAX_CURRENCY_CODE — currency of the tax amounts.
• Flags — EXEMPT_RATE_MODIFIER, EXEMPT_REASON, TAX_ONLY_LINE_FLAG, TAX_AMT_INCLUDED_FLAG, SELF_ASSESSED_FLAG, OVERRIDDEN_FLAG, MANUALLY_ENTERED_FLAG, and LAST_MANUAL_ENTRY, which capture exemption, inclusion, self-assessment, override, and manual-entry status.
• TAX_REGISTRATION_NUMBER — the tax registration number associated with the line (the commented-out third-party field is not exposed).

Common Use Cases and Queries

Typical scenarios include reconciliation of calculated tax lines, integration extracts feeding external tax engines, and diagnostics during tax calculation and import processing. Because the view filters on partner recording and excludes quotes, it is well suited to downstream partner-facing extracts. A representative query:

SELECT trx_id, trx_line_id, tax_regime_code, tax, tax_jurisdiction_code,
       tax_rate, taxable_amt, tax_amt, tax_amt_tax_curr, tax_currency_code
  FROM apps.zx_import_tax_lines_input_v
 WHERE trx_id = :p_trx_id;

Analysts commonly join it back to ZX_LINES or transaction headers by TRX_ID to validate amounts, or filter on OVERRIDDEN_FLAG, SELF_ASSESSED_FLAG, and MANUALLY_ENTERED_FLAG to audit manual interventions. Because both base objects are global temporary tables, the view must be queried within the session that populated them; outside that context it returns no rows.