Search Results base_formula_name




Overview
Explore in AI Chat

Overview

The APPS.FF_FORMULAS_F_VL view is a translated (TL) validation view within the Oracle E-Business Suite Payroll module (PAY). It presents payroll formula definitions together with their language-specific translations, exposing both the base (untranslated) values from the underlying formula table and the values current for the user's session language. The _VL suffix denotes a "view with language," indicating that this object joins a base table to its translation table and filters rows to the language of the querying session.

In Oracle EBS 12.1.1 and 12.2.2, payroll formulas are central objects in the Oracle FastFormula framework. Administrators and developers inspect formulas through the Formula window, but reporting, integration, and diagnostics frequently require direct SQL access. FF_FORMULAS_F_VL provides a stable, translatable interface to formula metadata and is typically the view oracle seeded forms and concurrent programs reference instead of the raw tables. Because it exposes both the base and translated columns side by side, it is well suited to comparisons, audits, and multilingually aware reports.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is owned by APPS and is defined over two documented base objects, both consumed through synonyms:

  • FF_FORMULAS_F — the base (untranslated) formula table, aliased as B. It holds the core formula definition, effective dating, legislation, type, and the compiled formula text.
  • FF_FORMULAS_F_TL — the translation table, aliased as TL. It stores language-specific FORMULA_NAME and DESCRIPTION values.

The view join condition is B.FORMULA_ID = TL.FORMULA_ID AND TL.LANGUAGE = USERENV('LANG'), which restricts translation rows to the language set for the current database session. This assures that the FORMULA_NAME and DESCRIPTION columns reflect the language actually seen by the user, while the corresponding BASE_* columns always expose the underlying language-independent values. The view status is recorded as VALID, confirming the object compiles correctly in the documented environment.

Key Columns

The view text exposes the following columns, several of which map directly to the user's search term "base_description":

Common Use Cases and Queries

Typical scenarios include auditing all formulas for a business group, comparing base versus translated descriptions, and locating a formula by its base description. A common query retrieving base descriptions is:

  • SELECT FORMULA_ID, BASE_FORMULA_NAME, BASE_DESCRIPTION, FORMULA_NAME, DESCRIPTION, LEGISLATION_CODE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.FF_FORMULAS_F_VL WHERE BASE_DESCRIPTION LIKE '%&keyword%';
  • Filtering to currently effective rows: add AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
  • Reporting formulas by legislation: WHERE LEGISLATION_CODE = 'US'.
  • Comparing translations against base text: select both BASE_DESCRIPTION and DESCRIPTION to detect untranslated or divergent entries.

Because the view is language-sensitive, queries executed in different session languages may return different DESCRIPTION values while BASE_DESCRIPTION remains constant, making it valuable for globalization testing and support diagnostics.