Search Results ams_dlg_branches_b_pk

Overview

The AMS_DLG_BRANCHES_B table is a core data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. It serves as the base table for storing the structural definitions of branches within a dialog flow. A dialog flow is a marketing automation construct used to design and execute multi-step, interactive customer communication campaigns. Branches represent the conditional logic paths that determine the next step in the flow based on specific criteria or customer responses. This table is fundamental for implementing complex, rule-based marketing journeys in Oracle EBS versions 12.1.1 and 12.2.2.

Key Information Stored

Based on the provided ETRM metadata, the table's primary purpose is to uniquely identify and link dialog branches to their parent flow components. The key documented columns are:

• BRANCH_ID: The primary key column (AMS_DLG_BRANCHES_B_PK) that uniquely identifies each branch record within the system.
• FLOW_COMPONENT_ID: A foreign key column that links the branch to its parent dialog flow component in the AMS_DLG_FLOW_COMPS_B table. This establishes the branch as a child object within a specific step of a larger dialog flow.

While the explicit metadata is limited, typical columns in such a structure would logically include attributes for the branch's execution order (SEQUENCE_NUMBER), the condition or rule that triggers the branch (e.g., CONDITION_TYPE, CONDITION_VALUE), and a reference to the target flow component to execute if the condition is met (e.g., NEXT_COMPONENT_ID). Status and audit columns like CREATION_DATE and LAST_UPDATE_DATE are also standard.

Common Use Cases and Queries

This table is primarily accessed for configuring, auditing, and troubleshooting marketing dialog flows. Common operational scenarios include querying all branches within a specific flow to understand its decision logic or identifying branches that reference a particular component. A typical analytical query would join this table with the flow components and dialog definition tables to generate a comprehensive flow map.

Sample Query Pattern:
SELECT dlg.NAME AS DIALOG_NAME, comp.COMPONENT_NAME, br.BRANCH_ID, br.SEQUENCE_NUMBER
FROM AMS_DLG_BRANCHES_B br,
AMS_DLG_FLOW_COMPS_B comp,
AMS_DIALOGS_VL dlg
WHERE br.FLOW_COMPONENT_ID = comp.FLOW_COMPONENT_ID
AND comp.DIALOG_ID = dlg.DIALOG_ID
ORDER BY dlg.NAME, comp.SEQUENCE_NUMBER, br.SEQUENCE_NUMBER;

This query would be used for impact analysis before modifying a flow component or for debugging a campaign that is not progressing through the dialog as expected.

Related Objects

The AMS_DLG_BRANCHES_B table exists within a tightly integrated schema for dialog management. The primary documented relationship is its foreign key dependency on AMS_DLG_FLOW_COMPS_B, which stores the master list of components (like emails, waits, or tasks) in a dialog. Branches define the connections between these components. It is also intrinsically related to the AMS_DIALOGS_B and AMS_DIALOGS_VL tables, which store the header definition and translated descriptions of the dialog itself. For accessing branch data, one would typically query through public APIs or views provided by the Oracle Marketing module rather than directly referencing the base table.