Process Orchestration
Orchestrate SAP-centric business processes in the right place
Business processes increasingly span SAP, external systems, APIs and people. Some belong inside SAP. Others are best orchestrated outside SAP. And existing SAP processes can often be made more effective by extending them into Microsoft Teams.
Arch provides complementary approaches for each scenario — using Stelo and Varo for integrated processes inside SAP, and Looply to extend or orchestrate processes beyond SAP.
Beyond SAP
Cross-system orchestration
APIs & automation
Extend into Teams
Existing SAP processes
Teams engagement
Inside SAP
Form-driven SAP processes
Data capture & process execution
Orchestrate SAP-centric processes beyond SAP
For processes that span SAP, external APIs, cloud services and potentially people, Looply can provide the orchestration layer itself.
The process might be fully automated, introduce Microsoft Teams only when human judgement is required, or combine automated and manual paths.
SAP remains central to the business transaction, while Looply coordinates what happens around it.
Build approval and exception processes that connect SAP, Microsoft Teams and external services — without requiring every process to be built as an SAP workflow.
When a new process requirement appears around SAP, the discussion often starts with workflow technology. Should the process be built using SAP Workflow or Flexible Workflow? Should it sit in SAP Build Process Automation on BTP?
Platforms that execute processes, rather than simply coordinate integrations, are fundamentally better suited to owning SAP-centric business outcomes.
Process Orchestration to bring work into Microsoft Teams
Where SAP Workflow, Flexible Workflow, SAP MDG, GRC or another process engine already owns the process, Looply can extend the user interaction into Microsoft Teams.
The underlying process stays where it is. Looply improves engagement, brings richer context to the user and allows decisions and actions to take place in Teams.
This article explores the main architectural approaches for integrating SAP work into Microsoft Teams and introduces a requirement-driven framework for selecting the right approach.
In an era where speed and accuracy are crucial, AI-driven approvals are not just an improvement—they’re a necessity. AI in Looply provides the tools to make informed, data-driven decisions faster and with greater confidence, ensuring that businesses stay agile and efficient in an increasingly complex world.
Orchestration custom processes in SAP
For processes where SAP owns the data, business logic and user interaction, Arch provides tools to build integrated, form-driven processes directly around SAP.
This is where Stelo/Varo belong: data capture, validation, multi-step processing and SAP updates where the process naturally belongs inside SAP.
Stelo gives you the freedom model end-to-end processes, not just the parts that trigger an update in S/4HANA.
Stelo transforms manual forms into fully integrated SAP Fiori Forms, helping businesses digitize and automate processes while reaping numerous benefits within the SAP ecosystem.
Digitising a form is not the same thing as digitising a process, and confusing the two is one of the most common causes of failed SAP digitisation initiatives.