Search Results wf_activities_tl

Overview

The WF_ACTIVITIES_TL table is a core translation table within the Oracle E-Business Suite (EBS) Application Object Library (FND) module. It is owned by the APPLSYS schema and is integral to the Oracle Workflow technology stack. Its primary role is to store translated text for workflow activity definitions, enabling the multilingual support that is critical for global EBS deployments. This table holds the user-facing, language-specific labels for activities defined in the base table, WF_ACTIVITIES. By separating translatable text into this table, Oracle Workflow can present process diagrams, notifications, and administrator interfaces in a user's preferred language without altering the underlying process logic or code.

Key Information Stored

The table's structure is designed to map translated text to a specific workflow activity and language. Its columns can be logically grouped into keys and translated attributes. The primary key, WF_ACTIVITIES_TL_PK, uniquely identifies a translation row and consists of the activity's ITEM_TYPE, NAME, VERSION, and LANGUAGE code. A second unique key, WF_ACTIVITIES_TL_U2, ensures uniqueness for the translated display name across the same dimensions. The most critical data columns include DISPLAY_NAME, which stores the translated label for the activity shown in user interfaces, and DESCRIPTION. The SOURCE_LANG column typically indicates the language of the original seed data from which a translation was made.

Common Use Cases and Queries

This table is primarily accessed by the Oracle Workflow engine during runtime to display activity information in the session language. Common administrative and reporting use cases include auditing translation coverage and extracting labels for custom reports. A typical query to retrieve all English and French translations for a specific activity would be:

• SELECT a.item_type, a.name, a.version, tl.language, tl.display_name
• FROM wf_activities a, wf_activities_tl tl
• WHERE a.item_type = tl.item_type
• AND a.name = tl.name
• AND a.version = tl.version
• AND tl.language IN ('US', 'F')
• AND a.name = 'MY_PROCESS_ACTIVITY';

Another common pattern is identifying activities missing a translation for a critical language by performing an outer join between the base and translation tables for a specific language code.

Related Objects

WF_ACTIVITIES_TL has a direct and essential relationship with its parent base table, WF_ACTIVITIES, which stores the non-translatable activity definition. It is also closely related to other Workflow translation tables following the same pattern, such as WF_ITEM_ATTRIBUTES_TL and WF_MESSAGES_TL. The primary access path for applications should be through the public Oracle Workflow APIs, which properly handle language session context. The table is a key component for views that present a language-specific perspective on workflow definitions, though these are typically internal to the product.