Search Results tax_exemptions_v




Overview
Explore in AI Chat

Overview

TAX_EXEMPTIONS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) module. It consolidates customer tax exemption records held in the transaction table RA_TAX_EXEMPTIONS with the corresponding ship-to and bill-to context drawn from the Trading Community Architecture (TCA) party and site model. Rather than exposing raw exemption rows in isolation, the view resolves each exemption to the customer account and site use to which it applies, and it decodes internal reason and status codes into user-facing meanings.

Because tax determination in EBS depends on the correct exemption being applied to a given ship-to site at transaction time, this view serves as a diagnostic and integration surface. It allows implementers and support analysts to verify which exemptions exist for a customer, their effective dates, the percentage exempt, and their approval status without navigating the Receivables forms. It is equally usable from custom reports, extracts, and interfaces that must evaluate exemption eligibility before an invoice or order is processed.

Underlying Base Objects

The view is defined over seven documented base objects. The principal transaction object is RA_TAX_EXEMPTIONS, exposed as a synonym, which carries the exemption number, reason code, percentage, status, dates, tax code, and the location segmentation columns. The TCA objects HZ_CUST_SITE_USES, HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, and HZ_LOC_ASSIGNMENTS provide the site use, account site, party site, and location assignment context respectively, all accessed through synonyms.

Two lookup views, AR_LOOKUPS, supply the decoded meaning values for the status and reason code columns. AR_LOCATION_COMBINATIONS, itself a view, supplies the location identifier segments used to align the customer site with the exemption record. The join logic links site use to account site, account site to party site, and party site to location assignment, with an outer join to AR_LOCATION_COMBINATIONS. Organization ID conditions and USERENV client information are applied so that records are filtered to the appropriate operating unit context, consistent with multi-org security in 12.1.1 and 12.2.2.

Key Columns

Common Use Cases and Queries

A frequent requirement is verifying whether a customer holds a valid exemption for a specific site on a given date. The NVL expressions on the reason and status columns mean callers can rely on readable values without joining AR_LOOKUPS themselves.

  • List active exemptions for a customer: SELECT tax_exempt_number, tax_exempt_reason_meaning, percent_exempt, start_date, end_date FROM apps.tax_exemptions_v WHERE ship_to_customer_id = :customer_id AND TRUNC(SYSDATE) BETWEEN TRUNC(start_date) AND TRUNC(end_date).
  • Identify expired or unapproved records: SELECT * FROM apps.tax_exemptions_v WHERE status_meaning IN ('EXPIRED','UNAPPROVED') ORDER BY display_order.
  • Resolve the governing exemption for a site: filter by ship_to_site_use_id and order by display_order ascending, taking the first row, which mirrors the precedence logic embedded in the view.
  • Reconcile exemptions to tax codes: SELECT tax_code, COUNT(*) FROM apps.tax_exemptions_v GROUP BY tax_code.

Because the definition embeds multi-org and USERENV client filtering, the view returns results consistent with the caller's organization context, which should be considered when it is used in concurrent programs or external extracts.