Search Results okl_trx_csh_batch_all_b




Overview
Explore in AI Chat

Overview

The table OKL_TRX_CSH_BATCH_ALL_B is a core transactional entity within the Oracle E-Business Suite (EBS) module OKL (Leasing and Finance Management). It serves as the master record for a batch of manually entered cash receipts. This table is fundamental to the cash application process, providing a control and grouping mechanism for individual receipt transactions. Its role is to ensure data integrity and facilitate batch-level processing, auditing, and reporting for manual cash receipts entered directly through the OKL application interface. As a multi-org table denoted by the "_ALL_" suffix, it stores data for all operating units, with access controlled by the MOAC (Multi-Org Access Control) security model.

Key Information Stored

While the provided metadata does not list specific columns, the structure and relationships indicate the table's critical attributes. The primary key column, ID, uniquely identifies each cash receipt batch. Based on standard Oracle EBS patterns for batch entities, other significant columns likely include a batch name or number, batch date, status (such as 'Entered', 'Posted', or 'Closed'), total batch amount, currency code, and the operating unit identifier (ORG_ID). The table also contains standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing and the OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

This table is central to inquiries and processes involving batches of manual cash receipts. Common use cases include tracking the status of a cash batch during period-end close, reconciling batch totals to individual receipt lines, and auditing the history of cash entries. A frequent reporting requirement is to list all batches created within a specific date range for a given operating unit. A sample query to achieve this would join the batch table to its related receipt lines for a summary view:

  • SELECT btc.id AS batch_id, btc.batch_number, btc.batch_date, btc.status, SUM(rcpt.amount) AS total_receipt_amount FROM okl_trx_csh_batch_all_b btc JOIN okl_trx_csh_rcpt_all_b rcpt ON btc.id = rcpt.btc_id WHERE btc.org_id = :p_org_id AND btc.batch_date BETWEEN :p_from_date AND :p_to_date GROUP BY btc.id, btc.batch_number, btc.batch_date, btc.status;

Technical consultants also query this table to diagnose data issues where individual receipts are orphaned or to validate the batch hierarchy before migrating or interfacing cash data.

Related Objects

The OKL_TRX_CSH_BATCH_ALL_B table sits at the apex of a key data relationship, with two important transactional tables referencing it via foreign keys. This establishes a one-to-many relationship from a batch to its constituent transactions.

  • OKL_TRX_CSH_RCPT_ALL_B: This is the primary child table, storing the individual manual cash receipt lines. The foreign key column OKL_TRX_CSH_RCPT_ALL_B.BTC_ID joins to the primary key (ID) of the batch table, linking each receipt to its parent batch.
  • OKL_TXL_CNTRCT_LNS_ALL: This table, which manages contract line transactions, also references the batch. The foreign key column OKL_TXL_CNTRCT_LNS_ALL.BTC_ID joins to the batch table's ID, indicating that certain contract line transactions may be associated with or generated from a specific cash receipt batch.