Search Results taxed_quantity




Overview
Explore in AI Chat

Overview

The TAX_ADJUSTMENTS_VBR view is a reporting and integration object within the Oracle E-Business Suite Latin America Localizations (JL) module. Its name follows the EBS convention for tax repository views, where the "VBR" suffix denotes a view built for the E-Business Tax repository (EBTax) interface. The view presents tax adjustment data — records whose transaction line type is fixed as 'ADJ' — in the standardized column layout required by the tax engine's repository structure. It is designed to unify adjustment records from the Oracle Receivables adjustment tables into a tax-repository-compatible projection so that downstream tax reporting, audit queries, and integration processes can consume adjustment data using the same column vocabulary applied to other transaction types.

In Oracle EBS 12.1.1 and 12.2.2, these repository views typically back the tax reporting and audit trail functionality used by Latin American localizations for country-specific fiscal reporting. The view itself is not a stored table; it recomputes the tax-relevant projection at query time from its driving header and line objects.

Underlying Base Objects

The documented view text references two source aliases: H for the header-level object and L for the line-level adjustment object, with an additional currency-table alias C supplying currency attributes. The columns exposed from H include SHIP_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID, INVOICING_RULE_ID, EXCHANGE_RATE, SET_OF_BOOKS_ID, FOB_POINT, and TRX_NUMBER. The line alias L supplies ADJUSTMENT_ID (mapped to both TRX_LINE_ID and TRX_HEADER_ID), APPLY_DATE, GL_DATE, and AMOUNT.

The ETRM documentation records no referenced base objects for this view, meaning the wrapper objects (commonly AR_ADJUSTMENTS and AR_CASH_RECEIPTS or an analogous AR adjustment header source) are not explicitly listed in the metadata. Columns such as SHIP_TO_CUSTOMER_NAME, BILL_TO_CUSTOMER_NAME, SHIP_TO_CUSTOMER_NUMBER, and BILL_TO_CUSTOMER_NUMBER are projected as literal NULL in the view text, so customer-name values are not denormalized within this object.

Key Columns

  • TRX_LINE_ID / TRX_HEADER_ID — Both map to L.ADJUSTMENT_ID, identifying the adjustment as both the header and line key for this projection.
  • TRX_NUMBER — The adjustment transaction number from H.TRX_NUMBER.
  • TAX_AMOUNT — The adjustment amount (L.AMOUNT), carrying the tax-relevant monetary value.
  • TRX_DATE / GL_DATE — L.APPLY_DATE and L.GL_DATE, providing the application and accounting dates.
  • BILL_TO_CUSTOMER_ID / SHIP_TO_CUSTOMER_ID — Party identifiers from the header; the corresponding *_NAME and *_NUMBER columns are NULL.
  • CURRENCY_CODE, PRECISION, MINIMUM_ACCOUNTABLE_UNIT — Sourced from the currency alias C, supporting rounding and formatting.
  • LOCATION_QUALIFIER ('ALL'), TAXABLE_FLAG ('Y'), AUDIT_FLAG ('Y'), TRX_LINE_TYPE ('ADJ') — Literal constants that classify the row as an auditable, taxable adjustment.

Common Use Cases and Queries

Because a user searching for "bill_to_customer_name" reached this object, a common requirement is retrieving the adjustment's customer name. Since the view returns NULL for BILL_TO_CUSTOMER_NAME, the correct approach is to join to the customer/party tables on BILL_TO_CUSTOMER_ID. A representative query is:

SELECT v.TRX_NUMBER,
       v.TAX_AMOUNT,
       v.TRX_DATE,
       hp.party_name AS bill_to_customer_name
FROM   TAX_ADJUSTMENTS_VBR v,
       hz_parties hp
WHERE  hp.party_id = v.BILL_TO_CUSTOMER_ID;

Other scenarios include feeding adjustment tax data into EBTax reporting extracts, reconciling adjustment amounts by GL date, and auditing taxable adjustments by set of books and currency. As the view is listed as "not implemented in this database" in the documented environment, availability should be verified before use in production queries.