Search Results csp_cso_uk

Overview

The OKL_SLCTD_OPTNS table is a core data object within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. Its primary function is to establish and maintain the relationship between a lease contract and the specific product option values selected for that contract. This table acts as a critical junction, enabling the configuration of complex lease agreements by linking the master contract header to the detailed product features and options defined within the product catalog. Its role is essential for capturing the precise terms and conditions that define a financial instrument, ensuring that billing, accounting, and asset management processes operate on the correct contractual parameters.

Key Information Stored

The table's structure is designed to manage the many-to-many relationship between contracts and options. The most critical columns are its primary and foreign key fields. The table has two defined primary keys: a unique key (CSP_CSO_UK) on the combination of POV_ID and KHR_ID, and a primary key (OKL_SLCTD_OPTNS_PK) on the ID column, which is likely a surrogate key for internal processing. The key data columns are:

• ID: The primary key column, serving as a unique system identifier for each record.
• KHR_ID: A foreign key column that references the OKL_K_HEADERS table. This links the selected option to a specific lease contract header.
• POV_ID: A foreign key column that references the OKL_PDT_OPT_VALS table. This links the contract to a specific product option value from the product catalog.

The unique constraint on POV_ID and KHR_ID ensures that a given product option value cannot be redundantly assigned to the same contract more than once.

Common Use Cases and Queries

This table is central to reporting and data validation for configured lease contracts. A common business use case is generating a report of all product options selected for a specific lease agreement to verify contract setup. Another is identifying all contracts that include a particular product option, such as a specific insurance package or maintenance clause, for portfolio analysis. A typical SQL query would join OKL_SLCTD_OPTNS to the contract header and product option descriptions to produce a human-readable report.

SELECT khr.contract_number,
       pov.option_name,
       pov.option_value
FROM   okl_slctd_optns so,
       okl_k_headers khr,
       okl_pdt_opt_vals pov
WHERE  so.khr_id = khr.id
AND    so.pov_id = pov.id
AND    khr.contract_number = 'L-10001';

Data integrity checks often involve queries to find orphaned records where the foreign key references are invalid, which can indicate data corruption or incomplete contract setup processes.

Related Objects

The OKL_SLCTD_OPTNS table has defined dependencies on two primary master tables in the OKL schema, as documented by its foreign keys:

• OKL_K_HEADERS: This is the central lease contract header table. The relationship is established via the column OKL_SLCTD_OPTNS.KHR_ID, which references the OKL_K_HEADERS table. This join connects selected options to their parent contract.
• OKL_PDT_OPT_VALS: This table stores the valid values for product options. The relationship is established via the column OKL_SLCTD_OPTNS.POV_ID, which references the OKL_PDT_OPT_VALS table. This join provides the descriptive details and business rules for the selected option.

These relationships are fundamental, meaning that a record in OKL_SLCTD_OPTNS cannot exist without a corresponding, valid lease contract and a predefined product option value.