Results for “okl_bpd_ap_inv_lines_uv”

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

Overview

OKL_BPD_AP_INV_LINES_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. The view exposes payable invoice line details for display within the View Transactions Details screen, a standard OKL inquiry page used to audit leasing-related transactions. Functionally it joins Oracle Payables invoice headers and lines to their originating leasing contract, stream type, and transaction context, producing a denormalized result set suitable for both the concurrent user interface and downstream reporting or integration.

The "_UV" suffix follows the Oracle EBS naming convention for user views intended for presentation-layer consumption. As a view rather than a table, it stores no data of its own and always reflects the committed state of its underlying base objects. Because the view references standard Payables tables, it is frequently the target of ad hoc queries when users need to reconcile leasing invoices against their contract, vendor, or tax lines. The presence of the ZX_LINES synonym among its base objects makes it relevant to tax reporting as well as to invoice line inquiries.

Underlying Base Objects

The view is defined over a set of documented base objects in the APPS schema, combining Payables, OKL leasing, contract, and tax data:

• AP_INVOICES_ALL – Payables invoice headers, supplying invoice number, invoice ID, vendor, vendor site, and set of books.
• AP_INVOICE_LINES_ALL – Payables invoice distributions/lines, providing line number, description, amount, reference key, and application context.
• ZX_LINES – E-Business Tax lines, joined by application ID, transaction ID, transaction line ID, and entity code AP_INVOICES, with cancelled lines excluded.
• OKL_TRX_AP_INVS_ALL_B – Links a leasing transaction to its AP invoice, vendor, and invoice vendor site.
• OKL_TXL_AP_INV_LNS_B – Leasing-side invoice line table joined through the reference key, providing the KHR_ID (contract header) and stream type link.
• OKL_CNSLD_AP_INVS_ALL – Consolidated AP invoice information for leasing.
• OKC_K_HEADERS_B – Contract header table supplying the contract number.
• OKL_STRM_TYPE_V – Stream type view exposing stream type purpose and name.
• FND_APPLICATION – Application registry, restricted to short name OKL.
• OKL_ACCOUNTING_UTIL – Accounting utility package referenced by the view logic.

Because these are synonyms to the underlying transactional tables, data currency is immediate; no caching or materialization is involved.

Key Columns

• INVOICE_NUM / INVOICE_ID – Payables invoice identification, used to link to AP_INVOICES_ALL and to the leasing transaction.
• LINE_NUMBER / DESCRIPTION – Payables invoice line identity and narrative.
• AMOUNT – Line amount plus the summed non-cancelled ZX tax amount, producing a tax-inclusive line total where tax lines exist.
• SET_OF_BOOKS_ID – Ledger context for the invoice, critical to multi-org and multi-ledger reporting.
• STREAM_TYPE_PURPOSE / NAME – Stream type attributes from OKL_STRM_TYPE_V, indicating the leasing stream category.
• KHR_ID / CONTRACT_NUMBER – Leasing contract identification and user-visible contract number from OKC_K_HEADERS_B.

Note that the second union branch exposes the same columns but differs in the ordering of AMOUNT and DESCRIPTION, reflecting slightly different join paths for the two consolidation scenarios.

Common Use Cases and Queries

Typical usages include invoice line drill-downs, contract-to-invoice reconciliation, tax-additive amount verification, and stream type analysis. A representative query follows:

• SELECT invoice_num, line_number, description, amount, contract_number, stream_type_purpose FROM okl_bpd_ap_inv_lines_uv WHERE contract_number = :contract_number;
• SELECT invoice_num, SUM(amount) FROM okl_bpd_ap_inv_lines_uv WHERE set_of_books_id = :sob GROUP BY invoice_num;
• SELECT contract_number, stream_type_purpose, COUNT(*), SUM(amount) FROM okl_bpd_ap_inv_lines_uv GROUP BY contract_number, stream_type_purpose;

Because the view aggregates ZX tax through a correlated subquery, queries returning large invoice volumes should be filtered by invoice, contract, or ledger to avoid full scans of the Payables and Tax lines tables.