Results for “payment_method_name”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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
- ID and OBJECT_VERSION_NUMBER — primary identifier and optimistic locking version of the underlying detail record.
- DNZ_CHR_ID, CHR_ID, CLE_ID, CPL_ID — contract, role, line/entity, and party role linkage identifiers supplied by the CPLB join.
- VENDOR_ID, VENDOR_NAME, VENDOR_NUMBER (SEGMENT1) — supplier identity and number from PO_VENDORS.
- PAY_SITE_ID — the primary key of the vendor payment site, referenced from OKL_PARTY_PAYMENT_DTLS.PAY_SITE_ID, joined to PO_VENDOR_SITES.VENDOR_SITE_ID. This is the column most commonly filtered by users.
- PAY_SITE_NAME (VENDOR_SITE_CODE) and PAY_SITE_DESCR — the site code and the formatted address produced by ARP_ADDR_LABEL_PKG.
- PAYMENT_TERM_ID, PAYMENT_TERM_NAME, PAYMENT_TERM_DESCR — payment terms from AP_TERMS_TL.
- PAYMENT_METHOD_CODE, PAYMENT_METHOD_NAME, PAYMENT_METHOD_DESCR — payment method and its decoded display values.
- PAY_GROUP_CODE, PAY_GROUP_NAME, PAY_GROUP_DESCR — pay group identification and decoded lookup descriptions.
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.
-
User interface view for subsidies party payment details page
APPS.OKL_PARTY_PAYMENT_DTLS_UV·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ ARP_ADDR_LABEL_PKG·Explore OKL module →
-
View: PAY_PAYMENT_COSTS_V 12.2.2
APPS.PAY_PAYMENT_COSTS_V·↳ GL_CODE_COMBINATIONS·↳ HR_CHKFMT·↳ HR_GENERAL·Explore PAY module →
-
View: PAY_PAYMENT_COSTS_V 12.1.1
APPS.PAY_PAYMENT_COSTS_V·↳ GL_CODE_COMBINATIONS·↳ HR_CHKFMT·↳ HR_GENERAL·Explore PAY module →
-
APPS.ARBPA_CUSTOMER_TRX_HEADER·↳ AR_RECEIPT_METHODS·↳ FND_GLOBAL·↳ FND_TERRITORIES_TL·Explore FND module →
-
View: PAY_KR_ASG_PAYMENTS_V 12.1.1
APPS.PAY_KR_ASG_PAYMENTS_V·↳ FND_GLOBAL·↳ HR_API·↳ HR_LOOKUPS·Explore PAY module →
-
View: PAY_KR_ASG_PAYMENTS_V 12.2.2
APPS.PAY_KR_ASG_PAYMENTS_V·↳ HR_API·↳ HR_LOOKUPS·↳ PAY_ASSIGNMENT_ACTIONS·Explore PAY module →
-
User interface view for vemdor (payment) details for a lessee(TCA party)
APPS.OKL_LESSEE_AS_VENDORS_UV·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ ARP_ADDR_LABEL_PKG·Explore OKL module →
-
View: OKL_OR_SUBSIDY_REFUNDS 12.2.2
APPS.OKL_OR_SUBSIDY_REFUNDS·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ FND_GLOBAL·Explore OKL module →
-
User interface view for subsidies party payment details page
APPS.OKL_PARTY_PAYMENT_DTLS_UV·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ ARP_ADDR_LABEL_PKG·Explore OKL module →
-
IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i
-
User interface view for funding request header.
APPS.OKL_FUND_REQ_HEADERS_UV·↳ AP_TERMS_V·↳ FND_CURRENCIES_TL·↳ FND_GLOBAL·Explore OKL module →
-
Customer Interface table for Payment Methods
-
User interface view to indicate passthrough vendors on a Passthrough Fee or Service
APPS.OKL_LA_PASSTHRU_VENDOR_UV·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ FND_GLOBAL·Explore OKL module →
-
View: OKL_OR_SUBSIDY_REFUNDS 12.1.1
APPS.OKL_OR_SUBSIDY_REFUNDS·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ FND_GLOBAL·Explore OKL module →
-
User interface view for vemdor (payment) details for a lessee(TCA party)
APPS.OKL_LESSEE_AS_VENDORS_UV·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ ARP_ADDR_LABEL_PKG·Explore OKL module →
-
View: IBY_EXT_FD_PMT_1_0_V 12.1.1
APPS.IBY_EXT_FD_PMT_1_0_V·↳ FND_GLOBAL·↳ IBY_EXT_FD_PMT_1_0_VT·↳ IBY_FD_EXTRACT_GEN_PVT·Explore IBY module →
-
View: ARFV_CASH_RECEIPTS 12.1.1
This shows information about payments remitted by the customer as payment for goods or services.
APPS.ARFV_CASH_RECEIPTS·↳ AR_CASH_RECEIPTS·↳ AR_RECEIPT_METHODS·↳ CE_BANK_ACCOUNTS·Explore AR module →
-
User interface view for funding request header.
APPS.OKL_FUND_REQ_HEADERS_UV·↳ AP_TERMS_V·↳ FND_CURRENCIES_TL·↳ FND_GLOBAL·Explore OKL module →
-
Customer Interface table for Payment Methods
-
User interface view to indicate passthrough vendors on a Passthrough Fee or Service
APPS.OKL_LA_PASSTHRU_VENDOR_UV·↳ AP_LOOKUP_CODES·↳ AP_TERMS_TL·↳ FND_GLOBAL·Explore OKL module →
-
View: IBY_EXT_FD_PMT_1_0_V 12.2.2
APPS.IBY_EXT_FD_PMT_1_0_V·↳ FND_GLOBAL·↳ IBY_EXT_FD_PMT_1_0_VT·↳ IBY_FD_EXTRACT_GEN_PVT·Explore IBY module →
-
APPS.ARBPA_CUSTOMER_TRX_HEADER·↳ AP_AMOUNT_UTILITIES_PKG·↳ AR_BPA_UTILS_PKG·↳ AR_INVOICE_COUNT_TERMS_V·Explore FND module →
-
View: IBY_PAYMENT_METHODS_VL 12.1.1
APPS.IBY_PAYMENT_METHODS_VL·↳ IBY_PAYMENT_METHODS_B·↳ IBY_PAYMENT_METHODS_TL·Explore IBY module →
-
View: IBY_PAYMENT_METHODS_VL 12.2.2
APPS.IBY_PAYMENT_METHODS_VL·↳ IBY_PAYMENT_METHODS_B·↳ IBY_PAYMENT_METHODS_TL·Explore IBY module →
-
View: ARFV_CASH_RECEIPTS 12.2.2
This shows information about payments remitted by the customer as payment for goods or services.
APPS.ARFV_CASH_RECEIPTS·↳ AR_CASH_RECEIPTS·↳ AR_RECEIPT_METHODS·↳ CE_BANK_ACCOUNTS·Explore AR module →