Search Results okl_cs_billingtrx_uv




Overview
Explore in AI Chat

Overview

OKL_CS_BILLINGTRX_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Lease and Finance Management — and is documented in the ETRM reference as displaying transaction-level billing information. In practice, the view consolidates invoice and payment-schedule detail for leased assets so that billing transactions can be reported without navigating the full underlying contract, asset, and receivables model.

The "UV" suffix indicates a user view intended for reporting, inquiry, and downstream integration rather than for transactional processing. Because the view is defined over sources that include AutoInvoice-related payment schedules and OKL billing detail structures, rows returned reflect the state of billing at the time the query executes. The view is marked VALID, confirming that its dependencies resolve correctly in the documented environment. Its role is largely analytical: it exposes lease billing history at the transaction level, joining lease contracts to fixed assets and to Oracle Receivables payment schedules.

Underlying Base Objects

The documented view text defines OKL_CS_BILLINGTRX_UV over a union of billing detail sources. The principal reporting source is OKL_CS_BPD_INV_DTL_V, itself a view, from which invoice number, invoice amount, line amount, tax, amounts applied and remaining, payment terms, invoice type, and the AR invoice identifiers are drawn. This source is joined to AR_PAYMENT_SCHEDULES_ALL (a synonym to the Receivables table) on AR_INVOICE_ID = CUSTOMER_TRX_ID, supplying exchange rate type, exchange rate, exchange date, and transaction date.

Contract structure comes from OKC_K_ITEMS, OKC_K_LINES_B, OKC_LINE_STYLES_B, and OKC_K_LINES_TL, restricted to lines whose line style code is 'FIXED_ASSET'. Asset identification is resolved through FA_ADDITIONS_B, linked via JTOT_OBJECT1_CODE = 'OKX_ASSET', while OKL_K_HEADERS supplies the contract header and is constrained to exclude deals of type 'LOAN'. Transaction type names are resolved from OKL_STRM_TYPE_TL with LANGUAGE = USERENV('LANG'). The documented base object list also references the packages OKL_BILLING_UTIL_PVT, OKL_CS_LC_CONTRACT_PVT, and FND_GLOBAL, indicating that the view's dependency chain includes PL/SQL logic as well as tables.

Key Columns

Common Use Cases and Queries

Typical usage includes reconciliation of lease billing to Receivables, reporting outstanding and credited balances by contract or asset, and analysis of tax and exchange rate treatment on billed transactions. Because the view excludes loan-type deals and restricts to fixed-asset lines, it is well suited to equipment lease reporting.

Sample query — outstanding balances by contract:

  • SELECT contract_number, invoice_number, transaction_type, currency_code, amount_remaining, due_date FROM okl_cs_billingtrx_uv WHERE amount_remaining > 0 ORDER BY due_date;

Sample query — billing by asset:

  • SELECT asset_number, contract_number, SUM(invoice_amount) billed, SUM(amount_remaining) outstanding FROM okl_cs_billingtrx_uv GROUP BY asset_number, contract_number;

Sample query — tax and credits for a period:

  • SELECT invoice_number, tax_original, amount_credited, ar_exchange_rate FROM okl_cs_billingtrx_uv WHERE invoice_date BETWEEN :from_date AND :to_date;

Queries should be scoped by contract, customer, or date to limit the cost of the union and its underlying joins.