Results for “xdp_service_wi_map_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XDP_SERVICE_WI_MAP_TL is the Multi-Language Support (MLS) translation table for XDP_SERVICE_WI_MAP, owned by the XDP schema within the Provisioning product module of Oracle E-Business Suite. It stores language-specific descriptive attributes for the base service-to-work-item mapping records, allowing the same underlying mapping row to carry translated text in multiple installed languages. In EBS 12.1.1 and 12.2.2, translation tables of this type follow the standard MLS pattern: a parent/base table holds the language-independent key and transactional data, while the _TL companion table holds one row per (entity, language) pair for translatable columns.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. The table behaves as a descriptive satellite whose grain is the parent mapping combined with language; it carries attributes and audit context rather than serving as a standalone hub or link. Its identity is entirely dependent on the parent XDP_SERVICE_WI_MAP record.

Key Information Stored

The table comprises 11 documented columns. The most significant are:

• SERVICE_WI_MAP_ID — The surrogate identifier referencing the parent mapping row in XDP_SERVICE_WI_MAP. This is the primary join back to the base table.
• LANGUAGE — The language code for the translated row, populated from the installed language set (NLS_LANGUAGE / language_code).
• SOURCE_LANG — The language of the source (typically the base/en language) from which the translation originates, used by the MLS framework for translation tracking.
• DESCRIPTION — The translated descriptive text for the mapping. This is the primary translatable business attribute.
• ZD_EDITION_NAME — The editioning column introduced for EBS 12.2's Online Patching (adop) architecture, distinguishing rows across edition cycles.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-org or security-group scoping.
• LAST_UPDATE_DATE / LAST_UPDATED_BY
• CREATION_DATE / CREATED_BY
• LAST_UPDATE_LOGIN — Standard WHO audit columns recording user and session traceability.

The primary key is the composite XDP_SERVICE_WI_MAP_TL_PK (SERVICE_WI_MAP_ID, LANGUAGE). A unique index, XDP_SERVICE_WI_MAP_TL_U1 (SERVICE_WI_MAP_ID, LANGUAGE, ZD_EDITION_NAME), serves as the business-key candidate once the editioning column is included, reflecting the 12.2 edition-aware uniqueness requirement.

Common Use Cases and Queries

Typical usage centers on retrieving translated descriptions for service/work-item mappings in a specific language. A common query joins the base table to retrieve the base key and translated text:

• SELECTING translated description for a language: SELECT s.SERVICE_WI_MAP_ID, t.DESCRIPTION FROM XDP_SERVICE_WI_MAP s, XDP_SERVICE_WI_MAP_TL t WHERE s.SERVICE_WI_MAP_ID = t.SERVICE_WI_MAP_ID AND t.LANGUAGE = USERENV('LANG').
• Listing all translations for a mapping to audit coverage across installed languages.
• Reporting on rows missing translations by comparing base records against _TL rows for a given language.
• Filtering by SECURITY_GROUP_ID or ZD_EDITION_NAME in reporting extracts to align with security and edition context.

Related Objects

The most significant related objects are:

• XDP_SERVICE_WI_MAP — The base table; joined on SERVICE_WI_MAP_ID. This is the mandatory parent (FK).
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID (FK), linking translations to security scoping.
• FND_LANGUAGES / FND_LANGUAGE (NLS views) — Provide valid LANGUAGE codes for the MLS framework.
• FND_LOOKUPS and related MLS translation tables — Share the same _TL design pattern and translation workflow.

These relationships confirm that XDP_SERVICE_WI_MAP_TL functions as a dependent translation satellite to its base mapping table, with its integrity governed by the composite primary key and the FK to XDP_SERVICE_WI_MAP.