Search Results ff_globals_f_tl




Overview
Explore in AI Chat

Overview

FF_GLOBALS_F_TL is the translated-name table for Oracle Fast Formula globals within the Oracle E-Business Suite Payroll (PAY) module. It resides in the HR schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. Fast Formula globals are reusable variables and constants that can be referenced across multiple formula definitions; FF_GLOBALS_F_TL stores the language-specific display text associated with each global so that the same underlying global can present a localized name and description in each installed language. The "_TL" suffix identifies this as a translation table following the standard EBS multi-language design, where the base ("_F" or "_B") table holds language-independent attributes and the "_TL" table holds the translatable name and description columns.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. This is a heuristic suggestion only: FF_GLOBALS_F_TL carries no outbound foreign keys of its own and is primarily referenced by the base globals table and dependent formulas. In dimensional or Data Vault terms it behaves as a satellite carrying descriptive, language-dependent attributes (GLOBAL_NAME and GLOBAL_DESCRIPTION) keyed to a parent hub (the base globals record) plus a language discriminator.

Key Information Stored

The table contains 11 documented columns. The most operationally significant are:

  • GLOBAL_ID – Surrogate identifier linking each translation row to the base global record; the primary correlation key to the parent globals entity.
  • LANGUAGE – The language code for the translated text; combined with GLOBAL_ID it forms the core business key.
  • SOURCE_LANG – The language from which the translation originated, used by the translation framework to track derivation.
  • GLOBAL_NAME – The user-visible, translated name of the Fast Formula global.
  • GLOBAL_DESCRIPTION – The translated long description explaining the global's purpose.
  • ZD_EDITION_NAME – Editioning column introduced in the 12.2 online patching architecture; participates in the unique index.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE – Standard EBS WHO (audit) columns recording creation and last-modification metadata.

The documented primary key is FF_GLOBALS_F_TL_PK on (GLOBAL_ID, LANGUAGE). A unique index candidate that includes ZD_EDITION_NAME — (GLOBAL_ID, LANGUAGE, ZD_EDITION_NAME) — reflects the edition-aware uniqueness enforced under 12.2.2, ensuring each global has exactly one translated row per language per edition.

Common Use Cases and Queries

Typical scenarios include auditing which globals are translated, locating a global by its display name, and generating bilingual reports of global definitions. A representative query resolves the translated name for a given language:

  • SELECT t.GLOBAL_ID, t.GLOBAL_NAME, t.GLOBAL_DESCRIPTION FROM HR.FF_GLOBALS_F_TL t WHERE t.LANGUAGE = 'US' AND t.GLOBAL_ID = :p_global_id;
  • Searching by display name: SELECT GLOBAL_ID FROM HR.FF_GLOBALS_F_TL WHERE UPPER(GLOBAL_NAME) LIKE UPPER(:p_name) AND LANGUAGE = USERENV('LANG');
  • Identifying untranslated globals by joining back to the base table on GLOBAL_ID and filtering for missing language rows.

Because it is a translation table, reporting tools should always constrain LANGUAGE to avoid duplicate rows per global.

Related Objects

The following objects are most significant in relation to FF_GLOBALS_F_TL:

  • FF_GLOBALS_F – The base (language-independent) globals table; joined on GLOBAL_ID, supplying the parent record.
  • FF_GLOBALS_F_TL_PK – The primary key constraint/index enforcing uniqueness on (GLOBAL_ID, LANGUAGE).
  • FF_FORMULAS_F – Fast Formula definitions that reference globals by name.
  • FF_FORMULA_CONTEXTS – Context definitions that frequently bind globals into formula execution.
  • FF_GLOBALS_F_TL synonyms/views exposed through the PAY and HR product schemas for application access.
  • FND_LANGUAGES – Reference table validating the LANGUAGE and SOURCE_LANG values.

All joins rely on GLOBAL_ID as the shared key, with LANGUAGE providing the per-locale dimension.