Search Results okl_trx_csh_rcpt_all_b




Overview
Explore in AI Chat

Overview

The table OKL_TRX_CSH_RCPT_ALL_B is a core transactional entity within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module, specifically in versions 12.1.1 and 12.2.2. It serves as the detailed repository for individual cash receipts processed as part of a batch operation. This table is fundamental to the cash application lifecycle, capturing the granular details of each payment received against lease or finance contracts. Its role is to provide an auditable, line-item record of receipts that can be aggregated, reconciled, and applied to specific contract lines, thereby supporting critical financial processes like revenue recognition, cash flow analysis, and customer account management.

Key Information Stored

While the provided metadata does not list specific columns, the documented relationships and primary key structure reveal essential data points. The primary key column, ID, uniquely identifies each receipt record. A critical foreign key column, BTC_ID, links the individual receipt to its parent batch in the OKL_TRX_CSH_BATCH_ALL_B table, establishing the batch processing context. Other inferred columns would typically include receipt amount, currency, receipt date, status, payment method identifier, and references to the customer and the specific lease or finance contract line item against which the payment is being applied. The table's multi-org structure, indicated by the "_ALL_B" suffix, signifies it stores data for all operating units.

Common Use Cases and Queries

This table is central to queries involving cash receipt details. Common use cases include reconciling batch totals to individual receipt lines, investigating application details for a specific customer payment, and generating detailed cash receipt registers for accounting or audit purposes. A typical reporting query would join this table to its parent batch and related contract information. For example, to list all receipts within a specific batch, one might use:

  • SELECT rct.id, rct.receipt_number, rct.receipt_amount, rct.receipt_date
  • FROM okl_trx_csh_rcpt_all_b rct
  • WHERE rct.btc_id = <batch_id>;

Another critical pattern involves tracing how a receipt was applied by joining to the OKL_TXL_CNTRCT_LNS_ALL table via the RCT_ID foreign key to see the specific contract line items credited.

Related Objects

The table maintains documented relationships with other key OKL transactional tables, as per the provided metadata. The primary foreign key relationship is with the cash receipt batch header: the BTC_ID column in OKL_TRX_CSH_RCPT_ALL_B references the OKL_TRX_CSH_BATCH_ALL_B table. Conversely, this receipt detail table is referenced by the contract lines table: the RCT_ID column in OKL_TXL_CNTRCT_LNS_ALL is a foreign key pointing back to the OKL_TRX_CSH_RCPT_ALL_B table. This latter relationship is crucial as it creates the link between an incoming cash receipt and its application to a specific contractual obligation line, forming the backbone of the cash application process.