Results for “ff_globals_f_vl”

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

Overview

FF_GLOBALS_F_VL is a bilingual (VL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PAY — Payroll product family and resides in the Oracle HRMS / Fast Formula infrastructure. The view exposes payroll global values, which are named constants defined at the business group or legislation level and referenced from Fast Formula expressions, payroll processes, and configuration logic. Because globals frequently differ by localization and by language, the view implements Oracle's standard translatable-entity pattern: it merges the base table with its translation table to return the translated name and description for the session language while still exposing the base (untranslated) values.

For reporting and integration purposes, FF_GLOBALS_F_VL presents a flattened, user-friendly projection of payroll globals. It is the object referenced by descriptive flexfields and by the "Global Description" lookup context in many EBS diagnostics and reports. Users searching for "global_description" are typically locating the column that stores the human-readable description of a payroll global — in this view that attribute is exposed twice: as BASE_GLOBAL_DESCRIPTION (the untranslated value) and as GLOBAL_DESCRIPTION (the language-specific translation).

The view carries a status of VALID in the ETRM metadata, confirming that its definition resolves cleanly against the underlying synonyms in a standard installation.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the APPS schema:

• FF_GLOBALS_F — the base (F) table holding the non-translatable attributes of each global: identity, effective dating, business group, legislation, data type, value, and the base-language name and description.
• FF_GLOBALS_F_TL — the translation (TL) table holding the language-specific GLOBAL_NAME and GLOBAL_DESCRIPTION for each global.

The join is performed on GLOBAL_ID, with the additional predicate TL.LANGUAGE = USERENV('LANG'), which restricts the translation row to the language of the current session. This is the defining characteristic of a _VL view: it returns one row per global, translated into the caller's language, and automatically returns the base values if no translation exists. The view also surfaces B.ROWID as ROW_ID, which is required so that Oracle Forms and OAF-based maintenance screens can treat the view as updatable.

Key Columns

• GLOBAL_ID — primary identifier of the global; the join key between the base and translation tables.
• GLOBAL_NAME / BASE_GLOBAL_NAME — the translated and untranslated names of the global. Formula authors reference the global by its name.
• GLOBAL_DESCRIPTION / BASE_GLOBAL_DESCRIPTION — the translated and untranslated descriptive text. These are the columns most relevant to the "global_description" search.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the global value.
• BUSINESS_GROUP_ID — owning business group; identifies the enterprise context of the global.
• LEGISLATION_CODE — the country/legislation the global applies to, critical for payroll localization.
• DATA_TYPE — the data type of the stored value (e.g., number, text, date).
• GLOBAL_VALUE — the actual value substituted into formulas at runtime.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER support auditing and optimistic locking.

Common Use Cases and Queries

Typical uses include listing payroll globals for a business group, extracting global descriptions for documentation, joining globals into formula diagnostics, and driving localization reviews.

• List all globals with their descriptions for a business group and legislation.
• Search for a global by description text (the "global_description" scenario).
• Identify globals that have no translation in the current language (where GLOBAL_DESCRIPTION equals BASE_GLOBAL_DESCRIPTION or is null).
• Feed a report of effective-dated global values for audit.

Sample SQL:

• SELECT global_id, global_name, global_description, legislation_code, business_group_id, data_type, global_value FROM apps.ff_globals_f_vl WHERE business_group_id = :p_business_group_id ORDER BY global_name;
• SELECT global_id, global_name, global_description FROM apps.ff_globals_f_vl WHERE UPPER(global_description) LIKE UPPER('%&search_text%');
• SELECT global_name, global_description, global_value FROM apps.ff_globals_f_vl WHERE legislation_code = 'US' AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Because the view is language-aware, query results depend on the value of USERENV('LANG') at execution time; integrations that must return deterministic text should query the base description or explicitly set the session language.