Results for “payment_method_lookup_code”

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

Overview

OKL_BPD_DISB_LOV_UV is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. Its documented purpose is to populate the list of values (LOV) presented on the disbursement screen, allowing users to select a valid contract, vendor, vendor site, and payment term combination during disbursement processing. Because it is a view rather than a base table, it carries no stored data of its own; instead it dynamically joins leasing contract header data, vendor and vendor site information, and payment terms to present a single denormalized result set for the disbursement LOV.

Unlike transactional tables in OKL, this object exists purely to serve a user interface selection list. That role makes it relevant to reporting and integration as well: any custom report, concurrent program, or interface that needs to replicate the disbursement LOV behavior can select from the same view to obtain consistent contract-to-vendor-to-terms relationships without reconstructing the join logic manually.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, OKL_BPD_DISB_LOV_UV is defined over the following referenced objects:

• OKC_K_HEADERS_B (SYNONYM) — the contract header base table supplying contract ID, contract number, and currency.
• OKC_K_PARTY_ROLES_V (VIEW) — the party role view that maps the contract header to its vendor role (RLE_CODE = 'OKL_VENDOR').
• OKX_VENDORS_V (VIEW) — the vendor view supplying the vendor identifier and vendor name (V.ID1, V.NAME).
• PO_VENDOR_SITES_ALL (VIEW) — the vendor sites view supplying the active pay site, including VENDOR_SITE_ID, VENDOR_SITE_CODE, PAY_GROUP_LOOKUP_CODE, PAYMENT_METHOD_LOOKUP_CODE, and the TERMS_ID column.
• OKL_BPD_PAY_TERMS_V (VIEW) — the payment terms view supplying the descriptive TERMS value matched against V_SITE.TERMS_ID = V_TERMS.TERM_ID.
• FND_GLOBAL (PACKAGE) — the standard EBS global context package referenced for session and responsibility context during runtime evaluation.

The joins are driven from OKC_K_HEADERS_B through the OKL_VENDOR party role, then to the vendor and its flagged pay site, and finally to the payment terms view. Because it is a view, no DML is permitted against it, and no indexes exist directly on it; performance depends on the underlying tables and views.

Key Columns

• CONTRACT_ID / CONTRACT_NUMBER — Internal identifier and user-facing number of the leasing contract (from OKC_K_HEADERS_B).
• CURRENCY_CODE — Contract currency, used to contextualize disbursement amounts.
• VENDOR_ID / VENDOR_NAME — Vendor identifier (from OKX_VENDORS_V.ID1) and vendor name.
• VENDOR_SITE_ID / VENDOR_SITE_CODE — The pay site associated with the vendor, restricted to sites where PAY_SITE_FLAG = 'Y'.
• PAY_GROUP_LOOKUP_CODE / PAYMENT_METHOD_LOOKUP_CODE — Payment grouping and payment method codes carried from the vendor site, used to default disbursement payment attributes.
• TERMS_ID — The payment terms identifier from the vendor site, matched to OKL_BPD_PAY_TERMS_V.TERM_ID. This is the column referenced by users searching on "TERMS_ID" and is central to linking the selected vendor site to its terms record.
• TERMS — The descriptive payment terms value returned from the payment terms view.

Common Use Cases and Queries

Typical usage includes validating disbursement selections, auditing which contracts and vendors carry which payment terms, and building custom LOVs or reports that mirror the disbursement screen. A sample query listing contract, vendor, and terms follows:

• SELECT contract_number, vendor_name, vendor_site_code, terms_id, terms FROM apps.okl_bpd_disb_lov_uv WHERE contract_number = :p_contract_number;
• SELECT contract_id, vendor_id, vendor_site_id, terms_id FROM apps.okl_bpd_disb_lov_uv WHERE terms_id = :p_terms_id;
• SELECT DISTINCT terms_id, terms FROM apps.okl_bpd_disb_lov_uv ORDER BY terms; — to enumerate available terms.

Because TERMS_ID originates from PO_VENDOR_SITES_ALL and is joined to OKL_BPD_PAY_TERMS_V, queries filtering on TERMS_ID return only those combinations where the vendor site holds a valid, matching payment terms record, ensuring consistency with the disbursement LOV behavior in Oracle EBS 12.1.1 and 12.2.2.