Results for “principal_payment”

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

Overview

The view OKL_CS_AMORT_SCHEDULES_UV is an Oracle E-Business Suite (EBS) database object owned by the APPS schema and defined within the Oracle Lease and Finance Management (OKL) module. It presents a consolidated, per-line amortization schedule for lease and finance contracts, joining principal repayment activity, interest repayment activity, and outstanding principal balances onto a common stream element date. As a "UV" (user view) object, it is intended to expose a denormalized, report-friendly projection of contractual cash flows rather than to store transactional data itself.

Its principal role is to support reporting, inquiry, and integration scenarios where a complete amortization profile — total payment, principal portion, interest portion, and remaining principal balance — must be surfaced on a single row per contract line per due date. Because the view is defined entirely over other views and does not itself contain stored data, it behaves as a read-only analytical layer. This makes it well suited for ad hoc querying, custom reports, and interface extraction without risking modification to underlying lease accounting records.

The object carries a status of VALID, confirming that it compiles successfully against its referenced base objects in supported EBS releases including 12.1.1 and 12.2.2.

Underlying Base Objects

The documented metadata identifies several base objects over which the view is constructed:

• OKC_K_HEADERS_V (VIEW) — contract header information, supplying the contract ID, contract number, and currency code.
• OKC_K_LINES_V (VIEW) — contract line information, providing the join between the header and the line-level stream elements.
• OKL_CS_SCHPRINC_PAYMENTS_UV (VIEW) — scheduled principal payment amounts.
• OKL_CS_SCHINTR_PAYMENTS_UV (VIEW) — scheduled interest payment amounts.
• OKL_CS_SCHPRINC_BALANCE_UV (VIEW) — scheduled principal balance amounts.
• OKC_UTIL (PACKAGE) — a shared OKC utility package referenced in the dependency chain.

The view joins header and line records from the OKC contract views to the three OKL schedule views on a common KLE_ID and STREAM_ELEMENT_DATE. Amounts from each schedule source are aggregated with SUM and grouped by stream element date, contract ID, contract number, currency, and KLE. This join strategy ties each amortization row to a specific contract line and a specific cash-flow date.

Key Columns

• ID — the contract header identifier, derived from CTR_HDR.ID.
• CONTRACT_NUMBER — the human-readable contract number from the header.
• DUE_DATE / STREAM_ELEMENT_DATE — the scheduled date of the amortization cash flow; both columns carry the same stream element date.
• TOTAL_PAYMENT — the sum of principal and interest amounts for the period.
• PRINCIPAL_PAYMENT — the principal portion aggregated from the scheduled principal payments source.
• INTEREST_AMOUNT — the interest portion aggregated from the scheduled interest payments source.
• PRINCIPAL_BALANCE — the remaining principal balance aggregated from the scheduled principal balance source.
• ACCRUAL_AMOUNT — exposed as a literal 0 (zero) in the view definition; it is a placeholder column rather than a computed accrual figure.
• CURRENCY_CODE — the contract currency.
• KLE_ID — the contract line identifier used for the joins across the schedule views.

Common Use Cases and Queries

The view is typically queried to reconstruct an amortization table for a given contract or line, or to feed downstream reporting and reconciliation processes. A representative query returning the amortization schedule for a specific contract number is:

SELECT contract_number,
       due_date,
       total_payment,
       principal_payment,
       interest_amount,
       principal_balance,
       accrual_amount,
       currency_code
FROM   apps.okl_cs_amort_schedules_uv
WHERE  contract_number = :p_contract_number
ORDER BY due_date;

Because ACCRUAL_AMOUNT resolves to a constant zero, consumers requiring genuine accrual amounts must source that value elsewhere; the column exists mainly to preserve a uniform schedule layout. Integrations frequently select KLE_ID, STREAM_ELEMENT_DATE, and the three amount columns to reconcile scheduled principal, interest, and balance movements against subledger entries. Report builders join the view back to OKC_K_HEADERS_V or OKC_K_LINES_V on KLE_ID to enrich the schedule with additional contract attributes.

As the view is read-only and aggregates across multiple schedule sources, queries should account for the fact that totals are per stream element date and line, and should apply appropriate contract or date filters to avoid full-scan aggregation across all lease contracts.