Search Results xdo_ds_definitions_tl_pk

Overview

The XDO_DS_DEFINITIONS_TL table is a core translation (TL) object within the XML Publisher (XDO) product of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the multilingual repository for the user-facing names and descriptions of Data Source definitions. A Data Source in XML Publisher is a logical definition that specifies how to retrieve data for a report, typically via a SQL query, a PL/SQL package, or a concurrent program. While the base transactional data for these definitions is stored in XDO_DS_DEFINITIONS_B, the XDO_DS_DEFINITIONS_TL table holds the translated text, enabling the display of the Data Source name and description in the language of the EBS user. This separation is a standard Oracle application architecture pattern supporting global deployments.

Key Information Stored

The table stores translated attributes for each Data Source definition, keyed by language and the source definition's unique identifier. The primary columns, as defined by its documented constraints, are critical. The APPLICATION_SHORT_NAME and DATA_SOURCE_CODE columns, together with LANGUAGE, form the primary key (XDO_DS_DEFINITIONS_TL_PK). These columns link the translation record directly to its corresponding base record in XDO_DS_DEFINITIONS_B. The DATA_SOURCE_NAME column holds the translated, user-visible name of the Data Source. A unique key (XDO_DS_DEFINITIONS_TL_UK1) on APPLICATION_SHORT_NAME, DATA_SOURCE_NAME, and LANGUAGE ensures name uniqueness within a given application and language. While not explicitly listed in the provided metadata, a DESCRIPTION column is typically present in TL tables to store the translated description, and a SOURCE_LANG column is standard to denote the original language of the record.

Common Use Cases and Queries

The primary use case is to retrieve the localized name of a Data Source for UI display or reporting. A common query pattern involves joining to the base table to get a complete, translated list of Data Sources for a specific application or module. For instance, to find all Data Sources and their English names for the General Ledger (SQLGL) application, one would query:

• SELECT b.DATA_SOURCE_CODE, tl.DATA_SOURCE_NAME, tl.DESCRIPTION
• FROM XDO.XDO_DS_DEFINITIONS_B b,
• XDO.XDO_DS_DEFINITIONS_TL tl
• WHERE b.APPLICATION_SHORT_NAME = tl.APPLICATION_SHORT_NAME
• AND b.DATA_SOURCE_CODE = tl.DATA_SOURCE_CODE
• AND tl.LANGUAGE = USERENV('LANG')
• AND b.APPLICATION_SHORT_NAME = 'SQLGL';

This table is also central during the translation process, where seed data is inserted or updated via FNDLOAD or direct SQL to support additional languages.

Related Objects

This table has a direct and dependent relationship with the XDO_DS_DEFINITIONS_B table, which holds the base definition. The relationship is enforced through the primary and foreign key on the composite columns APPLICATION_SHORT_NAME and DATA_SOURCE_CODE. All Data Source translation records are child records of a parent in the base table. The table is also intrinsically linked to the broader XML Publisher data model, which includes objects like XDO_DS_DEFINITIONS_B (base), XDO_TEMPLATES_B/TL (for templates that use the data source), and XDO_LOBS (for stored XML data). Queries for report definitions or data model audits will frequently join through this translation table to present user-friendly names.