Results for “cnr_id”

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

Overview

The OKL_BPD_RECEIPT_DETAILS_UV view is a reporting and integration object owned by the APPS schema within Oracle E-Business Suite, delivered as part of the OKL - Lease and Finance Management product family. It consolidates receipt and application information originating from Oracle Receivables and links it to the consolidated Accounts Receivable streams held in Lease and Finance Management (OKL) tables. The view is classified as a User View (the _UV suffix), indicating that it is exposed for customer-facing reporting, inquiry, and integration use rather than being reserved for internal processing. In EBS 12.1.1 and 12.2.2 the object is shipped with a status of VALID.

The view is particularly relevant to users and developers who work with the receipt_method attribute, since it exposes the receipt method name directly and joins to the AR_RECEIPT_METHODS table on RECEIPT_METHOD_ID. This makes it a convenient single source for reporting how lease-related receipts were tendered, applied, and dated.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over five referenced base objects, all accessed through APPS-owned synonyms: AR_CASH_RECEIPTS_ALL (SYNONYM), AR_PAYMENT_SCHEDULES_ALL (SYNONYM), AR_RECEIPT_METHODS (SYNONYM), AR_RECEIVABLE_APPLICATIONS_ALL (SYNONYM), and OKL_CNSLD_AR_STRMS_B (SYNONYM).

The join relationships are explicit in the view text. OKL_CNSLD_AR_STRMS_B (aliased CNSLD) connects to AR_PAYMENT_SCHEDULES_ALL (PMTSCH) on RECEIVABLES_INVOICE_ID = CUSTOMER_TRX_ID. AR_RECEIVABLE_APPLICATIONS_ALL (ARAPP) links to PMTSCH via APPLIED_PAYMENT_SCHEDULE_ID = PAYMENT_SCHEDULE_ID, and to AR_CASH_RECEIPTS_ALL (ARCASH) via CASH_RECEIPT_ID. AR_RECEIPT_METHODS (ARRCPT) joins to ARCASH on RECEIPT_METHOD_ID. The transaction class is restricted with PMTSCH.CLASS = 'INV', so only invoice-class payment schedules are returned.

Key Columns

• CHECK_NUMBER — sourced from ARCASH.RECEIPT_NUMBER; the receipt number, labelled as the check reference.
• CURRENCY_CODE — the currency of the cash receipt.
• RECEIPT_DATE — the date the receipt was entered or received.
• RECEIPT_METHOD — sourced from ARRCPT.NAME; the receipt method name (for example, bank transfer or check) that answers the common receipt_method search.
• REMITTANCE_AMOUNT — ARCASH.AMOUNT, the gross receipt amount.
• GL_DATE — NVL(ARAPP.GL_POSTED_DATE, SYSDATE); the accounting date, defaulting to the current date when the application has not been posted.
• AMOUNT_APPLIED — ARAPP.AMOUNT_APPLIED, the portion of the receipt applied to the schedule.
• CNR_ID — CNSLD.ID, the consolidated AR stream identifier linking back to the OKL contract or stream record.

Common Use Cases and Queries

Typical uses include lease receipt reconciliation, receipt method analysis, and feeding downstream integrations or extract programs.

To list receipts by method for a given period:

• SELECT check_number, receipt_method, receipt_date, remittance_amount, amount_applied, gl_date, cnr_id FROM apps.okl_bpd_receipt_details_uv WHERE receipt_date BETWEEN :from_date AND :to_date ORDER BY receipt_date;

To analyze applied values grouped by receipt method:

• SELECT receipt_method, currency_code, SUM(remittance_amount) remitted, SUM(amount_applied) applied FROM apps.okl_bpd_receipt_details_uv GROUP BY receipt_method, currency_code;

Because the view is read-only and its joins are pre-defined, it can be queried directly for reporting without re-creating the underlying Receivables join logic.