Results for “vat_tax_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CUSTOMER_VENDOR_VAT_V is a VALID database view owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) product family. Its purpose, as documented in the ETRM repository, is to consolidate Customer and Vendor VAT/Tax Codes into a single queryable structure. The view exposes a single column, VAT_TAX_CODE, which returns the tax registration reference for a party regardless of whether that party is a customer or a supplier. Because VAT registration numbers are commonly used as a primary identifier for tax reporting, statutory filings, and intercompany trading documentation, this view provides a convenient union point that would otherwise require two separate queries against disparate tables in the Trading Community Architecture (TCA) and Purchasing schemas.

The view is documented as valid across Oracle EBS 12.1.1 and 12.2.2. The 12.2.2 ETRM metadata confirms APPS as the owner and identifies the referenced base objects, all of which are resolved through synonyms or views: HZ_CUST_ACCOUNTS (SYNONYM), HZ_PARTIES (SYNONYM), and PO_VENDORS (VIEW). This object is typically encountered when searching for terms such as "cad vat number," reflecting the common usage of a customer's VAT number as a search or cross-reference key.

Underlying Base Objects

The documented view text establishes a UNION between two distinct data paths:

• Customer path: Joins HZ_CUST_ACCOUNTS to HZ_PARTIES on PARTY_ID, extracting PARTY.TAX_REFERENCE as VAT_TAX_CODE. HZ_PARTIES is the master party record within TCA, and TAX_REFERENCE holds the party's tax registration identifier. HZ_CUST_ACCOUNTS links that party to the customer account context.
• Vendor path: Selects VAT_REGISTRATION_NUM from PO_VENDORS, which in the documented metadata is itself resolved as a view. This column stores the supplier's VAT registration number used in Purchasing and Payables.

Because the two branches use UNION (not UNION ALL), duplicate tax codes that appear in both the customer and vendor populations are collapsed into a single distinct row. The structure is therefore a reference set of unique VAT/Tax codes drawn from both the Receivables/TCA and Purchasing domains.

Key Columns

• VAT_TAX_CODE — The only column exposed by the view. It carries the tax registration reference value originating from HZ_PARTIES.TAX_REFERENCE for customer parties or from PO_VENDORS.VAT_REGISTRATION_NUM for suppliers. Both source columns are aliased to the same output name so that the union presents a uniform schema.

No party identifier, party name, party type, or account number is projected. Consequently, the view is not suitable for determining which party owns a given VAT code; it functions strictly as a distinct value list.

Common Use Cases and Queries

The view is most often used for validation and lookup purposes, such as verifying whether a supplied VAT number exists anywhere in the customer or vendor base, or populating a list of Tax codes for tax reporting and reconciliation. Because the view returns only distinct tax codes, it is unsuitable for joins that require the owning party or account.

• Confirming a specific VAT number:
  SELECT VAT_TAX_CODE FROM APPS.AR_CUSTOMER_VENDOR_VAT_V WHERE VAT_TAX_CODE = :p_vat_number;
• Retrieving the full reference list:
  SELECT VAT_TAX_CODE FROM APPS.AR_CUSTOMER_VENDOR_VAT_V ORDER BY VAT_TAX_CODE;
• Counting distinct registrations across both populations:
  SELECT COUNT(*) FROM APPS.AR_CUSTOMER_VENDOR_VAT_V;
• Case-insensitive pattern search on a partial VAT number:
  SELECT VAT_TAX_CODE FROM APPS.AR_CUSTOMER_VENDOR_VAT_V WHERE UPPER(VAT_TAX_CODE) LIKE UPPER('%'||:p_frag||'%');

Where party-level detail is required, developers must query HZ_PARTIES.TAX_REFERENCE (joined via HZ_CUST_ACCOUNTS) for customers and PO_VENDORS.VAT_REGISTRATION_NUM for suppliers directly, rather than relying on this consolidated view.