Search Results okl_batch_receipts_summary_uv




Overview
Explore in AI Chat

Overview

OKL_BATCH_RECEIPTS_SUMMARY_UV is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite, defined against the OKL (Leasing and Finance Management) product. It presents a unified, denormalized summary of batch receipt activity, joining receipt header data to customer, contract, and receivable invoice information. The view is read-only by design and serves as a single query surface for operational and analytical reporting on cash receipts processed through the OKL transaction cash batch mechanism.

The "UV" suffix denotes a user-validated reporting view intended for direct consumption by reports, concurrent programs, and downstream integrations rather than by application form logic. Because the view resolves foreign-key relationships internally, consumers do not need to reconstruct the complex joins between receipt batches, receipt details, customers, contracts, consolidated AR headers, and receivable transactions. The view is structured as a UNION of three branches, each representing a distinct receipt-to-receivable association path, which explains the presence of several NULL placeholder columns.

Underlying Base Objects

The view is documented as depending on the following base objects, all referenced through synonyms in the APPS schema:

The three UNION branches correspond to receipts applied to a contract (contract populated, invoice columns NULL), receipts applied to a consolidated invoice (INVOICE_TYPE = 'CONS'), and receipts applied to a standard AR transaction.

Key Columns

The INVOICE_TYPE column is significant for filtering: consumers selecting only standard or consolidated receivable receipts must account for the NULL returned by the contract branch and must not rely on INVOICE_TYPE alone to distinguish AR transactions from consolidated invoices without also testing INVOICE_ID against the appropriate source.

Common Use Cases and Queries

The view supports receipt reconciliation, batch balancing, customer-level cash application analysis, and feeds into leasing operational dashboards. Typical usage includes reporting receipts by batch, tracing a receipt to its applied contract or invoice, and reconciling OKL receipts against RA_CUSTOMER_TRX_ALL.

Retrieve all receipts regardless of application type:

SELECT RECEIPT_NUMBER, RECEIPT_AMOUNT, CUSTOMER_NAME,
       CONTRACT_NUMBER, INVOICE_NUMBER, INVOICE_TYPE
FROM   APPS.OKL_BATCH_RECEIPTS_SUMMARY_UV;

Isolate consolidated invoice receipts:

SELECT RECEIPT_NUMBER, INVOICE_NUMBER, INVOICE_ID, RECEIPT_AMOUNT
FROM   APPS.OKL_BATCH_RECEIPTS_SUMMARY_UV
WHERE  INVOICE_TYPE = 'CONS';

Aggregate receipts by batch and currency:

SELECT BATCH_ID, RECEIPT_CURRENCY, SUM(RECEIPT_AMOUNT) TOTAL_AMT
FROM   APPS.OKL_BATCH_RECEIPTS_SUMMARY_UV
GROUP  BY BATCH_ID, RECEIPT_CURRENCY;

Because the source includes views over transactional receipt tables, queries against this view should be restricted by receipt date or batch ID to limit execution cost, and should be granted appropriate APPS-schema access via a custom synonym or GRANT before use in external reporting tools.