Results for “due_arrears_yn”

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

Overview

OKL_CASH_FLOWS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Lease and Finance Management product family. Its documented purpose is to present "Cash Flows in the system," exposing the cash flow records that drive lease and finance contract calculations, including payment timing, classification, and descriptive flexfield attributes. The view is registered with a status of VALID in the ETRM dictionary for both release 12.1.1 and 12.2.2, indicating that its definition is consistent across these code lines.

Functionally, the view serves as a stable read interface over the cash flow entity. Because it is a view rather than a table, it carries no storage of its own; it projects the columns of the underlying cash flow table while abstracting the physical ROWID through a ROW_ID alias. This design allows reports, concurrent programs, and integrations to query lease cash flows without binding directly to the base table, which is the recommended pattern for custom development in EBS.

Underlying Base Objects

The view text is a simple projection over a single base object. The documented metadata records the referenced base object as OKL_CASH_FLOWS, exposed through a synonym, and the view definition aliases this object as CAF:

• OKL_CASH_FLOWS (alias CAF) — the sole source of rows. Every column in the view corresponds directly to a column in this table; no joins, unions, or aggregations are present.
• ROW_ID — derived from CAF.ROWID, providing a unique physical row identifier suitable for direct row addressing or for use in Forms-style block queries.

Because the view contains no filter predicates, it returns all cash flow records visible to the querying user, subject to standard EBS security and any row-level restrictions applied through the underlying table's grants or synonym. There is no business-event or MOAC predicate embedded in the view text.

Key Columns

The column list divides naturally into identification, classification, timing, denormalized references, and audit/attribute segments.

• ID — primary identifier of the cash flow row; ROW_ID — the corresponding ROWID.
• CFO_ID — reference to the parent cash flow object or owner entity that groups the cash flow.
• CFT_CODE — the cash flow type code. This is the column most commonly searched ("cft_code"), and it classifies each row by the nature of the cash flow (for example, payment, residual, or fee categories defined in the OKL cash flow type setup).
• STS_CODE and STY_ID — status code and status type identifier, used to track the lifecycle state of the cash flow record.
• DUE_ARREARS_YN — indicates whether the cash flow is due in advance or in arrears.
• START_DATE and NUMBER_OF_ADVANCE_PERIODS — define the timing basis for the cash flow stream, with the count of periods occurring before the start date.
• DNZ_KHR_ID and DNZ_QTE_ID — denormalized foreign keys to the associated quote or header records used in lease pricing and origination.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments available for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns; OBJECT_VERSION_NUMBER supplies optimistic locking support.

Common Use Cases and Queries

Typical uses include cash flow reporting by type, reconciliation of lease payment schedules, and data extraction for integration into pricing or treasury systems. The CFT_CODE column is frequently the primary selection predicate.

Retrieve all cash flows of a given type:

• SELECT id, cfo_id, cft_code, start_date, due_arrears_yn FROM okl_cash_flows_v WHERE cft_code = :p_cft_code;
• SELECT cft_code, COUNT(*) FROM okl_cash_flows_v GROUP BY cft_code ORDER BY cft_code;

Join to the parent cash flow object using ID or CFO_ID, and filter by status or date range to isolate active or future-dated streams. Because the view exposes ROW_ID, it can also be used for direct row navigation in custom Forms or for precise single-row lookups. When querying, restrict by START_DATE and STS_CODE where possible, and note that no MOAC predicate is included in the view definition, so any operating unit or legal entity restriction must be applied by the calling code against the base table's owning columns.