Every SAP customer we talk to has the same problem: approvals take too long because approvers don't live in Fiori. They live in Microsoft Teams. We built SAP Approvals for Teams to fix that.
The Problem We're Solving
If you run SAP S/4HANA, you know the drill. A purchase requisition gets submitted. It routes to an approver. The approver is supposed to open their Fiori Inbox, review the details, and click approve or reject.
In practice? Most approvers never open Fiori unless someone physically reminds them. The result:
- Purchase requisitions sit for days — sometimes weeks — waiting for a click
- Procurement teams chase approvers through email, Slack, and hallway conversations
- Requestors get frustrated and start finding workarounds (none of them compliant)
- Finance can't close the books because invoices are stuck in approval queues
The core issue isn't the approval workflow — SAP's workflow engine is fine. The issue is the user experience. Fiori Inbox is a great tool that nobody uses because it's not where people work.
Our Solution: Meet Them Where They Are
SAP Approvals for Teams brings approval workflows directly into Microsoft Teams using rich Adaptive Cards. When an approval is triggered in SAP, the approver gets a Teams notification with everything they need:
- Document type and number
- Requestor name
- Line-item details and amounts
- One-click approve or reject buttons
The decision flows back to SAP instantly. Full audit trail. No context switching. No Fiori required.
How It Works Under the Hood
The architecture is straightforward:
- S/4HANA triggers a workflow event when an approval is needed
- OneLoop Bridge (hosted on Azure) receives the event via OData/BAPI
- The Bridge maps the SAP user to a Microsoft 365 identity via Azure AD
- An Adaptive Card is sent to the approver in Teams via the Microsoft Graph API
- When the approver clicks approve or reject, the decision is written back to SAP
Everything runs on Azure. Your data never leaves your region. The Bridge handles retries, fallbacks, and audit logging automatically.
What's Supported
At launch, we support the most common SAP approval scenarios:
- Purchase Requisitions (PR) — the most requested approval type
- Purchase Orders (PO) — for organizations with PO approval workflows
- Supplier Invoices — accelerate invoice processing and payment cycles
- Time Sheets — for project-based organizations tracking time in SAP
Each approval type comes with a pre-configured Adaptive Card template. No designing cards from scratch.
What Makes This Different
You might be thinking: "Can't I build this with Power Automate?" Technically, yes. In practice, it's a six-month project.
Here's what makes SAP Approvals for Teams different:
- Opinionated defaults — We've already made the design decisions. You configure, not build.
- SAP-native — We use standard OData and BAPI interfaces, not screen scraping or fragile workarounds.
- Production-ready — Audit trail, fallback to Fiori, delegation support, and retry logic are built in.
- Two-week deployment — Most customers go live in under two weeks, not six months.
Get Early Access
We're currently onboarding pilot customers. If your organization runs SAP S/4HANA and Microsoft Teams, we'd love to talk.
We'll walk through the product, discuss your specific approval workflows, and determine if SAP Approvals for Teams is a good fit for your organization.