Results for “okl_slctd_optns”

50+ results




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

Overview

OKL_SLCTD_OPTNS is a transaction table within the OKL (Lease and Finance Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It links a lease or finance contract to the product option values selected for that contract. In leasing terms, a product option represents a configurable choice offered by a lease product — for example, an interest calculation method, a residual value treatment, a payment frequency, or a billing convention. When a contract is booked, the specific values chosen for each relevant option are recorded in OKL_SLCTD_OPTNS, making the table the authoritative record of how a given contract was configured.

From a dimensional modeling perspective, the FK structure supports classifying this object as a link. It sits between the contract header hub (OKL_K_HEADERS) and the product option value hub (OKL_PDT_OPT_VALS), resolving a many-to-many relationship between contracts and the option values they consume. This classification is a heuristic derived from the foreign key topology rather than a declared constraint, and should be treated as a modeling suggestion.

Key Information Stored

The table contains 25 documented columns. The most significant are:

  • ID — surrogate primary key (OKL_SLCTD_OPTNS_PK) and the target of unique index OKL_SLCTD_OPTNS_U1. Uniquely identifies each selected-option row.
  • KHR_ID — foreign key to OKL_K_HEADERS, identifying the lease contract header to which the selected option belongs.
  • POV_ID — foreign key to OKL_PDT_OPT_VALS, identifying the specific product option value chosen.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, available for customer-specific extensions of the option selection record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit lineage and last-touch information.

The business key is defined by unique index OKL_SLCTD_OPTNS_U2 over (POV_ID, KHR_ID), named CSP_CSO_UK. This guarantees that any given option value can be selected at most once per contract header, preventing duplicate configuration entries. The distinction between the surrogate ID and this composite business key is important when writing idempotent interfaces or reconciliation queries.

Common Use Cases and Queries

Typical usage centers on reproducing the exact configuration of a booked contract, driving downstream calculations, and auditing changes to contract terms.

  • Contract configuration report — join to OKL_K_HEADERS and OKL_PDT_OPT_VALS to list every option value selected for a contract:
    SELECT k.contract_number, p.option_code, p.option_value
    FROM   okl_slctd_optns s,
           okl_k_headers    k,
           okl_pdt_opt_vals p
    WHERE  s.khr_id = k.id
    AND    s.pov_id = p.id
    AND    k.contract_number = :contract_number;
  • Comparing configurations across contracts — group by POV_ID to identify which option values are most frequently selected, useful for product design analysis.
  • Audit and reconciliation — filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to detect option changes made after contract activation.
  • Interface loading — validate incoming interface rows against the (POV_ID, KHR_ID) unique key to avoid duplicate insert attempts.
  • DFF reporting — query ATTRIBUTE_CATEGORY plus relevant ATTRIBUTE columns for customer-specific option metadata.

Related Objects

  • OKL_K_HEADERS — parent contract header table; joined via OKL_SLCTD_OPTNS.KHR_ID = OKL_K_HEADERS.ID.
  • OKL_PDT_OPT_VALS — product option value reference table; joined via OKL_SLCTD_OPTNS.POV_ID = OKL_PDT_OPT_VALS.ID.
  • OKL_PDT_OPTIONS — option definition table that parent-owns option values referenced through POV_ID.
  • OKL_PRODUCTS / OKL_PDT_VERSIONS — product master and version tables that scope which options are available for a contract.
  • OKL_K_LINES — contract line table, frequently queried alongside selected options when reporting full contract detail.
  • OKL_STRMTS / OKL_STRMTS_DTLS — streams and stream details generated from option-driven pricing, useful when tracing how a selected option influenced billing.
  • OKL_TRX_CONTRACTS_API — public API for contract creation, which populates OKL_SLCTD_OPTNS as part of booking.