Search Results poo_address_code




Overview
Explore in AI Chat

Overview

The TAX_ADJUSTMENTS_V_V view is an Oracle E-Business Suite Receivables (AR) reporting object that exposes tax adjustment activity in a normalized, tax-engine-consumable format. Its documentation traces to Release 11.5, and it remains present in the 12.1.1 / 12.2.2 data model where it is consumed by the E-Business Tax (EBTax) tax determination and reporting architecture. The view presents a uniform, tax-relevant projection of adjustment records — one row per adjustment line — by union-compatible aliasing of adjustment data into the same column vocabulary used by other AR tax views (for example, transaction lines and tax lines). This design allows the tax engine to query a single column layout across disparate source documents.

The view is not directly maintained by users; it is a read-only query construct. It maps adjustment amounts, dates, and tax-relevant attributes into canonical column names such as TRX_DATE, TAX_AMOUNT, and TAXABLE_FLAG so that downstream reporting, tax calculation, and integration processes can treat adjustments consistently with customer transactions. Note that TAX_ADJUSTMENTS_V_V is documented as "Not implemented in this database" in the source metadata, which indicates the version of the environment from which the documentation was extracted did not instantiate the view; where implemented, it relies on helper functions in the ARP_TAX_VIEW_VERTEX package.

Underlying Base Objects

The ETRM metadata records no formally documented base objects for this view, classifying its referenced objects as none documented. The embedded view text, however, reveals the actual base tables through its join and column references:

The view therefore derives its content primarily from the AR adjustment lines, joined to headers for customer and site context, and enriched at query time by the tax vertex package for address and exemption resolution.

Key Columns

  • SHIP_TO_CUSTOMER_ID / BILL_TO_CUSTOMER_ID — customer identifiers inherited from the transaction header; central to party-level tax determination.
  • TRX_CHARGE_LINE_ID, TRX_LINE_ID, TRX_HEADER_ID — surrogate identifiers; for adjustments both TRX_LINE_ID and TRX_HEADER_ID carry the ADJUSTMENT_ID, and TRX_CHARGE_LINE_ID is NULL.
  • TRX_DATE / GL_DATE — the adjustment apply date and accounting date, critical for period-based tax reporting.
  • TAX_AMOUNT — populated from L.TAX_ADJUSTED, representing the tax portion of the adjustment.
  • TAXABLE_FLAG — hard-coded to 'Y' for adjustment rows, signalling taxability.
  • LOCATION_QUALIFIER — literal 'ALL', broadening the applicable location scope.
  • EXCHANGE_RATE, SET_OF_BOOKS_ID, CURRENCY_CODE, PRECISION, MINIMUM_ACCOUNTABLE_UNIT — monetary and currency context for correct rounding and conversion.
  • POO_ADDRESS_CODE, POA_ADDRESS_CODE, SHIP_FROM_ADDRESS_CODE — derived via ARP_TAX_VIEW_VERTEX, providing place-of-supply and ship-from address determinations.
  • VENDOR_CONTROL_EXEMPTIONS — exemption logic derived from the customer transaction type.
  • SHIP_TO_ADDRESS_CODE, TAX_EXEMPT_FLAG, TAX_RATE, EXTENDED_AMOUNT, REQUEST_ID and similar columns are returned as NULL placeholders to preserve columnar uniformity.

Because the searcher's term relates to numeric_attribute1, it is relevant that this view exposes no descriptive flexfield columns; the numeric attribute DFF segments reside on the underlying AR tables rather than in this tax projection. Reporting on numeric_attribute1 therefore requires querying RA_CUSTOMER_TRX_LINES_ALL or RA_CUSTOMER_TRX_ALL directly and joining to this view by adjustment identifier.

Common Use Cases and Queries

Primary uses include tax adjustment reconciliation, tax reporting extracts, and integration feeds to external tax engines. A representative query lists adjustment-driven tax amounts with customer and currency context:

  • Reconcile tax adjustments by period: SELECT TRX_LINE_ID, TRX_DATE, GL_DATE, TAX_AMOUNT, CURRENCY_CODE FROM TAX_ADJUSTMENTS_V_V WHERE GL_DATE BETWEEN :start AND :end;
  • Join to adjustment source tables to retrieve numeric_attribute1: SELECT v.TRX_LINE_ID, l.numeric_attribute1, v.TAX_AMOUNT FROM TAX_ADJUSTMENTS_V_V v, RA_CUSTOMER_TRX_LINES_ALL l WHERE v.TRX_LINE_ID = l.customer_trx_line_id;
  • Analyze tax by set of books and customer: SELECT SET_OF_BOOKS_ID, BILL_TO_CUSTOMER_ID, SUM(TAX_AMOUNT) FROM TAX_ADJUSTMENTS_V_V GROUP BY SET_OF_BOOKS_ID, BILL_TO_CUSTOMER_ID;
  • Exemption and address determination: SELECT TRX_LINE_ID, POO_ADDRESS_CODE, POA_ADDRESS_CODE, VENDOR_CONTROL_EXEMPTIONS FROM TAX_ADJUSTMENTS_V_V;

Where numeric_attribute1 is the reporting target, the DFF segment must be sourced from the base AR line or header table and correlated to the view through the adjustment identifier, since the view does not carry flexfield data.