SAP integration
Camunda's SAP integration consists of several features that can be used independently of one another: SAP OData, RFC, and BTP.
- SAP OData Connector: Interact with a S/4HANA or ECC System via OData v2 + v4 APIs, directly from your BPMN model.
- SAP RFC outbound Connector: Query BAPIs and remote-enabled function modules on SAP ECC systems.
- SAP BTP integration
- Use Tasklist's forms in the Fiori UI
- Operate SAP BTP services from BPMN tasks
- Inbound proxy endpoint to start process instances of BPMN models, including custom variables
These features run in the customer's SAP BTP instance. They do not require a proprietary Camunda setup, and instead re-use an existing infrastructure with minimal prerequisites.
Technical requirements
All SAP integration artifacts have the following technical requirements:
- They run on SAP BTP, Cloud Foundry environment, and thus need the respective service.
- (free) Destination Service for system and service connectivity.
- If the S/4 or ECC system is located on-premises:
- (free) Connectivity Service
- SAP Cloud Connector configured and connected to both S/4 ECC and the BTP subaccount where the Camunda SAP integration artifacts will run.
- Technical user with respective access right to the S/4 and/or ECC system.
SAP OData Connector
No additional requirements.
SAP RFC Connector
SAP BTP integration
For scaling out and up, either add multiple instances of an integration module (for example, the SAP OData Connector) or equip an integration module with more runtime memory (for example, the SAP BTP integration).
For more sophisticated tuning, all mechanisms of BTP can be applied (such as the (free) Application Autoscaler), as all SAP integration artifacts fully adhere to the BTP cloud-based development standards and can be fully configured just as any custom developed apps on BTP.