Results for “okl_trx_csh_batch_v”

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

Overview

OKL_TRX_CSH_BATCH_V is a reporting and integration view owned by the APPS schema in Oracle Lease and Finance Management (OKL). It presents a denormalized, language-resolved representation of manual cash receipt batches entered through Oracle Lease Management. The view exposes batch-level header information—status, quantities, totals, currency, deposit and GL request dates, and descriptive flexfield attributes—for each cash receipt batch processed in the OKL module.

Because the underlying transaction tables store batch headers and translations separately, the view provides a single logical row per batch per session language, making it suitable for concurrent program output, custom reports, and inbound/outbound interfaces. In the context of the user search term "date_entered," the view exposes DATE_ENTERED directly, allowing users to filter and report on the date a batch was originally entered into the system. The view is defined as VALID in the ETRM repository and is available in both EBS 12.1.1 and 12.2.2 environments, with object naming and structure remaining consistent across these releases.

Underlying Base Objects

The view is defined over two base objects, both referenced through synonyms in the APPS schema:

• OKL_TRX_CSH_BATCH_B — the base table holding batch header data, including batch identifiers, status, dates, totals, currency, and DFF attributes.
• OKL_TRX_CSH_BATCH_TL — the translation table storing language-specific batch names and descriptions.

The join condition is BTCB.ID = BTCT.ID AND BTCT.LANGUAGE = USERENV('LANG'), ensuring that the NAME and DESCRIPTION returned are rendered in the session's current language. The view also surfaces BTCB.ROWID as ROW_ID, which supports downstream processing that requires a row identifier. No additional joins or filters are applied, so the view returns all batch rows visible to the querying user based on standard EBS security and org context.

Key Columns

• ID / ROW_ID / OBJECT_VERSION_NUMBER — primary identifier, physical row identifier, and optimistic locking version for the batch header.
• NAME / DESCRIPTION — language-resolved batch name and description from the translation table.
• TRX_STATUS_CODE — current status of the cash receipt batch in the OKL transaction workflow.
• DATE_ENTERED — the date the batch was entered, applicable directly to the user's search context. This is a key filter and reporting column.
• DATE_GL_REQUESTED / DATE_DEPOSIT — the date GL posting was requested and the deposit date associated with the batch.
• BATCH_QTY / BATCH_TOTAL / BATCH_CURRENCY — count of receipts in the batch, summed amount, and the batch currency.
• BATCH_COMPLETE_YN / SFWT_FLAG — completion indicator and a flag used in OKL processing logic.
• IRM_ID / REMIT_BANK_ID — identifiers linking the batch to the instrument/remittance and remittance bank.
• CURRENCY_CONVERSION_TYPE / RATE / DATE — currency conversion attributes applied to the batch.
• ATTRIBUTE1–ATTRIBUTE15 / ATTRIBUTE_CATEGORY — descriptive flexfield columns for extensible batch metadata.
• ORG_ID — operating unit context for multi-org filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns.

Common Use Cases and Queries

Typical uses include reconciliation of manual cash receipt batches, audit reports by entry date, GL posting tracking, and integration extracts. A common query filters by DATE_ENTERED for a reporting period:

• SELECT id, name, trx_status_code, date_entered, batch_qty, batch_total, batch_currency FROM okl_trx_csh_batch_v WHERE date_entered BETWEEN :start_date AND :end_date AND org_id = :org_id ORDER BY date_entered DESC;
• SELECT id, name, date_entered, date_gl_requested, date_deposit, batch_complete_yn FROM okl_trx_csh_batch_v WHERE trx_status_code = 'ENTERED' AND batch_complete_yn = 'N';
• SELECT b.id, b.name, b.batch_total, b.batch_currency, b.attribute1 FROM okl_trx_csh_batch_v b WHERE b.date_entered >= TRUNC(SYSDATE) - 30;

Because the tl join is resolved by USERENV('LANG'), any query executed in a multilingual environment returns names and descriptions in the session language, making the view suitable for localized reporting without additional translation lookups.