SAP Master Data Governance · Workflow: Standard & Rule-Based

The static user-agent decision table can't express your routing — agents must be computed from change-request data at runtime. What mechanism handles this?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Workflow: Standard & Rule-Based

Your process deviates only slightly from an SAP-delivered task-based workflow template. Should you switch to the rule-based template WS60800086?

After you assign a processor to a change request step, the workflow immediately ends in an error instead of reaching that processor. What is the most likely cause?

In the user-agent decision table, what do the special User Agent Values INIT and LAST resolve to at runtime?

MDG Financials ships three workflow templates. Which one do you pick if approval must happen per individual object and be controllable by entity type?

If the rule-based template WS60800086 is generic and not tied to any domain or change request type, what makes one rule-based process differ from another?

For the standard supplier and customer templates, are the processing agents determined in the rule-based DT_USER_AGT_GRP decision tables?

Start learning today

Free to start — download the app or use it in your browser.