Results for “xdp_wi_fa_mapping_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XDP_WI_FA_MAPPING_TL is the Multi-Language Support (MLS) translation table that accompanies the XDP_WI_FA_MAPPING base table within the XDP – Provisioning product module of Oracle E-Business Suite. In Oracle EBS 12.1.1 and 12.2.2, MLS architecture separates language-independent business data from its translatable text attributes. The base table stores the operational record, while the _TL table holds the language-specific descriptive content keyed by a language code. This table is critical for deployments that support multiple installed languages, since each translatable row is replicated once per active language, allowing user-facing text to render in the session language selected by the user.
From a data-modeling perspective, the supplied metadata classifies this object as satellite-leaning. That heuristic suggests the table behaves primarily as a descriptive satellite attached to a parent business entity rather than as an independent hub or an associative link. The parent entity is represented by XDP_WI_FA_MAPPING, and the _TL table enriches it with language-dependent attributes while inheriting its identity.
Key Information Stored
The table contains eleven documented columns. The most significant are:
- WI_FA_MAPPING_ID – Surrogate foreign key to the parent XDP_WI_FA_MAPPING record; the core identity component linking a translation to its base row.
- LANGUAGE – The language code (for example, US or FR) identifying which installed language this row's translated text belongs to.
- SOURCE_LANG – The language of the source text from which translations were derived, used by MLS tooling for audit and translation workflow.
- DESCRIPTION – The translatable descriptive text, the primary user-facing attribute whose value varies by language in this table.
- SECURITY_GROUP_ID – References FND_SECURITY_GROUPS, enforcing multi-tenant or operating-unit level data segregation.
- ZD_EDITION_NAME – Editioning column supporting Oracle EBS 12.2 online patching; part of the unique business key.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO columns tracking record audit history.
The surrogate primary key is XDP_WI_FA_MAPPING_TL_PK, defined on (WI_FA_MAPPING_ID, LANGUAGE). A separate unique index, XDP_WI_FA_MAPPING_TL_U1, defined on (WI_FA_MAPPING_ID, LANGUAGE, ZD_EDITION_NAME), functions as the business-key candidate in the 12.2 editioning model. The distinction matters: the primary key guarantees one translation per language per parent, while the unique index adds edition scope for online patching concurrency.
Common Use Cases and Queries
The most frequent requirement is retrieving the translated description for a parent record in a specific language, typically joining the _TL table to its base table and filtering by LANGUAGE. A representative pattern selects the base record joined by WI_FA_MAPPING_ID and constrains LANGUAGE to the session or reporting language. For multilingual reporting, developers aggregate across languages to compare available translations or identify missing ones. Administrators often audit translation completeness by counting rows per WI_FA_MAPPING_ID against the number of installed languages. During patching or troubleshooting, DBAs query by ZD_EDITION_NAME to isolate edition-specific rows. Security-conscious queries include SECURITY_GROUP_ID predicates to respect data segregation, aligning with the FND_SECURITY_GROUPS foreign key.
Related Objects
- XDP_WI_FA_MAPPING – The primary base table; joined on WI_FA_MAPPING_ID, supplying the language-independent operational record.
- FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID, providing the security group validation and segregation context.
- FND_LANGUAGES – Logical lookup validating the LANGUAGE code against installed languages.
- FND_TERRITORIES – Related foundation table supporting locale context for translated content.
- XDX_WI_FA_MAPPING (or equivalent editioning views) – Editioning and MLS views that expose translated content transparently.
- FND_APPLICATION / XDP module objects – Provisioning module components consuming mapping descriptions.
Because access to XDP_WI_FA_MAPPING_TL is structured around the WI_FA_MAPPING_ID and LANGUAGE pair, efficient queries should filter on those columns and join upward to the base table. Understanding this MLS satellite reduces errors when reporting translated provisioning data across multi-language EBS environments.
-
XDP_WI_FA_MAPPING_TL is the MLS (Multi-Language Support) table for the XDP_WI_FA_MAPPING table
-
XDP_WI_FA_MAPPING_TL is the MLS (Multi-Language Support) table for the XDP_WI_FA_MAPPING table
-
View: XDP_WI_FA_MAPPING_VL 12.1.1
The view XDP_WI_FA_MAPPING_VL defines the list of Fulfillment Actions to be excuted in order to fulfill a given workitem.
APPS.XDP_WI_FA_MAPPING_VL·↳ XDP_WI_FA_MAPPING·↳ XDP_WI_FA_MAPPING_TL·Explore XDP module →
-
View: XDP_WI_FA_MAPPING_VL 12.2.2
The view XDP_WI_FA_MAPPING_VL defines the list of Fulfillment Actions to be excuted in order to fulfill a given workitem.
APPS.XDP_WI_FA_MAPPING_VL·↳ XDP_WI_FA_MAPPING·↳ XDP_WI_FA_MAPPING_TL·Explore XDP module →
-
The view XDP_WI_FA_MAPPING_DISP_V defines the list of Fulfillment Actions to be excuted in order to fulfill a given workitem.
APPS.XDP_WI_FA_MAPPING_DISP_V·↳ XDP_FULFILL_ACTIONS·↳ XDP_FULFILL_ACTIONS_TL·↳ XDP_WI_FA_MAPPING·Explore XDP module →
-
The view XDP_WI_FA_MAPPING_DISP_V defines the list of Fulfillment Actions to be excuted in order to fulfill a given workitem.
APPS.XDP_WI_FA_MAPPING_DISP_V·↳ XDP_FULFILL_ACTIONS·↳ XDP_FULFILL_ACTIONS_TL·↳ XDP_WI_FA_MAPPING·Explore XDP module →
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - XDP Tables and Views 12.2.2
Fulfillment Worklist Details
-
eTRM - XDP Tables and Views 12.1.1
Fulfillment Worklist Details
-
12.2.2 DBA Data 12.2.2