Results for “okl_parameters_v”

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

Overview

OKL_PARAMETERS_V is a seeded, VALID view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) module. Its documented purpose is to present the list of parameters required by the Formulae. In the Oracle E-Business Suite release 12.1.1 and 12.2.2 architecture, this view serves as the metadata layer that exposes the parameter definitions consumed by the lease pricing and calculation engine, which dynamically evaluates formulae at contract origination, rebooking, and restructuring time.

The view is functionally important because the OKL module stores calculation parameters (interest methods, rate factors, date conventions, and similar inputs) in normalized base tables. Rather than allowing reports, custom concurrent programs, and integrations to query those base tables directly, Oracle provides this view as the supported read interface. It also enforces the language join required by the multi-language tables convention, returning translated descriptions according to the session language. The presence of the CUSTOMIZATION_LEVEL column reflects the Oracle EBS convention for flagging whether the metadata is Oracle-seeded or customer-extended, which is directly relevant to upgrade and supportability assessments.

Underlying Base Objects

OKL_PARAMETERS_V is defined over two documented base tables:

• OKL_PARAMETERS_B — the base (non-translated) table holding the parameter definition rows, including name, datatype, customization level, and standard WHO audit columns.
• OKL_PARAMETERS_TL — the translation table holding the description (and any other translatable attributes) keyed by language.

The view joins the two on ID, applying the language predicate PMRT.LANGUAGE = USERENV('LANG'). Two additional derivations occur: the view exposes ROW_ID from OKL_PARAMETERS_B.ROWID, and it surfaces SFWT_FLAG, a value sourced from the translation table. The view also carries OBJECT_VERSION_NUMBER, the standard EBS optimistic locking column used when the underlying rows are updated through the application. Both base objects are referenced through APPS synonyms.

Key Columns

• ROW_ID — the physical rowid of the base-table row; useful for join diagnostics, though normally ID should be used.
• ID — the surrogate primary key for the parameter, used by formulae and configuration records to reference the parameter.
• OBJECT_VERSION_NUMBER — optimistic locking version for the parent row.
• SFWT_FLAG — a control flag originating from the translation table, applied by the formulae logic.
• CUSTOMIZATION_LEVEL — indicates whether the parameter is Oracle-seeded or customer-added; this is the column most frequently searched in the context of this view, since it governs whether a row survives upgrade or is flagged as user extension.
• NAME — the internal parameter identifier referenced by formula definitions.
• DATATYPE — the data type of the parameter (for example, number, date, or character), governing how the value is interpreted during formula evaluation.
• DESCRIPTION — the user-facing, language-translated parameter description.
• Created/updated audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN follow the standard EBS WHO convention and are retained for audit and diagnostics.

Common Use Cases and Queries

The view is typically queried when diagnosing formula behavior, listing parameter definitions visibly in a given language, or distinguishing Oracle-provided parameters from customer-created ones. A representative query filtered on the customization level is:

SELECT id, name, datatype, customization_level, description FROM apps.okl_parameters_v WHERE customization_level = 'U' ORDER BY name;

For a complete inventory of parameters, including seeded rows, the customization level column can be examined alongside the name and datatype to document the parameter baseline ahead of an upgrade. Because the language predicate is built into the view, running the query in a session whose language is not a defined translation falls back per standard EBS multi-language behavior; users should confirm the session language when descriptions appear missing. Sample query patterns include joining ID to formula detail tables to trace which parameters a given formula consumes, and comparing CUSTOMIZATION_LEVEL counts between environments to detect customer modifications. Queries should not rely on ROW_ID for stable identity; ID is the supported key.