Results for “chr_id”

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

Overview

The view OKL_RECONCILE_CURES_UV is a reporting object owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, delivered as part of the OKL – Leasing and Finance Management product family. Its name incorporates the "_UV" suffix, which conventionally designates a user-facing or reconciliation-oriented view intended to aggregate transaction data for display rather than for transactional processing.

Functionally, the view consolidates cure payment activity that has been classified with the status CURES_IN_POSSESSION. In leasing terminology, a "cure" represents a payment made by a lessee to bring a delinquent contract back into good standing. The CURES_IN_POSSESSION status indicates that the cure funds have been received and are being held by the lessor, pending reconciliation against the associated contract. The view therefore serves as a focused reconciliation dataset, allowing the collections, cash application, and lease accounting functions to determine the total cure amounts held per contract header.

Because the view is restricted to a single status value, it does not represent the complete cure payment population. It is a purpose-built slice that supports the reconciliation process for in-possession funds, providing a summarized monetary position per contract (CHR_ID).

Underlying Base Objects

According to the documented ETRM metadata for Release 12.2.2, OKL_RECONCILE_CURES_UV is defined over a single base object: the synonym OKL_CURE_PAYMENT_LINES. This table stores the individual payment line records generated when cure payments are captured against lease contracts. The view's defining query selects exclusively from this table and applies a filter on the STATUS column, retaining only rows where the status equals CURES_IN_POSSESSION.

The view then groups the qualifying rows by CHR_ID and sums the AMOUNT column, applying NVL(AMOUNT, 0) so that null amounts are treated as zero and do not distort the aggregate. Two additional positions are projected: NVL(NULL, 0) and a literal NULL. These evaluate to a constant zero and a null value respectively, indicating that the view was designed to satisfy a downstream interface or report requiring a fixed column shape where the AMOUNT_RECEIVED and CURED_FLAG columns are not populated from the base table at this stage of the reconciliation lifecycle.

Key Columns

• CHR_ID — The contract header identifier. This is the grouping key for the view and links each summarized cure amount back to its originating lease contract.
• AMOUNT — The aggregated sum of cure payment line amounts held in possession for the contract, with nulls coerced to zero.
• CURES_IN_POSSESSION — The status literal that defines the view's filter; it appears among the documented columns and denotes the reconciliation state of the underlying lines.
• AMOUNT_RECEIVED — Exposed as a constant zero in the view definition, reserved for a subsequently populated received-amount value.
• CURED_FLAG — Exposed as a null literal, intended to hold the indicator of whether the contract has been fully cured once reconciliation completes.

Common Use Cases and Queries

The view is typically consumed by reconciliation reports, cash application dashboards, and collection worklists that need to identify contracts holding unreconciled cure funds. The following query returns the total cure amount in possession for each contract:

• SELECT chr_id, amount FROM apps.okl_reconcile_cures_uv ORDER BY chr_id;
• SELECT SUM(amount) FROM apps.okl_reconcile_cures_uv; — obtains the total value of all cure funds currently in possession.
• SELECT c.chr_id, c.amount FROM apps.okl_reconcile_cures_uv c WHERE c.amount > 0; — isolates contracts with a positive held cure balance for follow-up.
• Joining the view to OKL_CURE_PAYMENT_LINES on CHR_ID supports drill-down from the summarized position to the individual payment lines.

Because the view applies aggregation and status filtering at the database layer, it is suited for direct inclusion in concurrent program data sources and Oracle Reports layouts where a compact, reconciled cure position per contract is required.