Search Results vendor_adr1

Overview

OKL_CS_VENDOR_SEARCH_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Leasing and Finance Management) product family. It is a customer-facing search view designed to expose supplier (vendor) information for the leasing and finance contract lifecycle. The view consolidates vendor master data, supplier site address details, primary contact information, and consolidated supplier invoice data into a single denormalized result set. Its primary purpose is to support vendor search and lookup functionality in leasing applications, allowing users to locate vendors by name, number, address, phone, or associated invoice references.

The view is registered in EBS as status VALID and is documented as part of the ETRM 12.2.2 metadata set, with a parallel structure supported in 12.1.1. Because OKL frequently requires vendor selection during quote-to-contract and payables matching processes, this view acts as a convenient search interface that avoids repeated navigation across AP supplier and OKL invoice tables.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through synonyms in the APPS schema:

• AP_SUPPLIERS — Supplier master records; supplies vendor name and vendor number (SEGMENT1).
• AP_SUPPLIER_CONTACTS — Supplier contact records; supplies last name and first name for the primary contact.
• AP_SUPPLIER_SITES_ALL — Supplier site and address information; supplies address lines, city, state, country, postal code, area code, phone, and customer number.
• OKL_CNSLD_AP_INVS_ALL — OKL consolidated supplier invoice staging table; supplies invoice number and vendor invoice number. This is the OKL-specific table that ties the view to the leasing application.

The join logic links AP_SUPPLIER_SITES_ALL to AP_SUPPLIERS on VENDOR_ID, to AP_SUPPLIER_CONTACTS on VENDOR_SITE_ID (outer join, indicated by the (+) syntax), and to OKL_CNSLD_AP_INVS_ALL on both IPVS_ID (matched to VENDOR_SITE_ID) and VENDOR_ID. The outer join to supplier contacts permits sites without a defined contact to remain in the result set.

Key Columns

• VENDOR_NAME, VENDOR_NUMBER, VENDOR_ID — Vendor name, the SEGMENT1 vendor number, and the internal vendor identifier.
• LAST_NAME, FIRST_NAME — Primary contact name for the supplier site.
• VENDOR_ADR1, VENDOR_CITY, VENDOR_STATE, VENDOR_COUNTRY, VENDOR_ZIP — Site-level address components.
• VENDOR_AREA_CODE, VENDOR_PHONE — Site telephone details. The VENDOR_PHONE column is especially relevant for the "vendor_phone" search requirement, as it exposes the supplier site phone number directly for lookup and reporting.
• VENDOR_CUSTOMER_NUM — Customer number associated with the supplier site, useful in leasing where vendors may also act as customers.
• INVOICE_NUMBER, VENDOR_INVOICE_NUMBER — Consolidated AP invoice references from the OKL invoice staging table.

Common Use Cases and Queries

Typical uses include vendor lookup screens in OKL lease and financing flows, AP invoice reconciliation, and ad-hoc reporting on vendor contact and phone details. A sample query returning vendors filtered by phone suffix:

• SELECT vendor_name, vendor_number, vendor_phone, vendor_city FROM okl_cs_vendor_search_uv WHERE vendor_phone LIKE '%555%';
• SELECT vendor_name, last_name, first_name, invoice_number FROM okl_cs_vendor_search_uv WHERE vendor_name LIKE 'ACME%';
• SELECT vendor_id, vendor_number, vendor_adr1, vendor_phone FROM okl_cs_vendor_search_uv WHERE vendor_customer_num = :p_customer_num;

Because the view is a simple join without aggregation, filters on any exposed column are applied efficiently. Organizations typically wrap the view in custom OKL search pages or use it as a base for supplier-facing extents. As the view is owned by APPS and marked VALID, it is safe to query from custom reports, though direct DML is not permitted on a view of this construction.