Results for “amount_remaining”

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

Overview

OKL_CS_BPD_INV_DTL_V is an APPS-owned database view in the OKL (Leasing and Finance Management) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is described in the ETRM repository as the "New CS Billing base view." Its purpose is to present a unified, consolidated picture of billing invoice detail for leasing contracts across two distinct origination paths — consolidated lease invoices created within OKL and standard Oracle Receivables invoices. Because it merges these sources into a single row-per-invoice-line result set, the view functions as a reporting and integration foundation for downstream billing analysis, reconciliation, and customer-facing invoice extracts rather than as a transaction-entry object. It exposes party, currency, amount, tax, and applied/credited/remaining balance information via calls to the OKL_BILLING_UTIL_PVT package.

Underlying Base Objects

The documented base objects reveal a UNION-based definition spanning the leasing consolidation tables and the Receivables tables:

• OKL_CNSLD_AR_HDRS_B — consolidated AR invoice headers (aliased CNR), supplying the consolidated invoice number, currency, due date, amount, and consolidation date.
• OKL_CNSLD_AR_LINES_B (LLN) and OKL_CNSLD_AR_STRMS_B (LSM) — the consolidated AR lines and streams, providing line-level amount, tax, and the associated AR invoice and contract identifiers.
• OKC_K_HEADERS_B (KHR) — the contract header, supplying CONTRACT_NUMBER and linking billing detail back to the lease or contract.
• AR_PAYMENT_SCHEDULES_ALL (APS) — payment schedules, contributing tax remaining, transaction number, and due/amount data.
• RA_CUSTOMER_TRX_LINES_ALL (RACTRL) and RA_CUSTOMER_TRX_ALL — the standard Receivables transaction and line tables used to derive the AR invoice leg and line identifiers.
• OKL_TRX_AR_INVOICES_B, OKL_TXL_AR_INV_LNS_B, and OKL_TXD_AR_LN_DTLS_B — leasing transaction invoice and invoice-line/detail tables referenced for the Receivables-side arm.
• OKL_BILLING_UTIL_PVT and FND_GLOBAL — PL/SQL packages invoked within the select list for amount-applied/credited/remaining computation and session context.
• FND_LOOKUPS — the standard lookup view.

Key Columns

• INVOICE_ID / AR_INVOICE_ID — the invoice identity; the AR invoice id is the Receivables CUSTOMER_TRX_ID.
• INVOICE_NUMBER / INVOICE_TYPE — the consolidated invoice number, with a literal invoice type distinguishing 'OKL-CONS-INV' (consolidated lease invoice) from 'AR-INVOICE'.
• CHR_ID / KHR_ID / LSM_ID — contract header, LSM line, and consolidated-line linkage keys.
• INVOICE_AMOUNT / LINE_AMOUNT / TAX_AMOUNT / TAX_REMAINING — header and line monetary values, including tax.
• AMOUNT_ORIGINAL, AMOUNT_APPLIED, AMOUNT_CREDITED, AMOUNT_REMAINING — computed balances returned by OKL_BILLING_UTIL_PVT functions.
• DUE_DATE, INVOICE_DATE, INVOICE_CURRENCY_CODE, ORG_ID, BILL_TO_SITE_USE_ID, CUSTOMER_ACCT_ID, CONTRACT_NUMBER, PAYMENT_TERM, LINE_IDENTIFIER, INVOICE_LINE_ID — reporting attributes for aging, organization, customer, and line reconciliation.

Common Use Cases and Queries

Typical usage includes billing detail extracts, open-balance and aging analysis, tax reconciliation, and reconciliation between consolidated lease invoices and their AR counterparts.

• Invoice listing by contract:
  SELECT contract_number, invoice_number, invoice_type, invoice_amount, due_date FROM okl_cs_bpd_inv_dtl_v WHERE contract_number = :p_contract;
• Outstanding balance review:
  SELECT invoice_number, invoice_amount, amount_applied, amount_remaining FROM okl_cs_bpd_inv_dtl_v WHERE amount_remaining > 0 ORDER BY due_date;
• Separating consolidated versus AR invoices:
  SELECT invoice_type, COUNT(*), SUM(invoice_amount) FROM okl_cs_bpd_inv_dtl_v GROUP BY invoice_type;

Because the view performs inline package function calls, performance-sensitive queries should filter on INVOICE_ID, CONTRACT_NUMBER, or ORG_ID to limit row volume.