Results for “batch_qty”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKL_BPD_BTCH_CONT_SUMRY_UV view is a reporting and integration object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, owned by the APPS schema and belonging to the OKL – Leasing and Finance Management product family. It provides a consolidated summary of cash batch receipts that have been transmitted to the general ledger interface through the Receipt Application and batch deposit process. The view presents one row per cash batch, aggregating receipt-level details to expose batch quantity, batch total, currency, deposit dates, GL request dates, transaction status, and currency conversion attributes.

Its primary role is to support operational reporting and downstream integration where summarized batch-level cash receipt information is required. Because it joins multiple receipt-related views and filters for records tied to a specific application path, it is particularly useful for reconciliation of batch deposits, monitoring GL transfer status, and supporting the transaction status reporting frequently associated with the trx_status_code column.

Underlying Base Objects

The view is defined over three documented underlying views:

• OKL_TRX_CSH_BATCH_V (alias A) – the driving batch-level view that supplies batch identity, currency, deposit date, GL requested date, and transaction status.
• OKL_TRX_CSH_RECEIPT_V (alias B) – the receipt-level view that links receipts back to their parent batch via BTC_ID.
• OKL_TXL_RCPT_APPS_V (alias C) – the receipt application view that ties receipts to applied amounts via RCT_ID_DETAILS.

The join conditions require A.ID = B.BTC_ID and B.ID = C.RCT_ID_DETAILS, with filters ensuring C.KHR_ID IS NOT NULL and C.CNR_ID IS NULL — meaning only receipts that have been applied (KHR_ID populated) and not yet cancelled/reversed (CNR_ID null) are eligible. A correlated subquery restricts results to the earliest receipt ID per batch, so the view returns one representative receipt row per batch together with the batch summary attributes.

Key Columns

• ID – the batch identifier inherited from the driving batch view; serves as the primary linkage key.
• NAME – batch name or description.
• BATCH_QTY – number of receipts contained in the batch.
• BATCH_TOTAL – batch control total, formatted as a string using the TO_CHAR mask '99, 999, 999, 999.99'.
• CURRENCY_CODE – currency of the batch.
• DATE_DEPOSIT and DATE_GL_REQUESTED – deposit and GL request dates.
• TRX_STATUS_CODE – the transaction status code of the batch, most commonly queried to determine whether the batch has been transferred to GL, is pending, or has encountered an error.
• IRM_ID and ORG_ID – implementation/receipt method and operating unit identifiers used for multi-org filtering.
• CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_DATE – currency conversion attributes carried forward from the batch view.

Common Use Cases and Queries

A frequent requirement is identifying batches whose transaction status indicates the GL transfer has not completed. For example:

• SELECT id, name, batch_qty, batch_total, currency_code, trx_status_code FROM okl_bpd_btch_cont_sumry_uv WHERE trx_status_code = 'PROCESSED';
• SELECT id, trx_status_code, date_deposit, date_gl_requested FROM okl_bpd_btch_cont_sumry_uv WHERE date_gl_requested IS NULL AND org_id = :p_org_id;
• SELECT currency_code, trx_status_code, COUNT(*) FROM okl_bpd_btch_cont_sumry_uv GROUP BY currency_code, trx_status_code;

These queries support batch reconciliation, GL transfer monitoring, and status dashboards, while the currency conversion columns enable reporting for batches transacted in a foreign currency.