Search Results txn_line_type




Overview
Explore in AI Chat

Overview

OKL_BPD_AR_INV_LN_DTLS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. Its documented purpose is to support the Oracle Lease Management "Search Invoice" page, presenting invoice line detail that combines lease contract structure, consolidated receivables streams, and Oracle Receivables payment schedules into a single denormalized result set. The view acts as the integration point between the leasing data model (contract, stream, consolidated AR line) and the Receivables data model (transaction, payment schedule, application), allowing the billing and invoice inquiry UI to display receivables balances and applied amounts without requiring the calling form to join across both schemas directly.

Because it is a view rather than a table, it holds no data of its own and reflects the current state of the underlying tables at query time. In 12.1.1 and 12.2.2 it remains VALID and is referenced by the OKL billing/AR invoice pages and by any custom report or interface that needs lease-level receivables detail.

Underlying Base Objects

The view is defined over a mixture of OKL leasing tables and Receivables tables, joined primarily through RECEIVABLES_INVOICE_ID / CUSTOMER_TRX_ID linkage:

Key Columns

Common Use Cases and Queries

Typical uses include invoice search page back-ends, lease receivables aging reports, and reconciliation extracts feeding downstream systems. A representative query retrieves invoice line balances for a contract:

  • Filter by contract: SELECT CONTRACT_NUMBER, CONSOLIDATED_LINE_NUMBER, RECEIVABLES_INVOICE_NUMBER, AMOUNT_DUE_ORIGINAL, AMOUNT_PAID, BALANCE FROM OKL_BPD_AR_INV_LN_DTLS_V WHERE CONTRACT_NUMBER = :p_contract.
  • Open-item analysis: SELECT CUSTOMER_TRX_ID, SUM(BALANCE) FROM OKL_BPD_AR_INV_LN_DTLS_V GROUP BY CUSTOMER_TRX_ID HAVING SUM(BALANCE) > 0.
  • Cash versus credit memo split: SELECT STREAM_TYPE, STREAM_PURPOSE_MEANING, AMOUNT_APPLIED, AMOUNT_CREDITED FROM OKL_BPD_AR_INV_LN_DTLS_V WHERE ORG_ID = :p_org_id.

Because of the correlated subqueries and multi-table join, queries should be constrained by ORG_ID, CONTRACT_NUMBER, or CUSTOMER_TRX_ID to avoid full-scan performance degradation on large lease portfolios.