Results for “voucher_number”

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

Overview

The view OKL_BPD_AP_DISB_DTL_LN_UV (owner: APPS) belongs to the Oracle Leasing and Finance Management (OKL) product family and is documented as AP Disbursements Details. It is a reporting and inquiry view that joins Oracle Payables invoice data (AP_INVOICES_ALL) to the consolidated Accounts Payable invoice records maintained by OKL (OKL_CNSLD_AP_INVS_ALL), enriched with lease contract, stream, and investor agreement context. Its purpose is to present a single, business-user-friendly row per AP disbursement detail line, exposing both the internal invoice identifier and the user-facing voucher information.

The name suffix _UV indicates a user-facing view (as opposed to an internal or _V view), and its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; every query executes the underlying join logic at runtime. This makes it suitable for ad hoc reporting tools, custom concurrent programs, and integration extracts where disbursement-level details are required without directly navigating the complex OKL stream and transaction structures.

Underlying Base Objects

Per the documented metadata, the view is defined over the following base objects (all resolved through APPS synonyms unless noted):

• AP_INVOICES_ALL — the Payables invoice header table, supplying the internal invoice ID and linking to the OKL consolidated invoice through REFERENCE_KEY1.
• OKL_CNSLD_AP_INVS_ALL — the OKL consolidated AP invoice table, the source of the vendor invoice number, invoice number, currency, and invoice date.
• OKL_TRX_AP_INVOICES_V, OKL_TXL_AP_INV_LNS_V — transaction and transaction-line views that connect OKL transaction records to AP invoices and provide the amount used for the invoice amount.
• OKL_STREAMS_V, OKL_STRM_ELEMENTS_V, OKL_STRM_TYPE_V — stream, stream element, and stream type views that supply stream classification.
• OKC_K_HEADERS_B — used twice, once as the lease contract header (KHR) and once as the investor agreement (IA).
• FND_APPLICATION — restricts results to the OKL application.
• OKL_ACCOUNTING_UTIL (package) — formats the amount using FORMAT_AMOUNT.

The join predicates enforce that the AP invoice belongs to application OKL with PRODUCT_TABLE = 'OKL_CNSLD_AP_INVS_ALL', that the transaction status is 'PROCESSED', and that the consolidated invoice ID matches AP_INVOICES_ALL.REFERENCE_KEY1. This tightly scopes the view to processed OKL-originated disbursements only.

Key Columns

• INVOICE_ID — the AP invoice identifier from AP_INVOICES_ALL; useful for joins back to Payables.
• INVESTOR_AGREEMENT — the contract number of the investor agreement (OKC_K_HEADERS_B alias IA).
• INVOICE_NUMBER — the OKL consolidated invoice number.
• VOUCHER_NUMBER — the vendor invoice number from OKL_CNSLD_AP_INVS_ALL; this is the column users search on when looking up a voucher.
• INVOICE_CURRENCY_CODE — the currency of the consolidated invoice.
• INVOICE_DATE — the date the invoice was created in OKL.
• LEASE_CONTRACT — the lease contract number from the stream header.
• STREAM_TYPE — the descriptive name of the stream type.
• INVOICE_AMOUNT — the formatted transaction line amount, defaulted to zero when null.

Common Use Cases and Queries

The most frequent use case is locating a disbursement by voucher number, which is the vendor invoice number recorded on the OKL consolidated invoice. A typical query is:

SELECT invoice_id, voucher_number, invoice_number, lease_contract, stream_type, invoice_currency_code, invoice_date, invoice_amount FROM apps.okl_bpd_ap_disb_dtl_ln_uv WHERE voucher_number = :p_voucher_number;

Other practical scenarios include reconciling OKL disbursements against Payables invoices by joining INVOICE_ID to AP_INVOICES_ALL.INVOICE_ID, reporting disbursements grouped by investor agreement or lease contract, and exporting processed stream transactions for a given period using INVOICE_DATE. Because the view already restricts to PROCESSED transactions and the OKL application, callers do not need to reproduce that filtering logic. For performance, queries should filter on selective columns such as VOUCHER_NUMBER, INVOICE_ID, or INVOICE_DATE, since the view joins several OKL stream and header views that can be costly to scan in full.