Results for “okl_bpd_contract_remaining_v”

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

Overview

The OKL_BPD_CONTRACT_REMAINING_V view is a reporting object in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents the outstanding receivables balance owed by a customer against each lease or finance contract, aggregated at the customer site-use level and expressed in both functional and transaction currency. The view joins the consolidated receivables hierarchy maintained by OKL to the Oracle Receivables payment schedules, allowing remaining balances on billed invoices to be reported by contract. It is typically consumed by operational dashboards, collections analysis, and integration interfaces that require contract-level exposure figures without directly joining the underlying consolidated AR tables.

Underlying Base Objects

The view is owned by APPS and is defined over several documented base objects. The consolidated AR tables OKL_CNSLD_AR_HDRS_B, OKL_CNSLD_AR_LINES_B, and OKL_CNSLD_AR_STRMS_B form the lease-side billing hierarchy and link to AR_PAYMENT_SCHEDULES_ALL via ST.RECEIVABLES_INVOICE_ID = PS.CUSTOMER_TRX_ID. Contract header information is sourced from OKC_K_HEADERS_ALL_B, while customer identity is resolved through HZ_CUST_ACCOUNTS and HZ_PARTIES. The stream type is validated against the OKL_STRM_TYPE_V view, which filters out streams whose STREAM_TYPE_PURPOSE is 'CURE'. The metadata also lists OKL_ACCOUNTING_UTIL as a referenced package, indicating accounting-related logic is involved in the broader OKL flow. The join path from contract to customer runs through HD.IXX_ID to HZ_CUST_ACCOUNTS, and then to HZ_PARTIES.

Key Columns

• CONTRACT_ID / CONTRACT_NUMBER — Identifier and human-readable number of the lease or finance contract (KH.ID, KH.CONTRACT_NUMBER).
• CUSTOMER_ID / CUSTOMER_NAME / CUSTOMER_NUMBER — Customer party ID, party name, and account number resolved from HZ_PARTIES and HZ_CUST_ACCOUNTS.
• CURRENCY_CODE — Currency of the contract, taken from OKC_K_HEADERS_ALL_B.
• CUSTOMER_SITE_USE_ID — Site-use identifier used as the aggregation grain; balances are reported per site.
• FUNCTIONAL_AMOUNT — SUM(PS.ACCTD_AMOUNT_DUE_REMAINING), the remaining amount due converted into the ledger's functional currency, and the column most commonly referenced by users searching on this term.
• AMOUNT — SUM(PS.AMOUNT_DUE_REMAINING), the remaining amount due in the transaction currency.

Because the view groups by contract, customer, currency, and site-use, consumers should expect one row per contract-site combination rather than one row per invoice.

Common Use Cases and Queries

A frequent scenario is reporting total remaining functional exposure across a customer's active lease contracts. For example:

• SELECT CONTRACT_NUMBER, CUSTOMER_NAME, FUNCTIONAL_AMOUNT FROM OKL_BPD_CONTRACT_REMAINING_V WHERE CUSTOMER_NUMBER = :p_cust;
• SELECT CONTRACT_ID, SUM(FUNCTIONAL_AMOUNT) FROM OKL_BPD_CONTRACT_REMAINING_V GROUP BY CONTRACT_ID;
• SELECT CURRENCY_CODE, SUM(AMOUNT) FROM OKL_BPD_CONTRACT_REMAINING_V GROUP BY CURRENCY_CODE;

These queries support collections aging, reconciliation of billed-versus-remaining balances, and feeds into external receivables analysis. Note that only non-CURE stream types are included, so cure-related balances are excluded by design.