Results for “application_code”

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

Overview

ZX_P2P_CALC_TXN_INPUT_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Tax (ZX). It was introduced to support the Procure-to-Pay (P2P) tax calculation flow, exposing the pre-processed transaction payload that feeds the E-Business Tax calculation engine. The view consolidates transactional header, line, party, and pre-processing option data into a single denormalized result set that the tax engine consumes when computing taxes on purchasing documents such as purchase orders, receipts, and invoices.

Because the view is a database object rather than a public API, it is not intended for direct end-user querying. Its role is to act as an integration surface between the source P2P documents and the ZX tax determination and calculation services. It is referenced internally by packages such as ZX_TPI_SERVICES_PKG and is materialized through global temporary tables populated during the tax calculation call sequence.

Underlying Base Objects

The view is defined over the following documented base objects:

• ZX_EVNT_CLS_MAPPINGS — supplies the event class mapping used to translate a tax event type into the correct tax regime/configuration context.
• ZX_LINES_DET_FACTORS — provides line-level tax determinants including transaction level type, line level action, and document sequence values.
• ZX_PRVDR_HDR_EXTNS_GT — global temporary table holding provider (party/legal entity) header extension attributes.
• ZX_PRVDR_LINE_EXTNS_GT — global temporary table holding provider line extension attributes.
• ZX_PTNR_LOCATION_INFO_GT — global temporary table capturing partner (ship-to/bill-to) location information.
• ZX_TRX_PRE_PROC_OPTIONS_GT — global temporary table containing pre-processing options such as RECORD_FOR_PARTNERS_FLAG, PARTNER_PROCESSING_FLAG, and INCLUSIVE_TAX_OVERRIDE_FLAG.
• ZX_TPI_SERVICES_PKG — the package whose runtime logic populates the temporary structures consumed by this view.

The view itself performs no DML; it projects and decodes columns from these objects, most notably transforming LINE_LEVEL_ACTION values based on the partner and processing flags described in the inline DECODE logic.

Key Columns

• INTERNAL_ORGANIZATION_ID, TRX_ID, TRX_LINE_ID — identifiers linking the row back to the operating unit and the source transaction/line.
• TAX_EVENT_TYPE_CODE, EVENT_CLASS_MAPPING_ID — drive tax event classification and regime determination.
• TRX_DATE, TRX_DUE_DATE, TRX_CURRENCY_CODE — used for effective-dated rate lookup and currency conversion.
• TRX_NUMBER, TRX_DESCRIPTION, DOC_SEQ_VALUE — descriptive and sequencing attributes for the document.
• LEGAL_ENTITY_NUMBER, ESTABLISHMENT_NUMBER — party tax registration context from the provider header extension.
• ALLOW_TAX_CALCULATION_FLAG — indicates whether tax calculation is permitted for the transaction.
• TRX_LEVEL_TYPE — indicates whether the row represents a header or line level entry.
• LINE_LEVEL_ACTION — the derived action (CREATE, UPDATE, CANCEL, QUOTE) computed via DECODE against RECORD_FOR_PARTNERS_FLAG, PARTNER_PROCESSING_FLAG, and INCLUSIVE_TAX_OVERRIDE_FLAG.

The presence of INCLUSIVE_TAX_OVERRIDE_FLAG in the decode chain is directly relevant to users investigating the override_tax search term: the flag controls whether an inclusive tax override forces a LINE_LEVEL_ACTION of UPDATE for partner-processed lines.

Common Use Cases and Queries

Typical use is diagnostic — tracing why a purchasing document did or did not create or update a tax line during P2P tax calculation. A representative query might look for transactions where the inclusive override flag drove an UPDATE action:

• Select TRX_NUMBER, TRX_LINE_ID, LINE_LEVEL_ACTION from ZX_P2P_CALC_TXN_INPUT_V where TRX_ID = :p_trx_id to review the pre-processed state of a single transaction.
• Filter on TAX_EVENT_TYPE_CODE and ALLOW_TAX_CALCULATION_FLAG to confirm tax calculation eligibility.
• Join back to ZX_LINES to compare the input action with the resulting tax line disposition, particularly for override scenarios involving INCLUSIVE_TAX_OVERRIDE_FLAG and PARTNER_PROCESSING_FLAG.

Because it depends on global temporary tables populated at runtime by ZX_TPI_SERVICES_PKG, meaningful results are only obtainable within an active tax calculation session or after the pre-processing step has executed.