Results for “date_gl_requested”

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

Overview

OKL_TRX_CSH_BATCH_ALL_B is a transactional table in the OKL (Leasing and Finance Management) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores batches of manual cash receipts entered through the OKL module, functioning as the header or grouping entity for individual receipt records captured during contract-related cash application. In the leasing and finance lifecycle, this table represents the batch-level control structure that consolidates receipts before they are processed for general ledger posting and deposit reconciliation.

From a Data Vault modeling perspective, the metadata's heuristic classification is hub-leaning. This suggests the table behaves primarily as a hub of unique batch identities, with the primary key ID serving as the durable business key candidate and foreign keys in downstream tables pointing back to it. The presence of descriptive attributes such as status, totals, and dates indicates it also carries some satellite-like characteristics, but its central role is establishing the batch entity around which receipt and contract-line references are organized.

Key Information Stored

The table contains 41 documented columns. The most operationally significant include:

• ID — Surrogate primary key (OKL_TRX_CSH_BATCH_ALL_B_PK); also exposed in the unique index OKL_TRX_CSH_BATCH_ALL_B_U1, making it the business-key candidate for batch identity.
• TRX_STATUS_CODE — Current processing state of the batch (for example entered, complete, or posted).
• BATCH_QTY and BATCH_TOTAL — Aggregated count and monetary value of receipts within the batch.
• BATCH_COMPLETE_YN — Flag indicating whether batch entry is finished.
• BATCH_CURRENCY — Currency in which the batch is denominated.
• DATE_ENTERED, DATE_DEPOSIT, DATE_GL_REQUESTED — Entry, deposit, and GL request dates driving accounting and treasury timing.
• CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — Conversion parameters when the batch currency differs from the functional currency.
• REMIT_BANK_ID — Remittance bank associated with the deposit.
• ORG_ID — Operating unit, enabling multi-org security and reporting.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — Concurrent program context for batch creation or processing.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Audit and optimistic locking.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — DFF extensibility.

Common Use Cases and Queries

Typical usage includes batch status monitoring, deposit and GL posting reconciliation, and reporting on cash application volumes by operating unit or currency. A common pattern joins the batch header to its receipts:

• Listing incomplete batches: SELECT id, batch_qty, batch_total FROM okl_trx_csh_batch_all_b WHERE batch_complete_yn = 'N';
• Reconciling receipt totals per batch against the header total via OKL_TRX_CSH_RCPT_ALL_B.BTC_ID.
• Reporting batches by operating unit and currency for treasury deposit analysis.
• Identifying batches created by specific concurrent programs using REQUEST_ID and PROGRAM_ID.

Related Objects

The FK metadata documents two downstream dependencies:

• OKL_TRX_CSH_RCPT_ALL_B — Individual cash receipts referencing the batch through BTC_ID; the primary child for receipt detail.
• OKL_TXL_CNTRCT_LNS_ALL — Contract line records referencing the batch through BTC_ID, linking cash batches to leasing contract lines.

These relationships, together with the batch totals and currency fields, form the core join path for cash receipt reporting and reconciliation in OKL.