Search Results okl_trx_csh_receipt_b




Overview
Explore in AI Chat

Overview

The OKL_TRX_CSH_RECEIPT_B table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Leasing and Finance Management (OKL) product. It serves as the transactional repository for individual cash receipts processed as part of a batch. Its primary role is to record the detailed receipt information generated from customer payments, which are then allocated against outstanding lease or finance contract invoices. This table is fundamental to the cash application and revenue recognition processes within the leasing module, acting as the central point for receipt details before further distribution to applications or external systems.

Key Information Stored

While the provided ETRM excerpt does not list specific columns, the table's primary key is documented as ID, which uniquely identifies each receipt record. Based on its description and foreign key relationships, the table is expected to store critical attributes for a cash receipt. These typically include the receipt amount, currency, receipt date, payment method, and a reference to the originating batch via the BTC_ID column. It also likely holds identifiers for the customer (payer), the bank account, and status flags indicating whether the receipt is applied, unapplied, or on-account. The ID column is the central unique identifier leveraged by all related transactional tables.

Common Use Cases and Queries

This table is central to cash management and reconciliation reporting within Oracle Lease Management. Common operational and analytical queries involve joining this table to its related objects to track the lifecycle of a payment. For instance, a report to list all unapplied receipts within a specific date range would query this table filtered by status and joined to the batch table for batch details. Another critical use case is tracing the application of a specific receipt to contract lines, which requires joining through OKL_TXL_RCPT_APPS_B. A sample query pattern to retrieve receipt details with their batch information would be:

  • SELECT rct.id, rct.receipt_number, rct.receipt_date, rct.amount, batch.batch_name
  • FROM okl_trx_csh_receipt_b rct, okl_trx_csh_batch_b batch
  • WHERE rct.btc_id = batch.id AND rct.receipt_date BETWEEN :p_start_date AND :p_end_date;

Related Objects

The OKL_TRX_CSH_RECEIPT_B table maintains documented foreign key relationships with several other key transactional tables in the OKL schema, as per the provided metadata. These relationships are crucial for data integrity and form the basis for most receipt-related reporting.

  • OKL_TRX_CSH_BATCH_B: The parent batch table. Joined via OKL_TRX_CSH_RECEIPT_B.BTC_ID to OKL_TRX_CSH_BATCH_B.ID.
  • OKL_TXL_RCPT_APPS_B: Stores the detailed applications of a receipt to specific contract lines. Joined via OKL_TXL_RCPT_APPS_B.RCT_ID_DETAILS to OKL_TRX_CSH_RECEIPT_B.ID.
  • OKL_TXL_CNTRCT_LNS: The contract lines table, which can reference a receipt identifier. Joined via OKL_TXL_CNTRCT_LNS.RCT_ID to OKL_TRX_CSH_RECEIPT_B.ID.
  • OKL_EXT_CSH_RCPTS_B: Likely used for interfacing with external cash management systems. Joined via OKL_EXT_CSH_RCPTS_B.RCT_ID to OKL_TRX_CSH_RECEIPT_B.ID.