Results for “okl_cure_amounts_v”

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

Overview

OKL_CURE_AMOUNTS_V is a reporting view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. It exposes cure and repurchase amounts generated per contract per period, providing a read-oriented interface to the transactional data held for lease contracts managed under Oracle Lease Management. In Release 12.1.1 and 12.2.2, this view is primarily consumed by reporting, inquiry, and integration components that need to evaluate the financial exposure of a contract in a cure or repurchase situation without directly querying the base transaction table.

The view is documented as storing cure and repurchase amounts generated per contract per period. In practical terms, it surfaces the amounts a lessee would need to pay to cure a default, alongside the repurchase amounts associated with the contract, and the resulting outstanding and past-due balances. Because the view includes the OUTSTANDING_AMOUNT column, it is frequently referenced by reports and extracts that resolve a user's search for "outstanding_amount" on a lease contract. The view also carries standard EBS audit and multi-org columns, making it suitable for integration and reconciliation routines.

Underlying Base Objects

The documented view definition selects exclusively from OKL_CURE_AMOUNTS, using the alias CAM. The view is therefore a thin projection over a single base table; it does not join to contract, customer, or period tables. The view text maps each base table column to an identically named view column, with CAM.ROWID exposed as ROW_ID. All attribute columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15), the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), the concurrent request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), and the multi-org column (ORG_ID) are passed through unchanged.

The ETRM metadata for Release 12.2.2 records no additional referenced base objects beyond OKL_CURE_AMOUNTS, and the object is noted as not implemented in the documentation database from which the excerpt was drawn. Any enrichment of contract-level context (such as contract number or customer name) must therefore be obtained by joining to contract header tables such as OKL_HEADERS via the CHR_ID column.

Key Columns

• CURE_AMOUNT_ID — Primary identifier for the cure amount record.
• CHR_ID — Contract header identifier linking the record to a lease contract.
• CURE_TYPE — Classification of the cure event.
• CURE_AMOUNT — Amount required to cure the contract.
• REPURCHASE_AMOUNT — Repurchase amount associated with the contract.
• EFFECTIVE_DATE — Date on which the cure or repurchase amount takes effect.
• TIMES_CURED — Number of times the contract has been cured.
• PAYMENTS_REMAINING — Remaining payment count on the contract.
• ELIGIBLE_CURE_AMOUNT — Portion of the balance eligible for cure.
• OUTSTANDING_AMOUNT — The outstanding balance against the contract for the period; this is the column most commonly targeted by searches referencing outstanding_amount.
• PAST_DUE_AMOUNT — Amount that is past due on the contract.
• CURES_IN_POSSESSION — Indicator of cures held in possession.
• STATUS — Status of the cure amount record.
• ORG_ID — Operating unit identifier supporting multi-org security.
• OBJECT_VERSION_NUMBER — Optimistic locking version for the row.

Common Use Cases and Queries

Typical scenarios include retrieving the outstanding cure balance for a contract, listing all cure records for an operating unit, and identifying contracts with past-due cure amounts for collections or investor reporting. Integration programs frequently extract these rows into a downstream data warehouse or investor reporting system. Because the view exposes ROW_ID and OBJECT_VERSION_NUMBER, it can also support update-orchestration logic in custom code that must correlate view rows back to their base table rows.

The following query returns outstanding, past-due, and eligible cure amounts for a specific contract:

• SELECT chr_id, cure_type, effective_date, eligible_cure_amount, outstanding_amount, past_due_amount, status FROM okl_cure_amounts_v WHERE chr_id = :p_chr_id ORDER BY effective_date;

To summarize outstanding exposure by operating unit for a given period:

• SELECT org_id, SUM(outstanding_amount) outstanding_total, SUM(past_due_amount) past_due_total FROM okl_cure_amounts_v WHERE effective_date BETWEEN :p_from AND :p_to GROUP BY org_id;

To locate contracts with a nonzero outstanding amount requiring attention:

• SELECT chr_id, cure_amount_id, outstanding_amount FROM okl_cure_amounts_v WHERE outstanding_amount > 0 AND status = :p_status ORDER BY outstanding_amount DESC;

Because the view is a direct projection of OKL_CURE_AMOUNTS, query performance depends largely on the indexing present on that base table; predicates on CHR_ID, ORG_ID, and EFFECTIVE_DATE are the most effective filters for restricting the result set.