Search Results pay_site_name




Overview
Explore in AI Chat

Overview

The OKL_PARTY_PAYMENT_DTLS_UV view is a user interface (UI) view owned by the APPS schema within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It is explicitly documented in ETRM as the "User interface view for subsidies party payment details page." The view consolidates disbursement and payment information associated with parties (vendors) participating in a lease or finance contract, presenting supplier, payment site, payment term, payment method, and pay group details in a denormalized, display-ready form. Rather than functioning as a transactional base table, the view serves as a read-oriented presentation layer that joins several disparate EBS entities — supplier master data, vendor sites, payment terms, contract party roles, and lookup codes — into a single flattened result set suitable for forms, OA Framework pages, and reporting queries.

Underlying Base Objects

The view is defined over OKL_PARTY_PAYMENT_DTLS (a synonym) as its driving table, aliased PPYD, which holds the core party payment detail records. Supplier information is sourced from PO_VENDORS (PV) and PO_VENDOR_SITES (VS), joined on VENDOR_ID and, for the site, via an outer join on VENDOR_SITE_ID matching PPYD.PAY_SITE_ID. Contract party role context is obtained from OKC_K_PARTY_ROLES_B (CPLB), a synonym linked through CPLB.ID = PPYD.CPL_ID. Payment terms are resolved from AP_TERMS_TL (APT), outer-joined on TERM_ID and filtered by the session language through FND_GLOBAL / USERENV('LANG'). Payment method and pay group display names are derived from AP_LOOKUP_CODES (APLK) and PO_LOOKUP_CODES (POLK) respectively, both outer-joined by lookup code and type. Address formatting is performed by the ARP_ADDR_LABEL_PKG package through its FORMAT_ADDRESS function, which receives the vendor site address components and returns a formatted address string truncated to 80 characters.

Key Columns

Common Use Cases and Queries

Because the view resolves supplier, site, terms, method, and pay group descriptions in a single SELECT, it is typically used to populate the party payment details page and to support reporting on subsidy disbursements. A frequent query retrieves all payment details for a given contract and payment site:

SELECT vendor_number, vendor_name, pay_site_id, pay_site_name, payment_term_name, payment_method_name, pay_group_name FROM apps.okl_party_payment_dtls_uv WHERE chr_id = :p_chr_id AND pay_site_id = :p_pay_site_id;

Because PAY_SITE_ID is outer-joined to PO_VENDOR_SITES, records with no designated site still return, with PAY_SITE_NAME and PAY_SITE_DESCR null; queries should therefore handle null site values in reporting logic. Language-dependent columns (payment term names) resolve according to the runtime session language, so consistent NLS configuration is important for reproducible output. The view is read-only and should not be used for DML; updates belong to OKL_PARTY_PAYMENT_DTLS and its controlling forms.