Results for “okl_cure_refunds_v”

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

Overview

The OKL_CURE_REFUNDS_V view belongs to the Oracle Lease and Finance Management (OKL) module, part of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. The view presents refund transactions made to a vendor for cured contracts. In lease and finance workflows, a contract may default and subsequently be "cured" — that is, brought back into good standing after the lessee remedies the default. When a cure process results in a monetary adjustment owed back to the originating vendor or lessor party, an OKL cure refund record is created and tracked. This view exposes those refund records for reporting, inquiry, and integration purposes.

Because the view is a thin passthrough over the OKL_CURE_REFUNDS base table, it inherits the standard Oracle EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the descriptive flexfield column set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15). The DBA documentation notes the object is "Not implemented in this database," meaning the view exists as shipped metadata but may not be compiled in every environment. Practitioners should verify existence with ALL_VIEWS or USER_VIEWS before referencing it in code.

Underlying Base Objects

The view is defined over a single base table, OKL_CURE_REFUNDS (aliased CRF in the view text). No other tables, joins, or aggregate sources are documented; the SELECT projects columns directly from that one table and derives ROW_ID from CRF.ROWID. Consequently, the view is read-mostly and DML against it would only be meaningful through an INSTEAD-OF trigger or by operating on the base table directly. The absence of documented referenced base objects beyond OKL_CURE_REFUNDS is consistent with the passthrough definition shown in the view text.

Key Columns

The column most relevant to the user's search — TOTAL_REFUND_DUE — captures the full refund amount owed on the cure transaction. It should be distinguished from related monetary columns: AMOUNT (the refund amount recorded), BALANCE (the outstanding remainder), and DISBURSEMENT_AMOUNT (the portion actually disbursed).

• CURE_REFUND_ID — primary key identifying the refund record.
• REFUND_NUMBER — user-facing refund document number.
• STATUS — lifecycle state of the refund (for example pending, processed, or applied).
• TAP_ID — link to the transaction/application record driving the cure.
• VENDOR_SITE_ID — vendor site receiving the refund.
• CHR_ID — contract/header reference associated with the cure.
• REFUND_DATE — date the refund was issued or recognized.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program execution context.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — descriptive flexfield storage.

Common Use Cases and Queries

Typical uses include cure refund reconciliation, vendor refund aging, and downstream integration extracts. A minimal query retrieving refunds still owed and older than a cutoff is shown below.

SELECT CURE_REFUND_ID, REFUND_NUMBER, VENDOR_SITE_ID, CHR_ID, TOTAL_REFUND_DUE, BALANCE, REFUND_DATE FROM OKL_CURE_REFUNDS_V WHERE TOTAL_REFUND_DUE > 0 AND STATUS NOT IN ('CLOSED') AND REFUND_DATE < SYSDATE - 30 ORDER BY REFUND_DATE;

A second pattern isolates fully disbursed refunds by comparing disbursed and total amounts, useful for audit trails confirming that TOTAL_REFUND_DUE equals DISBURSEMENT_AMOUNT once processing completes.