Results for “okl_fmaopd_serch_uv”

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

Overview

OKL_FMAOPD_SERCH_UV is a database view owned by the APPS schema in Oracle E-Business Suite, registered as a VALID object under the OKL – Leasing and Finance Management product family. In ETRM releases 12.1.1 and 12.2.2 the view serves as a lightweight, denormalized search and lookup structure that joins formula operand assignments to their multilingual operand definitions. Its name reflects its purpose: it exposes the operand records attached to a formula (FMA) so that concurrent programs, OA Framework pages, and integration extracts can resolve an operand identifier to a user-facing label and name without performing the multi-table join themselves.

Within the leasing configuration model, a formula (FMA) is composed of operands, and each operand carries a language-dependent name plus a language-independent label. The view collapses the base object, the translation table, and the formula-to-operand assignment table into a single projection, which makes it suitable for LOV queries, reporting, and validation routines that need to confirm the operands associated with a particular formula identifier.

Underlying Base Objects

The view text is defined over three documented base objects, each referenced through an APPS synonym:

• OKL_FMLA_OPRNDS – the formula operand assignment table. It supplies the primary key (ID), the LABEL, the operand surrogate key (OPD_ID), and the foreign key to the formula (FMA_ID).
• OKL_OPERANDS_B – the operand base table, holding language-independent attributes. It is joined on OPD_ID = OKL_OPERANDS_B.ID.
• OKL_OPERANDS_TL – the operand translation table, providing the NAME in the session language. It is joined on OKL_OPERANDS_B.ID = OKL_OPERANDS_TL.ID.

The join is filtered by OPDT.LANGUAGE = USERENV('LANG'), so the view returns exactly one translated row per operand for the language of the current session. Because OKL_OPERANDS_TL is a _TL table, the view inherits standard multilingual behavior: the same query returns different NAME values depending on the NLS_LANG or session language setting. No outer join is applied, so operands lacking a translation row in the active language will not appear.

Key Columns

• ID – the identifier of the formula operand assignment row, taken from OKL_FMLA_OPRNDS.ID. This is the natural key for the assignment record itself.
• LABEL – the sequence or display label assigned to the operand within the formula context, sourced from OKL_FMLA_OPRNDS.LABEL.
• OPD_ID – the surrogate identifier of the operand, sourced from OKL_FMLA_OPRNDS.OPD_ID and joined to OKL_OPERANDS_B.ID.
• FMA_ID – the identifier of the parent formula. This is the column most commonly used as a search predicate, and it is the key behind the "fma_id" search pattern.
• NAME – the language-specific operand name obtained from OKL_OPERANDS_TL.NAME, suitable for display in list of values and report output.

Common Use Cases and Queries

The most frequent scenario is retrieving all operands attached to a known formula so they can be displayed or validated. The following query lists the operands for a given FMA_ID, ordered by their in-formula label:

• SELECT id, label, opd_id, fma_id, name FROM apps.okl_fmaopd_serch_uv WHERE fma_id = :p_fma_id ORDER BY label;

A second common pattern is a list of values driven by the operand name, for example when a user must select an operand already configured on a formula:

• SELECT opd_id, name FROM apps.okl_fmaopd_serch_uv WHERE fma_id = :p_fma_id AND UPPER(name) LIKE UPPER(:p_search)||'%';

Integration and reconciliation jobs frequently use the view to join back to the formula tables, resolving FMA_ID and OPD_ID to descriptive text without re-implementing the translation logic:

• SELECT f.fma_id, v.label, v.name FROM apps.okl_fmaopd_serch_uv v, apps.okl_formulas_b f WHERE v.fma_id = f.id AND f.id = :p_formula_id;

Because the view performs the language restriction internally, callers should always query it from a session whose language matches the desired output; otherwise, translated names for other languages must be obtained directly from OKL_OPERANDS_TL. Performance is generally adequate for lookup volumes, but large reporting extracts should filter on FMA_ID to constrain the underlying joins on OKL_FMLA_OPRNDS.