Results for “okl_bpd_btch_sumry_uv”

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

Overview

The APPS.OKL_BPD_BTCH_SUMRY_UV view is a reporting and integration construct within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents a consolidated summary of lease cash receipt batches processed through the Batch Processing Detail (BPD) engine, expressing batch header attributes alongside status, currency, receipt method, and consolidated invoice context. The view is implemented as a UNION of two query blocks. The first block returns batches associated with a consolidated AR header (CNR_ID is not null), and the second block returns batches associated with a contract header (CHR_ID), where CNR_ID and CONSOLIDATED_INVOICE_NUMBER are nulled out. A constant column TYPE with value 'CONS' identifies the first branch. The view thereby serves as a single reporting surface for batch-level lease cash activity regardless of whether the batch relates to a consolidated invoice or a lease contract header.

Underlying Base Objects

Documented base objects include OKL_TRX_CSH_BATCH_V and OKL_TRX_CSH_RECEIPT_V, the primary drivers of batch and receipt detail. OKL_TXL_RCPT_APPS_V provides the applications receipt link and carries the KHR_ID (contract header) and CNR_ID (consolidated header) references. AR_RECEIPT_METHODS supplies the receipt method name via IRM_ID, FND_LOOKUPS resolves the batch status from TRX_STATUS_CODE for lookup type OKL_BATCH_RULES_SEARCH_TYPE, and OKL_CNSLD_AR_HDRS_B supplies the consolidated invoice number. OKC_K_HEADERS_B supports the contract header branch, and FND_GLOBAL is referenced for environment context. The view is owned by APPS and joins these objects through equality on batch ID, receipt ID, receipt method ID, consolidated header ID, and lookup code.

Key Columns

• TRX_STATUS_CODE — The batch transaction status, for example WORKING; drives the derived UPDATE_STATUS and REMOVE_STATUS columns.
• BATCH_STATUS — The lookup meaning resolved from FND_LOOKUPS for the transaction status code.
• UPDATE_STATUS / REMOVE_STATUS — DECODE-derived flags: batches in WORKING return 'ENABLEDUPDATE'/'ENABLEDREMOVE', otherwise 'DISABLEDUPDATE'/'DISABLEDREMOVE'.
• ID, NAME, BATCH_QTY, BATCH_TOTAL — Batch identifier, description, receipt count, and monetary total.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — Currency and conversion attributes for the batch.
• DATE_DEPOSIT, DATE_GL_REQUESTED — Deposit and GL request dates for accounting timing.
• IRM_ID, RECEIPT_METHOD — Receipt method identifier and its AR name.
• CNR_ID, CONSOLIDATED_INVOICE_NUMBER — Consolidated AR header identity, populated only in the first UNION branch.
• CHR_ID, CONTRACT_NUMBER — Contract header identity, populated only in the second branch.
• ORG_ID — Operating unit for multi-org security.
• TYPE — Constant 'CONS' identifying consolidated-invoice batches.

Common Use Cases and Queries

Typical usage includes batch status reporting, receipt method analysis, and reconciliation of lease cash batches to consolidated invoices or contracts. Filtering on TRX_STATUS_CODE is the most frequent pattern, since the user search term indicates interest in transaction status.

SELECT id, name, batch_status, receipt_method,
       consolidated_invoice_number, contract_number,
       batch_total, currency_code
FROM   apps.okl_bpd_btch_sumry_uv
WHERE  trx_status_code = 'WORKING'
AND    org_id = :p_org_id;

A second common query determines actionable batches from the derived status columns:

SELECT id, name, update_status, remove_status, date_deposit
FROM   apps.okl_bpd_btch_sumry_uv
WHERE  update_status = 'ENABLEDUPDATE'
AND    date_gl_requested IS NULL;

Because the view is owned by APPS and references secured transactional tables, queries should be executed through the Apps schema or with the appropriate MO/ORG_ID security context applied. No DML is permitted against this object.