Results for “okl_cure_amounts_all”

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

Overview

The OKL_CURE_AMOUNTS_ALL table is a core transactional entity within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. Its documented purpose is to store cure and repurchase amounts generated per contract per period. In the context of lease servicing, a "cure" refers to the remediation of a contract default — typically a delinquent or non-performing lease — whereby the lessee or a third party brings the obligation back into good standing, or the lessor exercises a repurchase right. OKL_CURE_AMOUNTS_ALL captures the monetary values associated with these events, including cure amounts, repurchase amounts, past-due balances, and negotiated or received funds.

The table resides in the OKL schema and is present and valid in both EBS 12.1.1 and 12.2.2. Its documented physical schema comprises 49 columns, with the primary key OKL_CURE_AMOUNTS_ALL_PK defined on the surrogate column CURE_AMOUNT_ID. A unique index, OKL_CURE_AMOUNTS_ALL_U1, also covers CURE_AMOUNT_ID. Applying heuristic Data Vault modeling, the table is classified as hub-leaning: CURE_AMOUNT_ID behaves as a durable business key that anchors downstream references, while the substantial set of descriptive and financial columns functions as satellite-style attributes attached to that hub. This classification is a modeling suggestion derived from the FK structure rather than a documented Oracle design decision.

Key Information Stored

Among the 49 documented columns, the most functionally significant are the following:

• CURE_AMOUNT_ID — the surrogate primary key and the value referenced by dependent tables; it is also the business-key candidate covered by OKL_CURE_AMOUNTS_ALL_U1.
• CHR_ID — links the cure record to the underlying contract or charge identifier.
• CRT_ID and QTE_ID — foreign references to the associated contract and quote entities.
• CURE_TYPE — classifies the nature of the cure event.
• CURE_AMOUNT, REPURCHASE_AMOUNT, NEGOTIATED_AMOUNT, RECEIVED_AMOUNT, SHORT_FUND_AMOUNT, ELIGIBLE_CURE_AMOUNT, OUTSTANDING_AMOUNT, PAST_DUE_AMOUNT, DELINQUENT_AMOUNT — the financial measures that quantify the cure, repurchase, and delinquency position of the contract.
• TIMES_CURED, PAYMENTS_REMAINING, CURES_IN_POSSESSION — counters and eligibility indicators relevant to repeated cure activity.
• EFFECTIVE_DATE, STATUS, PROCESS, SHOW_ON_REQUEST, SELECTED_ON_REQUEST — temporal, lifecycle, and workflow-control attributes.
• ORG_ID — the multi-org operating unit discriminator.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and batch audit columns.
• Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the fifteen ATTRIBUTE flex columns support auditing, optimistic locking, and extensibility.

Common Use Cases and Queries

Typical scenarios include cure and repurchase reporting, delinquency aging, and reconciliation of amounts generated per contract per period. A straightforward reporting pattern joins the table to its dependent report-amounts table:

• SELECT ca.CURE_AMOUNT_ID, ca.CRT_ID, ca.CURE_TYPE, ca.CURE_AMOUNT, ca.REPURCHASE_AMOUNT, ca.STATUS FROM OKL_CURE_AMOUNTS_ALL ca WHERE ca.ORG_ID = :org_id AND ca.EFFECTIVE_DATE BETWEEN :from_date AND :to_date;
• SELECT ca.CURE_AMOUNT_ID, ra.* FROM OKL_CURE_AMOUNTS_ALL ca JOIN OKL_CURE_REPORT_AMTS_ALL ra ON ra.CURE_AMOUNT_ID = ca.CURE_AMOUNT_ID WHERE ca.CRT_ID = :contract_id;
• Aggregation of delinquency exposure: SUM(ca.PAST_DUE_AMOUNT), SUM(ca.OUTSTANDING_AMOUNT) grouped by ca.CURE_TYPE or ca.CHR_ID.

Because the table includes scheduled process columns, it is also useful for auditing which concurrent program generated a given cure amount and for tracing record versions via OBJECT_VERSION_NUMBER.

Related Objects

The documented relationship data identifies OKL_CURE_REPORT_AMTS_ALL as the dependent child table, joined on the CURE_AMOUNT_ID column (OKL_CURE_REPORT_AMTS_ALL.CURE_AMOUNT_ID references OKL_CURE_AMOUNTS_ALL). Additional related objects implied by the column names include the contract entity referenced through CRT_ID, the charge entity referenced through CHR_ID, and the quote entity referenced through QTE_ID, along with the OKL concurrent program infrastructure referenced through REQUEST_ID and PROGRAM_ID. Together these objects form the cure-and-repurchase processing chain within Oracle Lease and Finance Management.