Results for “okl_cure_payment_lns_all”

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

Overview

OKL_CURE_PAYMENT_LNS_ALL is a transactional table in the OKL (Lease and Finance Management) schema of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. Its stated purpose is to store line-level information for OKL CURE PAYMENTS — the financial records generated when a delinquent or problem lease contract is brought back into good standing ("cured") through payment, refund, or adjustment activity. Where the header tables capture the overall cure event, this table holds the individual detail rows that make up each cure payment, linking that detail to the originating transaction, the related receivable invoice, and the contract itself.

Under the heuristic Data Vault classification mined from its foreign-key structure, the table is satellite-leaning. This is a modeling suggestion rather than a physical design statement: because the table carries descriptive and status attributes (amounts, flags, approval fields) around a set of foreign keys, it behaves more like a satellite describing a business event than a pure hub or link. In practice, implementers should treat it as a detail/child table of the cure payment header and a dependent of the contract and receivables invoice entities.

Key Information Stored

The documented physical schema exposes 41 columns. The most significant are:

• CURE_PAYMENT_LINE_ID — the surrogate primary key and unique identifier for each cure payment line.
• CURE_PAYMENT_ID — foreign key to OKL_CURE_PAYMENTS_B, tying the line to its parent cure payment header; this is the principal join path and a business-key candidate in combination with the line identifier.
• AMOUNT — the monetary value applied on this line.
• CHR_ID — reference to the contract (charge/contract header) against which the cure is being applied.
• TRANSACTION_ID — the lease transaction from which the cure payment originates.
• TAI_ID — foreign key to OKL_TRX_AR_INVOICES_B, identifying the related Oracle Receivables invoice for the line.
• CURE_REFUND_ID — identifies a refund associated with the cure line, where the cure produces a credit back to the lessee.
• CURED_FLAG and STATUS — indicate whether the line has been fully cured and its current workflow status.
• APPROVAL_STATUS and APPROVAL_REASON — capture the outcome and justification of approval processing, which is often subject to internal controls.
• PROCESS_STATUS and PROCESS_STATUS_2 — concurrent program processing state flags used by the cure batch processes.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking token.
• ORG_ID — the multi-org operating unit identifier, essential for any secured reporting.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY — the standard EBS audit columns.

Common Use Cases and Queries

Typical usage includes reconciliation of cure activity against open receivables, approval audit reporting, and exception monitoring where lines remain in a non-cured or pending status. A common join pattern links the line to its header and the receivables invoice:

• Join OKL_CURE_PAYMENT_LNS_ALL to OKL_CURE_PAYMENTS_B on CURE_PAYMENT_ID = CURE_PAYMENT_ID.
• Join to OKL_TRX_AR_INVOICES_B on TAI_ID = TAI_ID to retrieve invoice detail.
• Filter by ORG_ID and STATUS to report outstanding, uncured lines by operating unit.
• Aggregate SUM(AMOUNT) grouped by CHR_ID for contract-level cure totals.
• Query APPROVAL_STATUS and APPROVAL_REASON for audit and SOX-style control reporting.
• Monitor PROCESS_STATUS columns after running the cure concurrent programs to detect failures.

Related Objects

• OKL_CURE_PAYMENTS_B — parent header table joined on CURE_PAYMENT_ID.
• OKL_CURE_PAYMENT_LINES — related cure payment line entity referenced via CURE_PAYMENT_LINE_ID.
• OKL_TRX_AR_INVOICES_B — receivables invoice table joined on TAI_ID.
• Contract and transaction tables in the OKL schema referenced through CHR_ID and TRANSACTION_ID.
• Standard EBS audit and multi-org components relying on CREATED_BY, LAST_UPDATED_BY, and ORG_ID.

The table is proprietary Oracle documentation; schema and column details should be validated against the specific 12.1.1 or 12.2.2 instance in use.