Search Results okl_vendor

Overview

The APPS.OKL_BPD_DISB_CONTRACT_LOV_UV view is an Oracle E-Business Suite dictionary object owned by the APPS schema. It is a reporting and integration view used within the Oracle Contracts (OKC) and Oracle Lease and Finance Management (OKL) functional areas to present a list-of-values (LOV) style result set that pairs lease or contract headers with their associated vendor (party) information. The view is commonly referenced in the context of searches for okl_vendor, since the vendor role code it filters on is the literal value OKL_VENDOR. Its primary purpose is to expose a denormalized relationship between contract headers and vendor records so that forms, concurrent programs, BI Publisher reports, and external integrations can retrieve contract-to-vendor mappings without writing the join logic themselves. Because it joins header, party role, and vendor views, it serves as a convenient abstraction layer for disbursement and contract-vendor LOV functionality.

Underlying Base Objects

The view is defined over three primary objects, all documented in the ETRM 12.2.2 metadata:

• OKC_K_HEADERS_B (SYNONYM) — the base contract header table, aliased as KHR, supplying the contract identifier, contract number, and currency code.
• OKC_K_PARTY_ROLES_V (VIEW) — the party roles view, aliased as PARTY_ROLE, which stores the association between a contract and its participating parties, including the role code.
• OKX_VENDORS_V (VIEW) — the vendors view, aliased as V, providing the vendor master attributes such as vendor name and party number.

The metadata also lists FND_GLOBAL (PACKAGE) as a referenced base object, reflecting the standard EBS practice of deriving runtime context such as USER_ID, RESP_ID, and ORG_ID through the FND_GLOBAL package. The joins bind contract headers to party roles on KHR.ID = PARTY_ROLE.CHR_ID, restrict the role to RLE_CODE = 'OKL_VENDOR', and then link the party role to the vendor view via V.ID1 = PARTY_ROLE.OBJECT1_ID1.

Key Columns

The view exposes six columns, each originating from one of the underlying objects:

• CONTRACT_ID — sourced from KHR.ID; the unique identifier of the contract header.
• CONTRACT_NUMBER — sourced from KHR.CONTRACT_NUMBER; the human-readable contract number.
• CURRENCY_CODE — sourced from KHR.CURRENCY_CODE; the contract's currency.
• VENDOR_ID — sourced from V.ID1; the internal vendor identifier used for joins to vendor and disbursement data.
• VENDOR_NAME — sourced from V.NAME; the descriptive vendor name.
• VENDOR_NUMBER — sourced from V.PARTY_NUMBER; the party number associated with the vendor.

Common Use Cases and Queries

The view is typically queried for LOV validation, reconciliation of disbursement contracts with their vendors, and reporting. A representative query is:

• SELECT contract_id, contract_number, currency_code, vendor_id, vendor_name, vendor_number FROM apps.okl_bpd_disb_contract_lov_uv WHERE contract_number = :p_contract_number;
• SELECT vendor_id, vendor_name, vendor_number FROM apps.okl_bpd_disb_contract_lov_uv WHERE contract_id = :p_contract_id;

Because the view already enforces the OKL_VENDOR role restriction, callers do not need to filter on role code themselves, reducing the risk of inconsistent results across reports and integrations.