Search Results okl_cash_flow_objects_v




Overview
Explore in AI Chat

Overview

OKL_CASH_FLOW_OBJECTS_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. The view exposes records from the cash flow objects repository, which links individual cash flow records to the source business objects that generated them. In lease and finance contracts, cash flows represent scheduled payment, receipt, and interest amounts derived from contract terms; each cash flow row is associated with a source object such as a contract, stream, or asset through an object type code and a source identifier.

As a view rather than a base table, OKL_CASH_FLOW_OBJECTS_V provides a stable, read-only presentation layer over the underlying transactional entity. It is typically consumed by concurrent programs, Oracle Reports, Oracle Forms LOVs, and custom SQL used for reconciliation, analytics, and outbound integration with external financial systems. The view inherits the standard EBS audit and concurrency columns, making it suitable for change tracking and for integration interfaces that must detect updated records since a prior extract. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and the structure documented in ETRM is consistent across those releases.

Underlying Base Objects

The view is defined over a single base object: OKL_CASH_FLOW_OBJECTS, accessed in the APPS schema through the synonym of the same name. The view text performs a simple projection of columns from this table, using the alias CFOV, without joins, unions, or aggregation. The only transformation applied is the exposure of the physical row identifier as the ROW_ID column, obtained via CFOV.ROWID, which allows consumers to address individual rows uniquely and to correlate view output back to the base table row.

Because the view is a one-to-one, non-distorting projection, no rows are filtered, multiplied, or consolidated. Every row in OKL_CASH_FLOW_OBJECTS corresponds to exactly one row in OKL_CASH_FLOW_OBJECTS_V, and DML performed against the base table is immediately visible through the view. No indexed access paths are created by the view itself; query performance for predicates on ID, OTY_CODE, SOURCE_TABLE, or SOURCE_ID depends on the indexes defined on the underlying OKL_CASH_FLOW_OBJECTS table.

Key Columns

  • ROW_ID – The ROWID of the underlying OKL_CASH_FLOW_OBJECTS row, providing a unique physical identifier for correlation and diagnostics.
  • ID – The primary surrogate key of the cash flow object record; used to join to related cash flow tables.
  • OTY_CODE – Object type code identifying the category of the associated object, allowing consumers to classify the cash flow by origin.
  • SOURCE_TABLE and SOURCE_ID – The source table name and the primary key value within that table, forming a polymorphic reference to the originating business entity.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – The standard Oracle descriptive flexfield storage columns, describing the source object and supporting extensible, client-specific attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns recording who created and last modified the record and when.
  • OBJECT_VERSION_NUMBER – Optimistic locking token used to detect concurrent modification of the record.

Common Use Cases and Queries

The view is most frequently queried to enumerate all objects attached to a given cash flow or, conversely, to find all cash flows associated with a particular source record. Because the source reference is polymorphic, joins to the target table must generally be constructed dynamically or per source table name.

  • Retrieve all objects for a specific source record: SELECT * FROM okl_cash_flow_objects_v WHERE source_table = 'OKL_STRM_HDRS' AND source_id = :p_source_id;
  • List objects by object type: SELECT id, oty_code, source_table, source_id FROM okl_cash_flow_objects_v WHERE oty_code = :p_oty_code;
  • Incremental extraction for integration, using audit columns: SELECT * FROM okl_cash_flow_objects_v WHERE last_update_date >= :p_since_date;
  • Resolve a specific record via its primary key: SELECT * FROM okl_cash_flow_objects_v WHERE id = :p_id;

These patterns support cash flow reconciliation, source-to-cashflow traceability reporting, and interface extracts that must communicate the origin of each scheduled amount to downstream financial applications.