Results for “ams_dlg_comp_types_tl”

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

Overview

The AMS_DLG_COMP_TYPES_TL table is a Marketing (AMS) module data object in Oracle E-Business Suite that stores the translatable (language-dependent) attribute values for Dialog Component Types. Dialog Component Types define the reusable building blocks — such as text, question, list, or instruction elements — that make up a marketing dialog or campaign interaction flow. Because these component types carry user-facing labels and descriptions that must be presented in a user's preferred language, the translatable text is separated from the language-independent definition into this "_TL" companion table.

Within the Oracle EBS architecture, "_TL" tables follow a consistent convention: a "_B" base table holds the structural, non-translatable columns, while the "_TL" table holds the translated name, description, and similar textual attributes keyed by language. In this case, AMS_DLG_COMP_TYPES_TL is the translation satellite for AMS_DLG_COMP_TYPES_B. Applying a Data Vault modeling lens, the ETRM metadata classifies this object as satellite-leaning: it is not an independent hub, but a dependent descriptor table that enriches a core entity with attributes and carries a composite, language-qualified identity. It should therefore be modeled as a satellite attached to the AMS_DLG_COMP_TYPES_B hub.

Key Information Stored

The table's documented structure is compact, centering on identity and translated content:

• COMPONENT_TYPE_ID — The identifier of the dialog component type. This is the surrogate primary key component linking back to the base table; it is not unique on its own within this table.
• LANGUAGE — The language code identifying the translation locale for the row. Combined with COMPONENT_TYPE_ID, it forms the composite primary key.
• Translatable name and description columns — The "_TL" convention implies at least a translated Name and Description attribute holding the human-readable label and explanatory text in the given LANGUAGE. These are the principal business-content columns; exact column names are not enumerated in the supplied metadata.
• Source language and audit columns — Oracle EBS translation tables typically include SOURCE_LANG plus the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) governing row lifecycle and audit lineage.

The surrogate primary key is AMS_DLG_COMP_TYPES_TL_PK, defined across (COMPONENT_TYPE_ID, LANGUAGE). COMPONENT_TYPE_ID alone is a business-key candidate only in combination with LANGUAGE; the pair guarantees one translation row per component type per locale. COMPONENT_TYPE_ID is also the foreign-key link to the base table.

Common Use Cases and Queries

Reporting and integration scenarios most often require joining the translation to its base definition, filtered to a specific language, to present display-ready component type names. A typical pattern:

• Listing component types for a given language: SELECT t.component_type_id, t.language, t.name FROM ams_dlg_comp_types_tl t WHERE t.language = :lang;
• Joining base and translation: SELECT b.component_type_id, t.name FROM ams_dlg_comp_types_b b, ams_dlg_comp_types_tl t WHERE b.component_type_id = t.component_type_id AND t.language = USERENV('LANG');
• Validating translation coverage: identifying component types with no row for a target LANGUAGE, to detect missing localization.

These queries support localization audits, marketing configuration reports, and extraction of dialog metadata into downstream campaign tooling. Because the table is marked "Not implemented in this database" in the ETRM excerpt, availability depends on whether the AMS Dlg component-type feature is deployed and seeded in a given instance; queries should be guarded accordingly.

Related Objects

• AMS_DLG_COMP_TYPES_B — the base table; joined on COMPONENT_TYPE_ID = COMPONENT_TYPE_ID. This is the primary parent referenced by the documented foreign key.
• AMS_DLG_COMP_TYPES_TL_PK — the composite primary key constraint on (COMPONENT_TYPE_ID, LANGUAGE).
• AMS_DLG_COMPONENTS (or equivalent) — dialog components that reference a component type and depend on translated labels.
• AMS_DLG_* base/translation pairs — sibling metadata tables following the same _B/_TL pattern within the AMS Marketing dialog framework.
• FND_LANGUAGES — provides the valid LANGUAGE codes and installed-language context used to resolve translations.

Together these objects form the dialog component-type metadata layer consumed by the AMS marketing dialog configuration and runtime components.