When enterprises need to orchestrate processes across SAP modules and external systems, they typically evaluate three approaches: Camunda as a dedicated orchestration engine, SAP CPI (Cloud Platform Integration) as SAP's native middleware, or custom ABAP code built directly in the SAP system.
Each approach has legitimate strengths. This article provides an honest comparison based on production implementations.
The Problem All Three Approaches Solve
SAP S/4HANA manages transactions within modules — MM handles purchasing, SD handles sales, TM handles logistics. But real business processes cross module boundaries. A single business event can trigger updates across multiple modules, external systems, and human decision points.
The question is: what sits in the middle and orchestrates the cross-system flow?
Approach 1: Camunda 8
Camunda is a dedicated process orchestration engine. It manages stateful process instances that coordinate work across any combination of systems, APIs, human tasks, and AI agents.
Strengths
Stateful orchestration. Every process instance maintains state across multiple API calls, retries, and human interactions. If a process fails at step 5 of 8, it resumes from step 5 — not from scratch.
Concurrency control. Message correlation guarantees that concurrent events targeting the same document are serialized within a single process instance. No custom locking code required.
Visual process model. The BPMN diagram is both the documentation and the executable code. Business analysts can read it. Developers can extend it. Operations can monitor it in Camunda Operate.
Three-tier error handling. Automatic retry with backoff, team notification, and human-in-the-loop review — all as reusable subprocesses.
Parallel execution. Parallel gateways enable concurrent updates to different systems. Multi-instance subprocesses iterate over document collections. Error boundaries isolate failures.
Agentic AI (8.8+). AI Agent Connector embeds AI agents inside BPMN-governed workflows. Agents handle exceptions, decision support, and intelligent routing — with full audit trail.
System agnostic. Camunda orchestrates any system — SAP, Salesforce, legacy APIs, databases, AI services. It is not locked to the SAP ecosystem.
Limitations
- Requires a separate runtime (Camunda SaaS or self-hosted on Kubernetes)
- Learning curve for teams unfamiliar with BPMN
- Additional infrastructure to maintain
- Not part of SAP's native toolchain — requires connector development for SAP APIs
Best For
Complex, cross-system processes with concurrency requirements, error handling needs, human decision points, or AI agent integration. Processes that span SAP and non-SAP systems.
Approach 2: SAP CPI / Integration Suite
SAP CPI is SAP's cloud-based integration platform. It handles message routing, data mapping, and API mediation between systems.
Strengths
Native SAP connectivity. Pre-built adapters for S/4HANA, SuccessFactors, Ariba, and other SAP products. OData, RFC, IDoc, and SOAP connectors are out of the box.
Data mapping. Graphical message mapping tools for transforming payloads between systems. XSLT and Groovy scripting for complex transformations.
Monitoring. Built-in message monitoring shows payload flow, errors, and retry status.
SAP ecosystem. Part of SAP BTP. Supported by SAP. Familiar to SAP consultants.
Limitations
No stateful process instances. CPI processes messages, not processes. It cannot track which documents in a batch succeeded and which failed. It has no concept of "resume from where we left off."
No concurrency control. Two messages for the same SAP document are processed independently. CPI has no mechanism to serialize them or prevent lock conflicts.
No human-in-the-loop. CPI cannot route exceptions to a human for review with a form and decision options. It either succeeds, retries, or fails.
Limited retry logic. Basic retry count with fixed intervals. No exponential backoff. No conditional retry based on error type.
No parallel execution with join. CPI cannot split a process into parallel tracks that later converge. Sequential processing only.
Best For
Point-to-point integration between SAP systems. API mediation. Data transformation. Scenarios where message routing is the primary requirement and stateful orchestration is not needed.
Approach 3: Custom ABAP
Custom ABAP code built directly in SAP's application layer. This includes ABAP programs, function modules, BAdIs, enhancement spots, and custom RFC/OData services.
Strengths
Deep SAP integration. Direct access to SAP's internal APIs, database tables, and business objects. No connector layer needed.
Performance. Runs inside the SAP kernel. No network overhead for internal SAP operations.
Familiar to SAP teams. Most SAP shops have ABAP developers. No new technology to learn.
Fine-grained control. Full access to SAP's locking mechanisms, authorization checks, and transaction handling.
Limitations
No visual process model. The logic is buried in code. Business analysts cannot read it. Changing the process requires a developer, code review, and transport.
No reusability. Each cross-module synchronization flow is built from scratch. There is no subprocess library or component reuse across processes.
No orchestration primitives. Parallel execution, message correlation, event-based gateways, timer events, and multi-instance loops must all be built from scratch for every process.
Clean Core violation. Custom ABAP in the core system violates SAP's Clean Core methodology. It increases upgrade risk, blocks S/4HANA cloud migration, and creates technical debt.
No external system orchestration. ABAP cannot natively orchestrate Salesforce, external APIs, or AI services without additional middleware.
Maintenance burden. Every SAP upgrade requires regression testing of custom code. The more custom ABAP, the higher the upgrade cost.
Best For
Simple, SAP-internal automations where performance is critical and the logic is unlikely to change. Scenarios where the process stays entirely within SAP and does not involve external systems or human decision points.
Head-to-Head Comparison
| Capability | Camunda 8 | SAP CPI | Custom ABAP | |---|---|---|---| | Stateful process instances | Yes | No | Custom code required | | Concurrency serialization | Native (message correlation) | Not available | Custom code required | | Stateful retry with backoff | Reusable subprocess | Basic retry count | Custom code required | | Human-in-the-loop review | User tasks with forms | Not available | Custom Fiori app needed | | Parallel multi-document updates | Parallel gateway + multi-instance | Sequential only | Custom threading | | Visual process model | Executable BPMN | Integration flows (not BPMN) | No visual model | | DMN business rules | Native | Not available | Custom decision logic | | Agentic AI integration | AI Agent Connector (8.8+) | Not available | Not applicable | | SAP Clean Core compliant | Yes (external orchestration) | Yes (BTP-based) | No (core modification) | | Non-SAP system orchestration | Any system via connectors | SAP-focused adapters | Requires middleware | | Audit trail | Camunda Operate | Message monitoring | Custom logging | | Time to modify a process | Minutes (BPMN + DMN) | Hours (iFlow redesign) | Days to weeks (code + transport) |
When to Use What
Use Camunda when:
- Your process spans SAP and non-SAP systems
- You need concurrency control for concurrent document updates
- You need human-in-the-loop exception handling
- You want AI agents governed by BPMN
- Process visibility and audit trail are requirements
- You need to change processes without code deployments (DMN tables)
- SAP Clean Core compliance matters
Use SAP CPI when:
- You need point-to-point integration between SAP products
- The primary need is data transformation and message routing
- You are already invested in SAP BTP and want to stay in the SAP ecosystem
- No stateful orchestration or concurrency control is needed
Use Custom ABAP when:
- The automation is entirely SAP-internal
- Performance is the top priority
- The logic is simple and unlikely to change
- You are on an older SAP system where BTP is not available
- You accept the Clean Core trade-off
The Hybrid Approach
In practice, most enterprise SAP landscapes use a combination:
- Camunda orchestrates the cross-system process, handles concurrency, and manages exceptions
- SAP CPI handles SAP-to-SAP message routing and data transformation where needed
- Custom ABAP provides specific SAP function imports or BAdI implementations that Camunda calls via OData
This is not an either/or decision. Camunda sits at the orchestration layer. CPI and ABAP operate at the integration and execution layers beneath it.
Cost Considerations
Camunda SaaS: Subscription-based pricing. Predictable cost. No infrastructure management.
Camunda Self-Managed: Kubernetes hosting cost. Requires DevOps capability. Full data sovereignty.
SAP CPI: Included in some SAP BTP bundles. Metered by API calls and message volume.
Custom ABAP: Developer time (most expensive resource in SAP ecosystems). Ongoing maintenance cost. Upgrade risk cost (often hidden until upgrade time).
The total cost of ownership calculation should include not just licensing, but developer time to build, modify, and maintain — and the business cost of manual exception handling that could be automated.
Evaluating orchestration approaches for your SAP landscape? Book a free process audit. We'll assess your specific cross-system flows and recommend the right combination of Camunda, CPI, and ABAP for your needs.