Results for “financial_asset_line”

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

Overview

APPS.OKL_PAYMENT_SCHDLE_DTLS_ALL_UV is a reporting view in the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL / ETRM) module. It consolidates payment schedule detail lines for lease and finance contracts, exposing one row per cash flow line that belongs to a payment schedule (CFT_CODE = 'PAYMENT_SCHEDULE'). The view is documented in ETRM 12.2.2 and applies equally to 12.1.1 deployments where the OKL schema is present.

The view's primary role is to resolve the descriptive identity of each payment line. Payment schedules may include financial asset lines, serviced asset lines, service lines, and fee lines. Rather than requiring consumers to join the various source objects themselves, the view applies conditional DECODE logic against the cash flow object type (CFO.OTY_CODE) to derive a human-readable Description and Line_Type. This makes it well suited for operational reports, dashboard extracts, and downstream integrations that need schedule-level detail without re-deriving line categorisation.

Because the term "financial_asset_line" is embedded as a literal in the view's DECODE expressions, the object is frequently located by searches for that token. It is the mechanism through which asset-lines are labelled "Asset" and described by the corresponding line NAME value.

Underlying Base Objects

The view is defined over the following documented base objects and synonyms:

• OKL_CASH_FLOWS (synonym) — the primary fact source, aliased CAF. Supplies stream, status, flow type, due/arrears flag, and advance period counts.
• OKL_CASH_FLOW_LEVELS (synonym) — aliased CFL; joined on CAF.ID = CFL.CAF_ID.
• OKL_CASH_FLOW_OBJECTS (synonym) — aliased CFO; carries OTY_CODE, the discriminator driving the DECODE logic.
• OKL_TRX_QTE_CF_OBJECTS (synonym) — aliased QCO; links cash flow objects to their base source.
• OKC_K_LINES_V (view) — aliased L; supplies line NAME and ITEM_DESCRIPTION for asset and service lines.
• OKC_K_HEADERS_ALL_B (synonym) — aliased HDR; provides the contract and CURRENCY_CODE.
• OKC_K_ITEMS (synonym) — aliased CIM; outer-joined to resolve the stream type of fee lines.
• OKL_STRM_TYPE_B and OKL_STRM_TYPE_V — aliased STM1 and STM2; supply the stream type code/name.
• OKL_ACCOUNTING_UTIL (package) — a referenced package in the documented metadata, relevant to accounting derivation around these cash flows.

Joins are predominantly inner, with outer joins (denoted by (+)) applied to OKC_K_LINES_V and OKC_K_ITEMS so that fee and stream records without a matching line still appear.

Key Columns

• QTE_ID / DNZ_KHR_ID — quote identifier and contract (header) identifier anchoring each schedule line.
• DESCRIPTION — derived from line NAME, ITEM_DESCRIPTION, or stream name depending on OTY_CODE.
• LINE_TYPE — returns 'Asset' for FINANCIAL_ASSET_LINE, 'Serviced Asset', 'Service', or 'Fee'.
• STY_ID / STREAM_TYPE — the stream identifier and its code.
• BASE_SOURCE_ID — the underlying contract line or item identifier.
• ADV_ARR — the due_arrears_yn flag indicating advance versus arrears timing.
• ADVANCE_PAYMENTS — number_of_advance_periods for the line.
• TOTAL — aggregated sum of amount multiplied by number_of_periods, plus stub amounts.
• CURRENCY_CODE, PAYMENT_STATUS_CODE, CFT_CODE — contract currency, status, and cash flow type (filtered to PAYMENT_SCHEDULE).

Common Use Cases and Queries

Typical usage includes extracting schedule totals per contract, reporting asset versus service versus fee composition, and feeding downstream reconciliation. A representative query:

SELECT qte_id, dnz_khr_id, line_type, description,
       stream_type, total, currency_code, payment_status_code
FROM   apps.okl_payment_schdle_dtls_all_uv
WHERE  cft_code = 'PAYMENT_SCHEDULE'
AND    dnz_khr_id = :contract_id
ORDER BY line_type, description;

To isolate financial asset lines specifically:

SELECT description, total, adv_arr
FROM   apps.okl_payment_schdle_dtls_all_uv
WHERE  line_type = 'Asset';

Because TOTAL is aggregate-derived, consumers should not further sum across stream rows without considering STY_ID grouping. The view is read-only and intended for reporting rather than transactional update.