
Use-case patterns describe recurring business scenarios or problems that require integration.
These patterns are categorised based on specific business needs, such as real-time order processing, master data synchronisation, or IoT device monitoring.
Use-case patterns are built based on the identified appropriate Integration Styles that suit the business problem:

Use-case patterns help us choose the best approach for our integration needs.
🔹 For real-time business events → Use Event-Driven Messaging.
🔹 For orchestrated workflows → Use Process Integration.
🔹 For moving large data sets → Use Data Integration.
🔹 For analytics and reporting → Use Analytics Integration.
🔹 For user-centric experiences → Use UI-Based Integration.
📌 Event-Driven Integration does not replace Analytics Integration, but rather enhances it by providing real-time data feeds for analytics.
📌 Analytics Integration involves both structured and unstructured data, unlike Process or Event-Driven Integration.
| Integration Style | Use-Case Pattern | Example Scenario |
|---|---|---|
| Process Integration | API-based Integration | SAP S/4HANA Cloud exposing APIs to SAP SuccessFactors. |
| Process Integration | Orchestration Workflow | Automating order fulfilment between SAP and external logistics providers. |
| Data Integration | Batch Data Replication | Synchronizing customer master data between SAP and a data lake. |
| Data Integration | Real-time Streaming | Streaming transactional data from SAP ERP to a cloud analytics platform. |
| Event-Driven Integration | Event-driven Messaging | Using Data Event Integration to notify downstream systems of sales order changes. |
| User Integration | UI-based Integration | Providing SAP Fiori applications for users to interact with cloud and on-premise systems. |
| Thing Integration | IoT Edge Processing | Collecting real-time machine data and integrating it into SAP Digital Manufacturing Cloud. |