SAP MDG · WORKFLOWS
How do I configure SAP Business Workflow as a local workflow engine in SAP MDG Cloud-Ready Mode?
From MDG on SAP S/4HANA 2023 FPS02, you can trigger a local SAP Business Workflow from an MDG process step instead of a BTP workflow definition. The guide’s pattern is: maintain BOR event linkage in SWE2, build two standard tasks in PFTC for process and record URLs using CL_MDC_WF_PROCESS_URL, create the workflow in SWDD with BUS2240.START_STEP_WF, add Send Mail, then assign the activated workflow in Process Template Steps → Local Workflow and add a checkpoint.
From MDG on SAP S/4HANA 2023 FPS02, you can trigger a local SAP Business Workflow from an MDG process step instead of a BTP workflow definition. The guide’s pattern is: maintain BOR event linkage in SWE2, build two standard tasks in PFTC for process and record URLs using CL_MDC_WF_PROCESS_URL, create the workflow in SWDD with BUS2240.START_STEP_WF, add Send Mail, then assign the activated workflow in Process Template Steps → Local Workflow and add a checkpoint.
From MDG on SAP S/4HANA 2023 FPS02, SAP Business Workflow can be used as a local workflow engine for selected MDG process steps. The guide shows an approval scenario where the workflow retrieves process and record URLs, sends them by email, and is assigned back to the MDG process step through the Local Workflow customizing.
Process flow
- Work in the customizing client and maintain BOR event linkage in SWE2.
- Create a standard task in PFTC for Get Process URL using CL_MDC_WF_PROCESS_URL=>GET_PROCESS_URL.
- Create a second standard task in PFTC for Get Records URL using CL_MDC_WF_PROCESS_URL=>GET_RECORDS_URL.
- Create the workflow pattern in SWDD and add the workflow activity steps.
- Add triggering event BUS2240.START_STEP_WF in the workflow.
- Create workflow containers MDC_PROCESS, PROCESS_URL, and RECORDS_URL.
- Configure event and activity bindings so MDC_PROCESS feeds the task input and the URL results return to the workflow.
- Add the Send Mail step and bind MDC_PROCESS, PROCESS_URL, and RECORDS_URL on the Control tab, then maintain the recipient and mail text as needed. Save and activate the workflow, then assign it in Configure Process Templates for Cloud-Ready
SWE2Customizing client → BOR event type linkage
Maintain the event linkage for BUS2240.START_STEP_WF so the MDG process step can start the local workflow.
Development client → Standard task creation
Create the Get Process URL standard task using ABAP class CL_MDC_WF_PROCESS_URL and method GET_PROCESS_URL.
Development client → Standard task creation
Create the Get Records URL standard task using ABAP class CL_MDC_WF_PROCESS_URL and method GET_RECORDS_URL.
Workflow Builder → Create workflow pattern
Model the SAP Business Workflow, add the two URL retrieval activities, the triggering event, and the Send Mail step.
SE80Workflow repository maintenance
Open the workflow object, maintain the triggering event, container, and bindings in the workflow repository.
Referenced tables
| Object | Purpose |
|---|---|
Workflow Structure | Shows the execution flow from MDG process step to BUS2240.START_STEP_WF, then SAP Business Workflow, URL retrieval, and Send Mail. |
Critical Technical Objects | Summarizes the exact transactions, BOR object, methods, and container names used in the guide. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is local workflow in SAP MDG Cloud-Ready Mode?
- Can SAP Business Workflow be used instead of BTP Workflow?
- From which release is local SAP Business Workflow supported?
Possible questions
- How do I configure the event linkage for local MDG workflow?
- How do I create the Get Process URL task?
- How do I assign the local workflow to an MDG process step?
- Which class returns the MDG Process URL?
- How do I configure the Send Mail step bindings?