Results for “kle_id”

50+ results




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

Overview

OKL_IN_RAMOUNT_BC_V 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 is delivered as part of the OKL product family, Oracle Lease and Finance Management, and carries a VALID status in the data dictionary. The view answers a single, recurring business question: how much has actually been received against each lease-related invoice line. It derives this figure by comparing the original amount due on an Accounts Receivable transaction line with the amount still outstanding, effectively treating the reduction in the outstanding balance as cash applied.

Because the view pre-aggregates results down to the lease contract level, it is well suited to reporting, reconciliation, and integration use cases where a single "amount received" value is required per contract rather than per transaction line. It is a consolidation view rather than a transactional capture view; no data is written to it, and its output reflects the current state of the underlying AR and OKL tables at query time.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS-resident synonyms: OKL_TXD_AR_LN_DTLS_B, OKL_TXL_AR_INV_LNS_B, and RA_CUSTOMER_TRX_LINES_ALL. The OKL tables are the lease-specific transactional detail and line headers, while RA_CUSTOMER_TRX_LINES_ALL is the standard Receivables transaction line table.

The join path is the defining characteristic of the view. It links OKL_TXD_AR_LN_DTLS_B to RA_CUSTOMER_TRX_LINES_ALL through a denormalized relationship: TLD.ID = RACTRL.INTERFACE_LINE_ATTRIBUTE14. The delivered comment in the view text states the assumption explicitly — attribute 14 is expected to carry the OKL line detail identifier. From there, OKL_TXD_AR_LN_DTLS_B is joined to OKL_TXL_AR_INV_LNS_B on TLD.TIL_ID_DETAILS = TIL.ID, which resolves each AR line back to its lease contract through TIL.KLE_ID. The result set is grouped by KLE_ID, so one row is returned per lease contract, not per invoice line.

Key Columns

  • AMOUNT_RECEIVED — The aggregate amount received, computed as SUM(RACTRL.AMOUNT_DUE_ORIGINAL - RACTRL.AMOUNT_DUE_REMAINING). This represents the portion of the original amount due that has been extinguished by payment application. Because it is a difference of two AR-maintained columns, it inherits the currency of the underlying transaction line; the view performs no currency conversion and applies no exchange rate logic.
  • KLE_ID — The lease contract identifier from OKL_TXL_AR_INV_LNS_B. This is the grouping key and the primary means of joining the view to other lease contract views and tables in the OKL schema. It is the only non-measure column exposed.

The view exposes no contract number, customer, date, or currency column. Any reporting that requires those attributes must join outward on KLE_ID.

Common Use Cases and Queries

The most common use is a straightforward contract-level receipt lookup, typically joined to a lease contract view to obtain descriptive context:

  • Receipt summary per lease — selecting KLE_ID and AMOUNT_RECEIVED for a list of contracts to display cash collected against billed amounts.
  • Reconciliation of AR applications to lease lines — comparing AMOUNT_RECEIVED against billed amounts to identify under- or over-collected contracts.
  • Integration extracts — sourcing a single amount per lease contract into downstream reporting or a data warehouse.

A representative query is:

SELECT kle_id, amount_received FROM apps.okl_in_ramount_bc_v WHERE kle_id = :p_kle_id;

Because the view aggregates at the contract level, adding filter predicates on KLE_ID is the most efficient access path. Note that the attribute-14 assumption documented in the view text means correctness depends on the AR interface configuration reliably populating INTERFACE_LINE_ATTRIBUTE14 with the OKL line detail ID; if that linkage is absent for a given transaction, the corresponding receipts will not appear in AMOUNT_RECEIVED.