Results for “okl_bpd_disb_contract_lov_uv”

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

Overview

OKL_BPD_DISB_CONTRACT_LOV_UV is a VALID Oracle EBS view owned by the APPS schema within the OKL - Leasing and Finance Management product family. Its documented purpose is to populate a List of Values (LOV) on the disbursement screen. In Oracle Leasing and Finance Management, disbursement processing requires the operator to associate a funding request with a specific lease or loan contract and the vendor that is party to that contract. This view serves as the query source behind that selection control, returning a restricted, presentation-ready result set rather than the full contract population.

Because it is defined as a view and not a table, it stores no data of its own. It functions purely as a read-only projection layered over contract header and party-role data, joining the contract to the vendor acting in the OKL_VENDOR role. This makes it relevant both to the disbursement UI and to any reporting or integration process that must resolve the vendor associated with a given lease contract.

Underlying Base Objects

The view is defined over three referenced objects, with a fourth dependency documented in the ETRM metadata:

• OKC_K_HEADERS_B (SYNONYM) — the contract header, supplying contract identity (ID), contract number, and currency code.
• OKC_K_PARTY_ROLES_V (VIEW) — the contract party-role view, which resolves the parties attached to a contract and the role each plays. The view restricts this to RLE_CODE = 'OKL_VENDOR'.
• OKX_VENDORS_V (VIEW) — the vendors view, supplying the vendor name and party number for the identified vendor.
• FND_GLOBAL (PACKAGE) — the standard EBS concurrent/global context package, referenced for session context (such as organization or user context) used by the underlying objects.

The join path is: OKC_K_HEADERS_B.ID equals OKC_K_PARTY_ROLES_V.CHR_ID, and OKX_VENDORS_V.ID1 equals OKC_K_PARTY_ROLES_V.OBJECT1_ID1, filtered to the vendor role. Only contracts that have a party recorded in the OKL_VENDOR role therefore appear in the LOV.

Key Columns

• CONTRACT_ID — the internal identifier of the contract (from OKC_K_HEADERS_B.ID); typically the returned value bound to the disbursement record.
• CONTRACT_NUMBER — the user-facing contract number, displayed in the LOV list.
• CURRENCY_CODE — the contract currency, useful for validating disbursement amounts against the contract.
• VENDOR_ID — the vendor identifier (from OKX_VENDORS_V.ID1) associated with the contract in the vendor role.
• VENDOR_NAME — the vendor name, generally the descriptive column shown to the user.
• VENDOR_NUMBER — the vendor party number, the external-facing supplier reference.

Common Use Cases and Queries

Typical uses include driving the disbursement LOV, validating that a contract has an assigned vendor before disbursement, and reporting the vendor-to-contract relationship for leasing activity. A sample query is shown below.

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;

For integration or reporting, the view can be joined to disbursement and funding tables using CONTRACT_ID and VENDOR_ID as the linkage keys. Because the result set is filtered to contracts carrying an OKL_VENDOR party role, callers should not treat absence of a row as absence of a contract; it indicates only that no vendor role is defined.