Results for “okl_bpd_k_due_dates_v”

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

Overview

The view OKL_BPD_K_DUE_DATES_V is an Oracle Applications database object owned by the APPS schema and validated within the OKL — Lease and Finance Management product module. Its purpose is to present aggregated amounts due per contract and due date, giving both reporting layers and integration processes a consolidated, pre-joined picture of lease receivables that remain outstanding. Rather than forcing callers to reconcile payment schedules against consolidated AR streams and lines manually, the view performs the join, grouping, and filtering internally, exposing only the contract identifier, the due date, and the summed amount still owed.

In Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed in the context of receivables-driven lease reporting. When a user searches for "amount_due," this object is relevant because its third column, AMOUNT_DUE, is literally the field that surfaces the outstanding balance per contract and due date. The view therefore acts as a convenient abstraction layer over the more granular underlying Transactions and stream tables.

Underlying Base Objects

The view definition references three base objects through APPS synonyms:

• AR_PAYMENT_SCHEDULES_ALL — the core Receivables table holding installments, due dates, and the AMOUNT_DUE_REMAINING balance.
• OKL_CNSLD_AR_STRMS_B — the consolidated AR streams table for leases, which links a receivables invoice to lease lines.
• OKL_CNSLD_AR_LINES_B — the consolidated AR lines table, which carries the lease line identifier and the related contract (KHR) reference.

The join chains leases to their receivables schedules: OKL_CNSLD_AR_STRMS_B.RECEIVABLES_INVOICE_ID = AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_TRX_ID and OKL_CNSLD_AR_STRMS_B.LLN_ID = OKL_CNSLD_AR_LINES_B.ID. Only payment schedule classes INV (invoices) and CM (credit memos) are considered.

Key Columns

The view exposes exactly three columns:

• CONTRACT_ID — derived from OKL_CNSLD_AR_LINES_B.KHR_ID, this is the lease contract header identifier to which the receivable relates. It is the primary grouping key.
• DUE_DATE — taken from AR_PAYMENT_SCHEDULES_ALL.DUE_DATE, representing the scheduled date on which the installment is due. It forms the second grouping dimension.
• AMOUNT_DUE — the sum of AR_PAYMENT_SCHEDULES_ALL.AMOUNT_DUE_REMAINING across qualifying schedule rows, representing the total remaining amount owed for that contract on that date. Only positive remainders survive because of the HAVING SUM(...) > 0 clause.

Note that the filtering condition removes fully settled or over-credited amounts, so AMOUNT_DUE is always a net outstanding figure rather than a raw installment value.

Common Use Cases and Queries

Typical usage involves aging and cash-flow reporting, reconciliation of lease receivables, and feeding downstream integration or dashboards. A simple query lists all outstanding dues for a lease:

• SELECT contract_id, due_date, amount_due FROM apps.okl_bpd_k_due_dates_v WHERE contract_id = :p_contract_id ORDER BY due_date;
• SELECT due_date, SUM(amount_due) FROM apps.okl_bpd_k_due_dates_v GROUP BY due_date ORDER BY due_date; — to obtain total outstanding dues by date across all contracts.
• SELECT contract_id, SUM(amount_due) FROM apps.okl_bpd_k_due_dates_v GROUP BY contract_id; — to obtain the total remaining receivable per lease contract.

Because the view already aggregates and filters, it is well suited for direct use in concurrent programs, BI Publisher data templates, and OAF pages that need a "due amounts" summary without additional join logic. Callers should remember that only positive remaining amounts appear, and that credit memo and invoice classes are combined, so a net exposure view is produced rather than a gross billing schedule.