Search Results okl_bpd_ap_invoice_uv




Overview
Explore in AI Chat

Overview

OKL_BPD_AP_INVOICE_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Lease and Finance Management) product. Its documented purpose is to display Payable Invoice details in the View Transactions Search screen. In functional terms, it presents a unified, denormalized projection of consolidated Oracle Payables invoice data as it relates to lease and finance contracts, exposing supplier invoice header attributes alongside contract-level identifiers such as the contract number, contract header ID, and product ID.

The view plays a reporting role rather than a transactional one. It contains no DML logic and exists to support query-driven screens and integration extracts that need to associate AP invoice records with the originating lease contract and transaction. Because it joins Payables invoice data to OKL transaction invoice structures, it is most relevant to reconciliation, audit, and inquiry scenarios where a user or process must trace a payable invoice back to its lease contract context.

Underlying Base Objects

The view is defined over eight referenced objects, all accessed through APPS synonyms: AP_INVOICES_ALL, AP_INVOICES_PKG, FND_APPLICATION, OKC_K_HEADERS_B, OKL_CNSLD_AP_INVS_ALL, OKL_K_HEADERS, OKL_TRX_AP_INVOICES_B, and OKL_TXL_AP_INV_LNS_B. The core driver is OKL_CNSLD_AP_INVS_ALL (aliased CIN), which links to AP_INVOICES_ALL (INV) through REFERENCE_KEY1. Invoice transaction lines reside in OKL_TXL_AP_INV_LNS_B (TPL), which supplies the KHR_ID and TAP_ID used to reach the contract header (OKC_K_HEADERS_B, OKL_K_HEADERS) and the lease transaction invoice (OKL_TRX_AP_INVOICES_B). FND_APPLICATION constrains rows to the OKL application, and AP_INVOICES_PKG.GET_APPROVAL_STATUS is invoked as a scalar function to derive the transaction status. The view aggregates line amounts via SUM(TPL.AMOUNT) against the KHR_ID and therefore carries a GROUP BY across invoice header, contract, and transaction identifiers.

Key Columns

Common Use Cases and Queries

Typical use cases include contract-to-invoice reconciliation, payable inquiry from the View Transactions screen, and audit tracing of lease transaction invoices. A representative query lists invoices for a given contract:

  • SELECT invoice_num, invoice_date, contract_number, khr_line_amount, invoice_amount, transaction_status FROM apps.okl_bpd_ap_invoice_uv WHERE contract_number = :contract_number;
  • SELECT invoice_num, transaction_status, payment_status_flag, invoice_currency_code FROM apps.okl_bpd_ap_invoice_uv WHERE invoice_id = :invoice_id;
  • Aggregation by contract for reconciliation: SELECT contract_number, SUM(invoice_amount) total_invoiced FROM apps.okl_bpd_ap_invoice_uv GROUP BY contract_number;

Because TRANSACTION_STATUS is computed at query time through AP_INVOICES_PKG, queries returning large result sets may incur additional processing overhead. Filtering by contract, invoice, or organization is recommended to limit the rows fetched.