Search Results xdp_wi_fa_mapping_tl




Overview
Explore in AI Chat

Overview

The XDP_WI_FA_MAPPING_TL table is a critical component within the Oracle E-Business Suite (EBS) Provisioning (XDP) module, specifically designed to support Multi-Language Support (MLS) or translation requirements. Its primary role is to store translated, language-specific versions of the descriptive content associated with work item and fulfillment action mapping definitions. This table operates as a companion to the base table, XDP_WI_FA_MAPPING, enabling the provisioning system to present user-facing text, such as mapping names or descriptions, in multiple languages based on the user's session language setting. This functionality is essential for global deployments of Oracle EBS 12.1.1 and 12.2.2, ensuring that provisioning workflows are accessible and understandable to users across different locales.

Key Information Stored

The table's structure is characteristic of Oracle EBS translation tables. It stores language-specific textual attributes for each record in the corresponding base table. The key columns include the WI_FA_MAPPING_ID, which is a foreign key linking directly to the primary key of the XDP_WI_FA_MAPPING table, ensuring a one-to-many relationship where one mapping definition can have multiple language entries. The LANGUAGE column identifies the language code (e.g., 'US' for American English, 'KO' for Korean) for each translated row. Together, these two columns form the table's primary key (XDP_WI_FA_MAPPING_TL_PK). The table typically contains one or more descriptive columns, such as MAPPING_NAME or DESCRIPTION, which hold the actual translated text. A SOURCE_LANG column is also commonly present in TL tables to denote the original language in which the data was created, facilitating synchronization during translation processes.

Common Use Cases and Queries

The primary use case is the dynamic retrieval of translated text for the provisioning user interface and reports. When a user accesses a screen displaying work item to fulfillment action mappings, the application automatically queries this table based on the session's LANGUAGE and WI_FA_MAPPING_ID to fetch the appropriate description. A common reporting query involves joining the base and translation tables to produce a language-specific list. For example, to retrieve all mapping names in American English, one might use:

  • SELECT b.WI_FA_MAPPING_ID, t.MAPPING_NAME
  • FROM XDP_WI_FA_MAPPING b, XDP_WI_FA_MAPPING_TL t
  • WHERE b.WI_FA_MAPPING_ID = t.WI_FA_MAPPING_ID
  • AND t.LANGUAGE = USERENV('LANG');

Data maintenance scripts for loading translations also frequently interact with this table, often using the SOURCE_LANG column to identify base records requiring translation updates.

Related Objects

The XDP_WI_FA_MAPPING_TL table has a direct and singular dependency on its base table, as defined by the documented foreign key relationship. The related objects are:

  • Primary Key Constraint: XDP_WI_FA_MAPPING_TL_PK on columns (WI_FA_MAPPING_ID, LANGUAGE).
  • Foreign Key Constraint: The table references the XDP_WI_FA_MAPPING base table. The foreign key column in XDP_WI_FA_MAPPING_TL is WI_FA_MAPPING_ID, which joins to the primary key column of the same name in XDP_WI_FA_MAPPING. This enforces referential integrity, ensuring every translation record corresponds to a valid base mapping definition.

This table is typically accessed indirectly through the provisioning module's application programming interfaces (APIs) or base views, which handle the language-sensitive logic, rather than via direct SQL in custom code.