Search Results ams_dlg_comp_type_outcome_b




Overview
Explore in AI Chat

Overview

The AMS_DLG_COMP_TYPE_OUTCOME_B table is a core data entity within the Oracle E-Business Suite Marketing (AMS) module, specifically in the context of the Dialog Engine. This table functions as a master definition table that stores the valid outcomes or results that can be associated with a specific component type used in marketing dialogs. A dialog is a structured, multi-step interaction with a customer, and its components are the building blocks of that interaction. By defining permissible outcomes for each component type, this table enables the tracking and routing of dialog execution based on user responses or system events, forming a critical part of the campaign and interaction management logic in Oracle Marketing.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign keys define the essential structure. The central column is OUTCOME_ID, which serves as the unique primary key identifier for each outcome record. The COMPONENT_TYPE_ID is a crucial foreign key column that links each outcome to its parent component type defined in the AMS_DLG_COMP_TYPES_B table. This relationship ensures that outcomes are scoped to relevant dialog components. Additional columns, typical for such definition tables, would likely include creation and last update dates, a system status flag, and potentially a numeric sequence for ordering outcomes. The descriptive, translatable name for each outcome is stored not in this base table, but in its corresponding translation table, AMS_DLG_COMP_TYPE_OUTCOME_TL.

Common Use Cases and Queries

This table is primarily accessed for configuration and runtime operations within marketing dialogs. Administrators would query it to review or set up the possible outcomes for components like a question or an action. During dialog execution, the application logic references this table to determine the valid next steps based on a captured outcome. A typical reporting query might join this table to the component types table to list all configured outcomes for analysis.

SELECT ct.COMPONENT_TYPE_CODE, b.OUTCOME_ID, tl.OUTCOME_NAME
FROM AMS_DLG_COMP_TYPE_OUTCOME_B b,
     AMS_DLG_COMP_TYPES_B ct,
     AMS_DLG_COMP_TYPE_OUTCOME_TL tl
WHERE b.COMPONENT_TYPE_ID = ct.COMPONENT_TYPE_ID
AND b.OUTCOME_ID = tl.OUTCOME_ID
AND tl.LANGUAGE = USERENV('LANG')
ORDER BY ct.COMPONENT_TYPE_CODE;

Related Objects

The table maintains defined foreign key relationships with two other key AMS entities, as documented in the metadata:

  • AMS_DLG_COMP_TYPES_B: This is the parent table. The relationship is established via the column AMS_DLG_COMP_TYPE_OUTCOME_B.COMPONENT_TYPE_ID, which references the primary key in AMS_DLG_COMP_TYPES_B. This links an outcome to its specific dialog component type.
  • AMS_DLG_COMP_TYPE_OUTCOME_TL: This is the child translation table. The relationship is from AMS_DLG_COMP_TYPE_OUTCOME_TL.OUTCOME_ID to the primary key (OUTCOME_ID) of this base table. The TL table holds the language-specific names for the outcomes defined here.

It is important to note the metadata indicates this table was "Not implemented in this database" for the specific ETRM instance, suggesting potential version or instance-specific customization. However, its defined structure and relationships confirm its logical role in the Dialog Engine data model.