Results for “okl_cure_report_amounts_v”

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

Overview

The OKL_CURE_REPORT_AMOUNTS_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). Owned by the APPS schema and marked VALID in both 12.1.1 and 12.2.2, the view stores and exposes line-level information for the OKL_CURE_REPORTS table hierarchy. In the leasing lifecycle, a "cure" refers to the remediation of a contractual default — for example, a lessee making good on past-due obligations to restore an agreement to compliance. The view consolidates the amounts, cure counts, and status attributes necessary to evaluate cure eligibility, track cure history, and feed downstream reporting or integration processes such as delinquency dashboards, credit risk analysis, and automated notification workflows. Because it is implemented as a simple view over a single base table, it functions as a secured, presentation-oriented layer that shields callers from the physical column order while surfacing business-friendly column names (for example, ROW_ID in place of the physical ROWID) and limiting direct DML against the underlying entity.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over a single referenced base object: OKL_CURE_REPORT_AMOUNTS, accessed through a synonym. The view text confirms this, selecting exclusively from OKL_CURE_REPORT_AMOUNTS (aliased CRA) with no joins, unions, or aggregations. Consequently, the view is a direct projection: every row of the view corresponds one-to-one with a row of the base table, and no row filtering or transformation is applied. The table itself stores the line-level detail for the cure reporting process, while its parent OKL_CURE_REPORTS structure holds header-level context. Because the view mirrors its source table, any changes to the underlying record — updates to cure amounts, status transitions, or reprocessing by concurrent programs — are immediately visible through the view without materialization or refresh latency.

Key Columns

• CURE_REPORT_AMOUNT_ID — Primary identifier for the cure report amount line.
• CURE_AMOUNT_ID / CURE_REPORT_ID — Foreign keys linking the line to the parent cure amount and cure report records.
• REQUEST_TYPE — Classifies the nature of the cure request being reported.
• CURES_IN_POSSESSION — Indicates the number or state of cures held in possession at line level.
• CLAIMED_CURE_AMOUNT, PAST_DUE_AMOUNT, ELIGIBLE_CURE_AMOUNT — The core financial measures: what the lessee claims, what is overdue, and what qualifies for cure treatment.
• REPURCHASE_AMOUNT / OUTSTANDING_AMOUNT — Repurchase exposure and remaining balance figures used in residual and end-of-term analysis.
• TIMES_CURED — The count of prior cures applied, directly relevant to the search term "times_cured" and used to assess cure frequency and borrower behavior.
• PAYMENTS_REMAINING — Number of scheduled payments still outstanding.
• STATUS — Lifecycle state of the cure report amount line (for example, open or processed).
• ORG_ID — Multi-org operating unit discriminator; essential for row-level security in R12.
• Audit and concurrency columns — OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the Program/Request ID columns that relate the row to concurrent processing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield storage for client-specific extensions.

Common Use Cases and Queries

Typical consumption includes cure history reporting by lease or lessee, aging of eligible cure amounts, and reconciliation of claimed versus outstanding balances. Because TIMES_CURED captures repeated remediation activity, analysts frequently query the view to identify agreements with recurring defaults:

• SELECT cure_report_id, cure_amount_id, claimed_cure_amount, past_due_amount, eligible_cure_amount, times_cured, status FROM apps.okl_cure_report_amounts_v WHERE org_id = :p_org_id AND status = 'OPEN';
• SELECT cure_report_id, times_cured, SUM(eligible_cure_amount) eligible_total FROM apps.okl_cure_report_amounts_v GROUP BY cure_report_id, times_cured HAVING times_cured > 1;
• SELECT cra.claimed_cure_amount, cra.outstanding_amount, cra.payments_remaining FROM apps.okl_cure_report_amounts_v cra WHERE cra.cure_report_amount_id = :p_id;

As the view is read-only in practice, integrations should write to OKL_CURE_REPORT_AMOUNTS through supported APIs rather than attempting DML against the view.