Results for “ctr_hdr”

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

Overview

APPS.OKL_CS_AMORT_SCHEDULES_UV is a supplementary view in the Oracle EBS ETRM (Enterprise Contracts / Oracle Lease and Finance Management) module. It belongs to the OKL schema design data set (FND Design Data: OKL.OKL_CS_AMORT_SCHEDULES_UV) and is owned by the APPS schema. The view presents a consolidated, form-friendly projection of lease and loan contract amortization schedules, exposing the periodic payment stream broken down into principal, interest, accrual, and balance components. Its primary role is to simplify forms coding in the Contracts and Lease Management stack rather than to serve as a public reporting interface.

Oracle explicitly warns that this is a supplementary view intended to simplify forms coding, and recommends against querying or altering data through it because its definition may change dramatically in subsequent minor or major releases. Consumers should therefore treat it as an internal, version-sensitive object and validate any dependency against the specific patch level in use (12.1.1 or 12.2.2).

Underlying Base Objects

The view is defined over a mix of contract header and line views, a utility package, and three specialized amortization sub-views:

• OKC_K_HEADERS_V (VIEW) — Contract header information, including contract number and identifying attributes.
• OKC_K_LINES_V (VIEW) — Contract line details that anchor the schedule rows to specific contract lines.
• OKC_UTIL (PACKAGE) — Shared utility logic used across the OKL schedule views (for example, currency and date handling).
• OKL_CS_SCHINTR_PAYMENTS_UV (VIEW) — Interest component of scheduled payments.
• OKL_CS_SCHPRINC_PAYMENTS_UV (VIEW) — Principal component of scheduled payments.
• OKL_CS_SCHPRINC_BALANCE_UV (VIEW) — Principal balance carried forward across the schedule.

The view is not referenced by any other database object, confirming its role as a terminal, presentation-layer object for forms. It combines the header/line context from OKC with the schedule detail from the OKL sub-views to yield one row per scheduled due date.

Key Columns

• ID (NUMBER, mandatory) — Primary key column for the view row.
• CONTRACT_NUMBER (VARCHAR2(120)) — Contract number from the OKC header/line context.
• DUE_DATE (DATE) — The scheduled payment due date.
• TOTAL_PAYMENT (NUMBER) — The total scheduled payment amount for the period. This is the column most commonly searched for; it represents the aggregate of the principal and interest components.
• PRINCIPAL_PAYMENT (NUMBER) — The principal portion of the scheduled payment.
• INTEREST_AMOUNT (NUMBER) — The interest portion of the scheduled payment.
• PRINCIPAL_BALANCE (NUMBER) — The outstanding principal balance associated with the schedule period.
• ACCRUAL_AMOUNT (NUMBER) — Accrued amount for the period.
• CURRENCY_CODE (VARCHAR2(15)) — Currency of the monetary amounts.
• KLE_ID (NUMBER) — Identifier linking the row to the contract line element.
• STREAM_ELEMENT_DATE (DATE) — Date of the underlying stream element driving the schedule row.

Common Use Cases and Queries

Typical use is within ETRM forms and diagnostics that need a flattened amortization schedule per contract. A representative query to retrieve total payments for a contract ordered by due date:

• SELECT contract_number, due_date, total_payment, principal_payment, interest_amount, principal_balance, currency_code FROM apps.okl_cs_amort_schedules_uv WHERE contract_number = :p_contract ORDER BY due_date;
• Reconciling TOTAL_PAYMENT against PRINCIPAL_PAYMENT + INTEREST_AMOUNT to validate schedule integrity.
• Summing TOTAL_PAYMENT per contract to derive total scheduled cash flow.

Because Oracle documents this view as form-support only and subject to change, reporting solutions should preferably target the three underlying OKL_CS_SCH* views or certified ETRM reporting objects instead of embedding a hard dependency on OKL_CS_AMORT_SCHEDULES_UV.