Results for “component_type_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The AMS_DLG_COMP_TYPES_B table is a foundational data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. It resides in the AMS schema and serves as the base table for storing Dialog Component Types, which define the discrete building blocks used to construct marketing dialogs and campaigns. A dialog component type describes a reusable category or definition of an interactive element — for example, a specific type of offer, question, or action — that can be wired into a dialog flow. By centralizing these definitions, the table provides the metadata backbone that allows marketing dialogs to be assembled consistently and reused across campaigns.

The table's primary key, AMS_DLG_COMP_TYPES_B_PK, is defined on COMPONENT_TYPE_ID. A unique index, AMS_DLG_COMP_TYPES_B_U1, also covers COMPONENT_TYPE_ID, meaning the surrogate identifier doubles as the documented business-key candidate in the available metadata. Following Data Vault modeling heuristics derived from the foreign-key structure, this object is classified as hub-leaning: it is a relatively stable, key-centric reference of component type definitions, with descriptive attributes carried on satellite-style translations and parameter tables that reference it.

Key Information Stored

The table is documented with ten columns. The most significant are:

  • COMPONENT_TYPE_ID — the surrogate primary key and unique business-key candidate; the identifier propagated to all dependent tables.
  • COMPONENT_TYPE_CODE — a functional, human-readable code that distinguishes one component type from another and is typically the value used in configuration and lookups.
  • CLASS_NAME — identifies the implementing class associated with the component type, linking the stored definition to its runtime behavior.
  • SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enforcing the multi-tenant security model used throughout the AMS schema.
  • OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates, standard in Oracle EBS 12.1.1 and 12.2.2.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit columns tracking who created and last modified each record and when.

The descriptive, translated text for each component type is held separately in AMS_DLG_COMP_TYPES_TL, while structural detail is held in the parameter and outcome child tables, leaving this base table as the compact identity and control record.

Common Use Cases and Queries

Because it is a definition table, AMS_DLG_COMP_TYPES_B is most often queried to enumerate, join, or validate available component types rather than to record transactions. Typical patterns include:

  • Listing all defined component types: SELECT COMPONENT_TYPE_ID, COMPONENT_TYPE_CODE, CLASS_NAME FROM AMS.AMS_DLG_COMP_TYPES_B;
  • Resolving translated names by joining to the TL table on COMPONENT_TYPE_ID and filtering by LANGUAGE.
  • Reporting on component usage by joining AMS_DLG_FLOW_COMPS_B back to this table to see which types appear in which dialog flows.
  • Configuration and migration scripts that map COMPONENT_TYPE_CODE to COMPONENT_TYPE_ID when loading dialog definitions.

Reporting use cases center on catalog inventories of dialog components, impact analysis before changing a component type, and auditing class-name assignments.

Related Objects

The following objects depend on or reference AMS_DLG_COMP_TYPES_B, joined via COMPONENT_TYPE_ID:

  • AMS_DLG_COMP_TYPES_TL — translated (language-specific) names and descriptions.
  • AMS_DLG_COMP_TYPE_OUTCOME_B — outcome definitions for each component type.
  • AMS_DLG_COMP_TYPE_PARAMS_B — parameter definitions belonging to each component type.
  • AMS_DLG_FLOW_COMPS_B — associates component types with dialog flows.
  • HXC_TIME_CATEGORY_COMPS — an additional referencing table that consumes COMPONENT_TYPE_ID.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.

Together these relationships confirm the table's role as a hub-like definition source within the AMS dialog framework.