Results for “okl_cure_header_uv”

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

Overview

The OKL_CURE_HEADER_UV view is a reporting and integration object within the Oracle EBS Lease and Finance Management (OKL) module. The suffix _UV denotes a "user view," indicating that it is a denormalized, user-facing construct intended for reporting, LOV (List of Values) population, and programmatic access rather than for transactional data entry. In Oracle EBS 12.1.1 and 12.2.2, this view is owned by the APPS schema and is documented as VALID within the ETRM (E-Business Suite Technical Reference Manual) repository.

The view consolidates vendor, vendor site, and vendor contact information into a single flattened row per vendor contact, presenting attributes such as the vendor name, contact person, contact telephone, and a concatenated mailing address. Its principal role is to supply curated vendor contact data to Lease and Finance Management flows — for example, contract or "cure" header processing — where a user or program must resolve a vendor contact and deliverable address without querying multiple purchasing tables directly. Although the view itself does not reference any OKL-specific tables, it is documented under the OKL product because its consumer logic resides there.

Underlying Base Objects

The view is defined over four documented base objects, all joined through a single SELECT statement:

• PO_VENDORS (VIEW) — supplies the supplier header, aliased as VND.
• PO_VENDOR_SITES_ALL (VIEW) — supplies the vendor site and address data, aliased as VSV.
• PO_VENDOR_CONTACTS (VIEW) — supplies the contact person and phone data, aliased as VCV.
• FND_GLOBAL (PACKAGE) — referenced by the view definition for session context such as ORG_ID resolution.

The join predicates are: VND.VENDOR_ID = VSV.VENDOR_ID and VSV.VENDOR_SITE_ID = VCV.VENDOR_SITE_ID. This means the view returns one row for every combination of vendor, vendor site, and vendor contact, restricted by the multi-org site context (ORG_ID). Because it reads from the PO_* synonym views, only suppliers and sites visible in the current operating unit and with valid contacts are surfaced.

Key Columns

• VENDOR_ID — Surrogate key of the supplier from PO_VENDORS; the primary join key to supplier records.
• VENDOR_NAME — The supplier's display name.
• VENDOR_CONTACT_ID — Surrogate key of the contact in PO_VENDOR_CONTACTS; the column most commonly searched when resolving a contact.
• VENDOR_CONTACT_NAME — A derived value combining the contact's last name and first name using CONCAT(VCV.LAST_NAME||', ', VCV.FIRST_NAME), producing the familiar "Last, First" format. This is the column users informally refer to as vendor_contact_name.
• VENDOR_CONTACT_PHONE — The contact phone number, dynamically formatted: if AREA_CODE is null the raw phone is returned; otherwise the area code is wrapped in parentheses and concatenated to the phone.
• VENDOR_ADDRESS — A concatenated address string assembled from ADDRESS_LINE1 through ADDRESS_LINE3, CITY, STATE, and ZIP, with each non-null component appended using a comma delimiter.
• VENDOR_SITE_ID — Surrogate key of the vendor site, linking the contact to its physical address and operating unit.
• ORG_ID — The operating unit identifier, carried from PO_VENDOR_SITES_ALL for multi-org security and filtering.

Common Use Cases and Queries

The view is typically queried to resolve a supplier contact and its mailing address for lease correspondence, cure notices, and vendor-side documentation. A representative query searches the derived contact name:

• Locate a supplier contact by name:
  SELECT vendor_name, vendor_contact_name, vendor_contact_phone, vendor_address
FROM apps.okl_cure_header_uv
WHERE vendor_contact_name LIKE 'Smith%';
• Resolve all contacts for a given supplier:
  SELECT vendor_contact_id, vendor_contact_name, vendor_address
FROM apps.okl_cure_header_uv
WHERE vendor_id = :p_vendor_id;
• Filter by operating unit:
  SELECT * FROM apps.okl_cure_header_uv WHERE org_id = :p_org_id;

Because the view already formats the contact name, phone, and address, it eliminates the need for redundant string concatenation in downstream reports and forms. Users should note that the view returns duplicate supplier rows when multiple sites or contacts exist, and that multi-org filtering via ORG_ID must be applied explicitly in ad-hoc queries.