SAP MDG · WORKFLOWS
How do I configure MDG Rule-Based Workflow decision tables and extend BRFplus agent determination with additional MDG data model fields?
MDG rule-based workflow uses three BRFplus decision tables per change request type: DT_SINGLE_VAL for the next step and status, DT_USER_AGT_GRP for dialog agents, and DT_NON_USER_AGT_GRP for automatic steps. To use additional MDG master-data fields in agent determination, enhance the rule context with BAdI USMD_SSW_RULE_CONTEXT_PREPARE and then reference the added fields in the BRFplus decision table.
MDG rule-based workflow uses three BRFplus decision tables per change request type: DT_SINGLE_VAL for the next step and status, DT_USER_AGT_GRP for dialog agents, and DT_NON_USER_AGT_GRP for automatic steps. To use additional MDG master-data fields in agent determination, enhance the rule context with BAdI USMD_SSW_RULE_CONTEXT_PREPARE and then reference the added fields in the BRFplus decision table.
MDG change requests on workflow template WS60800086 are driven by three BRFplus decision tables per CR type. DT_SINGLE_VAL_<CR> is the transition table: it uses the current step and previous action to return the next step, new CR status, and a Condition Alias that joins the flow to either DT_USER_AGT_GRP_<CR> or DT_NON_USER_AGT_GRP_<CR>. If you also need processor determination based on additional MDG data-model fields such as LABOR, extend the rule context with USMD_SSW_RULE_CONTEXT_PREPARE and then use the new field in the BRFplus table.
Process flow
- Maintain DT_SINGLE_VAL_<CR> for step transition and Condition Alias output.
- Maintain DT_USER_AGT_GRP_<CR> for dialog agent determination.
- Maintain DT_NON_USER_AGT_GRP_<CR> for automatic/background steps.
- Implement
USMD_SSW_RULE_CONTEXT_PREPAREwhen BRFplus must use extra MDG data-model fields. - Expose the extra field in the rule context and reference it in the BRFplus decision table.
- Test the CR flow end to end and verify step, status, alias, and processor assignment.
Rule-Based Workflow / decision tables for WS60800086
Maintain DT_SINGLE_VAL_<CR>, DT_USER_AGT_GRP_<CR>, and DT_NON_USER_AGT_GRP_<CR> for the change request type.
Referenced tables
| Object | Purpose |
|---|---|
DT_SINGLE_VAL_<CR> | Determines the next workflow step, new CR status, and Condition Alias from the current step and previous action. |
DT_USER_AGT_GRP_<CR> | Determines dialog-step agents from the Condition Alias. |
DT_NON_USER_AGT_GRP_<CR> | Determines automatic-step agent group, process pattern, and optional service name from the Condition Alias. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How does the three-table MDG rule-based workflow model work?
- Which decision table determines the next MDG workflow step?
- How do I add additional MDG fields to BRFplus agent determination?
Possible questions
- What does DT_SINGLE_VAL do in MDG RBWF?
- How are agents determined in DT_USER_AGT_GRP?
- What is DT_NON_USER_AGT_GRP used for?
- How do I enhance BRFplus decision tables with MM fields like LABOR?
- Which BAdI is used to prepare extra workflow context fields?
- What is the condition alias in MDG rule-based workflow?