Search Results okl_cs_vendors_uv




Overview
Explore in AI Chat

Overview

OKL_CS_VENDORS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered as part of the OKL product family, Oracle Leasing and Finance Management, and resides in the ETRM (Enterprise Transaction and Relationship Management) layer that underpins contract and lease servicing. The view presents vendor parties that have been associated with an Oracle Contracts or lease contract as a party role, together with their address and contact details sourced from the Purchasing vendor master. It effectively joins the contract header to the party role assignment and then to the vendor and vendor site records, producing a denormalized, report-friendly result set.

The "_UV" suffix indicates a user-facing view intended primarily for reporting, ad hoc query, and downstream integration rather than for transactional maintenance. The view carries no update, insert, or delete semantics; consumers select from it directly. In the ETRM security model, access to the view is granted through the APPS schema and typically inherited by responsibility-level users who already have inquiry privileges on leasing contracts and vendors.

Underlying Base Objects

The view is defined over four primary base objects, with a fifth referenced for session context:

The join chain is: PO_VENDORS.VENDOR_ID = PO_VENDOR_SITES_ALL.VENDOR_ID, and PR.OBJECT1_ID1 = PO_VENDORS.VENDOR_ID, with PR.DNZ_CHR_ID = CHR.ID and PR.CHR_ID = CHR.ID linking the party role to the contract header.

Key Columns

  • CONTRACT_ID / CONTRACT_NUMBER — Identifier and human-readable number of the lease or contract header.
  • ROLE_NAME — The party role the vendor plays on the contract (for example, lessor or supplier role assignment).
  • AMT_GUARANTEED / PTYPE — Placeholder columns returned as empty string literals ('' and NVL('','')), reserved for residual/guarantee reporting extensions and not populated by the current definition.
  • COMPANY / CUSTOMER_NUMBER — Vendor name and vendor number segment from PO_VENDORS.
  • EMAIL / PHONE — Contact data from the vendor site; PHONE is concatenated as AREA_CODE || '-' || PHONE.
  • ADDRESS1–4, CITY, COUNTY, PROVINCE, STATE, POSTAL_CODE, COUNTRY — Full mailing address attributes drawn from PO_VENDOR_SITES_ALL.

Common Use Cases and Queries

Typical usage includes contract party listings, vendor contact extracts for lease documentation, and integration feeds requiring vendor address data tied to specific contracts.

List all vendors on a given contract:

SELECT contract_number, role_name, company, email, phone
FROM apps.okl_cs_vendors_uv
WHERE contract_number = :contract_number;

Locate contracts associated with a vendor company:

SELECT contract_number, role_name, city, state, country
FROM apps.okl_cs_vendors_uv
WHERE company = :vendor_name;

Produce a mailing extract for contract correspondence by filtering on postal attributes and excluding blank emails. Because the view is read-only and joins several base objects, queries should be constrained by contract or vendor to avoid broad full scans across OKC_K_HEADERS_B and the vendor master.