Results for “okl_k_vendor_programs_uv”

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

Overview

OKL_K_VENDOR_PROGRAMS_UV is a seeded, read-only view owned by the APPS schema in Oracle Lease and Finance Management (OKL). It presents a denormalized association between lessor vendors, their financing programs, and the leases or loans written against those programs. The view joins the contract header information for a "PROGRAM"-type contract (the vendor program), the corresponding "LEASE" or "LOAN" contract (the underlying lease agreement), and the vendor party that owns the program, exposing a single row per vendor-program-lease combination.

Because it flattens the vendor relationship across three core contract tables, OKL_K_VENDOR_PROGRAMS_UV is typically used for reporting and integration rather than for transactional updates. It provides a convenient source for identifying which lease and loan contracts are tied to a particular vendor program, and it is a common target when building dashboards, extracts, or inquiries in Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

Per the ETRM 12.2.2 metadata and the documented view text, the view is defined over the following referenced objects:

• OKC_K_HEADERS_V (VIEW) — The Contracts Core header view; referenced twice in the view text, once aliased as PROG (the program contract) and once as LEASE (the lease/loan contract).
• OKK_K_HEADERS / OKL_K_HEADERS (SYNONYM) — The OKL lease header table, aliased KHR, linking the program and lease headers via KHR.ID and KHR.KHR_ID.
• OKC_K_PARTY_ROLES_B (SYNONYM) — The Contracts Core party-role base table, aliased PTY; restricts the join to role code OKL_VENDOR.
• OKX_VENDORS_V (VIEW) — The suppliers/vendors view, aliased VND, supplying the vendor name and ID.
• OKC_UTIL (PACKAGE) — The Contracts Core utility package, referenced for supporting function logic.

The central join path ties KHR.ID to the lease header, KHR.KHR_ID to the program header, and the program header to the party-role record via PROG.ID = PTY.CHR_ID. The vendor is resolved through PTY.OBJECT1_ID1 and PTY.OBJECT1_ID2 matching the vendor view's ID1 and ID2.

Key Columns

• VENDOR_ID, VENDOR_NAME — Identifier and name of the supplier/vendor that owns the program, sourced from OKX_VENDORS_V.
• PROGRAM_ID, PROGRAM_NUMBER, PROGRAM_NAME — The internal ID, contract number, and short description of the program contract (SCS_CODE = 'PROGRAM').
• CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_DESCRIPTION — The associated lease or loan contract header (SCS_CODE in 'LEASE', 'LOAN').
• CURRENCY_CODE — The currency of the lease/loan contract, useful for financial aggregation and multicurrency reporting.

Common Use Cases and Queries

The view is used to reconcile vendor programs against the contracts they finance and to drive vendor-level portfolio reporting.

• Listing all leases and loans funded under a specific vendor program.
• Producing vendor exposure summaries by currency.
• Feeding integration extracts that require a flattened vendor-program-contract relationship.

Example query:

SELECT vendor_name, program_number, contract_number, currency_code
FROM apps.okl_k_vendor_programs_uv
WHERE vendor_id = :p_vendor_id
ORDER BY program_number, contract_number;

Because the view exposes no row-level security of its own, callers should apply operating-unit or vendor filters appropriate to the reporting context.