Results for “consolidated_invoice_id”

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

Overview

OKL_BPD_TRX_SUM_STRMS_RCPTS_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Leasing and Finance Management) product family. The view presents a transaction-level summary of lease and finance contract streams alongside their associated receipt and receivables activity. It is part of the BPD (Business Process Dashboard / Business Process Definition) family of views used across ETRM reporting, analytics, and dashboarding layers, and it exposes a flattened, denormalized picture of contract stream billing and collection status without requiring the caller to join the underlying leasing payment transaction tables directly.

The view was introduced and remains valid in both Oracle EBS 12.1.1 and 12.2.2. Its primary purpose is to support reporting on amounts billed versus amounts collected at the stream level within a contract, tying each contract stream to its consolidated invoice, receivables invoice, and payment status. By surfacing both original and remaining amounts due, it enables straightforward calculation of paid amounts and outstanding balances for leasing receivables.

Underlying Base Objects

The view is defined over two documented base objects:

• OKL_BPD_LEASING_PAYMENT_TRX_V (VIEW) — the primary source. All columns in OKL_BPD_TRX_SUM_STRMS_RCPTS_UV are selected from this view (aliased as A). It supplies consolidated invoice identifiers, contract and contract-line identifiers, tax amounts, line and stream names, stream type purpose, original and remaining amounts due, receivables invoice numbers, and stream IDs.
• OKL_ACCOUNTING_UTIL (PACKAGE) — invoked via the function GET_LOOKUP_MEANING to translate the coded STREAM_TYPE_PURPOSE value into a user-facing meaning using the OKL_STREAM_TYPE_PURPOSE lookup type.

Because the view reads from another view rather than landing tables, it inherits the join logic and filtering of OKL_BPD_LEASING_PAYMENT_TRX_V. It does not store data; it is purely a read-only projection intended for query and reporting workloads rather than transactional DML.

Key Columns

• CONSOLIDATED_INVOICE_NUMBER / CONSOLIDATED_INVOICE_ID — the consolidated (summary) invoice generated for the leasing transaction.
• CONSOLIDATED_LINE_NUMBER — the line on the consolidated invoice.
• CONTRACT_NUMBER / CONTRACT_LINE_ID — the lease or finance contract and its line.
• TAX_AMOUNT — tax amount, coalesced to zero via NVL when null.
• LINE_NAME / STREAM_NAME — descriptive names for the contract line and the billing stream.
• STREAM_PURPOSE_MEANING — decoded meaning of the stream type purpose (e.g., rental, tax, fee), derived via OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING.
• AMOUNT_DUE_ORIGINAL — the original amount billed to the customer.
• BALANCE — the remaining amount due (aliased from AMOUNT_DUE_REMAINING).
• AMOUNT_PAID — computed as AMOUNT_DUE_ORIGINAL minus AMOUNT_DUE_REMAINING.
• RECEIVABLES_INVOICE_NUMBER — the corresponding AR invoice tied to the stream.
• LSM_ID — the leasing stream identifier (aliased from STREAM_ID).

Common Use Cases and Queries

Typical uses include collections aging/reporting, receivables reconciliation between leasing streams and AR invoices, and dashboard tiles showing billed versus collected amounts by contract or stream purpose. Example query to see all outstanding balances by contract:

SELECT CONTRACT_NUMBER,
       STREAM_NAME,
       STREAM_PURPOSE_MEANING,
       AMOUNT_DUE_ORIGINAL,
       AMOUNT_PAID,
       BALANCE
FROM   APPS.OKL_BPD_TRX_SUM_STRMS_RCPTS_UV
WHERE  BALANCE > 0
ORDER  BY CONTRACT_NUMBER, STREAM_NAME;

Reconciliation view tying streams to AR invoices:

SELECT CONSOLIDATED_INVOICE_NUMBER,
       RECEIVABLES_INVOICE_NUMBER,
       SUM(AMOUNT_DUE_ORIGINAL) AS BILLED,
       SUM(AMOUNT_PAID)         AS COLLECTED,
       SUM(BALANCE)             AS OUTSTANDING
FROM   APPS.OKL_BPD_TRX_SUM_STRMS_RCPTS_UV
GROUP  BY CONSOLIDATED_INVOICE_NUMBER, RECEIVABLES_INVOICE_NUMBER;

Because the view resolves the stream purpose lookup at runtime, reports can group directly by STREAM_PURPOSE_MEANING without additional lookup joins, simplifying SQL for business users and BI Publisher data models.