SAP MDG · WORKFLOWS
How do the three BRF+ decision tables control the MDG rule-based workflow for a change request?
MDG rule-based workflow uses three BRF+ decision tables per CR type: DT_SINGLE_VAL sets the next step, CR status, and Condition Alias; DT_USER_AGT_GRP assigns dialog processors; DT_NON_USER_AGT_GRP drives automatic steps and services. The workflow loops through these tables on each action, and the service columns can call the MDG dynamic-agent or system-method BAdIs.
MDG rule-based workflow uses three BRF+ decision tables per CR type: DT_SINGLE_VAL sets the next step, CR status, and Condition Alias; DT_USER_AGT_GRP assigns dialog processors; DT_NON_USER_AGT_GRP drives automatic steps and services. The workflow loops through these tables on each action, and the service columns can call the MDG dynamic-agent or system-method BAdIs.
MDG change requests on workflow template WS60800086 are controlled by three BRF+ decision tables per CR type. DT_SINGLE_VAL is the transition table: it reads the current step plus the action just performed and returns the next step, the new CR status, and a Condition Alias. That alias then routes the request into either DT_USER_AGT_GRP for dialog processing or DT_NON_USER_AGT_GRP for automatic/background processing. The service columns can also dispatch into the MDG workflow BAdIs for dynamic agent selection or system methods...
Process flow
- Identify the current CR step and the action just performed.
- Read DT_SINGLE_VAL for that CR type using the current step plus action.
- Capture Condition Alias, New Step, New CR Status, and any Dyn Agt Sel Service.
- If the new step is dialog, resolve the alias in DT_USER_AGT_GRP.
- If the new step is automatic, resolve the alias in DT_NON_USER_AGT_GRP.
- If a service is maintained, ensure the matching
USMD_SSW_* BAdI implementation handles it. - Use the step type and action mapping to confirm which buttons and outcomes are expected next.
Referenced tables
| Object | Purpose |
|---|---|
DT_SINGLE_VAL_<CR> | Step engine table; returns Condition Alias, New Step, New CR Status, and optional Dyn Agt Sel Service. |
DT_USER_AGT_GRP_<CR> | Dialog-agent table; maps Condition Alias to step type and user/role assignment. |
DT_NON_USER_AGT_GRP_<CR> | Automatic-step table; maps Condition Alias to agent group, process pattern, and optional service name. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How does DT_SINGLE_VAL connect to DT_USER_AGT_GRP and DT_NON_USER_AGT_GRP in MDG workflow?
- How are dynamic agents and system methods triggered from MDG decision tables?
- How do I author or extend MDG workflow decision tables for a new change-request step?
Possible questions
- How do the three BRF+ decision tables control the MDG rule-based workflow for a change request?
- How does Condition Alias route a change request between dialog and automatic steps?
- Which table sets New Step, New CR Status, and Dyn Agt Sel Service in MDG workflow?
- How do DT_SINGLE_VAL, DT_USER_AGT_GRP, and DT_NON_USER_AGT_GRP work together?
- How do I add a new workflow step in MDG rule-based workflow?