Results for “okl_cure_received_uv”

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

Overview

OKL_CURE_RECEIVED_UV is an Oracle E-Business Suite database view owned by the APPS schema and defined in the OKL (Lease and Finance Management) product module. Its documented description is "Cures grouped by contract," which precisely describes its purpose: it aggregates cure payment amounts at the contract header level rather than at the individual cure transaction level. In the context of lease and finance management, a "cure" represents a payment made by a lessee to reinstate a delinquent or defaulted contract, and the OKL_CURE_AMOUNTS entity stores the individual cure amount records. This view summarizes those records so that one row is returned per contract, presenting the total amount received through cures for that contract.

The view carries VALID status in both Oracle EBS 12.1.1 and 12.2.2. As a read-only reporting view, it plays a supporting role in Oracle EBS reporting and integration: it simplifies query logic for downstream reports, concurrent programs, and integration interfaces that need a single summarized cure figure per contract without performing their own GROUP BY aggregation. The "_UV" suffix follows the common Oracle EBS naming convention for a user view, indicating it is intended for consumption by applications and reporting tools rather than being a base transactional object.

Underlying Base Objects

The view is defined over a single documented base object, OKL_CURE_AMOUNTS, referenced through a synonym. The view text is straightforward:

• SELECT CHR_ID, SUM(RECEIVED_AMOUNT) FROM OKL_CURE_AMOUNTS CAM WHERE 1=1 GROUP BY CHR_ID

The WHERE 1=1 clause is a conventional placeholder used in Oracle EBS view definitions; it is logically a no-op condition that leaves the result set unconstrained. The defining operation is therefore a GROUP BY on the CHR_ID column (contract header identifier) with a SUM aggregation of RECEIVED_AMOUNT. Since the view collapses many cure amount rows into one row per contract, it inherits no filtering or row-level security of its own and exposes the full aggregate for each contract present in OKL_CURE_AMOUNTS.

Key Columns

The view exposes two documented columns:

• CHR_ID — The contract header identifier. This is the grouping key for the view and the foreign key linking each summarized row to a specific lease or finance contract in the OKL contract tables. It is the natural join column when this view is combined with other contract-level entities.
• CURES_RECEIVED — The aggregated sum of RECEIVED_AMOUNT from OKL_CURE_AMOUNTS for the associated contract. This column represents the total cure amount received for the contract across all its cure transactions. Note that the underlying column is RECEIVED_AMOUNT, while the view renames the aggregate output to CURES_RECEIVED to reflect its summarized nature.

Common Use Cases and Queries

Typical uses center on contract-level reporting of cure activity, reconciliation of amounts received against cure obligations, and integration extracts that need one cure total per contract. Representative queries include retrieving the cure total for a specific contract, or joining the view to the contract header table to enrich the summary with contract attributes.

• Single contract lookup:
  SELECT chr_id, cures_received FROM okl_cure_received_uv WHERE chr_id = :p_chr_id;
• Joining to the contract header for descriptive reporting:
  SELECT h.chr_id, h.contract_number, u.cures_received FROM okl_cure_received_uv u, okl_contract_headers h WHERE u.chr_id = h.chr_id ORDER BY u.cures_received DESC;
• Identifying contracts with cure activity:
  SELECT chr_id, cures_received FROM okl_cure_received_uv WHERE cures_received > 0;

Because the view has no effective filtering predicate, it returns every contract header represented in OKL_CURE_AMOUNTS. Queries should therefore apply their own date, status, or organizational filters by joining to the appropriate OKL tables if a narrower result set is required.