Search Results wf_lookups_tl




Overview
Explore in AI Chat

Overview

The WF_LOOKUPS_TL table is a core translation table within the Oracle E-Business Suite (EBS) Application Object Library (FND) module. Owned by the APPLSYS schema, its primary role is to store translated text for the lookup codes defined in the base WF_LOOKUPS table. This structure is fundamental to the multi-language support in Oracle Workflow (WF), enabling the runtime display of user-facing lookup values—such as statuses, types, or categories—in the language of the user's session. It is a critical component for the internationalization (i18n) of Oracle Workflow processes and notifications in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table stores the translated meaning for a specific lookup code within a specific lookup type and language. Its structure is defined by a composite primary key and a translated description column. The key columns, as documented, are LOOKUP_TYPE, LOOKUP_CODE, and LANGUAGE. The LOOKUP_TYPE and LOOKUP_CODE columns together uniquely identify a specific lookup value from the base WF_LOOKUPS table. The LANGUAGE column holds the language code (e.g., 'US' for American English, 'D' for German) for the translation. The most significant data column is MEANING, which contains the actual translated text displayed to the end-user for that lookup code in the specified language. Additional standard translation table columns, such as SOURCE_LANG, may also be present to track the source language of the translation.

Common Use Cases and Queries

The primary use case is retrieving user-friendly, translated descriptions for workflow-related codes within reports, forms, or custom program logic. A typical query joins this table with WF_LOOKUPS, filtering by the user's session language. For example, to retrieve all translated lookup meanings for a specific lookup type:

  • SELECT wlt.lookup_code, wlt.meaning FROM wf_lookups_tl wlt WHERE wlt.lookup_type = '<LOOKUP_TYPE>' AND wlt.language = USERENV('LANG');

Another common pattern is to report on missing translations for a given lookup type by comparing against the base table or the source language records. Developers and functional consultants query this table to verify that custom workflow lookup values have been properly seeded with translations for all implemented languages.

Related Objects

WF_LOOKUPS_TL has defined foreign key relationships that anchor it within the Workflow data model. As per the provided metadata, it references two key translation tables:

  • WF_LOOKUPS: The base table for lookup codes. The relationship is implicit through the primary key columns (LOOKUP_TYPE, LOOKUP_CODE).
  • WF_LOOKUP_TYPES_TL: The translation table for lookup type definitions. A documented foreign key exists from WF_LOOKUPS_TL.LOOKUP_TYPE and WF_LOOKUPS_TL.LANGUAGE to WF_LOOKUP_TYPES_TL, ensuring that a translated lookup code belongs to a valid translated lookup type.

This table is also intrinsically linked to the FND_LOOKUP_VALUES table, which serves a similar purpose for application lookups, though WF_LOOKUPS_TL is specific to the Oracle Workflow engine's internal data structures.