Search Results okl_formulae_v




Overview
Explore in AI Chat

Overview

OKL_FORMULAE_V is a validation view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL – Leasing and Finance Management product family. Its documented purpose is to expose the definition of formulae used by Oracle Lease and Finance Management, together with the context group associated with each formula. The view is marked VALID in the ETRM data dictionary and is available in both EBS 12.1.1 and 12.2.2.

From a reporting and integration standpoint, the view serves as the primary read interface for formula definitions. It joins the base definition table, OKL_FORMULAE_B, with the translation table, OKL_FORMULAE_TL, so that a single query returns both the code-level formula attributes and the language-specific name and description. Because it resolves the translated text using the session language, consumers receive content in the runtime language of the session rather than in a fixed language. This makes the view suitable for concurrent programs, Oracle Reports, OAF pages, and external integrations that must present formula metadata in a consistent, localized form.

Underlying Base Objects

The view is defined over two referenced objects, both exposed to APPS as synonyms:

  • OKL_FORMULAE_B – the base table holding the physical formula definition, including the formula string, context group identifier, formula type code, version, dates, descriptive flexfield attributes, organization identifier, and audit columns.
  • OKL_FORMULAE_TL – the translation table holding language-specific name and description, and the SFWT_FLAG marker.

The two are joined on the formula identifier: FMAB.ID = FMAT.ID, with the translation row filtered by FMAT.LANGUAGE = USERENV('LANG'). The view therefore inherits the standard EBS multilingual pattern of a base table plus a translation table, and it is a non-key-preserved join view because columns are drawn from both sources. The ROW_ID column is derived from the base table ROWID.

Key Columns

  • ID – the unique formula identifier, the join key between the base and translation rows.
  • NAME – the translated formula name, sourced from OKL_FORMULAE_TL.
  • FORMULA_STRING – the actual expression text of the formula; this is the column most commonly searched for when users look up "formula_string".
  • DESCRIPTION – the translated description of the formula.
  • CGR_ID – the context group identifier required by the formula, linking the formula to its context group.
  • FYP_CODE – the formula type code classifying the formula.
  • VERSION, START_DATE, END_DATE – version tracking and effective-dating columns.
  • SFWT_FLAG – translation-table flag from OKL_FORMULAE_TL.
  • THERE_CAN_BE_ONLY_ONE_YN – indicates whether only a single instance of the formula is permitted.
  • ORG_ID – the operating unit identifier supporting multi-org (MOAC) security.
  • OBJECT_VERSION_NUMBER – optimistic locking column used by the underlying business objects.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield context and segment columns.
  • ROW_ID – the ROWID of the underlying base-table row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.

Common Use Cases and Queries

Typical uses include listing all formulae for an operating unit, retrieving the formula string for a given formula name, and joining formulae to their context groups. The following query returns the identifier, name, and expression for all formulae visible to the session, ordered by name:

  • SELECT fmv.id, fmv.name, fmv.formula_string, fmv.fyp_code FROM apps.okl_formulae_v fmv ORDER BY fmv.name;

To search for a specific expression pattern — the "formula_string" lookup — filter on the string column:

  • SELECT fmv.id, fmv.name, fmv.formula_string FROM apps.okl_formulae_v fmv WHERE fmv.formula_string LIKE '%&pattern%';

Because the view honors USERENV('LANG'), results are automatically returned in the session language, and any query joining to contract or transaction data should join on the ORG_ID column where operating-unit security applies.