BlogBlogtypeA post on somebody's own site or a community platform. Nobody edits it after publication, so it dates from the day it was written.See every one →SAP Community

SAP MDG Cloud Ready Mode: 5 Solution Patterns, Zero BADIs: How We implemented 5 typical requirements

A field report from an 80%-complete SAP MDG-BP Cloud Ready Mode implementation, showing five requirements it met without BAdIs or modification: business-partner context and the MDG UI shown inside the My Inbox app, rule-based multi-step approval routing with exclusive-choice nodes, agent determination through BTP role collections, and role-specific Fiori App Variants that give Finance Experts only bank-detail fields while Approvers get full write access. Each pattern works the same way underneath — a BTP Workflow service task reads business-partner attributes over OData into the workflow context, and a user task, route or app variant reacts to it — built with key-user extensibility or SAP Business Application Studio rather than custom ABAP.

Where it sits

Explains
Task and approval UIsBTPTask and approval UIscapabilityThe screen a person approves something on — a workflow or process task rendered as a form, embedded in an inbox that supplies its context. Distinct from workflow integration, which is about driving the engine: this is the half a human touches, and its hard part is that it cannot run without the engine that normally feeds it.Process automationBTPProcess automationcapabilityModelling and running a business process: the process flow, the forms people fill in, decision tables, bots for repetitive steps, and dashboards over the instances that run. Starting a process from an application and reacting to it is [workflow integration](capability:workflow-integration), and the screen a person approves a task on is [task and approval UIs](capability:task-uis).
Source
reachable

Who is behind it

steffen_ulmerauthor

Properties

About this work

declared and crawled
Published
declared
Published on
declared
Views
crawled
3,969

For task-uis

on the edge
Applies in
authored
btp

More on this11

Group by11 of 11 pieces
Piece, what it offersStill applies
Also explainingTask and approval UIs11
How Have SAP Customers Adopted n8n
YouTube — SAP Developers playlists, SAP
nothing recorded
How to Transform Business Rules into Conversational Experiences Using SAP BPA and SAP Joule Studio
SAP Community, Anushree01
nothing recorded
SAP Build Process Automationで「グループ宛て承認ワークフロー」を構築する
SAP Community, takayuki_tanaka
nothing recorded
Guide to Process Automation APIs - Part I - Getting Started
SAP Community, Dan_Wroblewski
nothing recorded
Integrate and Extend with SAP Build Process Automation
SAP Architecture Center, SAP Architecture CenterThe reasoningA reference
nothing recorded
Establish a central inbox with SAP Task Center
SAP Architecture Center, SAP Architecture CenterThe reasoningA reference
nothing recorded
How to Approve/Reject Task via API in SAP Build Process Automation
SAP Community, Dan_Wroblewski
nothing recorded
Configure Journal Entry Posting Approval from Store Template in Build Process Automation
SAP Community, SaranyaSampath
nothing recorded
Testing SAP Build Process Automation task UI in SAP Business Application Studio
SAP Community, Mio YasutakeThe reasoningRunnable code
nothing recorded
Generate agentic workflows using SAP-managed n8n in Joule Studio
SAP TechEd — session catalogueA recipe
nothing recorded
Navigating the road map for SAP Cloud ERP: Today, next, and beyond
SAP TechEd — session catalogueThe reasoning
nothing recorded

Details

Graph4 edges
POINTS OUT →
explainsTask and approval UIscapability, core only
explainsProcess automationcapability, core only
published onSAP Communitypublishing source
discovered viaSAP Communitybtp-tag
Source
Type
blog
Published on
Host
community.sap.com
First seen
History1
  • Entered the atlasDiscovered via SAP Community · btp-tag.
For your agent
Ref
content:sap-mdg-cloud-ready-mode-5-solution-patterns-zero-badis-how-we-implemented-5-typ
JSON
/content/sap-mdg-cloud-ready-mode-5-solution-patterns-zero-badis-how-we-implemented-5-typ.json
MCP
Connecting an agent