Results for “ar_customer_vendor_nif_v”

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

Overview

The AR_CUSTOMER_VENDOR_NIF_V view is an Oracle E-Business Suite Receivables (AR) database object owned by the APPS schema. Its documented purpose is to expose Customer and Vendor NIF codes within a single consolidated result set. The acronym NIF corresponds to "Número de Identificación Fiscal," the tax identification number used in Spain and several other jurisdictions. Because Oracle EBS stores customer tax identifiers and supplier tax identifiers in entirely different structures, this view provides a unified access point for reporting, integration, and reconciliation purposes.

The view is particularly relevant to users searching for num_1099. In the United States, the 1099 tax reporting framework requires tracking of a vendor's taxpayer identification number (TIN), and Oracle EBS historically stored this value in the NUM_1099 column of the PO_VENDORS table. The AR_CUSTOMER_VENDOR_NIF_V view surfaces this same column under the generic alias NIF_CODE, allowing federal tax identifiers for suppliers to be queried alongside the fiscal codes held for customers. This makes the view useful for global tax reporting where a single column name must represent multiple national identifier schemes.

Underlying Base Objects

The view is defined over three documented base objects. The first two, HZ_CUST_ACCOUNTS and HZ_PARTIES, are referenced as synonyms in the APPS schema and belong to the Trading Community Architecture (TCA) model that underpins Customers Online and Receivables. The third, PO_VENDORS, is referenced as a view. The definition joins HZ_CUST_ACCOUNTS to HZ_PARTIES on PARTY_ID to retrieve the customer-side value, and performs a UNION with PO_VENDORS to retrieve the supplier-side value.

Because the customer branch draws from the TCA party model and the vendor branch draws from the purchasing supplier records, the view spans two distinct data domains that are not otherwise related by a foreign key. There is no join condition between the two branches; they are combined solely by the UNION operator, which also implies that duplicate values are eliminated in the result set.

Key Columns

The view exposes a single documented column, NIF_CODE. Its meaning depends on the originating branch of the union:

• Customer records: NIF_CODE is populated from HZ_PARTIES.JGZZ_FISCAL_CODE, the flexfield attribute that stores a party's fiscal or tax registration number. Records flow in through the join between HZ_CUST_ACCOUNTS and HZ_PARTIES.
• Supplier records: NIF_CODE is populated from PO_VENDORS.NUM_1099, the 1099 taxpayer identification number maintained against a supplier. This is the element that directly answers a search for num_1099.

No other columns are documented, and no column identifies whether a given row originated from the customer or vendor branch. This ambiguity is important to note when interpreting results.

Common Use Cases and Queries

The view is typically consumed for tax reporting, data migration validation, and cross-referencing exercises where a list of fiscal identifiers must be produced from both customer and supplier populations. A representative query follows:

• SELECT NIF_CODE FROM APPS.AR_CUSTOMER_VENDOR_NIF_V; — returns the full consolidated list.
• SELECT NIF_CODE FROM APPS.AR_CUSTOMER_VENDOR_NIF_V WHERE NIF_CODE IS NOT NULL; — filters out parties and suppliers lacking a fiscal identifier.
• SELECT NIF_CODE, COUNT(*) FROM APPS.AR_CUSTOMER_VENDOR_NIF_V GROUP BY NIF_CODE HAVING COUNT(*) > 1; — identifies duplicate identifiers, which is meaningful because the view's own UNION removes exact duplicates but not duplicates arising from distinct customer and vendor records sharing a value.

In Oracle EBS 12.1.1 and 12.2.2, the view remains valid in the APPS schema and may be referenced directly in BI Publisher reports, custom concurrent programs, and SQL-based integrations. Because it is a read-only view over TCA and supplier data, it should not be used as a target for DML; updates must be applied to the underlying base objects instead.