Search Results transaction_line_date

Overview

The ZX_O2C_CALC_TXN_INPUT_V view is an Application Object Library (FND) database object owned by the APPS schema and shipped as VALID in Oracle EBS 12.1.1 and 12.2.2. It serves as a consolidated input view for the Oracle E-Business Tax (EBTax / ZX) tax calculation engine, presenting Order-to-Cash (O2C) transaction and transaction-line attributes in a single denormalized projection. Its primary role is to supply the tax determination and calculation processes — invoked through the ZX_TPI_SERVICES_PKG provider interface — with the columnar inputs required to evaluate tax regimes, rates, and rules against a transaction. Rather than forcing the tax engine to join dozens of order-management, receivables, and tax configuration tables at runtime, the view pre-assembles column-level, header-level, party, location, and amount attributes so that downstream calls to the tax service layer receive a normalized payload.

Because the view is owned by APPS and exposes SYNONYMs internally, it is intended for internal use by ZX tax calculation routines and for controlled reporting integrations rather than as a general-purpose public interface. Consultants searching on transaction_due_date typically encounter this view when tracing how payment terms and due dates flow into tax determination logic.

Underlying Base Objects

The documented base objects referenced by the view include:

• RA_CUST_TRX_TYPES_ALL — the Receivables transaction type definition, supplying document type context.
• ZX_LINES_DET_FACTORS — stores line-level tax determination factors used by the calculation engine.
• ZX_PRVDR_HDR_EXTNS_GT — global temporary staging table for header-level provider extensions.
• ZX_PRVDR_LINE_EXTNS_GT — global temporary staging table for line-level provider extensions.
• ZX_PTNR_LOCATION_INFO_GT — global temporary table for partner/location information.
• ZX_SCO_RATES and ZX_SCO_TAXES — tax rate and tax configuration source objects.
• ZX_TRX_PRE_PROC_OPTIONS_GT — temporary table holding pre-processing options controlling tax calculation.
• ZX_TPI_SERVICES_PKG — the packaged tax provider interface program unit that consumes the view data.

The presence of several Global Temporary (GT) objects confirms that the view operates within a session-scoped calculation context: rows are materialized into these staging tables during a tax calculation call and the view reads them back alongside persistent configuration data.

Key Columns

The view exposes a comprehensive set of transaction and line attributes:

• Identification: TRANSACTION_ID, TRANSACTION_LINE_ID, TRANSACTION_NUMBER, DOCUMENT_TYPE_ID, INTERNAL_ORGANIZATION_ID.
• Dates: TRX_DATE, TRANSACTION_DUE_DATE, TRANSACTION_SHIPPING_DATE, TRANSACTION_RECEIPT_DATE, TRANSACTION_LINE_DATE, PROVNL_TAX_DETERMINATION_DATE. TRANSACTION_DUE_DATE derives from the transaction payment terms and is used in tax point/date determination.
• Amounts: LINE_AMOUNT, UNIT_PRICE, CASH_DISCOUNT, VOLUME_DISCOUNT, TRADING_DISCOUNT, TRANSPORTATION_CHARGE, INSURANCE_CHARGE, OTHER_CHARGE, OTHER_INCLUSIVE_TAX_AMOUNT.
• Flags/Actions: ALLOW_TAX_CALCULATION, DOCUMENT_LEVEL_ACTION, LINE_LEVEL_ACTION, LINE_AMT_INCLUDES_TAX_FLAG, TRX_LEVEL_TYPE.
• Party/Location: SHIP_TO_PARTY_NUMBER/NAME, SHIP_FROM_PARTY_NUMBER/NAME, SHIP_TO_LOC_ID, SHIP_FROM_LOC_ID, and geography type/value pairs 1–10.
• Product: PRODUCT_ID, PRODUCT_CODE, PRODUCT_TYPE, UOM_CODE, LINE_CLASS, LINE_INTENDED_USE, FOB_POINT.

Common Use Cases and Queries

Primary use cases include diagnosing why tax was or was not calculated on a specific sales order or Receivables transaction, verifying that transaction_due_date and determination dates are populated correctly for tax point rules, and extracting calculation inputs for audit. A representative query is:

• SELECT transaction_id, transaction_line_id, trx_date, transaction_due_date, allow_tax_calculation, line_amount FROM zx_o2c_calc_txn_input_v WHERE transaction_id = :p_trx_id;
• SELECT transaction_number, transaction_due_date, provnl_tax_determination_date FROM zx_o2c_calc_txn_input_v WHERE transaction_due_date IS NULL;

Because the view depends on session-scoped GT tables, meaningful results are generally obtained only within an active tax calculation session or when invoked by the ZX_TPI_SERVICES_PKG provider.