Search Results ar_exchange_date




Overview

OKL_BILLING_TRX_ALL_UV is an APPS-owned database view within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It presents transaction-level billing information for leased and financed contracts, consolidating data drawn from Oracle Receivables and Oracle Assets with the OKL contract consolidation tables. The view is a reporting and integration object: it exposes one row per billing transaction stream line, allowing downstream reports, extract programs, and inquiry screens to retrieve invoiced amounts, applied amounts, remaining balances, tax, and credited amounts without navigating the underlying normalized consolidation schema directly. In the context of EBS 12.1.1 and 12.2.2, the view resides in the same schema and is referenced through APPS synonyms, so it behaves consistently across both releases; the 12.2.2 metadata lists the same base objects as 12.1.1, confirming structural continuity.

Underlying Base Objects

The view is defined as a UNION of two queries. The documented base objects include AR_PAYMENT_SCHEDULES_ALL, which supplies the Receivables transaction number, dates, currency, exchange rate, amount due original, amount applied, amount remaining, tax, and the AMOUNT_CREDITED column that is central to queries searching for credited amounts. FA_ADDITIONS_B provides asset number and asset identifier for the financed asset. OKC_K_HEADERS_ALL_B, OKC_K_LINES_B, OKC_K_ITEMS, OKC_K_LINES_TL, and OKC_LINE_STYLES_B supply the contract header, line, line style, and item context, with the line style code restricted to FIXED_ASSET and the item object code to OKX_ASSET. OKL_CNSLD_AR_HDRS_ALL_B, OKL_CNSLD_AR_LINES_B, and OKL_CNSLD_AR_STRMS_B hold the consolidated invoice header, line, and stream/billing schedule data. OKL_STRM_TYPE_TL supplies the translated transaction type name. OKL_K_HEADERS and OKL_CS_LC_CONTRACT_PVT, a package, complete the documented dependency set, the latter being used in the second leg of the UNION for contra or offsetting stream records.

Key Columns

Common Use Cases and Queries

Typical scenarios include billing reconciliation, credit memo analysis, contract-to-invoice drill-down, and aging extracts. Because AMOUNT_CREDITED is exposed at transaction level, a frequent query isolates transactions with credits applied:

  • SELECT contract_number, ar_invoice_number, transaction_amount, amount_applied, amount_credited FROM okl_billing_trx_all_uv WHERE amount_credited > 0;
  • SELECT contract_number, transaction_type, currency_code, amount_remaining FROM okl_billing_trx_all_uv WHERE amount_remaining > 0 AND due_date < SYSDATE;
  • SELECT asset_number, SUM(transaction_amount), SUM(amount_credited) FROM okl_billing_trx_all_uv GROUP BY asset_number;

These queries support operational review of billed, applied, and credited balances alongside contract and asset context across both EBS 12.1.1 and 12.2.2.