Results for “okl_bpd_tld_ar_lines_v”

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

Overview

OKL_BPD_TLD_AR_LINES_V is a valid APPS-owned database view in the Oracle E-Business Suite Release 12.1.1 / 12.2.2 environment, defined within the OKL Leasing and Finance Management module. Per the ETRM documentation, the view presents "TLD and receivables lines for variable rate and bill status API and remarketing view." It therefore functions as a consolidated read-only projection that joins transaction-line-detail (TLD) records originating in the leasing application with the corresponding Oracle Receivables transaction lines, invoice headers, and descriptive invoice information. Its principal consumers are the variable-rate and bill-status application programming interfaces, together with remarketing reporting that must reconcile a leasing schedule line against the receivable actually raised against a lessee. Because the view resolves the relationship between the leasing schedule and the AR subledger, it is a standard integration point for downstream reporting that requires both contract-side and receivables-side attributes in a single row.

Underlying Base Objects

The ETRM documented base objects for this view are:

• OKL_TXD_AR_LN_DTLS_B (SYNONYM) — the leasing transaction-line-detail table, aliased TLD, which supplies schedule and detail identifiers.
• RA_CUSTOMER_TRX_LINES_ALL (SYNONYM) — Oracle Receivables transaction lines, aliased RACTRL, providing invoice line amounts, interface attributes, and extended amounts.
• OKL_TXL_AR_INV_LNS_B (SYNONYM) — the leasing AR invoice lines table, aliased TIL, which links a TLD record to its invoice.
• OKL_TRX_AR_INVOICES_B (SYNONYM) — the leasing AR invoice base table, aliased TAI, holding invoice header attributes such as status and dates.
• OKL_TRX_AR_INVOICES_TL (SYNONYM) — the language-translated invoice table, aliased TAI_TL, supplying description text filtered by USERENV('LANG').
• OKL_BILLING_UTIL_PVT (PACKAGE) — a billing utility package whose functions are called directly within the view's SELECT list.

The join path is driven by a character comparison between TLD.ID and RACTRL.INTERFACE_LINE_ATTRIBUTE14, the interface attribute assumed to carry the TLD identifier. TLD.TIL_ID_DETAILS then links to the invoice-line table, which links to the invoice base table, which links to its translation row on ID and language.

Key Columns

• TLD_ID, KHR_ID, STY_ID, SEL_ID, TIL_ID_DETAILS, ISL_ID, IBT_ID, KLE_ID — primary and foreign key identifiers tying the row back to leasing contract, stream, and schedule structures.
• CONTRACT_NUMBER — derived from INTERFACE_LINE_ATTRIBUTE6; the leasing contract reference.
• STREAM_TYPE — derived from INTERFACE_LINE_ATTRIBUTE9; indicates the billing stream classification.
• CUSTOMER_TRX_ID / CUSTOMER_TRX_LINE_ID — the Receivables transaction header and line identifiers.
• TRX_STATUS_CODE, INVOICE_DATE (DATE_INVOICED), DATE_ENTERED — invoice status and audit-style date fields. DATE_ENTERED is supplied directly from OKL_TRX_AR_INVOICES_B and is the column most frequently referenced by users searching on this object.
• AMOUNT, LINE_AMOUNT, TAX_AMOUNT — monetary values; LINE_AMOUNT is taken from RACTRL.EXTENDED_AMOUNT, while TAX_AMOUNT is a scalar subquery summing EXTENDED_AMOUNT from RA_CUSTOMER_TRX_LINES_ALL where LINE_TYPE='TAX'.
• AMOUNT_DUE_REMAINING, AMOUNT_DUE_ORIGINAL — calculated at runtime by OKL_BILLING_UTIL_PVT.INVOICE_LINE_AMOUNT_REMAINING and INVOICE_LINE_AMOUNT_ORIG respectively.
• CONSOLIDATED_INVOICE_NUMBER and DESCRIPTION — supporting descriptive and grouping attributes.

Common Use Cases and Queries

Typical usage includes reconciling leasing billing schedules to receivable lines, driving the bill-status API, and feeding remarketing extracts. A representative query filtering on the popular date column is:

SELECT TLD_ID, CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, CONTRACT_NUMBER, TRX_STATUS_CODE, AMOUNT, TAX_AMOUNT, LINE_AMOUNT, DATE_ENTERED, INVOICE_DATE FROM APPS.OKL_BPD_TLD_AR_LINES_V WHERE TRUNC(DATE_ENTERED) BETWEEN :p_from_date AND :p_to_date ORDER BY CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID;

Because LINE_AMOUNT and the amount-due columns invoke packaged PL/SQL functions, queries joining this view to large data sets may incur per-row function calls; restricting by DATE_ENTERED, contract number, or transaction identifiers improves performance. Reported issues with this view in the ETRM support history include missing or duplicate rows, amount mismatches, and date filtering behavior, all of which are typically investigated through the AR line and leasing schedule relationships described above.