Search Results allocate_line_only_adjustment

Overview

The APPS.ZX_O2C_CALC_TXN_INPUT_V view is a tax calculation input interface within Oracle E-Business Suite's E-Business Tax (EBTax) module, part of the ETRM (E-Business Tax Repository Model) framework. It serves as a consolidated input source for the tax calculation engine, presenting order-to-cash (O2C) transaction data in a normalized form that the tax determination and calculation processes can consume. The view abstracts the complexity of multiple underlying staging and global temporary tables, exposing a denormalized row set describing transactions at both header and line level, together with the partner and legal entity context required for accurate tax determination. Because it is defined in the APPS schema, it is available to tax engine routines, reporting queries, and diagnostic investigations without exposing callers to the lower-level ETRM staging structures.

Underlying Base Objects

The view is defined over several documented objects. Transaction and line-level tax facts are sourced from ZX_LINES_DET_FACTORS, which holds the detailed determinants used to drive tax rules. Customer transaction type classification is obtained from RA_CUST_TRX_TYPES_ALL. Provider-side processing context comes from the global temporary tables ZX_PRVDR_HDR_EXTNS_GT and ZX_PRVDR_LINE_EXTNS_GT, while partner location context is supplied by ZX_PTNR_LOCATION_INFO_GT. Tax regime and rate determination draws on ZX_SCO_RATES and ZX_SCO_TAXES. The ZX_TRX_PRE_PROC_OPTIONS_GT temporary table carries pre-processing option flags, and the package ZX_TPI_SERVICES_PKG is referenced for supporting programmatic logic. Critically, several of these objects are global temporary tables populated during the tax calculation session, meaning the view's result set is scoped to the currently active calculation run.

Key Columns

The view exposes transactional identifiers including trx_id, trx_line_id, and trx_number, alongside organizational context via internal_organization_id and event_class_mapping_id. Tax-specific attributes include tax_event_type_code, trx_date, trx_currency_code, and trx_level_type. Partner and legal context is provided through legal_entity_number, establishment_number, and application_short_name. The allow_tax_calculation_flag governs whether a given row participates in calculation.

Of particular relevance to the search term line_level_action, the view applies extensive DECODE logic to normalize this column against record_for_partner_flag. Documented transformations include: when record_for_partner_flag='N', UPDATE, ALLOCATE_TAX_ONLY_ADJUSTMENT, ALLOCATE_LINE_ONLY_ADJUSTMENT, and LINE_INFO_TAX_ONLY are converted to CREATE, while DISCARD becomes CANCEL. When record_for_partner_flag='Y', CREATE_TAX_ONLY becomes QUOTE, COPY_AND_CREATE and adjustment actions become CREATE, and DISCARD becomes CANCEL; where PARTNER_PROCESSING_FLAG='F', UPDATE is converted to CREATE, and where inclusive_tax_override_flag='Y', the action is forced to UPDATE.

Common Use Cases and Queries

Typical uses include diagnosing why a tax line was or was not calculated, reconciling O2C transactions entering the tax engine, and extracting normalized input rows for interface validation.

• Diagnostic query on a specific transaction:

  SELECT trx_number, trx_line_id, tax_event_type_code,
         allow_tax_calculation_flag
  FROM   apps.zx_o2c_calc_txn_input_v
  WHERE  trx_number = :trx_number;

• Auditing normalized line-level actions for partner-related rows:

  SELECT trx_id, trx_line_id, tax_event_type_code
  FROM   apps.zx_o2c_calc_txn_input_v
  WHERE  tax_event_type_code IS NOT NULL;

• Identifying rows excluded from calculation via the allow_tax_calculation_flag to troubleshoot missing tax.

Because the view depends on global temporary tables, queries should generally be executed within the same session or concurrent program context that populates the staging data.