Results for “okl_strm_prc_params_uv”

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

Overview

OKL_STRM_PRC_PARAMS_UV is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Leasing and Finance Management module (OKL). In Oracle EBS 12.1.1 and 12.2.2, the view exposes the pricing parameters that the pricing engine evaluated during lease origination, renewal, or repricing activities. Each row pairs a lease stream transaction with a single pricing parameter interpreted by the pricing engine, together with the value supplied at run time and the seeded default value for that parameter.

The view is primarily a reporting and diagnostic construct. It does not store data itself; it flattens the relationship between stream interface records (the header-level transaction being priced) and the parameter records generated for each pricing engine invocation. Because the pricing engine identifier is surfaced as PRICING_NAME, users searching for "pricing_name" will find this view to be the natural entry point for answering which pricing engine was applied to a given lease transaction and which parameters that engine consumed. This makes it useful for audit trails, pricing troubleshooting, and reconciliation between expected and actual pricing inputs.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

• OKL_SIF_PRICING_PARAMS (SPP) — holds the individual pricing parameter rows, including the parameter name, the pricing engine identifier, the actual parameter value, and the default value.
• OKL_STREAM_INTERFACES (SIF) — holds the stream interface header records representing the lease transaction submitted to pricing, including the transaction number, the internal ID, and the associated contract/header reference KHR_ID.

The join condition is SPP.SIF_ID = SIF.ID, an inner join that discards pricing parameter rows lacking a matching stream interface header. The result set is ordered by TRANSACTION_NUMBER ascending and then by SIF.CREATION_DATE descending, so the most recently created interface record for any given transaction appears first within that transaction group. Both base objects are owned by APPS and are surfaced to the view owner through synonyms, which is standard for ETRM (Enterprise Territory and Revenue Management family) reporting views in this release.

Key Columns

• TRANSACTION_NUMBER — the business-facing identifier of the lease stream interface transaction, sourced from OKL_STREAM_INTERFACES.
• SIF_ID — the internal primary key of the stream interface record; the join key to OKL_STREAM_INTERFACES.
• KHR_ID — the contract header identifier (KHR) associated with the stream interface, linking pricing activity back to the lease contract.
• PARAMETER_NAME — the name of the pricing parameter as defined by the pricing engine configuration.
• PRICING_NAME — the pricing engine identifier (PRC_ENG_IDENT); this is the column most directly relevant to searches for "pricing_name" and identifies which pricing engine produced the parameter.
• PARAMETER_VALUE — the value actually supplied to or used by the pricing engine for that parameter on this transaction.
• DEFAULT_VALUE — the seeded or configured default for the parameter, allowing comparison against the actual value.

Common Use Cases and Queries

Typical scenarios include identifying which pricing engine was applied to a lease, comparing actual parameter values against defaults to detect overrides, and auditing parameter consumption across transactions. A representative query retrieving all parameters for a specific transaction is:

• SELECT transaction_number, pricing_name, parameter_name, parameter_value, default_value FROM apps.okl_strm_prc_params_uv WHERE transaction_number = :transaction_number ORDER BY pricing_name, parameter_name;
• SELECT transaction_number, pricing_name, parameter_name, parameter_value, default_value FROM apps.okl_strm_prc_params_uv WHERE pricing_name = :pricing_name; — used to determine every transaction priced by a given engine.
• SELECT transaction_number, parameter_name, parameter_value, default_value FROM apps.okl_strm_prc_params_uv WHERE parameter_value <> default_value; — used to isolate parameters that were overridden rather than defaulted.

Because the view is read-only and loosely coupled to interface staging tables, it should be treated as a query surface rather than a maintenance entry point; updates must be directed to OKL_SIF_PRICING_PARAMS through supported concurrent programs or APIs.