Use-Case Pattern

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:


What to select

Use-case patterns help us choose the best approach for our integration needs.

How to Select the Right Use-Case Pattern?

🔹 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.


Examples 

Integration StyleUse-Case PatternExample Scenario
Process IntegrationAPI-based IntegrationSAP S/4HANA Cloud exposing APIs to SAP SuccessFactors.
Process IntegrationOrchestration WorkflowAutomating order fulfilment between SAP and external logistics providers.
Data IntegrationBatch Data ReplicationSynchronizing customer master data between SAP and a data lake.
Data IntegrationReal-time StreamingStreaming transactional data from SAP ERP to a cloud analytics platform.
Event-Driven IntegrationEvent-driven MessagingUsing Data Event Integration to notify downstream systems of sales order changes.
User IntegrationUI-based IntegrationProviding SAP Fiori applications for users to interact with cloud and on-premise systems.
Thing IntegrationIoT Edge ProcessingCollecting real-time machine data and integrating it into SAP Digital Manufacturing Cloud.