Search Results allow_tax_calculation

Overview

APPS.ZX_P2P_CALC_TXN_INPUT_V is a reporting and integration view that exposes the procurement-to-pay (P2P) transaction input structure consumed by Oracle E-Business Tax (EBTax, formerly ETRM). It presents tax-relevant attributes for a source transaction — its header, lines, parties, places of supply, amounts, and product information — in the column layout expected by the tax calculation engine. The view is registered as FND Design Data object ZX.ZX_P2P_CALC_TXN_INPUT_V and is owned by the APPS schema. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2.

Functionally, the view acts as a denormalized staging surface. Applications and tax services read from it to obtain the transaction context needed to determine tax regimes, tax statuses, rates, and calculated tax lines. Because it consolidates data that would otherwise require joining multiple Purchasing, Payables, Receiving, and EBTax tables, it simplifies operational reporting and diagnostic queries.

Underlying Base Objects

The documented base objects referenced by the view are:

• ZX_EVNT_CLS_MAPPINGS
• ZX_LINES_DET_FACTORS
• ZX_PRVDR_HDR_EXTNS_GT
• ZX_PRVDR_LINE_EXTNS_GT
• ZX_PTNR_LOCATION_INFO_GT
• ZX_TPI_SERVICES_PKG (package)
• ZX_TRX_PRE_PROC_OPTIONS_GT

These are exposed through synonyms in the APPS schema. The global temporary tables (ZX_PRVDR_HDR_EXTNS_GT, ZX_PRVDR_LINE_EXTNS_GT, ZX_PTNR_LOCATION_INFO_GT, ZX_TRX_PRE_PROC_OPTIONS_GT) carry header-level, line-level, partner location, and pre-processing option data used during tax determination. ZX_EVNT_CLS_MAPPINGS associates event classes with tax processing logic. ZX_LINES_DET_FACTORS provides line-level tax determinant factors. ZX_TPI_SERVICES_PKG supplies PL/SQL logic invoked by the view, for example to resolve party or location details. The view therefore surfaces both stored determinants and values derived at query time through the package.

Key Columns

The view exposes header and line context, including:

• INTERNAL_ORGANIZATION_ID, DOCUMENT_TYPE_ID, TRANSACTION_ID — identifiers that bind the row to the operating unit, document type, and source transaction.
• APPLICATION_CODE, DOCUMENT_LEVEL_ACTION, TRX_LEVEL_TYPE — control how the transaction is classified and processed by the tax engine.
• TRX_DATE, TRANSACTION_DUE_DATE, TRANSACTION_SHIPPING_DATE, TRANSACTION_RECEIPT_DATE — dates used for effective-dated tax determination and recovery.
• TRX_CURRENCY_CODE, LINE_AMOUNT, UNIT_PRICE, LINE_AMT_INCLUDES_TAX_FLAG — monetary context including whether the line amount is tax-inclusive.
• LEGAL_ENTITY_NUMBER, ESTABLISHMENT_NUMBER — party tax registration context.
• PRODUCT_ID, PRODUCT_CODE, PRODUCT_TYPE, UOM_CODE — product information used for tax classification.
• SHIP_FROM_PARTY_NUMBER, SHIP_FROM_PARTY_NAME, SHIP_TO_PARTY_NUMBER, SHIP_TO_PARTY_NAME, SHIP_TO_LOC_ID — the parties and location involved in the movement of goods, expressed as party numbers, names, and location identifiers. Ship-from and ship-to values drive place-of-supply and jurisdiction determination.
• SHIP_TO_GEOGRAPHY_TYPE1..5 and SHIP_TO_GEOGRAPHY_VALUE1..5 — hierarchical geography attributes for the ship-to location.
• FOB_POINT, TRX_BUSINESS_CATEGORY, LINE_INTENDED_USE, LINE_CLASS — additional determinant factors.

Note that the documented column list shows SHIP_FROM_PARTY_NUMBER and SHIP_FROM_PARTY_NAME, while SHIP_TO_LOC_ID is present as a location identifier. A ship_from_loc_id attribute is commonly sought in P2P tax diagnostics, but the documented structure exposes ship-from via party number and name columns; the corresponding location may be resolved through the underlying partner location global temporary table and ZX_TPI_SERVICES_PKG.

Common Use Cases and Queries

Typical uses include verifying the tax determinants being passed for a purchasing document, diagnosing incorrect tax calculation, and feeding downstream recovery or reporting processes. A common query filters by organization and transaction identifiers:

• Retrieve the ship-from and ship-to party context for a given transaction: SELECT transaction_id, ship_from_party_number, ship_from_party_name, ship_to_party_number, ship_to_party_name, ship_to_loc_id FROM apps.zx_p2p_calc_txn_input_v WHERE transaction_id = :trx_id;
• Examine amounts and tax-inclusive flags for a document: SELECT transaction_number, line_amount, line_amt_includes_tax_flag, trx_currency_code FROM apps.zx_p2p_calc_txn_input_v WHERE transaction_number = :doc_number;
• Review geographic determinants by ship-to location: SELECT ship_to_loc_id, ship_to_geography_type1, ship_to_geography_value1, ship_to_geography_type5, ship_to_geography_value5 FROM apps.zx_p2p_calc_txn_input_v WHERE internal_organization_id = :org_id;

Because ZX_P2P_CALC_TXN_INPUT_V reads from global temporary tables, meaningful results require the calling session to have populated the tax pre-processing context; ad hoc queries outside that context may return partial or no rows. This view should be treated as a calculation-input structure rather than a persistent data store.