Results for “xdp_fes_tl”

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

Overview

XDP_FES_TL is a translation (TL) table in the XDP schema, belonging to the XDP – Provisioning product within Oracle E-Business Suite 12.1.1 and 12.2.2. The table holds language-specific descriptive details for network element instances, specifically the translatable display names and descriptions associated with field engineering specifications (FES, or "Fulfillment Element Specifications" in the context of provisioning) defined in the base table XDP_FES. In Oracle EBS multilingual deployments, the _TL suffix denotes a table that stores one row per translatable attribute per installed language, enabling runtime language selection based on the session's NLS_LANG and language settings.

From a Data Vault modeling perspective, the FK-derived heuristic classifies XDP_FES_TL as satellite-leaning. This suggests it should be modelled as a satellite attached to the XDP_FES hub, carrying descriptive, language-dependent attributes. The base entity identity (FE_ID) is inherited from the hub; the LANGUAGE component augments the key to form the composite primary key of the satellite.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• FE_ID – Foreign key to XDP_FES; identifies the network element / fulfillment element specification instance being described.
• LANGUAGE – The language code for the translation row (e.g., US, DE, FR). Together with FE_ID this forms part of the primary key.
• SOURCE_LANG – The source language from which the translation originates.
• DISPLAY_NAME – The user-facing translated name of the network element instance.
• DESCRIPTION – The translated long description for the network element instance.
• ZD_EDITION_NAME – Editioning column used in 12.2 EBR (Edition-Based Redefinition) deployments; it participates in the unique key alongside FE_ID and LANGUAGE.
• SECURITY_GROUP_ID – FK to FND_SECURITY_GROUPS, enforcing multi-org / data security scoping.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO columns for auditing and concurrency control.

The primary key XDP_FES_TL_PK is defined on (FE_ID, LANGUAGE). A unique index XDP_FES_TL_U1 on (FE_ID, LANGUAGE, ZD_EDITION_NAME) is the documented business-key candidate in the editioning scheme. The surrogate identity is the composite (FE_ID, LANGUAGE); no separate numeric surrogate is present, and the business-key attribute (DISPLAY_NAME) is not part of the key, confirming satellite character.

Common Use Cases and Queries

Typical usage centres on retrieving the correct translated display name for a network element in the user's current language, with fallback to the source language when a translation is missing.

• Fetching a translated name for a given element:

  SELECT TL.DISPLAY_NAME, TL.DESCRIPTION
  FROM   XDP_FES_TL TL
  WHERE  TL.FE_ID = :p_fe_id
  AND    TL.LANGUAGE = USERENV('LANG');

• Listing all translations for a specific element across languages:

  SELECT LANGUAGE, DISPLAY_NAME
  FROM   XDP_FES_TL
  WHERE  FE_ID = :p_fe_id;

• Reporting elements missing a translation in a target locale:

  SELECT F.FE_ID
  FROM   XDP_FES F
  LEFT JOIN XDP_FES_TL TL
    ON TL.FE_ID = F.FE_ID AND TL.LANGUAGE = 'DE'
  WHERE  TL.FE_ID IS NULL;

• Security-scoped lookups joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS for restricted data access.

Related Objects

• XDP_FES – Base (non-translated) parent table; joined via XDP_FES_TL.FE_ID = XDP_FES.FE_ID.
• FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID for data security scoping.
• XDP_FES_TL_PK / XDP_FES_TL_U1 – Primary key and unique business-key indexes supporting efficient lookups.
• XDP_FES_B / XDP_FES_VL – Typical base and view-layer companions in EBS multilanguage schemas exposing translated column values.
• FND_LANGUAGES – Reference table for validating LANGUAGE and SOURCE_LANG codes.

Developers integrating with XDP provisioning generally query the corresponding _VL view rather than the _TL table directly, allowing EBS to resolve the appropriate language row automatically.