SAP MDG · WORKFLOWS
How do the three MDG rule-based workflow decision tables work, and how do I author or extend them for a change request type?
SAP MDG rule-based workflow uses three BRF+ decision tables as one loop: DT_SINGLE_VAL decides the next step and status, DT_USER_AGT_GRP assigns dialog processors, and DT_NON_USER_AGT_GRP runs automatic/background processing. The tables are linked by Condition Alias, and custom steps are added by emitting a new alias in DT_SINGLE_VAL and then maintaining that alias in the correct agent table and BAdI service registration.
SAP MDG rule-based workflow uses three BRF+ decision tables as one loop: DT_SINGLE_VAL decides the next step and status, DT_USER_AGT_GRP assigns dialog processors, and DT_NON_USER_AGT_GRP runs automatic/background processing. The tables are linked by Condition Alias, and custom steps are added by emitting a new alias in DT_SINGLE_VAL and then maintaining that alias in the correct agent table and BAdI service registration.
SAP MDG rule-based workflow in template WS60800086 works like a state machine: DT_SINGLE_VAL decides where a change request goes next, then the emitted Condition Alias routes processing to either DT_USER_AGT_GRP for dialog work or DT_NON_USER_AGT_GRP for background work. To extend the flow, you add the new transition row first, then maintain the matching alias in the relevant agent table and register any required custom service in the corresponding BAdI.
Process flow
- Identify the current CR step and previous action.
- Create or adjust the matching DT_SINGLE_VAL row.
- Assign a unique Condition Alias for the new transition.
- Maintain the alias in DT_USER_AGT_GRP for dialog processing or DT_NON_USER_AGT_GRP for automatic processing.
- If runtime agent selection is needed, maintain DYNAMIC_AGT_SEL_SERVICE.
- If an automatic service is needed, maintain Service Name for Process Pattern 02 and implement the corresponding BAdI logic.
- Test the flow with the expected action buttons and check the returned next step and status.
Workflow rule sets for template WS60800086; maintain decision tables DT_SINGLE_VAL, DT_USER_AGT_GRP, DT_NON_USER_AGT_GRP
Define step transitions, dialog agent assignment, and automatic/background processing for MDG change requests
BAdI implementation for GET_DYNAMIC_AGENTS
Resolve dynamic dialog agents from DT_SINGLE_VAL services
BAdI implementation for CALL_SYSTEM_METHOD
Execute custom automatic services referenced from DT_NON_USER_AGT_GRP with Process Pattern 02
Referenced tables
| Object | Purpose |
|---|---|
DT_SINGLE_VAL_<CR> | Transition table that maps current step plus action to next step, CR status, condition alias, and optional runtime service |
DT_USER_AGT_GRP_<CR> | Dialog agent assignment table keyed by Condition Alias |
DT_NON_USER_AGT_GRP_<CR> | Automatic/background processing table keyed by Condition Alias |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How does DT_SINGLE_VAL relate to DT_USER_AGT_GRP and DT_NON_USER_AGT_GRP?
- How do I add a new workflow step in SAP MDG rule-based workflow?
- How do I assign agents and automatic services in MDG BRF+ workflow decision tables?
Possible questions
- How do the three MDG workflow decision tables interact?
- What is the role of Condition Alias in MDG rule-based workflow?
- How do I add a dialog step or background step in MDG workflow?
- Which BAdIs are used by MDG workflow decision tables?
- What are the common step patterns in MDG rule-based workflow?