Results for “okl_cure_payment_lines_v”

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

Overview

OKL_CURE_PAYMENT_LINES_V is an Oracle Lease and Finance Management (OKL) view that exposes line-level detail for CURE payment transactions. Within the ETRM 12.1.1 / 12.2.2 data model, CURE payments represent cure amounts applied against delinquent or non-performing lease contracts, and this view provides the individual payment lines that make up each cure payment header. Its documented purpose is to store and present the granular information associated with OKL CURE payments at the line level, which supports reconciliation, approval tracking, refund handling, and downstream accounting.

The view is a thin projection over the base table OKL_CURE_PAYMENT_LINES, aliased as CPN in the view text. It exposes the base table's ROWID as ROW_ID and surfaces the majority of the table's columns without joins, filters, or transformations. Because the view is not implemented in the current database per the ETRM metadata, references to it should be validated against the target instance before use in production reporting or integrations.

Underlying Base Objects

The view is defined solely over OKL_CURE_PAYMENT_LINES. No additional base tables, lookup joins, or security predicates are documented in the view text. Every column in the SELECT list maps directly to a column of the base table, with the exception of ROW_ID, which is derived from CPN.ROWID. Consequently, the view does not itself enforce operating unit or status filtering; ORG_ID is exposed as a stored column rather than applied as a predicate.

Because there is a one-to-one correspondence between view columns and base table columns, the view inherits the base table's performance characteristics. Queries filtering on CURE_PAYMENT_ID, CHR_ID, TRANSACTION_ID, RCT_ID, or ORG_ID should benefit from the indexes defined on the underlying table.

Key Columns

• ROW_ID — The physical ROWID of the underlying OKL_CURE_PAYMENT_LINES row, useful for direct row identification.
• CURE_PAYMENT_LINE_ID — Primary identifier of the cure payment line.
• CURE_PAYMENT_ID — Foreign key linking the line to its parent CURE payment header.
• CHR_ID — Reference to the contract or charge associated with the cure activity.
• AMOUNT — Monetary value of the individual cure payment line.
• CURED_FLAG — Indicates whether the line has been cured.
• STATUS — Current processing status of the line.
• RCT_ID — Reference to the associated receipt.
• CURE_REFUND_ID — Reference to any refund generated from the cure payment.
• TRANSACTION_ID — Link to the transaction generated for the line.
• APPROVAL_REASON — Captures the reason recorded when the line is approved or rejected, supporting audit and workflow review.
• APPROVAL_STATUS — Approval state of the line (for example, approved, rejected, or pending).
• TAI_ID — Identifier for the associated transaction account interface record.
• PROCESS_STATUS — Indicates the line's position in the processing lifecycle.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the application.
• ORG_ID — Operating unit that owns the line, central to multi-org filtering.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent program audit columns identifying the process that last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns available for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard who-column audit trail.

Common Use Cases and Queries

Typical applications include reporting on cure payment line status, tracking approval outcomes, reconciling cure amounts against receipts and refunds, and feeding downstream accounting or integration extracts.

To list all lines for a given cure payment:

• SELECT cure_payment_line_id, amount, status, approval_status, approval_reason FROM okl_cure_payment_lines_v WHERE cure_payment_id = :p_cure_payment_id;

To review approval activity by operating unit:

• SELECT org_id, approval_status, approval_reason, COUNT(*) FROM okl_cure_payment_lines_v GROUP BY org_id, approval_status, approval_reason;

To identify lines pending processing for a concurrent request:

• SELECT cure_payment_line_id, process_status, request_id FROM okl_cure_payment_lines_v WHERE process_status = :p_status AND org_id = :p_org_id;

Because the view contains no built-in filters, queries should always include ORG_ID or a parent identifier such as CURE_PAYMENT_ID to constrain result sets.