Search Results ams_dlg_run_step_details




Overview
Explore in AI Chat

Overview

The AMS_DLG_RUN_STEP_DETAILS table is a core data object within the Oracle E-Business Suite Marketing (AMS) module, specifically for releases 12.1.1 and 12.2.2. It functions as an execution log or audit trail for dialog flows. A dialog flow represents a multi-step, automated marketing or customer interaction process. This table captures the runtime details of each individual step's execution within a specific run of a dialog flow. Its primary role is to provide a granular, historical record of how a marketing campaign's automated conversation logic was processed, enabling performance analysis, debugging, and auditing of customer interaction outcomes.

Key Information Stored

The table stores transactional records for each step execution. The primary identifier is the RUN_STEP_ID. A critical foreign key column is FLOW_COMPONENT_ID, which links the runtime step back to its definition in the AMS_DLG_FLOW_COMPS_B table. While the full column list is not exhaustively detailed in the provided metadata, a table of this nature typically includes columns to record the status of the step execution (e.g., SUCCESS, ERROR, PENDING), timestamps for start and completion, input and output data references or messages, the execution sequence order, and a foreign key to the parent dialog run identifier (likely RUN_ID, linking to a table such as AMS_DLG_RUNS). This structure allows for reconstructing the complete execution path of a dialog.

Common Use Cases and Queries

This table is essential for operational reporting and troubleshooting. Common use cases include analyzing the performance and success rate of specific dialog steps, identifying bottlenecks in marketing automation flows, and auditing the customer journey for compliance. A support analyst might query it to diagnose failures in a specific dialog run. A sample query pattern would join to the flow component definition table to get step names:

  • SELECT d.run_step_id, c.component_name, d.status, d.start_date, d.end_date
  • FROM ams_dlg_run_step_details d, ams_dlg_flow_comps_b c
  • WHERE d.flow_component_id = c.flow_component_id
  • AND d.run_id = :p_run_id
  • ORDER BY d.sequence_number;

Another common report aggregates step execution statistics across multiple dialog runs to identify chronically failing or slow components.

Related Objects

The table has documented relationships with other key AMS dialog objects, primarily through foreign key constraints. The provided metadata specifies one critical relationship:

  • AMS_DLG_FLOW_COMPS_B: This is the definition table for dialog flow components (steps). The foreign key AMS_DLG_RUN_STEP_DETAILS.FLOW_COMPONENT_ID references this table, linking each runtime execution record to its static definition. This join is fundamental for any report that requires the step's name or configuration details.

While not listed in the provided excerpt, this table is almost certainly a child of a parent run header table, such as AMS_DLG_RUNS, via a foreign key like RUN_ID. It may also have relationships with tables storing customer or list data (e.g., AMS_DLG_RUN_RECIPIENTS) to provide full context for the interaction.