Results for “ams_dlg_comp_types_vl”

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

Overview

AMS_DLG_COMP_TYPES_VL is a Marketing (AMS) module view in Oracle E-Business Suite that returns all Dialog Component Types. It serves as the primary _VL (translated/validated list) interface for the set of component types that can be assembled into a Dialog, the interactive marketing construct used by Oracle Marketing to render campaign content, offers, and message bodies. In EBS 12.1.1 and 12.2.2, the view is exposed as a read-consistent, language-aware access point over the Dialog Component Type entity, allowing reports, concurrent programs, and integration interfaces to resolve a component type's language-independent attributes alongside the display name and description in the user's current session language. The object is documented as a view returning all Dialog Component Types; the ETRM record notes that it is not implemented as a physical object in every database, which is expected because AMS Marketing functionality must be licensed and installed before the underlying tables exist.

Underlying Base Objects

The view is defined over two base tables joined on the COMPONENT_TYPE_ID key:

• AMS_DLG_COMP_TYPES_B — the language-independent (_B) table holding the operational attributes of each Dialog Component Type, including the surrogate COMPONENT_TYPE_ID, the developer-facing COMPONENT_TYPE_CODE, the implementing CLASS_NAME, and the standard WHO/audit and multi-organization columns.
• AMS_DLG_COMP_TYPES_TL — the translation (_TL) table holding NAME and DESCRIPTION per LANGUAGE. The join predicate restricts rows to T.LANGUAGE = USERENV('LANG'), so only the translated values for the current runtime language are returned.

The view text selects from AMS_DLG_COMP_TYPES_TL T and AMS_DLG_COMP_TYPES_B B, joining B.COMPONENT_TYPE_ID = T.COMPONENT_TYPE_ID with the language filter, and projects B.ROWID as ROW_ID along with the columns listed below. Because the source metadata does not document an owning schema or additional referenced objects, the view should be treated as a standard _B/_TL pair view with no further dependencies. Note that CLASS_NAME supplies the Java class bound to the component type, which the Dialog rendering framework instantiates at runtime; this column is therefore the technical counterpart to the user-facing NAME.

Key Columns

• COMPONENT_TYPE_ID — surrogate primary key of the component type; the join and foreign key used by dialog configuration and child entities.
• COMPONENT_TYPE_CODE — the searchable code identifier. This is the column most frequently queried, since it provides a stable, language-independent handle for a specific component type in code, lookups, and data migrations.
• CLASS_NAME — the implementation class responsible for rendering or processing the component; used when tracing runtime behavior or custom components.
• NAME, DESCRIPTION — the translated labels presented to end users in the session language, sourced from the _TL table.
• ROW_ID — the ROWID of the base _B row, exposed under the ROW_ID alias.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, supporting concurrency control and change tracking.
• SECURITY_GROUP_ID — the security grouping column used by the AMS application for access isolation.

Common Use Cases and Queries

The view is typically queried to enumerate available dialog component types, to resolve a code to its translated name, or to validate a component_type_code before inserting configuration data. Common operations include building value sets or LOVs for dialog configuration screens and joining to dialog definition tables by COMPONENT_TYPE_ID.

• Enumerate all types in the session language:
  SELECT component_type_id, component_type_code, name FROM ams_dlg_comp_types_vl ORDER BY component_type_code;
• Resolve a code to its display name:
  SELECT name, description FROM ams_dlg_comp_types_vl WHERE component_type_code = :p_code;
• Audit recent changes:
  SELECT component_type_code, last_update_date, last_updated_by FROM ams_dlg_comp_types_vl WHERE last_update_date > SYSDATE - 30;

Because NAME and DESCRIPTION depend on USERENV('LANG'), multilingual reporting requires care: run reports within a session whose language is set appropriately, or query the _TL table directly with an explicit LANGUAGE value when cross-language output is needed. If the view does not exist in a given instance, the AMS Marketing product is not installed or licensed in that database.