Results for “okl_leaseapp_datapoints_v”

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

Overview

The view OKL_LEASEAPP_DATAPOINTS_V is an Oracle E-Business Suite database object owned by the APPS schema and registered as VALID. It belongs to the OKL - Leasing and Finance Management product family and is documented in the ETRM repository for releases 12.1.1 and 12.2.2. The view presents lease application data point records used by the Oracle Lease and Finance Management (OLFM) application.

In OLFM, data points represent named attributes captured against a lease application. Each data point carries a category (the DATA_POINT_CATEGORY column, the term the user searched for) and a corresponding value (the DATA_POINT_VALUE column). This view exposes those records with a ROWID-based surrogate key and the standard EBS WHO columns, making the underlying intersection table available for reporting, integration, and extension development. It is a thin, read-oriented projection of the base table rather than an independent entity, so it isolates consumers from direct DML against the base object while preserving the same column semantics.

Underlying Base Objects

The documented base object referenced by the view is OKL_LEASEAPP_DATAPOINTS (exposed via a SYNONYM in the APPS schema). The view definition is a direct column projection over that table, aliased as LAD:

• SELECT ROWID ROW_ID, ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LEASEAPP_ID, DATA_POINT_ID, DATA_POINT_CATEGORY, DATA_POINT_VALUE FROM OKL_LEASEAPP_DATAPOINTS LAD

Because no joins, filters, or aggregations are applied, the view is effectively one-to-one with the base table. Its role is therefore structural rather than transformational: it provides the supported read interface while the base table holds the physical rows. The LEASEAPP_ID column links each row back to a parent lease application, and DATA_POINT_ID references the data point definition. The combination of lease application, data point, and category forms the logical business key for a captured value.

Key Columns

• ROW_ID — The ROWID of the base table row, exposed as the view's surrogate identifier.
• ID — The primary key of the underlying OKL_LEASEAPP_DATAPOINTS record.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to detect concurrent updates.
• LEASEAPP_ID — Foreign key to the lease application header with which the data point is associated.
• DATA_POINT_ID — Identifier of the data point definition being captured.
• DATA_POINT_CATEGORY — The category that classifies the data point, used to group points by functional area or business purpose.
• DATA_POINT_VALUE — The value captured for the data point on this lease application.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Standard audit trail columns maintained by the EBS concurrent and forms framework.

Common Use Cases and Queries

Typical uses include auditing captured lease application attributes, building reports grouped by DATA_POINT_CATEGORY, and extracting data point values for downstream integration. The view is also a convenient base for custom extensions that must not query the base table directly.

• Retrieve all data points for a lease application:
  SELECT data_point_id, data_point_category, data_point_value FROM okl_leaseapp_datapoints_v WHERE leaseapp_id = :p_leaseapp_id;
• Group collected values by category:
  SELECT data_point_category, COUNT(*) FROM okl_leaseapp_datapoints_v GROUP BY data_point_category ORDER BY 1;
• Report the latest captured values with audit context:
  SELECT leaseapp_id, data_point_id, data_point_value, last_updated_by, last_update_date FROM okl_leaseapp_datapoints_v ORDER BY last_update_date DESC;
• Filter a specific category for analysis:
  SELECT leaseapp_id, data_point_value FROM okl_leaseapp_datapoints_v WHERE data_point_category = :p_category;

Consumers should treat the view as read-only for reporting and integration, applying DML through the supported OLFM application programming interfaces rather than against the view or its base table.