SAP MDG · WORKFLOWS
How do I configure SAP MDG rule-based workflow decision tables for 0, 1, 2, or 3 approval levels?
Use workflow template WS60800086 and maintain the three BRFplus decision tables per change request type: DT_SINGLE_VAL for step transitions, DT_USER_AGT_GRP for dialog approvers, and DT_NON_USER_AGT_GRP for automatic steps. The supplied template covers 0, 1, 2, and 3 approval levels with standard aliases such as SUB, AP2, AP3, ACT, SYS, RBK, and COM.
Use workflow template WS60800086 and maintain the three BRFplus decision tables per change request type: DT_SINGLE_VAL for step transitions, DT_USER_AGT_GRP for dialog approvers, and DT_NON_USER_AGT_GRP for automatic steps. The supplied template covers 0, 1, 2, and 3 approval levels with standard aliases such as SUB, AP2, AP3, ACT, SYS, RBK, and COM.
SAP MDG rule-based workflow uses the generic template WS60800086 together with three BRFplus decision tables per change request type. The supplied generic templates show the standard patterns for 0, 1, 2, and 3 approval levels, including the step aliases, status flow, dialog-agent rows, and automatic system steps. Use DT_SINGLE_VAL_<CR> as the transition engine, DT_USER_AGT_GRP_<CR> for approvers, and DT_NON_USER_AGT_GRP_<CR> for activation, rollback, complete, and mail services.
Process flow
- Use WS60800086 as the generic rule-based workflow template.
- Choose the approval-depth pattern: 0, 1, 2, or 3 levels.
- Maintain DT_SINGLE_VAL_<CR> for step transitions and condition aliases.
- Maintain DT_USER_AGT_GRP_<CR> for dialog approvers, or leave it empty for 0 approval.
- Maintain DT_NON_USER_AGT_GRP_<CR> for automatic steps such as activation, mail, rollback, and completion.
- Map the standard aliases: SUB, AP2, AP3, ACT, AC2, SYS, COM, RBK, REJ, ERR.
- Ensure the activation branch uses step 91 with action 31 for success and <>31 for failure.
- Ensure completion uses alias COM to step 99 with process pattern 99 or 06 as shown in the template.
Referenced tables
| Object | Purpose |
|---|---|
DT_SINGLE_VAL_<CR> | Determines previous-step/action to next step, new CR status, condition alias, and optional dynamic agent selection service. |
DT_USER_AGT_GRP_<CR> | Maps the condition alias to dialog approver group, step type, agent type, and agent value. |
DT_NON_USER_AGT_GRP_<CR> | Maps the condition alias to automatic agent group, process pattern, and optional system service name. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What are the generic decision-table templates for MDG approval depths?
- How do I build DT_SINGLE_VAL, DT_USER_AGT_GRP, and DT_NON_USER_AGT_GRP for a 1-step or 3-step MDG workflow?
- How do I adapt the standard MDG rule-based workflow template for different approval levels?
Possible questions
- Which decision table decides the next workflow step in MDG RBWF?
- What aliases are used for approve, reject, activate, rollback, and complete in MDG RBWF?
- How do I model a straight-through MDG workflow with no dialog approver?
- How should I wire dynamic agent selection in DT_SINGLE_VAL?
- What rows are needed in DT_USER_AGT_GRP for approval levels 1 to 3?