Search Results receipt_currency




Overview
Explore in AI Chat

Overview

APPS.OKL_BATCH_RECEIPTS_SUMMARY_UV is an Oracle E-Business Suite view in the Oracle Lease and Finance Management (OLFM) module. It consolidates receipt and batch information associated with cash batches processed through the OKL_TRX_CSH (transaction cash) framework and surfaces it in a single, denormalized result set. The view is designed primarily to support reporting and inquiry on receipts created within lease and finance contracts, including the linkage between a receipt, the customer party, the customer account, and the originating transaction — whether that transaction is a contract, a consolidated invoice, or a standard Oracle Receivables transaction.

The "_UV" suffix indicates a user-facing view intended for reporting layers rather than transaction processing. It does not perform data manipulation; it is a read-only projection. Because it draws from both OLFM-specific tables and shared Receivables/HZ objects, it acts as a bridge between the leasing sub-ledger and the broader EBS financial data model. This makes it valuable for reconciliation, customer service inquiry screens, and custom operational reports that must show receipts alongside their contracts and invoices.

Underlying Base Objects

The documented base objects referenced by the view are:

  • OKL_TRX_CSH_BATCH_B — the cash receipt batch header, providing BATCH_ID.
  • OKL_TRX_CSH_RECEIPT_V — a receipt view supplying receipt number, amount, currency, effective date, and status.
  • OKL_TXL_RCPT_APPS_V — a receipt-application view that maps a receipt to its applied contract, consolidated invoice, or AR transaction.
  • OKC_K_HEADERS_B — the contract header, joined through the application line when a contract applies.
  • OKL_CNSLD_AR_HDRS_B — the consolidated AR invoice header used when the receipt applies to a consolidated invoice.
  • RA_CUSTOMER_TRX_ALL — the standard Receivables transaction table used when the receipt applies to an AR invoice.
  • HZ_CUST_ACCOUNTS and HZ_PARTIES — providing account number, party name, and party ID.

The view is constructed as a UNION of three branches, each representing a different application type: contract (KHR_ID populated), consolidated (CNR_ID populated), and AR (RA transaction populated). Columns that do not apply to a given branch are returned as NULL, with the literal INVOICE_TYPE distinguishing the branch ('CONS' for consolidated, 'AR' for Receivables, and the contract branch carrying NULL). This design lets consumers query a single object regardless of how the receipt was applied.

Key Columns

  • RECEIPT_NUMBER — sourced from the receipt check number; the receipt identifier exposed to users.
  • RECEIPT_AMOUNT — the applied or receipt amount.
  • CUSTOMER_NAME / CUSTOMER_ID — party name and party ID from HZ_PARTIES.
  • ACCOUNT_NUMBER / CUST_ACCOUNT_ID — customer account number and the ILE_ID (account) linked to the application line.
  • CONTRACT_NUMBER / CONTRACT_ID — the lease or finance contract, populated only for contract-applied receipts.
  • INVOICE_NUMBER / INVOICE_ID — the consolidated invoice number or AR transaction number, populated for the consolidated and AR branches respectively.
  • BATCH_ID — identifies the cash batch the receipt belongs to.
  • RECEIPT_ID — the internal receipt identifier.
  • RECEIPT_CURRENCY / RECEIPT_DATE — currency code and effective date of the receipt.
  • RCPT_STATUS_CODE — the receipt status, useful for filtering cleared versus uncleared items.
  • INVOICE_TYPE — discriminator ('CONS', 'AR', or NULL for contract applications).

Common Use Cases and Queries

Typical uses include batch receipt reconciliation, customer receipt inquiry, and reporting on receipts by contract, invoice, or batch. A simple extract filtered by receipt status might read:

  • SELECT batch_id, receipt_number, customer_name, contract_number, invoice_number, receipt_amount, receipt_date, invoice_type FROM apps.okl_batch_receipts_summary_uv WHERE rcpt_status_code = 'CLEARED';
  • SELECT invoice_type, COUNT(*), SUM(receipt_amount) FROM apps.okl_batch_receipts_summary_uv GROUP BY invoice_type;
  • SELECT * FROM apps.okl_batch_receipts_summary_uv WHERE batch_id = :p_batch_id ORDER BY receipt_number;

Because the view is a UNION across three sources without extensive filtering in the excerpt, consumers should apply appropriate predicates (status, date range, batch) to control result size. It is best treated as a reporting convenience object rather than a high-volume extraction source.