Results for “dialog_id”

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

Overview

The AMS_DLG_FLOW_COMP_REL table is a core configuration object within the Oracle EBS Marketing (AMS) module. It stores the directed relationships between the individual components that make up a Dialog Flow — the branching logic, outcome routing, and component sequencing that govern how an interactive marketing dialog progresses from one step to the next. Each row captures the association between a currently active flow component and the component that should follow it, keyed by a specific outcome value. In this sense the table is the connective tissue of a dialog definition: without it, dialog components exist in isolation with no defined navigation path.

From a dimensional or Data Vault modeling perspective, the mined metadata suggests classifying AMS_DLG_FLOW_COMP_REL as a link table. This is a modeling recommendation rather than a documented Oracle classification: the table's role is to resolve relationships between two participating business entities (the current flow component and its successor, both sourced from AMS_DLG_FLOW_COMPS_B) anchored to a parent dialog in AMS_DIALOGS_ALL_B. It carries no independent descriptive payload of its own beyond the routing outcome, which further supports a link interpretation rather than a hub or satellite.

Key Information Stored

The table exposes twelve documented columns in ETRM 12.2.2. The most significant are:

• FLOW_COMP_RELATIONSHIP_ID — the surrogate primary key, enforced by AMS_DLG_FLOW_COMP_REL_PK and also backed by unique index AMS_DLG_FLOW_COMP_REL_U1, making it the single business-key candidate and the definitive row identifier.
• DIALOG_ID — foreign key to AMS_DIALOGS_ALL_B, anchoring the relationship to its owning dialog definition.
• CURR_FLOW_COMPONENT_ID — foreign key to AMS_DLG_FLOW_COMPS_B, identifying the "from" component in the relationship.
• NEXT_FLOW_COMPONENT_ID — identifies the "to" component that follows, completing the directed edge between two dialog steps.
• OUTCOME — the result condition that triggers the transition, distinguishing e.g. a positive response from a negative or non-response branch.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant / operating-unit data isolation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF framework to prevent concurrent update conflicts during dialog design.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-audit columns tracking insertion and modification.

Common Use Cases and Queries

Typical consumers of this table include dialog designer tooling, marketing campaign setup, and reporting on dialog branching logic. A common pattern is to reconstruct the traversal path of a given dialog:

SELECT r.DIALOG_ID, r.CURR_FLOW_COMPONENT_ID, r.OUTCOME, r.NEXT_FLOW_COMPONENT_ID
FROM AMS.AMS_DLG_FLOW_COMP_REL r
WHERE r.DIALOG_ID = :p_dialog_id
ORDER BY r.CURR_FLOW_COMPONENT_ID, r.OUTCOME;

To trace which components are terminal (have no successor), a left outer join of the flow component base table to this relationship table, filtered on a null NEXT_FLOW_COMPONENT_ID, is effective. Administrators also query by SECURITY_GROUP_ID when troubleshooting cross-operating-unit visibility, and version checks via OBJECT_VERSION_NUMBER surface during concurrent design edits.

Related Objects

• AMS_DLG_FLOW_COMPS_B — joined on CURR_FLOW_COMPONENT_ID (and referenced again via NEXT_FLOW_COMPONENT_ID) to retrieve component detail.
• AMS_DIALOGS_ALL_B — joined on DIALOG_ID for the parent dialog definition.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for access control context.
• AMS_DLG_FLOW_COMP_REL_PK / AMS_DLG_FLOW_COMP_REL_U1 — the primary key constraint and unique index enforcing uniqueness of FLOW_COMP_RELATIONSHIP_ID.
• AMS dialog-flow design and rendering APIs within the Marketing module, which consume these relationships to drive runtime branching behavior.