Results for “okl_cure_refund_stage_v”

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

Overview

OKL_CURE_REFUND_STAGE_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Lease and Finance Management) product. Its documented purpose is to serve as a staging area of cured contracts that need to be refunded. In the leasing workflow, a contract moves through delinquency and cure processing; when a contract has been cured and a refund becomes due to the lessee or counterparty, the associated record is staged so that downstream refund processing can identify and act upon it. The view exposes this staging data in a stable, read-only shape suitable for concurrent programs, extract routines, BI Publisher reports, and integration interfaces, shielding consumers from direct DML against the underlying transactional table.

Underlying Base Objects

The view is a thin projection defined over the table OKL_CURE_REFUND_STAGE, referenced through the synonym of the same name. There is no join, aggregation, or filter logic: the view text selects the same column list from OKL_CURE_REFUND_STAGE CRS, prepending the table ROWID as an aliased column named ROW_ID. This one-to-one structural correspondence means every row in the view maps to exactly one staging row in the base table, and no data transformation or derivation is applied. Because it is defined only over a base object owned within the OKL schema, it inherits the standard Oracle EBS multi-org and security considerations of that table. The view status is documented as VALID and it participates in the normal dependency chain for grant and synonym management performed by the APPS schema.

Key Columns

The column set combines business identifiers, monetary values, an object version, a vendor reference, and standard EBS audit and descriptive-flexfield columns. Notably, the view exposes RECEIVED_AMOUNT, the field most commonly referenced by users searching for refund receipt totals. Key columns include:

• CURE_REFUND_STAGE_ID — primary identifier of the staged cure-refund record.
• ROW_ID — the base table ROWID, useful for precise row addressing.
• STATUS — processing state of the staged refund, controlling whether it is pending or complete.
• NEGOTIATED_AMOUNT — amount agreed during cure negotiation.
• RECEIVED_AMOUNT — amount actually received in respect of the refund; central to reconciliation queries.
• CHR_ID — identifier linking the record to the associated contract history or contract header reference.
• VENDOR_ID — supplier or payee party associated with the refund.
• OBJECT_VERSION_NUMBER — optimistic locking version, incremented on each update.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program execution context that last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for customer-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical use is to list staged cure refunds, filter by status, or reconcile negotiated against received amounts. For example, to retrieve refunds where the received amount differs from the negotiated amount:

• SELECT CURE_REFUND_STAGE_ID, STATUS, NEGOTIATED_AMOUNT, RECEIVED_AMOUNT, VENDOR_ID FROM OKL_CURE_REFUND_STAGE_V WHERE RECEIVED_AMOUNT <> NEGOTIATED_AMOUNT;
• SELECT CURE_REFUND_STAGE_ID, CHR_ID, RECEIVED_AMOUNT FROM OKL_CURE_REFUND_STAGE_V WHERE STATUS = 'PENDING';
• SELECT STATUS, COUNT(*), SUM(RECEIVED_AMOUNT) FROM OKL_CURE_REFUND_STAGE_V GROUP BY STATUS;

Because the view performs no joins, it can be safely joined to contract and vendor tables using CHR_ID and VENDOR_ID for enriched reporting. All access is read-only; inserts or updates must target the base table through supported OKL APIs.