Results for “okl_cash_flow_levels_v”

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

Overview

OKL_CASH_FLOW_LEVELS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Lease and Finance Management product family. It exposes the cash flow level definitions maintained within the lease management subsystem. In Oracle Lease and Finance Management, a cash flow is decomposed into one or more levels, each representing a distinct stream of payment or receipt amounts, rates, and periodicity. This view surfaces those level records in a readable, denormalized form suitable for concurrent program output, OBIEE or Discoverer reporting, and external integration interfaces.

The view was documented as VALID at release 12.2.2 and is present in 12.1.1; the object structure is unchanged between the two releases, which is significant for organizations performing a 12.1.1 to 12.2.2 upgrade, since no column-level remediation is required. As a simple projection view over a single base object, it carries no aggregation or join logic and therefore imposes minimal execution cost. Consumers should treat it strictly as a read-only construct, since all maintenance is performed against the underlying base table through the OKL forms and concurrent processes.

Underlying Base Objects

The view is defined exclusively over the synonym OKL_CASH_FLOW_LEVELS, which resolves to the APPS base table of the same name. The definition is a direct column-for-column projection with no WHERE clause, no DISTINCT, and no join:

• SELECT CFL.ROWID ROW_ID, CFL.ID ID, CFL.CAF_ID CAF_ID, … FROM OKL_CASH_FLOW_LEVELS CFL
• ROW_ID is exposed as a ROWID pseudo-column for row identification purposes.
• Because the view is not a join, it is inherently updatable in principle, but it should not be used for DML in a supported implementation.
• All descriptive and audit columns of the base table are carried through unchanged.

Key Columns

• ID – Primary identifier of the cash flow level record.
• CAF_ID – Foreign key to the parent cash flow (CAF) entity; the primary linking column for hierarchical queries.
• LEVEL_SEQUENCE – Ordinal position of the level within its parent cash flow. This is the column most frequently referenced in ORDER BY and analytic ranking, since it establishes the processing order of the levels.
• AMOUNT – Monetary amount associated with the level.
• NUMBER_OF_PERIODS – Count of periods over which the level amount is distributed.
• FQY_CODE – Frequency code defining the periodicity of the level (monthly, quarterly, and so on).
• START_DATE – Effective start date of the level.
• RATE – Interest or discount rate applied to the level.
• STUB_DAYS / STUB_AMOUNT – First- or last-period stub duration and amount, used when a level does not align to full periods.
• MISSING_PMT_FLAG – Indicator governing treatment of a missing payment for the level.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield storage.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER – Standard audit and optimistic locking columns.

Common Use Cases and Queries

Typical scenarios include reconstructing the level schedule for a given cash flow, validating that level sequences are contiguous, and feeding cash flow level data into downstream treasury or accounting extracts.

List all levels for a specific cash flow in processing order:

• SELECT caf_id, level_sequence, amount, number_of_periods, fqy_code, start_date, rate FROM okl_cash_flow_levels_v WHERE caf_id = :p_caf_id ORDER BY level_sequence;

Detect gaps or duplicates in the level sequence for each cash flow:

• SELECT caf_id, level_sequence, COUNT(*) FROM okl_cash_flow_levels_v GROUP BY caf_id, level_sequence HAVING COUNT(*) > 1;

Retrieve the highest-sequenced level per cash flow using an analytic function, useful for determining the final level in a waterfall structure. Because the view is a thin wrapper, query performance is governed entirely by the indexes on OKL_CASH_FLOW_LEVELS, and the CAF_ID and LEVEL_SEQUENCE columns should be included in any driving predicate or ordering clause.