Results for “okl_bpd_ar_lines_v”

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

Overview

The OKL_BPD_AR_LINES_V view is a reporting and integration object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, owned by the APPS schema and registered as a VALID database view. It belongs to the OKL product family, Oracle Lease and Finance Management, and is documented as the "View for Operations, Transactions Details page for contract." In practical terms, it exposes the Accounts Receivable invoice line details associated with a lease or finance contract so that the Transactions Details page and related reporting components can present contract billing activity in a consolidated, user-facing form.

The view is particularly relevant to users and developers searching on the term "line_amount." Rather than storing a static monetary value, the LINE_AMOUNT column is computed at runtime through a call to OKL_BILLING_UTIL_PVT.INVOICE_LINE_AMOUNT_ORIG, which derives the originating invoice line amount from the customer transaction and line identifiers. This design reflects the leasing model, where the billed amount must be resolved dynamically against contract, stream, and billing rules rather than read directly from a stored column.

Underlying Base Objects

The view is defined over four documented base objects. RA_CUSTOMER_TRX_LINES_ALL supplies the core Accounts Receivable transaction line information, including the line identifier, transaction identifier, line number, description, and the descriptive flexfield attribute columns exploited for contract and stream context. OKL_TXD_AR_LN_DTLS_B provides the lease-specific transaction detail row that links the AR line to the contract structure through its KHR_ID and ID relationships. OKL_STRM_TYPE_B supplies stream type and stream type purpose attributes. OKL_BILLING_UTIL_PVT is the billing utility package that performs the amount derivation logic.

The join path is significant. The view text joins OKL_TXD_AR_LN_DTLS_B to OKL_STRM_TYPE_B on STY_ID equal to STRM.ID, and joins that detail row to RA_CUSTOMER_TRX_LINES_ALL on the assumption that the transaction line detail identifier is carried on INTERFACE_LINE_ATTRIBUTE14. Contract number and stream type are drawn from INTERFACE_LINE_ATTRIBUTE6 and INTERFACE_LINE_ATTRIBUTE9 respectively, illustrating heavy reliance on the AR interface descriptive flexfield columns as the bridge between receivables and leasing data.

Key Columns

• ID — the CUSTOMER_TRX_LINE_ID from RA_CUSTOMER_TRX_LINES_ALL, uniquely identifying the AR invoice line.
• CUSTOMER_TRX_ID — the parent AR transaction identifier, used to group lines under a single invoice.
• CONTRACT_NUMBER — sourced from INTERFACE_LINE_ATTRIBUTE6, the lease or finance contract identifier.
• LINE_NUMBER — the AR line sequence number for ordering within the transaction.
• DESCRIPTION — the line description as recorded on the receivable transaction line.
• STREAM_TYPE — from INTERFACE_LINE_ATTRIBUTE9, indicating the billing stream classification.
• STREAM_TYPE_PURPOSE — the purpose attribute of the associated stream type.
• LINE_AMOUNT — the originating invoice line amount, computed by OKL_BILLING_UTIL_PVT.INVOICE_LINE_AMOUNT_ORIG using the transaction and line identifiers.
• KHR_ID — the lease contract header identifier from OKL_TXD_AR_LN_DTLS_B, tying the line back to the contract.

Common Use Cases and Queries

Typical usage includes reconciling contract billing streams to AR invoice lines, embedding the view in the Operations Transactions Details page, and feeding custom reports that analyze billed versus expected amounts. A common starting query retrieves all lines for a given transaction:

• SELECT contract_number, line_number, description, stream_type, stream_type_purpose, line_amount FROM apps.okl_bpd_ar_lines_v WHERE customer_trx_id = :p_trx_id ORDER BY line_number;
• SELECT contract_number, SUM(line_amount) FROM apps.okl_bpd_ar_lines_v GROUP BY contract_number;

Because LINE_AMOUNT is resolved through a package function, queries returning large result sets may incur additional processing overhead. Filtering by CUSTOMER_TRX_ID, CONTRACT_NUMBER, or KHR_ID before aggregating is therefore recommended for performance.