Search Results ship_to_postal_code




Overview
Explore in AI Chat

Overview

The TAX_ADJUSTMENTS_V view is an Oracle E-Business Suite Receivables (AR) reporting object that presents approved tax adjustments affecting transactions or receipt reversals. Within the Oracle EBS 12.1.1 and 12.2.2 releases it functions as a consolidation layer for tax-related adjustment activity, exposing a normalized column set that mirrors the structure of the ETRM tax lines interface. Because tax adjustments in Receivables are stored in the adjustments infrastructure rather than in the tax engine tables, this view provides a consistent projection enabling tax reporting, reconciliation, and downstream data extraction without requiring the caller to understand the underlying adjustment normalization.

It is important to note that the ETRM metadata records this view as “Not implemented in this database” in the documented instance, and the ownership of the view is not recorded. This indicates the view may exist only in environments where the tax adjustment extraction feature is deployed, and it should be validated against the ALL_VIEWS / DBA_VIEWS dictionary before being relied upon in a given instance.

Underlying Base Objects

The documented metadata does not enumerate referenced base objects; the view text, however, reveals that it is defined over at least two source objects, aliased H and L. The header alias H supplies transaction-level attributes from RA_CUSTOMER_TRX_ALL (or its customer/transaction header lineage) — for example SHIP_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, INVOICING_RULE_ID, EXCHANGE_RATE, SET_OF_BOOKS_ID, FOB_POINT, and TRX_NUMBER. The line alias L supplies adjustment-level attributes from AR_ADJUSTMENTS_ALL — notably ADJUSTMENT_ID, APPLY_DATE, GL_DATE, and AMOUNT. The currency attributes (CURRENCY_CODE, MINIMUM_ACCOUNTABLE_UNIT, PRECISION) derive from FND_CURRENCIES or GL_CURRENCIES.

The select list projects ADJUSTMENT_ID into both TRX_LINE_ID and TRX_HEADER_ID, and emits NULL for most tax-engine-specific columns (tax code, tax rate, exemption, tax line number), indicating the view is designed to be union-compatible with the standard ETRM tax line extraction views rather than to carry granular tax determinative data.

Key Columns

  • TRX_NUMBER — the transaction number of the header to which the adjustment applies.
  • TRX_LINE_ID / TRX_HEADER_ID — both populated from the adjustment identifier, allowing the row to be joined into tax-line extraction queries keyed on either grain.
  • TAX_AMOUNT — the approved adjustment amount, sourced from L.AMOUNT; this is the primary monetary measure.
  • TRX_DATE / GL_DATE — apply date and accounting date, supporting period-based reconcilations.
  • SHIP_TO_CUSTOMER_ID / BILL_TO_CUSTOMER_ID and their site-use identifiers — party and site attribution for the adjustment.
  • CURRENCY_CODE, EXCHANGE_RATE, SET_OF_BOOKS_ID — currency and ledger context for conversion and multi-org reporting.
  • TAXABLE_FLAG — hard-coded to 'Y'; LOCATION_QUALIFIER hard-coded to 'ALL'; TAX_CODE, TAX_RATE, and all exemption columns are NULL.
  • ATTRIBUTE1–5 and NUMERIC_ATTRIBUTE1–5 — reserved descriptive flexfield placeholders, currently NULL.

Common Use Cases and Queries

Typical scenarios include tax adjustment reconciliation by period, tax reporting extracts, and embedding the view into custom ETRM-style tax line queries. Because AMOUNT_INCLUDES_TAX_FLAG is not exposed as a column here, users searching for that attribute in the context of this view should recognize it is not part of the projected column set; the flag belongs to the transaction/tax line tables, not to adjustment rows.

SELECT trx_number,
       trx_date,
       gl_date,
       tax_amount,
       currency_code,
       set_of_books_id
  FROM tax_adjustments_v
 WHERE trx_date BETWEEN :p_start_date AND :p_end_date
   AND set_of_books_id = :p_ledger;

To reconcile adjustments against Receivables adjustments directly, join on TRX_LINE_ID to AR_ADJUSTMENTS_ALL.ADJUSTMENT_ID:

SELECT t.trx_number,
       t.tax_amount,
       a.adjustment_type,
       a.reason_code
  FROM tax_adjustments_v t,
       ar_adjustments_all a
 WHERE t.trx_line_id = a.adjustment_id;

Always confirm the view's presence and definition via the data dictionary before deploying dependent concurrent programs, given the documentation's note that it may not be implemented in all environments.