Results for “okl_leaseapp_datapoints”

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

Overview

OKL_LEASEAPP_DATAPOINTS is a transactional table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It serves as the data point value repository for lease applications, capturing the additional, user-entered data point values that are attached to a lease application during origination, underwriting, and approval workflows. Data points in OKL are configurable attributes — supported by the Oracle Contracts and Lease Management core — that allow implementers to capture business-specific information without modifying the underlying data model. This table stores the actual values entered against those configured data points for each lease application.

From a Data Vault modeling perspective, the heuristic classification of this table is standalone. In this context, it functions most naturally as a satellite-like structure relative to the lease application hub, holding descriptive, transaction-scoped attributes that are versioned by the standard audit columns. Because it holds only one foreign key reference (to AR_CMGT_DATA_POINTS_B), it is not a link table; the standalone classification reflects its role as an attribute-bearing child rather than a connector between multiple hubs.

Key Information Stored

The table contains 11 documented columns. The surrogate primary key is ID, enforced by the OKL_LEASEAPP_DATAPOINTS_PK constraint, and additionally protected by the unique index OKL_LEASEAPP_DATAPOINTS_U1 (ID). The primary foreign key, DATA_POINT_ID, references AR_CMGT_DATA_POINTS_B, which holds the definition of each configured data point. The LEASEAPP_ID column identifies the parent lease application to which the value belongs, effectively associating the row with the originating application header.

The DATA_POINT_CATEGORY column distinguishes the classification or grouping of the data point, allowing consumers to segment values by purpose. DATA_POINT_VALUE holds the actual user-entered value for the data point within the context of the lease application. Standard EBS audit and concurrency columns are present: OBJECT_VERSION_NUMBER supports optimistic locking, while CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide the mandatory who/when audit trail required for multitenant and audit-enabled deployments. No other business-key unique indexes are documented beyond the primary key on ID.

Common Use Cases and Queries

Typical use cases include lease application data extraction for feeder systems, reporting on user-entered data points by category, integration with downstream credit or compliance systems, and migration or archival of application-level attributes. A representative query to retrieve all data point values for a given lease application, joined to their definitions, is:

• SELECT ld.ID, ld.LEASEAPP_ID, ld.DATA_POINT_ID, ld.DATA_POINT_CATEGORY, ld.DATA_POINT_VALUE FROM OKL.OKL_LEASEAPP_DATAPOINTS ld WHERE ld.LEASEAPP_ID = :leaseapp_id;
• Reporting by category: group and filter using DATA_POINT_CATEGORY to aggregate values across applications.
• Integration extract: join to AR_CMGT_DATA_POINTS_B on DATA_POINT_ID to resolve the data point name, type, and display attributes.
• Audit reconciliation: leverage CREATED_BY/LAST_UPDATED_BY and CREATION_DATE/LAST_UPDATE_DATE to track when values were entered or subsequently modified.

Related Objects

• AR_CMGT_DATA_POINTS_B — referenced by DATA_POINT_ID; provides the data point definition header. Primary join path for resolving name/type metadata.
• AR_CMGT_DATA_POINTS_TL — translation table for data point definitions, typically joined for language-specific labels.
• OKL_LEASEAPP (lease application header) — parent of LEASEAPP_ID; the primary entity this table embellishes.
• OKL_LEASEAPP_DATAPOINTS_PK / _U1 — the constraining indexes on ID, relevant for DBA tuning and unique-key enforcement.
• OKL lease application API / concurrent programs — programmatic interfaces that insert or update data point values during application processing.
• OKL_LEASEAPP_ATTRIBUTES and related OKL lease application child tables — companion attribute structures frequently queried alongside this table.