Results for “execution_status”

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

Overview

AMS_DLG_RUN_STEP_DETAILS is a transactional table within the Oracle EBS Marketing (AMS) module that records the execution of individual steps belonging to a dialog flow. A dialog flow is a multi-stage marketing interaction — for example, a lead-nurturing or campaign follow-up sequence — composed of discrete components such as scripts, offers, or branch conditions. When a dialog runs for a given contact, each step in that flow is materialized in this table, allowing the application to track which steps executed, in what sequence, when they started and ended, and whether they succeeded or failed.

The table resides in the AMS schema and is present in both Oracle EBS 12.1.1 and 12.2.2, with 16 documented columns in the 12.2.2 physical schema. Its foreign keys to AMS_DLG_FLOW_COMPS_B (the flow component definition) and FND_SECURITY_GROUPS (the multi-org / data security construct) confirm its role as runtime execution detail rather than configuration. Based on the foreign-key structure — a single primary key surrogate with references out to parent entities — the heuristic Data Vault classification is satellite-leaning, suggesting the table would model as a satellite attached to a dialog-run hub or link keyed by RUN_ID and FLOW_COMPONENT_ID.

Key Information Stored

• RUN_STEP_ID — the surrogate primary key (AMS_DLG_RUN_STEP_DETAILS_PK) uniquely identifying each executed step instance. This is the column most often searched for (for example, "run_step_id").
• RUN_ID — the dialog run instance to which this step belongs; the effective business grouping of steps executed together.
• FLOW_COMPONENT_ID — foreign key to AMS_DLG_FLOW_COMPS_B, identifying which configured step definition was executed.
• EXECUTION_STATUS — the outcome state of the step (for example, in progress, completed, or errored).
• START_DATE / END_DATE / DUE_DATE — scheduling and elapsed-time context for the step execution.
• ERROR_CODE / ERROR_STACK — diagnostic information captured when a step fails.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing data-level access control.
• OBJECT_VERSION_NUMBER — optimistic locking column added by the EBS framework.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, used for audit and concurrency.

No unique business key is documented beyond the surrogate PK; meaningful identity derives from the combination of RUN_ID and FLOW_COMPONENT_ID.

Common Use Cases and Queries

Typical usage centers on diagnosing failed dialog executions and measuring throughput. A common pattern retrieves all steps of a run in chronological order:

• SELECT RUN_STEP_ID, FLOW_COMPONENT_ID, EXECUTION_STATUS, START_DATE, END_DATE FROM AMS.AMS_DLG_RUN_STEP_DETAILS WHERE RUN_ID = :run_id ORDER BY START_DATE;
• Filtering failures: SELECT RUN_STEP_ID, ERROR_CODE, ERROR_STACK FROM AMS.AMS_DLG_RUN_STEP_DETAILS WHERE EXECUTION_STATUS = 'ERROR' AND CREATION_DATE > SYSDATE - 7;
• Joining to AMS_DLG_FLOW_COMPS_B on FLOW_COMPONENT_ID to translate step identifiers into component names for reporting;
• Aggregating average step duration by combining START_DATE and END_DATE;
• Scoping by SECURITY_GROUP_ID for multi-org or security-restricted reporting.

Related Objects

• AMS_DLG_FLOW_COMPS_B — joined on FLOW_COMPONENT_ID; holds the step definition.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for access control.
• AMS_DLG_RUN_STEP_DETAILS_PK — the primary key constraint/index.
• Dialog run / flow parent tables in the AMS schema referenced by RUN_ID.
• AMS dialog flow APIs and concurrent programs that insert and update execution records.