Search Results ams_dlg_comp_types_b




Overview
Explore in AI Chat

Overview

The AMS_DLG_COMP_TYPES_B table is a core repository within the Oracle E-Business Suite Marketing (AMS) module, specifically for the Dialog Engine functionality in releases 12.1.1 and 12.2.2. It serves as the master definition table for dialog component types. In the context of Oracle Marketing's Dialog Engine, which manages interactive customer communications and marketing workflows, this table defines the fundamental building blocks or templates available for constructing a dialog flow. Each record represents a distinct type of component, such as an email dispatcher, a decision node, a wait activity, or a web service call, that can be placed within a marketing dialog. Its primary role is to provide a controlled, referential foundation for the actual dialog components instantiated in campaigns, ensuring consistency and enabling the configuration of type-specific parameters and outcomes.

Key Information Stored

The central piece of data stored in this table is the unique identifier for each component type. While the provided ETRM metadata explicitly names only the primary key column, the structure and naming conventions of related tables allow for reliable inference of other critical columns. The primary key, COMPONENT_TYPE_ID, is a numeric identifier that uniquely defines each component type. It is highly probable the table also contains columns such as COMPONENT_TYPE_CODE (a short name or key), ENABLED_FLAG (to control active status), and CREATION_DATE/CREATED_BY for auditing. This table stores the seed data for system-defined component types; custom component types may also be registered here. The associated translation table, AMS_DLG_COMP_TYPES_TL, holds the user-facing name and description for each COMPONENT_TYPE_ID in multiple languages.

Common Use Cases and Queries

This table is primarily referenced for setup, reporting, and administrative purposes rather than transactional processing. A common use case is generating a list of all available dialog component types for display in a setup UI or for validation within a custom extension. System administrators may query it to audit available components or check their status. When troubleshooting a dialog flow, one might join to this table to understand the type of a problematic component. A typical reporting query would join the base table with its translation table to get user-readable names:

  • SELECT b.COMPONENT_TYPE_ID, tl.NAME, tl.DESCRIPTION, b.ENABLED_FLAG FROM AMS_DLG_COMP_TYPES_B b, AMS_DLG_COMP_TYPES_TL tl WHERE b.COMPONENT_TYPE_ID = tl.COMPONENT_TYPE_ID AND tl.LANGUAGE = USERENV('LANG');

Another key use case is as a constraint for defining valid parameters; the AMS_DLG_COMP_TYPE_PARAMS_B table defines which parameters are valid for a given COMPONENT_TYPE_ID stored here.

Related Objects

The AMS_DLG_COMP_TYPES_B table sits at the top of a key hierarchy in the Dialog Engine data model, as evidenced by its multiple foreign key relationships. The documented relationships are as follows:

  • AMS_DLG_COMP_TYPES_TL: The translation table. Joined via AMS_DLG_COMP_TYPES_TL.COMPONENT_TYPE_ID = AMS_DLG_COMP_TYPES_B.COMPONENT_TYPE_ID to provide multilingual names and descriptions.
  • AMS_DLG_COMP_TYPE_OUTCOME_B: Defines the possible outcomes (e.g., "Success", "Error") for a specific component type. Joined via AMS_DLG_COMP_TYPE_OUTCOME_B.COMPONENT_TYPE_ID = AMS_DLG_COMP_TYPES_B.COMPONENT_TYPE_ID.
  • AMS_DLG_COMP_TYPE_PARAMS_B: Defines the configurable parameters for a specific component type. Joined via AMS_DLG_COMP_TYPE_PARAMS_B.COMPONENT_TYPE_ID = AMS_DLG_COMP_TYPES_B.COMPONENT_TYPE_ID.
  • AMS_DLG_FLOW_COMPS_B: The table storing actual instances of components within a dialog flow. Each instance references its type definition via AMS_DLG_FLOW_COMPS_B.COMPONENT_TYPE_ID = AMS_DLG_COMP_TYPES_B.COMPONENT_TYPE_ID.