Search Results okx_vendor




Overview
Explore in AI Chat

Overview

OKL_LEASE_VENDORS_UV is an Oracle Applications (APPS) reporting view that exposes the set of vendor parties associated with Oracle Lease Management (OKL) contract records. It sits at the intersection of Oracle Contracts (OKC) party-role data and the Oracle Payables supplier master, returning a flattened list of vendor identifiers, names, and descriptions linked to a lease contract header identifier (DNZ_CHR_ID).

The view is intended for query-only use, typically by lease management reports, vendor lookup forms, and integration interfaces that need to resolve which supplier records participate on a given lease. Because it resolves the supplier name and number from PO_VENDORS, consumers do not need to join to the supplier tables themselves. In Oracle EBS 12.1.1 and 12.2.2 the object is deployed in the APPS schema and remains a read-only, non-updatable view over the underlying contract party-role base table.

Underlying Base Objects

The documented base objects referenced by the view are:

  • OKC_K_PARTY_ROLES_B (SYNONYM) — the Contracts core table that stores the parties and roles attached to a contract or contract line. In this view it is aliased CHPB. The role of interest is RLE_CODE = 'OKL_VENDOR'.
  • PO_VENDORS (VIEW) — the supplier master, aliased POVV, supplying VENDOR_ID, VENDOR_NAME, and SEGMENT1. Note that PO_VENDORS is itself a view over the purchasing supplier base tables (PO_VENDOR_SITES_ALL / AP_SUPPLIERS lineage), so okx_vendor queries traverse two layers of views.

The join is driven by OKC_K_PARTY_ROLES_B.OBJECT1_ID1 = PO_VENDORS.VENDOR_ID, constrained so that OBJECT1_ID2 = '#', JTOT_OBJECT1_CODE = 'OKX_VENDOR', and CLE_ID IS NULL. The final predicate CHR_ID = DNZ_CHR_ID ties each row to a specific contract header version.

Key Columns

  • ID1 — the supplier VENDOR_ID from PO_VENDORS, serving as the primary vendor key for downstream lookups.
  • ID2 — the OKC_K_PARTY_ROLES_B.ID of the party-role row, uniquely identifying the contract-to-vendor association.
  • NAME — the vendor name (POVV.VENDOR_NAME) displayed to users.
  • DESCRIPTION — the vendor number (POVV.SEGMENT1), the human-readable supplier code used for cross-reference.
  • DNZ_CHR_ID — the contract header identifier (CHR_ID) to which the vendor relationship belongs, the primary filter column for contract-scoped queries.

Common Use Cases and Queries

The dominant use case is resolving the vendors attached to a particular lease contract, or joining vendor identity onto other lease reporting. Because the entity is the "okx_vendor" contract party, most queries filter on DNZ_CHR_ID.

  • List all vendors on a lease: SELECT id1, name, description FROM apps.okl_lease_vendors_uv WHERE dnz_chr_id = :p_chr_id;
  • Find contracts for a given supplier: SELECT dnz_chr_id, name FROM apps.okl_lease_vendors_uv WHERE id1 = :p_vendor_id;
  • Vendor-role population audit grouping by vendor to detect over-use.

Consumers should treat all columns as read-only and note that VENDOR_ID maps to the underlying AP supplier, so any restricted-supplier or site-level detail must be obtained from the supplier master itself rather than from this view.