Results for “ams_dlg_flow_comps_b”

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

Overview

AMS_DLG_FLOW_COMPS_B is a core configuration table within the Oracle Marketing (AMS) module of Oracle E-Business Suite, holding the defined properties of individual dialog flow components. A dialog flow represents the orchestrated sequence of steps—such as email deliveries, offers, decision branches, and lead creation actions—that a marketing campaign executes against a target audience. Each record in this table captures one component instance that participates in a flow, binding it to its parent dialog, its component type definition, and any identification rules, templates, or interest classifications that govern its runtime behavior.

Because the table carries the _B suffix, it stores the base (language-independent) definition of a flow component, with translatable descriptive content handled separately. The table is owned by the AMS schema and is available in both 12.1.1 and 12.2.2 releases. From a Data Vault modeling perspective, this object exhibits hub-leaning characteristics: it holds a single surrogate primary key with foreign references outward to multiple independent reference tables, making it a natural candidate for a hub entity in a dimensional or Data Vault style model.

Key Information Stored

The table contains 54 documented columns. The most significant are summarized below.

• FLOW_COMPONENT_ID — Surrogate primary key, enforced by AMS_DLG_FLOW_COMPS_B_PK and uniquely indexed by AMS_DLG_FLOW_COMPS_B_U1. This is the primary business-key candidate and the column referenced by downstream child tables.
• DIALOG_ID — Foreign key to AMS_DIALOGS_ALL_B, identifying the parent dialog flow to which the component belongs.
• COMPONENT_TYPE_ID — Foreign key to AMS_DLG_COMP_TYPES_B, classifying the component (for example, branch, delivery, or rule step).
• COMPONENT_TYPE_CODE — Denormalized code that identifies the component type without requiring a lookup join.
• IDENTIFY_RULE_ID — Foreign key to AMS_DLG_IDENTIFY_RULES_B, associating an audience identification rule with the component.
• DELIVERABLE_ID, IPAGE_ID, DISPLAY_TEMPLATE_ID — References to the content assets, interactive pages, and display templates used when the component executes.
• SKIP_FLAG — Controls whether the component is bypassed during flow execution.
• CREATE_NEW_USER_FLAG, CREATE_LEAD_NOW_FLAG — Flags governing lead and user creation behavior at runtime.
• INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID, COUNTRY_ID — Interest classification and geographic targeting attributes.
• COMPONENT_ATTRIBUTE_CATEGORY and COMPONENT_ATTRIBUTE1–15 — A descriptive flexfield region reserved for component-specific extensions.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard EBS DFF region for additional configurable properties.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on reporting, migration, and troubleshooting of campaign dialog flows. A common query reconstructs all components belonging to a dialog with their type descriptions:

• List all components for a given dialog: SELECT flow_component_id, component_type_code, skip_flag FROM ams.ams_dlg_flow_comps_b WHERE dialog_id = :p_dialog_id;
• Join to the type definition to obtain descriptive names: SELECT c.flow_component_id, t.component_type_name FROM ams.ams_dlg_flow_comps_b c, ams.ams_dlg_comp_types_b t WHERE c.component_type_id = t.component_type_id;
• Identify components with a specific identification rule or deliverable, useful when auditing audience segmentation.
• Extract DFF values by querying the COMPONENT_ATTRIBUTE_CATEGORY and COMPONENT_ATTRIBUTE1–15 columns for customer-specific extension data.
• Reconcile migrated flows by validating that each FLOW_COMPONENT_ID has matching entries in the relationship and branch tables.

Because the table is a hub, reporting joins typically fan out to the reference dimensions (dialog, component type, interest type) rather than reading it in isolation.

Related Objects

Several objects depend on or are referenced by AMS_DLG_FLOW_COMPS_B through the documented foreign keys:

• AMS_DLG_COMP_TYPES_B — Referenced via COMPONENT_TYPE_ID; defines the component type master data.
• AMS_DLG_IDENTIFY_RULES_B — Referenced via IDENTIFY_RULE_ID; supplies audience identification rules.
• AMS_DIALOGS_ALL_B — Referenced via DIALOG_ID; the parent dialog flow.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; enforces security group isolation.
• AS_INTEREST_TYPES_B — Referenced via INTEREST_TYPE_ID; defines interest classifications.
• AMS_DLG_BRANCHES_B — Child table referencing FLOW_COMPONENT_ID; stores branch definitions.
• AMS_DLG_FLOW_COMP_REL — Child table referencing CURR_FLOW_COMPONENT_ID; defines component sequencing relationships.
• AMS_DLG_RUN_STEP_DETAILS — Child table referencing FLOW_COMPONENT_ID; records runtime execution details.
• AMS_DLG_CONTEXT_FIELDS — Child table referencing FLOW_COMPONENT_ID; binds context fields to components.

Together these relationships position AMS_DLG_FLOW_COMPS_B as the central hub of the dialog flow configuration model, linking component definitions, execution metadata, and branch logic within the Oracle Marketing application.