Search Results okl_sif_pricing_params_u1

Overview

OKL_SIF_PRICING_PARAMS is a transactional configuration table in the Oracle Lease and Finance Management (OKL) schema. It stores the pricing parameters associated with Stream Interfaces, which are the objects that drive pricing, billing, and accounting generation during contract origination and lifecycle processing. Each row represents a single parameter — such as an interest rate, residual assumption, or fee indicator — that applies to a given stream interface and is consumed by the pricing engine at evaluation time. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, with its unique index in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the mined dependency structure suggests this object is best classified as a standalone satellite. It carries descriptive, parameter-level attributes that describe a business transaction (the stream interface), alongside audit and descriptive flexfield columns. The heuristic classification is a modeling suggestion rather than a physical constraint; implementations should treat the table as a dependent detail of the stream interface entity.

Key Information Stored

The primary key is ID, a NUMBER column defined as the primary key column and backed by the unique index OKL_SIF_PRICING_PARAMS_PK. The unique index OKL_SIF_PRICING_PARAMS_U1 (ID) is a business-key candidate, confirming ID as the enforced unique identifier. The remaining significant columns are:

• ID — Surrogate primary key, generated by sequence.
• SIF_ID — Foreign key to OKL_STREAM_INTERFACES, identifying the parent stream interface.
• KHR_ID — Foreign key to OKL_PRTFL_CNTRCTS_B, linking the parameter to the portfolio contract record.
• NAME — Name of the pricing parameter (VARCHAR2 150).
• DISPLAY_YN and UPDATE_YN — Flags governing whether the parameter is visible or editable.
• DEFAULT_VALUE and PARAMETER_VALUE — The default and currently effective values for the parameter (VARCHAR2 450).
• PRC_ENG_IDENT — Pricing engine identifier, documented as the pricing parameter end date.
• DESCRIPTION — User-defined description (VARCHAR2 1995).
• OBJECT_VERSION_NUMBER — Optimistic locking version column.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield context and segments.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The dominant use case is tracing how a contract's pricing parameters were derived. A typical query joins the parameter table to its parent stream interface to list all parameters for a given contract:

• SELECT p.name, p.default_value, p.parameter_value, p.display_yn, p.update_yn FROM okl_sif_pricing_params p WHERE p.sif_id = :sif_id;
• SELECT p.name, p.prc_eng_ident FROM okl_sif_pricing_params p, okl_stream_interfaces s WHERE p.sif_id = s.id AND p.khr_id = :khr_id;
• Reporting on parameters that differ from their defaults: SELECT * FROM okl_sif_pricing_params WHERE parameter_value <> default_value;

Additional scenarios include auditing which parameters permit user override (UPDATE_YN = 'Y'), extracting descriptive flexfield context for reporting via ATTRIBUTE_CATEGORY, and reconciling pricing engine identifiers (PRC_ENG_IDENT) against historical pricing runs. Because the table is transaction-level, queries should always be constrained by SIF_ID or KHR_ID to avoid full scans beyond the supporting indexes.

Related Objects

The following objects are most significant to OKL_SIF_PRICING_PARAMS:

• OKL.OKL_STREAM_INTERFACES — Parent entity referenced by SIF_ID; supplies the stream interface definition to which each parameter belongs.
• OKL.OKL_PRTFL_CNTRCTS_B — Referenced by KHR_ID via the OKL_SIF_KHR_FK_1 foreign key; identifies the portfolio contract associated with the parameter.
• OKL.OKL_SIF_PRICING_PARAMS_PK — Primary key index on ID.
• OKL.OKL_SIF_PRICING_PARAMS_U1 — Unique index on ID, the business-key candidate the user searched for.
• OKL.OKL_SIF_KHR_FK_1 — Non-unique index supporting the KHR_ID foreign key join.

The table participates in pricing engine processing rather than exposing a dedicated public API; changes are typically made through the contract and stream interface maintenance flows in the Lease Management application.