Results for “okl_cs_vendor_contacts_uv”

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

Overview

The view OKL_CS_VENDOR_CONTACTS_UV is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Lease and Finance Management product family. Its documented description is "List of Vendor Contacts." The view consolidates vendor contact information originating from the Oracle Purchasing vendor master and presents it in a denormalized form suitable for lease and finance workflows that must reference supplier contact personnel — for example, when building lease contract contact lists, quote intake, or third-party financing correspondence.

The _UV suffix follows the Oracle naming convention denoting a "user view," meaning the object is intended for customer-facing reference and extension rather than internal-only dependency. Because it is a view and not a table, it stores no data of its own; it is a read-only projection over the underlying Purchasing views and therefore always reflects the current state of the vendor master.

The search term "mail_stop" supplied by the user maps directly to the MAIL_STOP column exposed by this view, which surfaces the mail stop attribute held on the underlying PO_VENDOR_CONTACTS record.

Underlying Base Objects

The documented metadata identifies the referenced base objects as PO_VENDORS (VIEW), PO_VENDOR_CONTACTS (VIEW), and PO_VENDOR_SITES_ALL (VIEW), with a dependency on FND_GLOBAL (PACKAGE). The view's definition joins these Purchasing views as follows:

• PO_VENDOR_CONTACTS POC — the driving source of contact-level attributes such as name components, mail stop, phone, and title.
• PO_VENDOR_SITES_ALL POS — joined to POC on VENDOR_SITE_ID, providing the vendor site context for each contact.
• PO_VENDORS POV — joined to POS on VENDOR_ID, anchoring each contact to its owning vendor record.

The join condition is therefore: POV.VENDOR_ID = POS.VENDOR_ID AND POS.VENDOR_SITE_ID = POC.VENDOR_SITE_ID. This is an inner-join chain, meaning a contact appears only when a valid vendor and vendor site exist for it. The FND_GLOBAL reference is consistent with EBS multi-org and security conventions applied at runtime.

Key Columns

The view exposes seven columns, each derived or passed through from the base objects:

• CONTACT_NAME — concatenation of PREFIX, FIRST_NAME, MIDDLE_NAME, and LAST_NAME from PO_VENDOR_CONTACTS, separated by spaces.
• MAIL_STOP — the mail stop value from POC.MAIL_STOP; the attribute most directly matching the user's search term.
• PHONE — AREA_CODE concatenated with PHONE using a hyphen.
• DESCRIPTION — TITLE concatenated with PHONE using a hyphen.
• VENDOR_CONTACT_ID — primary identifier of the contact record, from PO_VENDOR_CONTACTS.
• VENDOR_ID — identifier of the owning vendor, sourced via PO_VENDORS.
• VENDOR_SITE_ID — identifier of the associated vendor site from PO_VENDOR_SITES_ALL.

Common Use Cases and Queries

Typical usage involves reporting or validating supplier contact details within lease and finance processes. A query to retrieve all contacts with a mail stop is:

• SELECT contact_name, mail_stop, phone, vendor_id, vendor_site_id FROM okl_cs_vendor_contacts_uv WHERE mail_stop IS NOT NULL;
• Filtering by vendor: SELECT * FROM okl_cs_vendor_contacts_uv WHERE vendor_id = :p_vendor_id;
• Searching by site: SELECT contact_name, mail_stop FROM okl_cs_vendor_contacts_uv WHERE vendor_site_id = :p_site_id;

Because the object is a view over Purchasing entities, no DML is permitted against it; inserts or updates must target PO_VENDOR_CONTACTS directly. Its principal value lies in providing a clean, join-ready contact projection for lease management reporting and integration interfaces.