Search Results consolidated_line_number




Overview
Explore in AI Chat

Overview

OKL_BPD_TRX_SUM_LINES_RCPTS_UV is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema, delivered as part of the Oracle Lease and Finance Management (OKL) module. It belongs to the Bill Presentment and Distribution (BPD) family of transaction summary views, which consolidate billing and receipt information for presentation to lessees and for downstream reporting. The view exposes summarized monetary amounts at the contract line level, aggregated by consolidated invoice number, contract number, contract line identifier, consolidated line number, and line name.

Its principal role is to provide a denormalized, read-only projection of transaction data that joins naturally to invoice presentation and receivables reconciliation processes. Because the view aggregates amounts rather than returning individual transaction rows, it is suited to reporting, ad hoc inquiry, and integration scenarios where line-level totals per contract and invoice are required without the overhead of assembling the detail manually. The same definition is applicable across EBS 12.1.1 and 12.2.2; the documented metadata reflects the 12.2.2 ETRM release.

Underlying Base Objects

The view is defined over two documented base objects:

  • OKL_BPD_TRX_SUM_STRMS_RCPTS_UV (VIEW) — the immediate source row set. This upstream view supplies stream-level receipt and transaction summary data. OKL_BPD_TRX_SUM_LINES_RCPTS_UV applies a GROUP BY and SUM against it, so it functions as a line-level aggregation layer above the stream-level view.
  • OKL_ACCOUNTING_UTIL (PACKAGE) — the accounting utility package referenced by the view's dependency chain. It provides the accounting-related logic and helper functions used by the BPD transaction summary stack. It is not joined directly but is invoked through the underlying view definition.

Because the view is layered on another reporting view rather than on base tables, its values reflect the filters and joins already applied by OKL_BPD_TRX_SUM_STRMS_RCPTS_UV. Operators should therefore treat the stream-level view as the authoritative place to inspect detail, and this view as the consolidated roll-up.

Key Columns

  • CONSOLIDATED_INVOICE_NUMBER — identifier of the consolidated invoice to which the summarized line belongs.
  • CONTRACT_NUMBER — the lease or finance contract number associated with the transaction.
  • CONTRACT_LINE_ID — internal identifier of the contract line; a grouping key for the aggregation.
  • CONSOLIDATED_LINE_NUMBER — the line number on the consolidated invoice.
  • LINE_NAME — descriptive name of the contract line.
  • AMOUNT_DUE_ORIGINAL — sum of the original amount due for the grouped lines; this is the column most commonly sought by users searching on "amount_due_original," being the gross amount billed before payments or adjustments.
  • TAX_AMOUNT — aggregated tax associated with the grouped lines.
  • AMOUNT_PAID — aggregated payments applied against the grouped lines.
  • BALANCE — aggregated outstanding balance remaining for the grouped lines.

The arithmetic relationship BALANCE = AMOUNT_DUE_ORIGINAL + TAX_AMOUNT − AMOUNT_PAID generally holds, subject to adjustments reflected in the stream-level source view.

Common Use Cases and Queries

Typical scenarios include reconciling consolidated invoices to contract lines, reporting billed-versus-paid position by contract, and feeding downstream analytics with line-level totals.

  • Retrieve all summarized lines for a contract:
    SELECT contract_number, consolidated_invoice_number, consolidated_line_number, amount_due_original, tax_amount, amount_paid, balance FROM apps.okl_bpd_trx_sum_lines_rcpts_uv WHERE contract_number = :p_contract_number ORDER BY consolidated_invoice_number, consolidated_line_number;
  • Identify lines with an outstanding balance:
    SELECT * FROM apps.okl_bpd_trx_sum_lines_rcpts_uv WHERE balance > 0;
  • Aggregate billed totals per consolidated invoice:
    SELECT consolidated_invoice_number, SUM(amount_due_original) billed, SUM(amount_paid) collected, SUM(balance) open_balance FROM apps.okl_bpd_trx_sum_lines_rcpts_uv GROUP BY consolidated_invoice_number;

Because the view performs aggregation, additional GROUP BY clauses at the query level are generally unnecessary unless the user is rolling up beyond the view's own grouping keys. All access should be granted through the APPS schema with appropriate responsibility-level security.