Search Results payee_address

Overview

OKL_CS_DISBURSEMENTS_DTL_UV is a reporting view within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It presents disbursement and payment detail associated with lease and finance contracts, consolidating data from Oracle Lease Management transaction tables and Oracle Payables (AP) tables into a single denormalized result set. The view exposes the linkage between a contract, its AP invoices, and the checks or payments issued against those invoices.

Its principal role is to support reporting and integration scenarios in which users need to reconcile lease contract disbursements against actual payment instruments. In both EBS 12.1.1 and 12.2.2, this view is defined as a database object; the ETRM metadata notes that it is "Not implemented in this database" in the source system context, meaning the object is documented but not necessarily instantiated in every environment. The "UV" suffix conventionally denotes a user or reporting view.

Underlying Base Objects

The view is defined over a join of OKL transaction tables and standard Oracle Payables and Purchasing tables. The documented base objects in the FROM clause are:

• OKL_TRX_AP_INVOICES_B (TAP) — the AP invoice header information for lease transactions.
• OKL_TXL_AP_INV_LNS_B (TPL) — the AP invoice line records for lease transactions.
• OKL_STRM_TYPE_TL (STYT) — the transaction stream type description used to populate TRANSACTION_TYPE.
• OKC_K_HEADERS_B (CHR) — the contract header, providing CONTRACT_NUMBER.
• AP_INVOICES_ALL (API) — standard Payables invoice header.
• PO_VENDORS (POV) — supplier master providing vendor name and number.
• AP_INVOICE_PAYMENTS_ALL (APP) — the payment-to-invoice association.
• AP_CHECKS_ALL (APC) — the payment instrument (check) details.
• AP_LOOKUP_CODES (APL) — lookup used to resolve the payment method description.

The join keys link OKL transaction lines to AP invoice headers by organization and vendor site, to Payables invoices by invoice number and vendor, then outward to payments and checks. The AP_LOOKUP_CODES join is outer (+) on LOOKUP_TYPE = 'PAYMENT METHOD'.

Key Columns

• CONTRACT_NUMBER — the lease or finance contract identifier from OKC_K_HEADERS_B.
• TRANSACTION_TYPE — the stream/transaction type name from OKL_STRM_TYPE_TL.
• VENDOR_INVOICE_NUMBER and INVOICE_NUMBER — supplier-facing and internal invoice references.
• PAYMENT_METHOD — decoded description of the payment method lookup.
• CHECK_DATE, CHECK_AMOUNT, CHECK_NUMBER, CHECK_CURRENCY — payment instrument attributes from AP_CHECKS_ALL.
• PAYEE_NAME (CHECKRUN_NAME) and PAYEE_ADDRESS (ADDRESS_LINE1) — payee details from the check record.
• INVOICE_STATUS — approval status of the Payables invoice.
• PAYMENT_ID — AP_INVOICE_PAYMENT_ID, linking invoice to payment.
• VENDOR_NAME and VENDOR_NUMBER — supplier identification from PO_VENDORS.
• DISBURSEMENT_AMOUNT and DISBURSEMENT_CURRENCY — the invoice amount and its currency; the currency column surfaces the user's check_currency search term, represented here as CHECK_CURRENCY (APC.CURRENCY_CODE).
• TAP_ID and KHR_ID — internal identifiers for the OKL AP invoice record and the contract header.

Common Use Cases and Queries

Typical uses include disbursement reconciliation, audit of lease payments by vendor, and currency analysis of checks issued against lease contracts.

• Disbursements by contract: retrieve all payments tied to a given contract number.
• Currency reconciliation: filter on CHECK_CURRENCY versus DISBURSEMENT_CURRENCY to identify mismatches between contract and payment currencies.
• Vendor payment audit: group disbursements by VENDOR_NAME and PAYMENT_METHOD.

Sample query:

SELECT CONTRACT_NUMBER, VENDOR_NAME, CHECK_NUMBER, CHECK_DATE, CHECK_AMOUNT, CHECK_CURRENCY, DISBURSEMENT_AMOUNT FROM OKL_CS_DISBURSEMENTS_DTL_UV WHERE CONTRACT_NUMBER = :contract_number;

Additional filters on CHECK_CURRENCY or TRANSACTION_TYPE support currency-specific and type-specific reporting requirements.