Search Results inv_lines

Overview

The view APPS.OKL_BPD_INVEST_TRX_SUM_LN_UV is an Oracle E-Business Suite reporting object used within the Oracle Lease and Finance Management (OKL) module. It presents a consolidated, line-level summary of investor-related transactions originating from Oracle Receivables. The suffix convention (_UV) indicates a user-facing view typically consumed by Oracle Business Intelligence (OBIEE) reports, Oracle BI Publisher templates, or custom PL/SQL reporting against investor agreement billing data.

The view combines invoice header attributes, investor identification details, payment scheduling information, and individual receivable line details into a single flattened result set. It is scoped specifically to transactions whose INTERFACE_HEADER_CONTEXT equals 'OKL_INVESTOR', meaning it isolates investor-created invoices generated through the lease investor agreement process. This makes it a specialised reporting vehicle rather than a general AR transaction query — the user searching for "inv_lines" is likely looking at how RA_CUSTOMER_TRX_LINES_ALL data surfaces inside this investor reporting context.

Underlying Base Objects

The view is defined across the following documented base objects and synonyms owned or referenced by APPS:

• RA_CUSTOMER_TRX (synonym) — invoice header source, aliased INV_HDR.
• RA_CUSTOMER_TRX_LINES_ALL (synonym) — invoice line source, aliased INV_LINES, the primary "inv_lines" reference.
• AR_PAYMENT_SCHEDULES_ALL (synonym) — provides DUE_DATE, AMOUNT_DUE_ORIGINAL, and AMOUNT_DUE_REMAINING.
• AR_RECEIPT_METHODS (synonym) — resolves the payment method name.
• RA_TERMS_VL (view) — supplies the payment term name.
• HZ_CUST_ACCOUNTS and HZ_PARTIES (synonyms) — investor account number and party name.
• OKX_CUST_SITE_USES_V (view) — bill-to address components.
• OKL_ACCOUNTING_UTIL (package) — supplies FORMAT_AMOUNT for currency-formatted monetary values.
• ARP_ADDR_LABEL_PKG (package) — referenced by the address label view layer.

Header-to-line joins are performed on CUSTOMER_TRX_ID, and header-to-schedule joins likewise ensure a single amount due per invoice line grouping.

Key Columns

• INVOICE_ID — the CUSTOMER_TRX_ID of the underlying receivable.
• INVESTOR_AGREEMENT — from INTERFACE_HEADER_ATTRIBUTE1, identifies the investor agreement.
• INVESTOR_NUMBER, INVESTOR_NAME — account number and party name of the investor.
• INVOICE_NUMBER, INVOICE_DATE, INVOICE_CURRENCY_CODE — core header facts.
• DUE_DATE, PAYMENT_METHOD, PAYMENT_TERM — scheduling and settlement context.
• ADDRESS1–COUNTRY — bill-to site address fields.
• INVOICE_AMOUNT, BALANCE — formatted original and remaining amounts.
• STREAM_TYPE — from INTERFACE_HEADER_ATTRIBUTE5.
• LINE_NUMBER, LINE_TYPE, INVOICE_LINE_AMOUNT — the "inv_lines" level detail: line sequence, type, and formatted extended amount.

Common Use Cases and Queries

Typical usage includes investor billing reconciliation, aged balance reporting by investor agreement, and drill-down from a summary report to invoice lines. A representative query:

• SELECT invoice_number, investor_name, line_number, line_type, invoice_line_amount FROM okl_bpd_invest_trx_sum_ln_uv WHERE investor_agreement = :agreement ORDER BY invoice_number, line_number;
• SELECT investor_name, SUM(invoice_amount) FROM okl_bpd_invest_trx_sum_ln_uv GROUP BY investor_name;
• SELECT invoice_number, balance FROM okl_bpd_invest_trx_sum_ln_uv WHERE balance > 0;

Because amounts are pre-formatted by OKL_ACCOUNTING_UTIL.FORMAT_AMOUNT, the columns are suitable for direct display rather than numeric aggregation without conversion.