Orchestrate SAP business processes
beyond SAP
Build approval and exception processes that connect SAP, Microsoft Teams and external services — without requiring every process to be built as an SAP workflow.
- Bring together data, APIs and people
- Deliver decisions in Microsoft Teams
- Update SAP and other systems
- Keep SAP as your system of record
Trigger. Enrich. Decide. Act.
Many business processes follow the same pattern. Looply brings these stages together in a single workflow.
Trigger
Start from an SAP event, request submission, document creation or API call.
Enrich
Combine SAP data with information from external services and APIs.
Decide
Route work to the right people and capture decisions in Microsoft Teams.
Act
Update SAP or another system to complete the business process.
How it works
An SAP-centric process, orchestrated in Looply.
Build SAP-centric processes without building everything in SAP
There are many business requirements where creating another SAP workflow may not be necessary.
Looply can provide the orchestration layer directly — responding to SAP events, applying business rules, gathering additional data, routing decisions through Microsoft Teams and triggering the final system action.
SAP can remain at the centre of the process, without every workflow step having to be implemented inside SAP.
- Trigger
- Business rules
- External data
- Human decisions
- Final system action
Three common process patterns
Start with a request
A user submits a request through SAP Build, Microsoft Power Apps, Fiori or another business application. Looply gathers any additional information required, routes the process through Microsoft Teams and triggers the final system action.
Start with an SAP event
An SAP event can start the process automatically — for example, when a supplier is created, master data changes or an exception is identified. Looply enriches the process, manages the required decisions and updates SAP when complete.
Start with an SAP document
A document is created in SAP and held for review while Looply manages the approval process. Once the required decisions have been made, Looply can release, unblock or update the document.
Build external data into your SAP processes
The information needed for a good business decision does not always live in SAP.
Looply can call external APIs during the workflow, bringing additional context into the process before the decision is presented to the user.
This might include tax or VAT validation, company information, risk and compliance data, document services, AI services or other enterprise systems.
Better context leads to better, faster decisions.
Use each platform for what it does best
Looply can orchestrate the process outside SAP, while SAP BTP remains the controlled integration layer into the SAP landscape.
That gives you flexibility without losing control.
Looply
Process orchestration
API integration
Business rules
Microsoft Teams interaction
SAP BTP
Secure connectivity
Authentication
Policy enforcement
Controlled SAP access
SAP Core
Business data
Core business logic
Authorisations
Transactional processing
External Services
Validation
Risk and compliance data
Document services
Specialist APIs and AI
Keep SAP protected and central, without requiring every part of the process to be built inside SAP or BTP.
Keep SAP at the centre
Using Looply as the orchestration layer does not mean moving business control away from SAP.
SAP can continue to own the data, rules and business logic that belong there, while Looply orchestrates the process around them.
SAP can continue to provide:
- approver determination
- organisational structures and roles
- delegation
- authorisation checks
- transaction validation
- document status
- business updates
Orchestration can sit outside SAP while governance and transactional control remain inside it
Orchestrate more than approvals
The same orchestration model can support much more than a simple approve-or-reject process.
Looply can coordinate business activity across SAP, Microsoft Teams and external services.
Multi-stage reviews
Exception management
Data enrichment
Additional information requests
Task assignment
Escalation
Document release
Master data governance
Use Looply to coordinate the process around SAP, not just the approval step.
Example: supplier review and release
A supplier is created in SAP and initially held for review. Looply then orchestrates the complete process around that transaction.
Supplier created in SAP
A supplier-creation event starts the Looply workflow.
Gather and enrich the data
Looply retrieves the relevant SAP data and calls external services for tax, company or risk information.
Present the decision in Teams
The combined information is presented to the appropriate reviewer in Microsoft Teams.
Manage any further approvals
Looply can route the process through additional review or approval stages if required.
Update SAP
Once the process is complete, Looply triggers the required SAP action — for example releasing, unblocking or updating the supplier.
One process can combine SAP data, external intelligence, human judgement and final system action.
Turn SAP events into complete business processes
An SAP event can be the start of a complete business process — not just another notification.
With Looply, that event can start a complete process — bringing together SAP data, external services and human decisions in Microsoft Teams, before triggering the final action back in SAP or another system.
Trigger. Enrich. Decide. Act.
Show us the process you want to automate, and we’ll help you explore the right orchestration approach.