Search Results wf_languages




Overview
Explore in AI Chat

Overview

APPS.WF_LANGUAGES is a reporting and integration view in the Oracle E-Business Suite Application Object Library (FND) product family. Its documented purpose is the presentation of "National Dialects" — that is, the language and territory combinations, together with their associated character sets, that are relevant to Oracle Workflow and to the broader EBS globalization layer. In EBS 12.1.1 and 12.2.2 the view is registered in the ETRM as a VALID object owned by the APPS schema, and it is exposed alongside other FND language and character-set objects for use by concurrent programs, PL/SQL APIs, and ad hoc reporting.

Functionally, the view consolidates installation status, translated display names, NLS attributes, and email character-set overrides into a single queryable structure. This makes it a convenient single source for code that must determine which languages are actually installed, how each language should be labelled to the end user, and whether an outbound email encoding override applies. Because it is a view rather than a table, no storage is consumed and no direct DML is permitted against it.

Underlying Base Objects

The ETRM 12.2.2 metadata documents three referenced base objects, all accessed through APPS synonyms: FND_LANGUAGES, FND_LANGUAGES_TL, and WF_OVERRIDE_CHARSETS.

  • FND_LANGUAGES supplies the core language rows, including LANGUAGE_CODE, the NLS language, territory, and codeset attributes, and the INSTALLED_FLAG that records whether a language is fully installed ('I'), partially installed at the binary level ('B'), or not installed ('N').
  • FND_LANGUAGES_TL is the translation table that provides the user-facing DESCRIPTION, exposed here as DISPLAY_NAME. It is joined to FND_LANGUAGES on LANGUAGE_CODE, with the additional predicate LTL.LANGUAGE = USERENV('LANG') so that only the description in the current session language is returned. This is significant for reporting: the display name is session-sensitive.
  • WF_OVERRIDE_CHARSETS provides the OVERRIDE_EMAIL_CHARSET value and is joined using a FULL OUTER JOIN on CODE. The outer join ensures that languages present only in the override table, or only in the language tables, are still returned by the view rather than being silently dropped.

The view text therefore produces the column CODE as NVL(B.LANGUAGE_CODE, C.CODE), and normalizes the installed flag so that both 'B' and 'I' map to 'Y' and 'N' maps to 'N'.

Key Columns

  • CODE — the language code, derived from FND_LANGUAGES.LANGUAGE_CODE or, where absent, from WF_OVERRIDE_CHARSETS.CODE. This is the primary join key for language-related lookups.
  • DISPLAY_NAME — the translated language description from FND_LANGUAGES_TL, resolved for the session language. Useful for user-facing lists of values.
  • NLS_LANGUAGE, NLS_TERRITORY, NLS_CODESET — the Oracle National Language Support attributes describing the language/territory pairing and its database character set.
  • INSTALLED_FLAG — a normalized indicator ('Y' or 'N') reflecting whether the language is installed; both the binary and installed states resolve to 'Y'.
  • OVERRIDE_EMAIL_CHARSET — the character set that should be used when transmitting email for that language, when an override is defined in WF_OVERRIDE_CHARSETS.

Common Use Cases and Queries

Typical scenarios include validating the languages available for a Workflow notification, driving a selection list of installed languages, and auditing email character-set behavior in multilingual deployments.

To list all installed languages with their NLS attributes:

SELECT code, display_name, nls_language, nls_territory, nls_codeset
FROM  apps.wf_languages
WHERE installed_flag = 'Y'
ORDER BY display_name;

To identify languages with an email character-set override:

SELECT code, display_name, override_email_charset
FROM  apps.wf_languages
WHERE override_email_charset IS NOT NULL;

Because the view is owned by APPS, access should be granted through the appropriate responsibility or directed synonym rather than queried directly by non-APPS schemas. Report authors should also note that DISPLAY_NAME depends on the session's LANG setting, so results may differ between interactive sessions and concurrent requests. For this reason, comparisons against DISPLAY_NAME in code should be avoided in favour of CODE.