Results for “ap_vendor_disp_v”

30 results




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

Overview

AP_VENDOR_DISP_V is a Payables-owned database view in the APPS schema that presents supplier (vendor) header and supplier site address information in a flattened, display-ready format. Its documentation status is VALID, and its object metadata is explicitly annotated with the note "(Release 10SC Only)" — indicating that this is a legacy display view whose origins predate the modern multi-org supplier model introduced with Oracle Purchasing and Payables in Release 11i. In Oracle EBS 12.1.1 and 12.2.2 the object remains resident in the APPS schema for backward compatibility, but it is not a supported interface for new development, and Oracle's documented position is that it was intended for the 10SC product line.

The view's purpose is purely informational: it joins supplier header attributes to supplier site address attributes and supplements them with territory and language descriptions, plus a pre-formatted concatenated mailing address. It does not enforce operating unit (ORG_ID) security and does not expose party, party site, or location identifiers used by the TCA (Trading Community Architecture) model. Consequently it functions as a read-only reporting convenience rather than a transactional or integration interface.

Underlying Base Objects

The documented definition selects from four base objects:

The join between supplier and site is an inner join on VENDOR_ID. Both territory and language are outer joins, so address and language columns may be null without eliminating rows. The documented referenced objects also include AP_VENDOR_SITES_PKG, whose FORMAT_ADDRESS function is invoked in the select list, and FND_GLOBAL, consistent with the pattern used by that formatting routine. In 12.2.2 PO_VENDORS and PO_VENDOR_SITES are themselves compatibility views over the supplier and supplier site tables; AP_VENDOR_DISP_V therefore sits two abstraction layers above the physical data.

Key Columns

  • ROW_ID — the ROWID of the PO_VENDOR_SITES row, available for uniquely addressing a site record within a query.
  • VENDOR_ID, VENDOR_NAME, VENDOR_NUMBER — supplier identifier, name, and SEGMENT1 number.
  • VENDOR_SITE_ID, VENDOR_SITE_CODE — site identifier and the user-visible site code.
  • ADDRESS_LINE1–ADDRESS_LINE4, CITY, COUNTY, STATE, PROVINCE, ZIP, COUNTRY — raw address components as stored on the site.
  • TERRITORY_SHORT_NAME — abbreviated country or territory name from FND_TERRITORIES_VL.
  • CONCATENATED_ADDRESS — the output of AP_VENDOR_SITES_PKG.FORMAT_ADDRESS, rendering the address according to the territory's address style.
  • AREA_CODE, PHONE, FAX_AREA_CODE, FAX, TELEX — site contact numbers.
  • LANGUAGE, LANGUAGE_DESCRIPTION — language code and its descriptive text.
  • INVOICE_CURRENCY_CODE, ADDRESS_STYLE — default invoicing currency for the site and the address style used for formatting.

Common Use Cases and Queries

Typical usage is ad hoc reporting or a quick supplier address lookup where the formatted address is required without invoking the formatting package directly. Note that no ORG_ID predicate is available, so results span all operating units and should be filtered by supplier or site when precision is required.

Retrieve a formatted address for a supplier:

  • SELECT vendor_name, vendor_number, vendor_site_code, concatenated_address FROM ap_vendor_disp_v WHERE vendor_id = :p_vendor_id;

List all active-looking sites for a supplier name pattern:

  • SELECT vendor_name, vendor_site_code, city, country, territory_short_name FROM ap_vendor_disp_v WHERE vendor_name LIKE 'ACME%' ORDER BY vendor_name, vendor_site_code;

Extract phone and fax for a mailing list:

  • SELECT vendor_name, vendor_site_code, area_code, phone, fax_area_code, fax, invoice_currency_code FROM ap_vendor_disp_v WHERE country = 'US';

Because the view exposes no party or location identifiers and is documented as 10SC-only, new reports and interfaces in 12.1.1 or 12.2.2 should be built against PO_VENDORS, PO_VENDOR_SITES, HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS, using the TCA-based supplier tables for future-proof, org-secured access.