Results for “ams_dlg_comp_type_params_b”

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

Overview

AMS_DLG_COMP_TYPE_PARAMS_B is a Marketing (AMS) module table that stores the parameter definitions associated with a given Dialog Component type. In the Oracle E-Business Suite Marketing application, Dialog Components are the reusable building blocks used to assemble interactive dialogs presented to customers or prospects. Each component type may expose one or more configurable parameters, and this table serves as the master (base-language) repository of those parameter records. It is the parent of a corresponding translation table, AMS_DLG_COMP_TYPE_PARAMS_TL, which holds the language-specific (translatable) attribute values.

The object is documented as not implemented in the standard database, meaning it is an ETRM-modeled / product-data-model artifact that may not be physically created in every 12.1.1 or 12.2.2 installation. Where it does exist, it anchors the parameter metadata used by the Dialog Component framework.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning. The metadata mined from the foreign-key structure shows that AMS_DLG_COMP_TYPE_PARAMS_B references AMS_DLG_COMP_TYPES_B through COMPONENT_TYPE_ID, and is in turn referenced by AMS_DLG_COMP_TYPE_PARAMS_TL through PARAMETER_ID. This positions the table as a descriptive record hanging off a component-type parent, consistent with a satellite pattern rather than a standalone hub or a pure link.

Key Information Stored

The most significant columns documented for this table are:

• PARAMETER_ID — the primary key column, defined by constraint AMS_DLG_COMP_TYPE_PARAMS_PK1. It is the surrogate identifier for each parameter record and is the column referenced by the translation table's foreign key.
• COMPONENT_TYPE_ID — the foreign key to AMS_DLG_COMP_TYPES_B, establishing which component type owns the parameter. This is the principal business-key candidate for joining parameter records back to their parent component type.

The base table holds the non-translatable attributes of each parameter, while descriptive text such as parameter names and prompts resides in the companion TL table. Consumers should treat PARAMETER_ID as the surrogate key and COMPONENT_TYPE_ID as the primary business relationship column.

Common Use Cases and Queries

Typical usage involves resolving parameters for a specific component type, or retrieving translated parameter text for a given language. A representative join pattern is:

• Selecting parameters by component type:

  SELECT p.parameter_id, p.component_type_id, t.parameter_name
  FROM ams_dlg_comp_type_params_b p,
  ams_dlg_comp_type_params_tl t
  WHERE p.parameter_id = t.parameter_id
  AND p.component_type_id = :component_type_id;

• Resolving the owning component type:

  SELECT c.* FROM ams_dlg_comp_types_b c, ams_dlg_comp_type_params_b p
  WHERE c.component_type_id = p.component_type_id;

Reporting scenarios include auditing parameter coverage across component types, validating that every parameter has a translation row, and reviewing configuration metadata during dialog design or upgrade assessment.

Related Objects

• AMS_DLG_COMP_TYPE_PARAMS_TL — the translation child table, joined on PARAMETER_ID.
• AMS_DLG_COMP_TYPES_B — the parent component-type base table, joined on COMPONENT_TYPE_ID.
• The Dialog Component framework views and APIs that read parameter metadata at runtime.

Together with its translation counterpart and component-type parent, AMS_DLG_COMP_TYPE_PARAMS_B defines the parameterization surface of Marketing Dialog Components.