Search Results wf_activity_attributes_tl




Overview
Explore in AI Chat

Overview

The WF_ACTIVITY_ATTRIBUTES_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 serves a critical role in the Oracle Workflow engine for versions 12.1.1 and 12.2.2. This table stores the translated, language-specific text for attributes associated with workflow activities. Its primary function is to enable the multilingual display of workflow attribute names and display names within the user interface, allowing a single workflow definition to support multiple installed languages. The table's existence is fundamental to the internationalization (i18n) capabilities of Oracle Workflow, ensuring that process notifications, administrator views, and runtime messages are presented in the user's preferred language.

Key Information Stored

The table's structure is defined by its composite primary and unique keys, which enforce data integrity for translations. The most significant columns include the identifiers that link back to the base attribute definition and the language-specific text itself. The ACTIVITY_ITEM_TYPE, ACTIVITY_NAME, ACTIVITY_VERSION, and NAME columns together form a foreign key to the WF_ACTIVITY_ATTRIBUTES table, uniquely identifying the base attribute to be translated. The LANGUAGE column holds the language code (e.g., 'US' for American English). The DISPLAY_NAME column contains the translated, user-friendly name of the attribute as it should appear in the UI. The NAME column itself is also stored, representing the internal, non-translated attribute name. The ACTIVITY_VERSION column is a crucial component, ensuring that translations are correctly associated with a specific version of a workflow activity, which is essential for version-controlled workflow processes.

Common Use Cases and Queries

A primary use case is querying the translated display names for workflow attributes for reporting or troubleshooting UI display issues. For example, an administrator may need to verify or audit all Spanish ('ES') translations for attributes in a specific workflow activity. Given the user's search context for "activity_version," a common query pattern would involve joining to the base table to retrieve comprehensive details for a specific activity version.

Sample Query:
SELECT t.ACTIVITY_ITEM_TYPE, t.ACTIVITY_NAME, t.ACTIVITY_VERSION, t.NAME, t.DISPLAY_NAME, t.LANGUAGE
FROM APPLSYS.WF_ACTIVITY_ATTRIBUTES_TL t
WHERE t.ACTIVITY_ITEM_TYPE = '<Item Type>'
AND t.ACTIVITY_NAME = '<Activity Name>'
AND t.ACTIVITY_VERSION = <Activity Version>
AND t.LANGUAGE = '<Language Code>';

Another critical scenario is during the development or upgrade of custom workflows, where developers must ensure that all necessary attribute translations are seeded or created for newly added attributes across all installed languages.

Related Objects

The table maintains a strict dependency on the base definition table through a documented foreign key relationship. The primary related object is the WF_ACTIVITY_ATTRIBUTES table, which holds the non-translated, master definition of workflow activity attributes. The foreign key from WF_ACTIVITY_ATTRIBUTES_TL references WF_ACTIVITY_ATTRIBUTES on the composite key of (ACTIVITY_ITEM_TYPE, ACTIVITY_NAME, ACTIVITY_VERSION, NAME). This relationship ensures that every translation record corresponds to a valid base attribute. For a complete view of a workflow activity's metadata, one would typically join this translation table with WF_ACTIVITY_ATTRIBUTES and its parent tables, such as WF_ACTIVITIES_TL and WF_ITEM_TYPES_TL.