Results for “jtot_object1_code”

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

Overview

The OKL_LA_ASSET_PARTIES_UV view is a user interface (UI) database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OKL product family — Leasing and Finance Management — and is documented as VALID within the ETRM reference for releases 12.1.1 and 12.2.2. The view is explicitly described as the "User interface view for asset vendor list of values page – funding," meaning it is designed to populate an Oracle Forms List of Values (LOV) that lets users select an asset vendor when entering funding-related lease data.

In practice, this view is not a reporting construct in the conventional sense; it is a functional dependency of the Leasing and Finance Management application. When a lease or asset funding record requires a vendor reference, the form invokes this view to present eligible vendors. Users searching for "okl_vendor" are typically encountering the underlying role code OKL_VENDOR, which is the filter key that identifies vendor-type parties within the contracts party-role model. This view therefore bridges the generic Oracle Contracts (OKC) party-role infrastructure with the Oracle Purchasing vendor master, exposing only those parties whose role code is OKL_VENDOR. Its role in integration is inseparable from the lease funding setup flow rather than from ad hoc reporting.

Underlying Base Objects

The view is defined over two documented base objects:

• OKC_K_PARTY_ROLES_B (referenced as a synonym) — the Oracle Contracts party-roles base table that stores the association between a contract/lease entity and the parties playing specific roles.
• PO_VENDORS (a view) — the Oracle Purchasing supplier master view that supplies the vendor name and vendor identifier.

The join is an inner join on PV.VENDOR_ID = CHP.OBJECT1_ID1. Two further predicates constrain the result set: CHP.RLE_CODE = 'OKL_VENDOR' restricts rows to vendor-role parties, and CHP.OBJECT1_ID2 = '#' restricts the party object to a specific qualifier pattern. Because OKC_K_PARTY_ROLES_B is a _B (base) table, the view exposes the base-language rows without translation joins, which is acceptable for an LOV where only identification data is required.

Key Columns

• ID — The party-role row identifier (CHP.ID); the primary handle for the underlying contract party record.
• DNZ_CHR_ID — The contract/lease header identifier (CHP.DNZ_CHR_ID) linking the party to its owning document.
• CLE_ID — The contract line/entity identifier to which the party role is attached.
• OBJECT1_ID1 — The first object identifier, which holds the vendor ID used to join to PO_VENDORS.
• OBJECT1_ID2 — The second object identifier, filtered to '#' in this view.
• JTOT_OBJECT1_CODE — The JTOT object-type code describing the object referenced in OBJECT1_ID1.
• VENDOR_NAME — The supplier name sourced from PO_VENDORS; the value displayed in the LOV.
• VENDOR_ID — The supplier identifier sourced from PO_VENDORS; the value returned to the form.

Common Use Cases and Queries

The view is most commonly referenced in diagnostic and extension work: confirming that a vendor is correctly attached to a lease as an OKL_VENDOR party, or replicating LOV behaviour in a custom form or concurrent program. Typical queries include:

• Listing all asset vendors visible to the funding LOV: SELECT vendor_id, vendor_name FROM apps.okl_la_asset_parties_uv;
• Finding vendors attached to a specific lease header: adding WHERE dnz_chr_id = :lease_id.
• Vendor lookup by name: ... WHERE UPPER(vendor_name) LIKE UPPER('%'||:name||'%');
• Auditing party-role coverage: joining cle_id back to OKC_K_PARTY_ROLES_B to inspect additional role assignments.

Because the view filters to a single role code and object qualifier, custom code should extend OKC_K_PARTY_ROLES_B directly if other role codes are required, rather than modifying or relying on this shipped LOV view.