Search Results xdp_fes_tl




Overview
Explore in AI Chat

Overview

The XDP_FES_TL table is a core data object within the Oracle E-Business Suite (EBS) Provisioning (XDP) module. It functions as a translation table, specifically designed to hold multilingual details for network element instances. In the context of service fulfillment and provisioning, a network element (FE) represents a physical or logical device or resource in the service provider's network that must be configured. The primary role of XDP_FES_TL is to store the user-facing, language-specific descriptions and names for these elements, enabling the provisioning applications to present interface data in the user's preferred language, a critical feature for global deployments.

Key Information Stored

The table's structure centers on a composite primary key and translated text columns. The key columns are FE_ID, which links to the base network element record in the XDP_FES table, and LANGUAGE, which identifies the translation language code (e.g., 'US', 'DE'). The most significant data columns are typically NAME and DESCRIPTION, which hold the translated textual labels for the network element. Additional columns may include SOURCE_LANG to track the original language of the translation and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing. The presence of a Translation Layer ('_TL') suffix indicates this table follows Oracle's standard multilingual architecture.

Common Use Cases and Queries

The primary use case is retrieving a localized description of a network element for display in user interfaces, reports, or integration messages based on the current session language. A standard query pattern involves joining XDP_FES_TL with its base table, XDP_FES, and filtering by the desired FE_ID and LANGUAGE. For example, to fetch all translations for a specific element, one might use:

  • SELECT t.fe_id, t.language, t.name, t.description FROM xdp_fes_tl t WHERE t.fe_id = :p_fe_id;

For application development, queries typically leverage the NLS_LANGUAGE session setting automatically. Reporting on the availability of translations across different network elements is another common administrative task, often checking for missing translations in key languages.

Related Objects

XDP_FES_TL has a direct and critical relationship with the XDP_FES table, as defined by its foreign key constraint. The foreign key XDP_FES_TL.FE_ID references XDP_FES, ensuring that every translation corresponds to a valid base network element record. This table is also intrinsically linked to the broader provisioning data model, which includes objects for service definitions, fulfillment processes, and order line assignments. While not explicitly listed in the provided metadata, it is common for such TL tables to have associated views (e.g., XDP_FES_VL) that provide a convenient, language-sensitive interface for application queries, automatically filtering records based on the user's session language.

  • Table: XDP_FES_TL 12.2.2

    owner:XDP,  object_type:TABLE,  fnd_design_data:XDP.XDP_FES_TL,  object_name:XDP_FES_TL,  status:VALID,  product: XDP - Provisioning ,  description: Table to hold details of network element instances. ,  implementation_dba_data: XDP.XDP_FES_TL , 

  • Table: XDP_FES_TL 12.1.1

    owner:XDP,  object_type:TABLE,  fnd_design_data:XDP.XDP_FES_TL,  object_name:XDP_FES_TL,  status:VALID,  product: XDP - Provisioning ,  description: Table to hold details of network element instances. ,  implementation_dba_data: XDP.XDP_FES_TL , 

  • Table: XDP_FES 12.2.2

    owner:XDP,  object_type:TABLE,  fnd_design_data:XDP.XDP_FES,  object_name:XDP_FES,  status:VALID,  product: XDP - Provisioning ,  description: This table holds all the names of the Fulfillment Elements (Network Elements). This data contains the definition of a fulfillment element. ,  implementation_dba_data: XDP.XDP_FES , 

  • View: XDP_FES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:XDP.XDP_FES_VL,  object_name:XDP_FES_VL,  status:VALID,  product: XDP - Provisioning ,  description: The XDP_FES_VL view will hold all the names of the Fulfillment Elements (Network Elements). This data contains the definition of a fulfillment element.Example: FE or NE is a DMS200, a Cisco CPC, HA Server. ,  implementation_dba_data: APPS.XDP_FES_VL , 

  • View: XDP_FES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:XDP.XDP_FES_VL,  object_name:XDP_FES_VL,  status:VALID,  product: XDP - Provisioning ,  description: The XDP_FES_VL view will hold all the names of the Fulfillment Elements (Network Elements). This data contains the definition of a fulfillment element.Example: FE or NE is a DMS200, a Cisco CPC, HA Server. ,  implementation_dba_data: APPS.XDP_FES_VL , 

  • Table: XDP_FES 12.1.1

    owner:XDP,  object_type:TABLE,  fnd_design_data:XDP.XDP_FES,  object_name:XDP_FES,  status:VALID,  product: XDP - Provisioning ,  description: This table holds all the names of the Fulfillment Elements (Network Elements). This data contains the definition of a fulfillment element. ,  implementation_dba_data: XDP.XDP_FES ,