Results for “data_source_code”

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

Overview

XDO_DS_DEFINITIONS_TL is the translation (language) table that accompanies XDO_DS_DEFINITIONS_B within the XML Publisher (XDO) product in Oracle E-Business Suite 12.1.1 and 12.2.2. The base table XDO_DS_DEFINITIONS_B stores the language-independent definition of a data source — the template-facing object used by XML Publisher, BI Publisher, and concurrent programs that generate reports against a data template. The _TL table holds the translated, language-specific attributes for those definitions, most notably the user-visible data source name and description. It is owned by the XDO schema and is registered as VALID.

In Oracle EBS, every _TL table is populated for each installed language (LANGUAGE column), with SOURCE_LANG identifying the language in which the row was originally authored. This permits XML Publisher data source names and descriptions to display in the session language of the report consumer without duplicating the underlying definition. Within the ETRM relationship data, XDO_DS_DEFINITIONS_TL is classified heuristically as a standalone satellite: it carries descriptive, translatable attributes keyed to a parent entity but with no mined foreign-key dependency to another table. That classification is a modeling suggestion only — physically, the _TL table is joined to its base table by convention on the shared key columns rather than through a declared FK constraint.

Key Information Stored

Of the twelve documented columns, the following are the most significant:

• APPLICATION_SHORT_NAME — the application owning the data source (for example, an EBS application short code). Part of both the primary key and the business-key unique indexes.
• DATA_SOURCE_CODE — the internal identifier of the data source. This is the user's search term and a core component of the primary key.
• LANGUAGE — the language of the translated row; part of the primary key.
• DATA_SOURCE_NAME — the translated, user-visible name of the data source. Forms the basis of the second unique index.
• DESCRIPTION — the translated descriptive text for the data source.
• SOURCE_LANG — the language in which the row was originally seeded, used by the translation process.
• ZD_EDITION_NAME — the editioning column introduced in the 12.2 online-patching architecture; it participates in both documented unique indexes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track row provenance.

The primary key is XDO_DS_DEFINITIONS_TL_PK (APPLICATION_SHORT_NAME, DATA_SOURCE_CODE, LANGUAGE). Two unique indexes serve as business-key candidates: XDO_DS_DEFINITIONS_TL_U1 (APPLICATION_SHORT_NAME, DATA_SOURCE_CODE, LANGUAGE, ZD_EDITION_NAME) and XDO_DS_DEFINITIONS_TL_U2 (APPLICATION_SHORT_NAME, DATA_SOURCE_NAME, LANGUAGE, ZD_EDITION_NAME). No separate surrogate column exists; the composite key acts as the identifier.

Common Use Cases and Queries

Typical usage centers on resolving the display name of a data source for a given session language, and on auditing translations across all installed languages.

• Resolve a data source by code: select the translated name and description for a specific code and language.

SELECT data_source_name, description
FROM   xdo.xdo_ds_definitions_tl
WHERE  application_short_name = :app_short_name
AND    data_source_code = :data_source_code
AND    language = USERENV('LANG');

• Translation coverage report: identify data sources lacking rows for a target language.
• Duplicated-name detection: the U2 index enforces uniqueness of DATA_SOURCE_NAME per application, language, and edition.
• Listing available data sources: joining to XDO_DS_DEFINITIONS_B to enumerate codes with their friendly names.

Related Objects

The most significant related objects and join columns are:

• XDO_DS_DEFINITIONS_B — base table; join on APPLICATION_SHORT_NAME and DATA_SOURCE_CODE.
• XDO_DS_DEFINITIONS_VL — the standard EBS view combining base and translated rows.
• XDO_DS_DEFINITIONS_TL_PK / U1 / U2 — key indexes enforcing identity and business uniqueness.
• FND_LANGUAGES — join on LANGUAGE and SOURCE_LANG to resolve language names.
• FND_APPLICATION — join on APPLICATION_SHORT_NAME to obtain application display names.