Search Results payment_method_descr




Overview
Explore in AI Chat

Overview

The OKL_LESSEE_AS_VENDORS_UV view is a user interface view within the Oracle Lease and Finance Management (OKL) product module. It presents vendor (payment) details for a lessee, where the lessee is represented as a TCA party. The view is owned by the APPS schema and has a VALID status in both Oracle EBS 12.1.1 and 12.2.2.

The view serves as a consolidated reporting and integration layer that surfaces payment-related attributes for lessees who are treated as vendors in the payables domain. It joins payment detail records from the lease management data model with vendor master information, vendor site details, payment terms, and role definitions. Because the join to OKC_K_PARTY_ROLES_B is restricted to the role code LESSEE, the view returns payment profiles only for parties acting in a lessee capacity.

The object is referenced by the user interface to render vendor payment fields, and it is equally suitable for custom reports, data extracts, and integration interfaces that require lessee payment information. The column of particular interest to users searching on payment_term_descr is PAYMENT_TERM_DESCR, which exposes the descriptive text of the payment term associated with the lessee's vendor record.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKL_PARTY_PAYMENT_DTLS (synonym) — the driving table, aliased PPYD, holding party payment detail records keyed by CPL_ID.
  • OKC_K_PARTY_ROLES_B (synonym) — aliased KPR, supplying the party role and the DNZ_CHR_ID contract identifier, filtered to RLE_CODE = 'LESSEE'.
  • PO_VENDORS (view) — aliased PV, providing vendor name and SEGMENT1 (vendor number).
  • PO_VENDOR_SITES (view) — aliased VS, providing the pay site code, address components, and site description.
  • AP_TERMS_TL (synonym) — aliased APT, providing the translated payment term NAME and DESCRIPTION.
  • AP_LOOKUP_CODES (view) — used in a scalar subquery to resolve PAYMENT METHOD display text.
  • PO_LOOKUP_CODES (view) — used in a scalar subquery to resolve PAY GROUP display text.
  • ARP_ADDR_LABEL_PKG (package) — invoked to format the pay site address into the PAY_SITE_DESCR column.
  • FND_GLOBAL (package) — referenced through USERENV('LANG') to align the payment term translation language.

Join conditions link vendor to vendor site by VENDOR_ID, connect the pay site through an outer join on VENDOR_SITE_ID, and attach payment terms through an outer join on TERM_ID with the language predicate. The lessee constraint is enforced by KPR.ID = PPYD.CPL_ID combined with RLE_CODE = 'LESSEE'.

Key Columns

Common Use Cases and Queries

Typical scenarios include displaying lessee payment profiles in lease management screens, extracting payment terms for downstream payables processing, and validating that lessee vendor records carry the correct payment method and pay group.

To retrieve payment terms for all lessees:

  • SELECT vendor_id, vendor_name, payment_term_name, payment_term_descr FROM okl_lessee_as_vendors_uv;

To locate lessees using a specific payment term description:

  • SELECT cpl_id, vendor_name, pay_site_name, payment_term_descr FROM okl_lessee_as_vendors_uv WHERE payment_term_descr LIKE '%NET%';

To report payment method and pay group by contract:

  • SELECT dnz_chr_id, vendor_name, payment_method_name, pay_group_name FROM okl_lessee_as_vendors_uv ORDER BY dnz_chr_id;

Because PAYMENT_TERM_DESCR originates from AP_TERMS_TL through an outer join, the column may be NULL when no payment term is assigned. Consumers should account for this in report logic and integration mappings.