Integration Guide ISA-M_TEMPLATE_Version 4.0

ISA-M_TEMPLATE_Version 4.0.pptx

1. SAP Integration Solution Advisory Methodology Derive Integration Guidelines for Your Organization < Your Organization > This document uses templates from the SAP Integration Solution Advisory Methodology (ISA-M) provided by SAP SE. SAP SE is not responsible for the content of this document. ISA-M Template Version 4.0 ISA-M SAP Integration Solution Advisory M e t h o d o l o g y

2. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

3. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

4. * Customers and partners must comply with the Terms of Use (“TOU”), see slide 5 Overview Helps enterprise architects to shape their integration strategy Collection of typical integration styles and patterns Mapping to integration services (based on customer context) Architecture blueprints for integration including decision criteria Open to SAP and third party integration technologies Target Group: Enterprise Architects / Integration Architects ISA-M Template for Use by Customers and Partners (*) Template to define customer-specific integration guidelines Successfully adopted in multiple global organizations Reusable within organizations, projects or services Can be adapted/extended to specific needs SAP Integration Solution Advisory Methodology (ISA-M) Simplify Integration by a Systematic Integration Approach Overview

5. SAP Integration Solution Advisory Methodology Template - Terms of Use Overview

6. SAP Integration Solution Advisory Methodology Template Adapt and Customize To Your Specific Needs Overview This element is used to introduce and describe concepts of the methodology and/or related product information. Explanation This element is used to give additional information on how to apply the ISA-M template to your customer context. How To Use

7. Version Date Changes 3.0 September , 2016 Updated description of integration domains Updated descriptions of integration styles New category ‘Enabling Services’ to capture integration related technologies Updated descriptions of reference use case patterns Updated decision table templates 3.1 March , 2017 Updated template to reflect naming changes in SAP Cloud Platform 3.2 October , 2018 Updated descriptions and examples for all integration styles, use case patterns and sample integration technology mappings Added information on SAP’s integration strategy for the intelligent enterprise and the role of ISA-M (slide 8-9) Added overview on ISA-M use cases for enterprise architects (slide 11-12) Added ‘How to Use’ and ‘Explanations’ to slides to give additional information on how ISA-M can be adapted by customers Added typical integration roles and their responsibilities (slide 15-17) Updated examples for integration technology mappings including links to further product information (slide 32-74) Added additional guidance based on integration patterns: Integration Layer vs. Application Layer (slide 44) Integration Layer vs. API Management Layer (slide 73) Added section and links for CIO Guides (slide 81-82) Added integration domain (slide 19) Business-to-Government (B2G) Renamed ‘Integration Solution Advisor Methodology’ to ‘Integration Solution Advisory Methodology’ Renamed Integration Styles to more ‘classical names’ (all slides) ‘Process Invocation’ to ‘Process Integration’ ‘Data Movement’ to “Data Integration” ‘User-Centric Consumption to ‘User Integration’ ‘Enabling Services’ to ‘Cross Use Cases’ Added new use case patterns (slide 30) API-Managed Integration Event-Based Integration Stream Analytics ISA-M Template Document History (I) Overview

8. Version Date Changes 3.3 May, 2020 Renamed Integration Solution Advisory Methodology to SAP Integration Solution Advisory Methodology ( slide 1 ff.) Removed section ‚CIO Guide‘ from the agenda and moved this information to the appendix of the deck (slide 2 ff.) Updated Intelligent Enterprise visual ( slide 9) Added new quote from Gartner (slide 11) Added ISA-M Cycle (slide 12, 17, 33, 84, 117) Updated use cases for Enterprise Architects according to the new ISA-M Cycle (slide 13) Updated Integration Maturity Level according to the new ISA-M Cycle (slide 14) Updated ISA-M overview visuals to show updated integration domain, use case patterns and technology mapping (slide 15) Moved section ‘Integration roles’ from position 2 to 7 according to the new ISA-M cycle (slides 116 – 121) Updated Integration Domains to include private cloud deployment options, removed integration style B2B and B2G (now defined as integration use cases) (slide 18 ff.) Added private cloud as application deployment option (slide 22) Updated use case patterns (slide 24 ff.): Process Integration Style: Removed ‘Business Network Integration’, added ‘Master Data Integration’ and ‘B2G Integration’ Data Integration Style: Removed ‘Master Data Synchronization’, added ‘Data Orchestration’ User Integration Style: Removed ‘Desktop Integration’, added ‘Chatbot Integration’ Cross Use Case Patterns: Added ‘Robotic Process Automation’ and ‘Digital Integration Hub’ Updated Integration Technology Mapping: Added integration technology categories such as ESB, IPaaS, IoT Platform (slide 34 ff.) Updated Sample Mapping to SAP Technologies / Services for the Process Integration Style such as product names (slide 40) Added slide about SAP Cloud Platform Integration Suite (slide 42) Updated and enhanced resources for the Process Integration Style (slide 48, 49) Updated Sample Mapping to SAP Technologies / Services for the Data Integration Style: Replaced SAP Data Hub with SAP Data Intelligence (slide 52 ff.) Replaced SAP HANA Data Management Suite with SAP Data Intelligence (slide 54) Updated and enhanced resources for the Data Integration Style (slide 56) Updated Sample Mapping to SAP Technologies / Service for the Integration Style such as product names (slide 59) Replaced SAP Fiori Launchpad with SAP Fiori Launchpad (ABAP) and SAP Fiori launchpad on SAP Cloud Platform (Cloud Foundry) (slide 60) Updated version of SAP Fiori Deployment Options (slide 61) Added Central Entry Point (Roadmap) (slide 62) Updated and enhanced resources for the User Integration Style (slide 63) ISA-M Template Document History (II) Overview

9. Version Date Changes 3.3 continued May, 2020 Updated Sample Mapping to SAP Technologies / Services for the Thing Integration Style: Replaced SAP Cloud Platform Internet of Things with SAP Leonardo IoT (slide 66) Replaced SAP Cloud Platform Internet of Things with SAP Leonardo IoT (Cloud Foundry) (slide 67) Updated version of SAP Leonardo IoT & SAP Edge Services overview (slide 68) Updated and enhanced resources for the Thing Integration Style (slide 69) Updated decision table template for Cross Use Cases to include SAP Intelligent Robot Process Automation (slide 73) Updated and enhanced resources for the Cross Use Cases (slides 76, 77) Replaced Interface Assessment for Data Replication with Data Orchestration (SAP Data Intelligence) New section about Architecture Blueprints introduced which includes sample solution diagrams for selected integration uses case patterns, complemented with decision criteria/characteristics, integration do’s and don’ts (slide 83 ff.) Replaced CIO Guides ‘SAP Vision for Integrating SAP Applications in Cloud and Hybrid Environments’ and ‘Identity Lifecycle in Hybrid Landscapes’ with link to all SAP CIO Guides from section 7 ‘CIO Guides’ (slide 122 ff.) 3.4 February, 2021 Updated visuals (e.g.

10. SAP‘s integration strategy in context of the intelligent enterprise,

11. int egration maturity levels,

12. SAP Data Intelligence,

13. SAP API Management overview ) New guidance regarding the Master Data Integration use case pattern introducing SAP Master Data Integration (slides 47/48) New integration style Analytics Integration (slides 62 ff.) Updated guidance regarding SAP Enterprise Information Management solutions (slides 58/59) Updated guidance regarding the User Integration Style introducing the SAP Launchpad service (slides 74/75) Updated reference to the new “Integration Architecture Guide for Cloud and Hybrid Landscapes” Updated SAP products names along the sunset of the SAP Leonardo and SAP Cloud Platform brand (e.g. „SAP Leonardo Internet of Things“ renamed to „SAP Internet of Things“, „SAP Cloud Platform Integration Suite“ renamed to „SAP Integration Suite“, Changed „Non-SAP“ to „third party“ Changed section 7 „Integration Roles“ to „Integration Roles & Governance“ (slides 2, 3 and more) New integration role of the Chief Integration Officer introduced (slides 136, 139) New topics integration governance and quality assurance introduced (slides 142 to 145) ISA-M Template Document History (III) Overview

14. Version Date Changes 4.0 August, 2022 Updated various SAP product names (e.g. SAP Enterprise Messaging to SAP Event Mesh, SAP Intelligent RPA and SAP Workflow together SAP Process Automation) and added new ones (e.g. SAP Mobile Start and SAP Work Zone) Updated Intelligent Enterprise visual (p. 11) Changed „out-of-the-box integration“ to „predefined integration“ (p.11, 12) Changed „use cases“ to „ phases “ (e.g. p. 14) Added link of the ISA-M landing page on sap.com (p. 16) Added Integration Assessment capability within SAP Integration Suite (e.g. p. 17, 18) Changed integration domain „OnPremise2Cloud“ to „Cloud2OnPremise“ (e.g. p. 21, 22) Removed „Key Characteristics“ (e.g. p. 26) Changed "sample integration patterns" to "sample key characteristics" (p. 53) Changed recommendation degrees from "recommended" to "good fit", "partially recommended" to "partial fit", "not recommended" to "not a fit" (p. 50, 53, 90) Updated positioning of SAP Integration Suite (p. 44, 46, 48) Updated positioning of SAP Data Intelligence (p. 57, 59, 60) Updated integration guideline for process-, data integration and selected cross use cases inline with integration policies of the Integration Assessment capability within SAP Integration Suite (p. 45, 58, 88) Updated positioning of SAP Analytics Cloud and SAP Data Warehouse Cloud (p. 68, 69, 70) Updated positioning of SAP products for the user integration style (p. 74, 75, 77) Updated positioning of SAP Internet of Things (p. 81, 83) Updated information about interface assessment to leverage the Integration Assessment capability within SAP Integration Suite (p. 93) Updated info sheets of architecture blueprints to include related missions of SAP Discovery Center (p. 105ff) Updated integration roles to also include tasks related to the Integration Assessment capability within SAP Integration Suite (p. 137, 138) Updated integration governance to leverage Integration Assessment (p. 143) Added information about how to get started with ISA-M (p. 148) Updated information rgd. the “Integration Architecture Guide for Cloud and Hybrid Landscapes (p. 149) Added information about SAP Community topic page about the SAP Integration Strategy (p. 150) ISA-M Template Document History (III) Overview

15. Intelligent Enterprises are Integrated Enterprises Key Integration Principles for the Intelligent Enterprise Overview Integration is a key enabler for intelligent enterprises. SAP’s integration strategy for the intelligent enterprise is based on four core principles. ISA-M complements SAP’s technology portfolio by a methodology that helps enterprise architects to shape their integration strategy. It provides a holistic view on integration including all types of integration use cases needed for full end to end integration. Source: Intelligent Enterprises Are Integrated Enterprises Explanation Predefined

16. Intelligent Enterprises are Integrated Enterprises SAP’s Integration Strategy for the Intelligent Enterprise Overview ISA-M supports the holistic integration principle by providing a systematic methodology for enterprise architects to define, asses and evolve their integration architecture. It supports enterprise architects in defining integration guidelines for their organizations and allows to include SAP as well as third party integration technologies / services (depending on the customer context). Explanation predefined

17. Integration Challenge for Enterprise Architects The Increased Scope of Integration Overview

18. ISA-M Cycle Overview: Adoption phases for Enterprise Architects Overview

19. ISA-M Phases for Enterprise Architects Simplify Integration by a Systematic Integration Approach Define Integration Best Practices 3 Define solution architecture blueprints Add decision criteria and key characteristics Establish integration as recognized discipline Assess your Integration Strategy 1 Document/review your integration architecture Scoping of focus areas e.g. future building blocks Use-case driven approach (technology-agnostic) Design your Hybrid Integration Platform 2 Map use case patterns to integration technologies Derive integration guidelines for your organization Reflect customer context This slide provides an overview on how ISA-M can be applied in organizations. Depending on the specific needs of your organization you can flexibly select from the possible use cases and use the ISA-M template as a starting point and adapt/extend it to your specific needs. Based on this template, you can create your customer-specific integration strategy and/or guidance document(s). How To Use Overview Enable a Practice of Empowerment 4 Democratize integration delivery Define areas for self service integration Establish a shared developer community

20. Increase Your Integration Maturity Level Simplify Integration by a Systematic Integration Approach This slide shows how you can increase your integration maturity level by moving from an non-systematic integration practice to a more systematic way of integration. Based on established integration standards, you could also define areas for self-service integration e.g. by allowing citizen integrators to implement simple integration scenarios on their own within the context of your overall integration governance. See landing page on sap.com Explanation Overview

21. Tool Based Approach for ISA-M to Enable Integration Governance Integration Assessment Capability within SAP Integration Suite ISA-M Framework This PPT Template Integration Assessment C apability within SAP Integration Suite Integration Assessment (powered by ISA-M) is a capability within SAP Integration Suite which will automate key parts of the SAP Integration Solution Advisory Methodology (ISA-M) and can be used to provide assessment and guidance within an organization to manage their hybrid integration platform (e.g. integration governance). See blog post Integration Assessment capability within SAP Integration Suite is general available now Explanation NEW

22. Integration Assessment Capability within SAP Integration Suite at a Glance Introduce integration governance Define policies to establish guidelines for the use of integration technologies within an organization Determine the most suitable integration technology for a specific integration scenario Improve the collaboration between integration architects, integration developers and business domain experts Shape your integration technology strategy Tool based approach for key parts of the SAP Integration Solution Advisory Methodology Includes SAP’s integration technology recommendations for a turnkey start Open to cover custom recommendations, incl. third party applications and technologies Gain insights into your integration landscape Build an inventory of existing integration technologies Get an overview of the use of integration technologies across an application landscape Document integration requirements, technology proposal and selection SAP Discovery Center Mission Get started with Integration Assessment

23. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

24. ISA-M Cycle Phase 1: Assess your Integration Strategy Objectives and approach Assess your integration maturity level Documentation/review of your integration architecture Scoping of focus areas e.g. future building blocks Use-case driven approach (technology-agnostic) Reasons for integration strategy assessment Need to cover new integration patterns Implementation of new cloud applications Transition to SAP S/4HANA Standardization and governance Integration technology consolidation Mergers and acquisitions

25. Integration Domains Assessment and Scoping of your Hybrid Integration Landscape On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 CX X … Third Party Cloud Apps S/4HANA Business Suite Third Party Applications OnPremise2 OnPremise Private Cloud Integration Domains Integration Styles Technology Mapping Integration Domain Business Partner Government Agency

26. Integration Domain Relevance Integration Services / Technologies Relevant Not Relevant Under Evaluation As Is To Be Cloud2Cloud Cloud2OnPremise Cloud2Cloud User2OnPremise User2Cloud Thing 2OnPremise Thing 2Cloud Integration Domains High-Level Assessment of Your Integration Architecture Integration domains provide the entry point into ISA-M and can be used as a “big picture” for integration. You can do an assessment of your integration architecture by selecting the integration domains that are relevant for your organization or that you might want to further evaluate. Next, you can list your current integration technologies / services (As Is) and also derive your future target architecture (To Be). Integration domains are technology agnostic and can therefore also help in blueprinting a hybrid integration platform consisting of multiple integration services/technologies (SAP/third party). You could also remove integration domains that are not relevant in your organization. How To Use Integration Domains Integration Styles Technology Mapping

27. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

28. Integration Styles Five Fundamental Archetypes of Integration Integration Domains Integration Styles Technology Mapping Integration styles describe basic categories or types of integration: process-, data-, analytics-, user-, and thing-centric integration. Each integration style has specific characteristics and can be refined by use-case patterns (see following slides). Integration styles build the key pillar of ISA-M. Explanation Process Integration How to chain business processes across business applications? Data Integration How to synchronize data between business applications? User Integration How to integrate user-centric applications with business applications? Thing Integration How to integrate real- world things with business applications? Analytics Integration How to derive and expose analytical data for business insights from business applications?

29. Integration Styles Technology-Agnostic: Open to SAP and Third Party Integration Domains Integration Styles Technology Mapping Integration Styles cover key integration archetypes: the process integration style connects business processes across applications whereas the data integration style allows to synchronize or access data across applications. The user integration style allows to connect user-centric applications (e.g. mobile apps) with applications whereas the thing integration style allows to connect real world objects (e.g. sensors, machines) with applications . The analytics integration style allows you to derive and expose data from data sources to support business intelligence, augmented analytics and/or enterprise planning scenarios. All integration styles are technology agnostic and are applicable within multiple integration domains (e.g. cloud, on-premise, hybrid). Cross Use Cases build a category for all integration-related use cases that complement one ore more of the five core integration styles. For example, API-Managed Integration provides full-lifecycle management for APIs that, e.g. can be leveraged in user- or process-centric integration scenarios. Further examples in this category will be explained on the next slides such as Event-Based Integration. Explanation Application Business Logic Data Application Business Logic On Premise Cloud Data Mobile Browser Chatbot User-Centric Application User Integration Interaction Logic Device Sensor Asset Real-World Things Thing Integration Cross Use Cases Process Integration Data Integration Interaction Logic Private Cloud On Premise Private Cloud Cloud Analytics Integration

30. Process Integration Data Integration Analytics Integration User Integration Thing Integration Objective Chaining of business processes Synchronization of data Deriving business insights from business applications and data sources Omni-channel access to backend applications Capturing and processing of real world data Interaction Type System-2-System System-2-System System-2-User User-2-System Thing-2-System Coupling to Application Process-Level Data-Level Data-Level / Business-Level UI-Level Data-Level / Process Level Primary Trigger Application Event Schedule or Application Event User Event User Event Thing Event Urgency of Completion (Near) Real-Time Batch or Near Real-Time (Near) Real-Time or Batch (Near) Real-Time (Near) Real-Time or Batch Unit of Data Exchange Single Objects Bulk-Data or Single Objects From aggregated to line item data Single Objects or Bulk-Data Single Objects or Bulk-Data Specific Requirements Transactional Integrity Reliable Messaging Message Orchestration B2B protocol support Data Orchestration Complex transformations Data Quality Management Big Data Processing Local and remote data sources Data & predictive modeling, planning Data privacy & authentication Data volume Online / Offline Support Device Management End-User Management Application Management Thing Management Edge Intelligence IoT protocol support Event Stream Processing Integration Styles Decision Criteria Integration Domains Integration Styles Technology Mapping This slide summarizes typical characteristics per integration style. It can help enterprise architects / integration architects to map integration styles to relevant capabilities of integration technologies / services (as part of the technology mapping). The listed criteria can be used as a starting for discussion and could be further refined in your specific context . How to Use

31. Integration Styles and Use Case Patterns Technology-Agnostic Library of Integration Use Cases 27 Integration Domains Integration Styles Technology Mapping Use Case Patterns: Each integration style can be refined by use case patterns which describe frequently found integration use cases in enterprise landscapes. Based on the same principles, the cross use cases category comprises use case patterns that complement one ore more of the five core integration styles – e.g. API-Managed Integration or Event-Based Integration. Use Case Patterns are technology-agnostic Extensible Library: ISA-M includes a typical set of use case patterns that you can use as a starting point for your organization. You can flexibly adjust the library of use case patterns to your specific needs e.g. by adding additional customer-specific use case patterns or removing patterns that are not relevant in your organization. In the next slides, all use case patterns are described in more detail including an example in the context of SAP. How To Use Integration Styles Use Case Patterns Data Integration Data Replication (ETL) Data Virtualization Data Quality Management Data Orchestration … Thing Integration Thing to Analytics Thing to Process Thing to Data Lake Thing to Thing … Cross Use Cases … User Integration UI Integration Mobile Integration Chatbot Integration Stream Analytics … Workflow Management API-Managed Integration Event-Based Integration Robotic Process Automation Digital Integration Hub Process Integration A2A Integration Master Data Integration B2B Integration B2G Integration … Analytics Integration Embedded Analytics Cross Application Analytics Customer-Specific Use Case

32. Process Integration Style Use Case Patterns Integration Domains Integration Styles Technology Mapping A2A Integration Chaining of business process steps between business applications by the exchange of transactional data. Example: Lead-to-cash process with integration of SAP Customer Experience and SAP S/4HANA: exchange of sales orders. B2G Integration Transform transactional data into predefined exchange formats and transfer it electronically to external legal or tax authority systems. Example: File goods and service tax returns from SAP S/4HANA to the Goods and Services Tax Network (GSTN) organization India in prescribed format and protected fashion. Master Data Integration API-based exchange of master data across business applications. Example: Exchange of business partner master data between SAP S/4HANA and SAP Sales Cloud and SAP Commerce Cloud. B2B Integration Chaining of business process steps between business partners by the exchange of transactional data leveraging standard B2B protocols. Example: Design-to-operate process with integration of a manufacturer with suppliers: exchange of purchase orders using B2B standards like ANSI X.12 or UN/EDIFACT. Application Application Application Application Partner 1 Application Application Application Application Partner 2 Organization Government Agency Application

33. 1 Also APIs might be used for this use case Data Integration Style Use Case Patterns Integration Domains Integration Styles Technology Mapping Data Replication Table-based integration of data covering data replication, migration, or analytical use cases based on ETL/ELT 1 . Example: Replication of data from legacy applications or databases into SAP HANA e.g. for migration, analytics or big data warehousing. App / DWH Application DB Data Orchestration Pipeline-driven data integration for disparate kinds of data supporting also distributed processing. Example: Enable data science and machine learning across all enterprise data assets by integrating data across diverse landscapes. Data Virtualization Provisioning of a virtual data layer by federation of queries to remote data sources without physical data movement. Example: Lookup of shared master data from various data sources, e.g. Virtual data access in SAP HANA to remote data sources. Virtual Data Layer Data Source Data Source Data Quality Management Integration of data from multiple sources for cleansing, matching or consolidation (central business terms). Example: Cleansing of address data. Embedded DQM services in apps to validate address data and/or enrich with geocodes. DQM Data Source Data Source Pipelining IoT Stream Unstructured ML/Predictive Application Data Lake DWH

34. Analytics Integration Style Use Case Patterns Integration Domains Integration Styles Technology Mapping Embedded Analytics Embed analytical content such as reports and dashboards into a business application. Example: Treasury Executive Dashboard. By e mbedding SAP Analytics Cloud into SAP S/4HANA Cloud. Application Analytics Cross Application Analytics Combine data of one or more source systems using an analytics or data ware-house solution. On top of the combined data an analytic consumption model can be built to enable (cross app) reporting. Example : Financial analytics dashboard for SAP Analytics Cloud Analytics Analytics Data Source Application Analytics Platform / Data Warehouse

35. User Integration Style Use Case Patterns Integration Domains Integration Styles Technology Mapping UI Integration Integration of multiple application UIs into a single point of entry including the consumption of backend application services in a web user interface. Example: Central entry point to SAP business application like SAP S/4HANA or SAP SuccessFactors. Web UI Application Application Mobile Integration Consumption of backend application services in a mobile app, leveraging native or hybrid device capabilities including offline data synchronization. Example: iOS or Android mobile apps that access data from on-premise or cloud-based data sources via OData with offline data synchronization. Mobile App Application Application Chatbot Integration Integration of chatbots into various communication channels including integration with backend applications to trigger a transaction or retrieve further information. Example : Digital Assistant as part of SAP SuccessFactors to enable interaction with business users using natural language. Digital Assistant Application

36. Thing to Analytics Real-time integration of thing or machine data for monitoring and analytics. Example: Monitoring of connected devices or machines and to gain real-time visibility of shop floor based production operations. Thing to Thing Exchange of data between two or more things, e.g. machine-to-machine (M2M). Example: Communication between two robots during production process. Thing to Data Lake Collection of thing or machine data to derive future value out of it (e.g. by machine learning). Thing to Process Integration of thing or machine data for triggering a business process step. Example: Triggering of a service order process based on machine alerts (e.g. in the context of SAP Predictive Maintenance & Service). Example: Optimizing asset maintenance with anomaly detection, spectral analysis, and machine learning algorithms. Thing Integration Style Use Case Patterns Integration Domains Integration Styles Technology Mapping Analytical Application Thing Thing Business Application Thing Thing Data Lake Thing Thing Thing Thing

37. Cross Use Cases Use Case Patterns (I) Integration Domains Integration Styles Technology Mapping API-Managed Integration Provisioning of omni-channel and secure access to business applications by managed APIs. Example: Expose APIs to business partners. Managed APIs leverage API traffic management policies, API security policies and API Analytics. Application Layer API Management API Consumption Layer … … Application Application Managed API Managed API Event-Based Integration Decoupling of applications, extensions or IoT data by messaging principles (pub/sub). Example: Event-driven extensions for SAP S/4HANA: Application extensions can react to events from SAP S/4HANA. Event Brokering Application Thing Mobile Application … … Application Pub/Sub Pub/Sub Pub/Sub Pub/Sub Stream Analytics Real-time processing & analytics of event streams including the reaction on event patterns. Example: Monitor incoming IoT-, click-, social media- or business transaction streams for trends, patterns or correlations and respond in real time. Event Stream Processing Input Streams … … Application Application

38. Cross Use Cases Use Case Patterns (II) Integration Domains Integration Styles Technology Mapping Workflow Management Automation and extension of business processes that spawn across multiple applications. Example: Extension of SAP S/4HANA core business processes with additional process logic such as approval steps involving interactive user tasks. Workflow Management Application … … UI / Mobile API Task API Robot Process Automation Automation of workflows across user interfaces and applications using configured scripts (bots). Example: Automate the upload of supplier invoices into SAP S/4HANA. Bot (attended/unattended) Application … … UI API Connector API Digital Integration Hub Provisioning of large-scale, high-throughput APIs by inserting a high performance in-memory data store layer between the API service layer and the system of record. Example: Responsive multichannel access to a customer self service portal which integrates with various backend applications using SAP HANA in-memory database and further integration technologies. High Performance Data Store Web UI Application Mobile Application … … Dara Source Pub/Sub Pub/Sub Event Based Integration Layer

39. 35 Advanced View: Integration Areas Combination of Integration Domains and Integration Styles Integration Domains Integration Styles Technology Mapping Integration Domain N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Cloud2Cloud Cloud2OP OP2OP User2OP User2Cloud Thing2OP Thing2Cloud Process Integration Data Integration Analytics Integration User Integration Thing Integration Integration Style IA-2 IA-3 IA-4 IA-5 IA-6 IA-1 IA-9 IA-10 IA-11 IA-12 To derive integration guidelines for complex landscapes, the combination of integration domains and integration styles might be required. On this slide, possible combinations of integration domains and integration styles are listed. Each combination is defined as an integration area (IA-1 to IA-12). Example: If you want to define a policy for process integration between two cloud applications your can refer to IA-3. Important Note: This step is optional and might be helpful for complex landscapes where fine-grained integration guidelines need to be defined. Please skip, if not useful for your organization. How To Use IA-7 IA-8

40. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

41. ISA-M Cycle Phase 2: Design your Hybrid Integration Platform Objectives and approach Mapping of use case patterns to integration technologies and services Open to SAP and third party integration services Derive integration guidelines for your organization Highly depends on the customer context Sample customer context Enterprise architecture strategy Future application landscape Existing investments Skillsets Commercial aspects

42. Integration Technology Mapping Overview Technology-agnostic concepts SAP and/or third-party components Integration technology categories Use case patterns Integration styles P1 P2 … D1 D2 … A1 A2 … U1 U2 … Data integration Process integration Analytics integration User integration Thing integration T1 T2 … Customer context … ESB IPaaS Analytics platform Data mgt IoT platform … T1, T2, … T3, T4, … T5, T6, … T7, T8, … T9, T10, … Capabilities Cross-use cases C1 C2 … Integration Domains Integration Styles Technology Mapping In the third step of the methodology, integration styles and use case patterns (all technology-agnostic) can be mapped to integration technologies or services that should be used in your customer context (SAP and/or third party). This mapping highly depends on your specific customer context – some sample factors that might need to be considered are listed on the next slide. This allows you to derive your own decision framework. How To Use

43. The mapping to integration technologies / services highly depends on your specific customer context. This slide shows some sample factors that might need to be evaluated or considered in your organization. The listed factors can be adapted/extended to your specific needs. How To Use Integration Domains Integration Styles Technology Mapping Integration Technology Mapping Customer Context Industry & Business Requirements Existing & Future Application Landscape IT / Enterprise Architecture Strategy Existing Investments Preestablished integration Existing Skillsets …

44. Integration Domains Integration Styles Technology Mapping Integration Technology Mapping Recommendation Degrees Recommendation Degree Description General Recommendation Assign this degree to your default recommendation for a specific integration style and/or use case pattern, e.g. if you want to establish SAP Integration Suite as your company standard for hybrid or cloud integration scenarios. Reasonable Alternative Assign this degree to possible alternatives that are valid for specific integration scenarios, e.g. if you want to allow certain SAP-to-SAP scenarios to be implemented with a direct integration approach e.g. for migration purposes. Possible Exception Assign this degree to possible exceptions for your general recommendations that you would like to allow for restricted use cases, e.g. if you want to allow for some restricted scenarios file-based interfaces. To Be Avoided Assign this degree to explicitly cover integration techniques / approaches that you would not like to be further used for new integration scenarios, e.g. to phase out some non strategic integration technologies in you organization. ISA-M foresees various levels of recommendation degrees that you can assign to integration technologies / services in your organization. This allows you to define integration guidelines for your organization including default recommendations, reasonable alternatives, possible exceptions or techniques that you would like to avoid in your organization. The table below provides some further explanations. How To Use

45. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F In the next sections, decision table templates are provided per integration style (A to F) that allow you to define integration guidelines for your organization. This template also includes examples on how to map integration styles to technologies/services from the SAP portfolio (based on a typical hybrid landscape). The technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific customer context. Explanation Cross Use Cases C

46. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

47. Integration Domains Integration Styles Technology Mapping Process Integration Style Overview This section provides a decision table template that allows you to define integration guidelines for the process integration style for your organization including the highlighted integration domains. ISA-M is open to also include third party integration technologies/services. The ISA-M template also includes examples on how to map this integration style to sample technologies/services from the SAP portfolio. Where applicable, we have also added references to the Integration Architecture Guide for Cloud and Hybrid Landscapes or links to other documents where you will find more information. Important Note: The sample technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific context and requirements. SAP also provides consulting services in case you need further support. How To Use On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

48. 1 Integration Domain(s) and Integration Style 44 Integration Domains Integration Styles Technology Mapping Process Integration Style Sample Technology Mapping SAP Integration Suite SAP’s IPaaS for cloud and hybrid integration Prepackaged integration content for SAP and third party apps Integration Advisor capability ( s implified integration supported by Artificial Intelligence ) Trading Partner Management capability ( manage B2B relationships with multiple trading partners ) Open Connectors capability (+160 pre-built connectors for third party apps) Complementary: SAP Process Orchestration and SAP Application Interface Framework (AIF) Key Characteristics A2A, Master Data Integration, B2B, B2G integration use cases API-based integration and near real-time processing Transactional process integrity 2 Sample Mapping to SAP Technologies / Services On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

49. Integration Domains Integration Styles Technology Mapping Process Integration Style Decision Table Template Integration Guidelines Integration Technology / Service Sample Values: 1) Cloud Integration capability within SAP Integration Suite 2) SAP Process Orchestration 3) SAP Application Interface Framework 4) Third party … Recommendation Degree Sample Values: 1) General Recommendation 2) Reasonable Alternative 3) Possible Exception 4) To be avoided … Description Optionally: refer to use case patterns Relevant Integration Domains OP2OP Cloud2OP Cloud2Cloud Cloud Integration capability within SAP Integration Suite General Recommendation Use whenever packaged integration content from SAP or SAP partners is available (see https://api.sap.com/discoverintegrations) or your custom build integration scenario requires mediation capabilities (such as mappings, routings, protocol conversions).   SAP Process Orchestration General Recommendation Use for on premise to on premise processes integration scenarios.  SAP Application Interface Framework General Recommendation Use whenever you want business users to monitor interfaces and to do error handling as part of a SAP S/4HANA or SAP ERP (as optional add-on).   … … … This table allows you to define integration guidelines for the process integration style for your organization. Per row, you can add one integration guideline: In column 1 , you can select the relevant integration technology/service for which you want to define the guideline (e.g. Cloud Integration capability of SAP Integration Suite). In column 2 , you can define the recommendation degree that you would like to assign to the integration technology/service within your organization (e.g. General Recommendation). In column 3 , you can further describe your integration guideline, optionally by referring to the relevant use case patterns. Column 4 allows you to assign the integration technology/service to the relevant integration domain(s), e.g. Cloud2OnPremise or Cloud2Cloud. Please adjust the decision template to your specific needs. Important Note: The sample technology mappings shown in the table above are only illustrative examples that need to be aligned with your specific context and requirements. Also the inclusion of third party integration technologies / services is possible. How To Use

50. Process Integration Style SAP Integration Suite SAP Integration Suite is a modular Enterprise Integration Platform as-a-Service solution for cloud-to-cloud and cloud-to-on premise integration use cases, covering both SAP and third party applications. Together with SAP integration software it can form a customer’s hybrid integration platform. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes Explanation Integration Domains Integration Styles Technology Mapping

51. Integration Domains Integration Styles Technology Mapping Process Integration Style SAP Integration Suite & SAP Process Orchestration SAP Integration Suite builds the foundation of SAP’s integration strategy for supporting A2A, Master Data Integration, B2B, and B2G use cases. When using SAP Process Orchestration please explore options for transitioning to SAP Integration Suite . Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation

52. Integration Domains Integration Styles Technology Mapping Process Integration Style Cloud Integration capability of SAP Integration Suite & SAP Process Orchestration Comparison of the Cloud Integration capability of SAP Integration Suite and SAP Process Integration. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . How To Use   Cloud Integration capability within SAP Integration Suite SAP Process Orchestration Deployment • Data centers owned and run by SAP or SAP partners, for example, Microsoft Corporation, Amazon.com Inc, or Alibaba Group • Fully vendor-managed multi-cloud in major hyperscale environments • Customer landscape • Private cloud • Customer-managed in hyperscale environments Operations* SAP Customer License model Monthly subscription fee, pay per use Product license Architecture • Multitenancy with data isolation • Virtualization with automated failover • Rolling software updates • Single-tenant solution • Failover to be configured by customer • Near-zero downtime maintenance for updates through support packages or enhancement packages Prepackaged integration content Availability for a wide variety of cloud solutions from SAP, third-party applications, and business-to-business and business-to-government scenarios • Availability for a wide variety of on-premise SAP® software and third-party software • Runtime of the Cloud Integration capabilities of the suite (starting from SAP Process Orchestration software, release 7.5) for reuse of cloud integration content Preferred integration domains • Cloud to cloud • On premise to cloud (for customers with a cloud focus) • On premise to on premise • On premise to cloud (for customers with an on-premise focus), however recommends moving hybrid integration scenarios to SAP Integration Suite Decision criteria • Center of gravity – deployment of most or leading applications – in the cloud • No need to invest in on-premise middleware* (i nstallation, operation, upgrades) • Fast innovation cycle • Flexible license model • Scenarios with a need for compliance, such as e-invoicing / payroll, to integrate with legal authorities • Center of gravity – deployment of most or leading applications – on premise • Interest in leveraging an existing investment in SAP Process Orchestration • Customer interest in having full control over integration (installation, operation, upgrades) * including maintenance, updates, upgrades

53. Integration Domains Integration Styles Technology Mapping Process Integration Style SAP Master Data Integration SAP Master Data Integration service introduces a hub and spoke mechanism in cloud for exchanging and synchronizing master data. This service enables an out-of-the box integration for SAP-to-SAP integration scenarios exchanging semantically aligned data (based on SAP One Domain Model). Customers and third party applications can access the service through the Cloud Integration capability within SAP Integration Suite. Check out the SAP Road Map Explorer regarding the planned availability dates of supported master data objects and scenarios. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation Customer and third party applications Exposure through SAP Integration Suite (Ready integrated) SAP applications SAP Master Data Integration service Change API (inbound) Distributed and scalable master data event log Log API (outbound) Change requests using SAP One Domain Model object representation) Change event notification (using SAP One Domain Model object representation)

54. Process Integration Style SAP Master Data Integration & SAP Master Data Governance Integration Domains Integration Styles Technology Mapping SAP Master Data Governance is still the recommended solution for master data management and can interact through the SAP Master Data Integration service. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes Explanation

55. Integration Domains Integration Styles Technology Mapping Process Integration Style Simplification: Evolution of SAP Integration Content SAP applications can synchronize business objects with common attributes and use common semantics, which reduces SAP-to-SAP integration efforts for customers: New implementations can take advantage of SAP Master Data Integration for scenarios for which SAP has delivered aligned domain models. SAP Integration Suite supports both types of integration scenarios – those for unaligned as well as aligned APIs Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes .. Explanation

56. Integration Domains Integration Styles Technology Mapping Process Integration Style SAP Application Interface Framework (AIF) SAP Application Interface Framework (AIF) complements SAP Integration Suite and SAP Process Orchestration with a deep integration capability into the application layer of SAP S/4HANA or SAP Business Suite. Among others, it provides monitoring and error handling for business users. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation Integration Layer Application Layer SAP S/4HANA or SAP Business S uite SAP Application Interface Framework API Layer Standard Applications Interface Customizing (e.g. Data Validation, Value Mapping) Monitoring & Error Handling (Forward Error Correction) Alert Management Application Log Security / Authorizations Custom Functions Data SAP Functions Integration Developer Business User SAP Integration Suite On-Premise Applications Cloud Applications B2B / B2G SAP Process Orchestration On-Premise Applications Cloud Applications B2B / B2G …

57. Integration Domains Integration Styles Technology Mapping Process Integration Style Sample Key Characteristics – Integration and Application Layer A key question for integration architects is which patterns to implement in the integration layer and which patterns to implement in the application layer. This slide lists some typical patterns and their best practices and can be extended/adapted to capture best practices in your organization. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation Sample key characteristics

58. 54 Integration Domains Integration Styles Technology Mapping Process Integration Style Further Information Resource Link Description Integration Architecture Guide for Cloud and Hybrid Landscapes Link This guide follows the concepts of ISA-M and provides detailed guidance regarding SAP integration technologies for process integration such as SAP Integration Suite, SAP Process Orchestration and SAP Application Interface Framework. In addition, it includes guidance for customers migrating from SAP Business Suite to SAP S/4HANA with regards to integration topics such as transition paths. SAP API Business Hub Link Discover and consume digital content packages with APIs, pre-packaged integrations, business process models and sample apps from SAP and select partners. Beside APIs, the SAP API Business Hub provides the central place for pre-packaged integration content for SAP Integration Suite (Cloud Integration capability) that is available for integration of the various SAP applications like SAP S/4HANA, SAP SuccessFactors, SAP Fieldglass, SAP Customer Experience to integrate with SAP and also third party applications. SAP Integration Suite Link SAP’s Integration Platform-as-a-Service (IPaaS): It simplifies integration by connecting people, processes, data, and devices everywhere by allowing people with different skills to leverage a wide variety of integration approaches, intuitive tools, and prepackaged content to achieve results faster and gain business agility with a versatile, dynamic, and enterprise-grade cloud integration platform. SAP Process Orchestration Link SAP’s on-premise integration platform: Model, implement, integrate, and monitor custom process applications and integration scenarios, quickly and flexibly. SAP Application Interface Framework Link Implement, monitor, and manage application interfaces from a central location within SAP S/4HANA or SAP Business Suite to simplify interface handling across your system landscape. SAP Activate Roadmap Viewer Link Provides access to SAP Activate methodology implementation roadmaps for SAP solutions. These offer a comprehensive view of associated activities, deliverables, and tasks with accompanying accelerator assets which also covers integration aspects. Interactive SAP Roadmap Explorer Link Search for a SAP integration technology to find its planned innovations. To find information about planned integration scenarios select a product, process or industry, choose “More Filters” -> Focus Topics -> “Integration”. This slides provides links where you can find further information such as additional guidance, product information and roadmaps. How To Use

59. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

60. Integration Domains Integration Styles Technology Mapping Data Integration Style Overview This section provides a decision table template that allows you to define integration guidelines for the data integration style for your organization including the highlighted integration domains. ISA-M is open to also include third-party integration technologies/services. The ISA-M template also includes examples on how to map this integration style to sample technologies/services from the SAP portfolio. Where applicable, we have also added references to the Integration Architecture Guide for Cloud and Hybrid Landscapes or links to other documents where you will find more information. Important Note: The sample technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific context and requirements. SAP also provides consulting services in case you need further support. How To Use On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

61. 1 Integration Domain(s) and Integration Style Integration Domains Integration Styles Technology Mapping Data Integration Style Sample Technology Mapping 2 Sample Mapping to SAP Technologies / Services SAP Data Intelligence Comprehensive data management solution that governs, integrates, processes, and orchestrates the volume, velocity, and variety of data across hybrid landscapes Cloud, private cloud and on premise deployment option Pipelining and orchestration of big data Leverages SAP EIM tools, e.g. SAP HANA Smart Data Integration (SDI) or SAP Data Services (DS) Key Characteristics Support of multiple data integration use cases Data focused (table/view, storages, processing, libraries) High frequent event processing (e.g. via Kafka) Advanced data transformations & processing (e.g. ML) On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

62. Integration Domains Integration Styles Technology Mapping Data Integration Style Decision Table Template Integration Guidelines Integration Technology / Service Sample Values: 1) SAP Data Intelligence 2) SAP HANA Smart Data Integration 3) SAP Data Services 4) Third party … Recommendation Degree Sample Values: 1) General Recommendation 2) Reasonable Alternative 3) Possible Exception 4) To be avoided … Description Optionally: refer to use case patterns Relevant Integration Domains OP2OP Cloud2OP Cloud2Cloud SAP Data Intelligence General Recommendation Use for data integration needs with option to reuse existing SAP data integration products to orchestrate in a pipeline.   SAP HANA Smart Data Integration General Recommendation Use to move data from Non-ABAP sources into SAP HANA.   SAP Data Services General Recommendation Use for moving, integrating or cleansing structured data in on premise landscapes, with high transformation needs.  … … … This table allows you to define integration guidelines for the data integration style for your organization. Per row, you can add one integration guideline: In column 1 , you can select the relevant integration technology/service for which you want to define the guideline (e.g. SAP Data Intelligence ). In column 2 , you can define the recommendation degree that you would like to assign to the integration technology/service within your organization (e.g. General Recommendation). In column 3 , you can further describe your integration guideline, optionally by referring to the relevant use case patterns. Column 4 allows you to assign the integration technology/service to the relevant integration domain(s), e.g. Cloud2OnPremise or Cloud2Cloud. Important Note: The sample technology mappings shown in the table above are only illustrative examples that need to be aligned with your specific context and requirements. Also the inclusion of third-party integration technologies / services is possible. How To Use

63. Data Integration Style SAP Data Intelligence Integration Domains Integration Styles Technology Mapping The SAP Data Intelligence solution is a comprehensive data management solution that governs, integrates, processes, and orchestrates the volume, velocity, and variety of data in on-premise, cloud, multi-cloud, and hybrid distributed system landscapes. It is SAP’s strategic data management solution and the tool of choice, in particular for cloud and hybrid data integration, metadata management, and data processing needs. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation

64. Data Integration Style SAP Solutions for Enterprise Information and Data Management Integration Domains Integration Styles Technology Mapping SAP understands that customers have made significant investments in SAP solutions for enterprise information management and SAP Database and Data Management solutions and strives to help them protect those investments. All existing solutions are integrated with SAP Data Intelligence in the best way whenever it makes sense from a business and technology standpoint, for example, to establish additional connectivity to new target systems. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation

65. Data Integration Style Mapping of Use Case Pattern to SAP EIM & DM Solutions Integration Domains Integration Styles Technology Mapping Recommended technologies for the use case patterns data replication (ETL), data virtualization, data quality management, and data orchestration Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation

66. Integration Domains Integration Styles Technology Mapping Technology Guidance Cloud Integration capability within SAP Integration Suite and SAP Data Intelligence

67. Integration Domains Integration Styles Technology Mapping Data Integration Style Further Information Resource Link Description SAP Data Intelligence Link The SAP Data Intelligence solution is a comprehensive data management solution that governs, integrates, processes, and orchestrates the volume, velocity, and variety of data in on-premise, cloud, multi-cloud, and hybrid distributed system landscapes. It is SAP’s strategic data management solution and the tool of choice, in particular for cloud and hybrid data integration, metadata management, and data processing needs. SAP HANA Smart Data Integration (SDI), SAP HANA Smart Data Access (SDA) , S AP HANA Smart Data Quality (SDQ) Link All are part of the SAP HANA platform: SDI is a log-based, real-time data replication tool with transformation capabilities. Its focus is to move data from non-ABAP sources into SAP HANA. SDA enables remote data to be accessed as if it were stored in local tables in SAP HANA, without copying the data into SAP HANA. SDQ is a set of functionality provided by several components, which you can use to cleanse and enrich data. SAP Data Services Link Software to integrate, transform, improve, and load accurate and complete data to support operational and analytical data-driven initiatives. SAP Cloud Integration for data services Link Cloud-based data integration tool for batch data integration between on-premise application and cloud applications SAP Landscape Transformation Replication Server Link A trigger-based real-time data replication product with basic transformation capabilities. Its focus is to move high volumes of data from ABAP and non-ABAP systems into SAP HANA or any ABAP-based system. SAP Information Steward Link Software that provides data stewards and IT users with a single environment to discover, assess, define, monitor, and improve the quality of their enterprise data and metadata. Interactive SAP Roadmap Explorer Link Search for a SAP integration technology to find its planned innovations. To find information about planned integration scenarios select a product, process or industry, choose “More Filters” -> Focus Topics -> “Integration”. This slides provides links where you can find further information such as additional guidance, product information and roadmaps. How To Use

68. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

69. Integration Domains Integration Styles Technology Mapping Analytics Integration Style Overview This section provides a decision table template that allows you to define integration guidelines for the analytics integration style for your organization including the highlighted integration domains. For the embedded analytics use case the cloud applications have also been highlighted. ISA-M is open to also include third party integration technologies/services. The ISA-M template also includes examples on how to map this integration style to sample technologies/services from the SAP portfolio. Important Note: The sample technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific context and requirements. SAP also provides consulting services in case you need further support. How To Use On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

70. 1 Integration Domain(s) and Integration Style Integration Domains Integration Styles Technology Mapping Analytics Integration Style Sample Technology Mapping 2 Sample Mapping to SAP Technologies / Services SAP Analytics Cloud* Enterprise BI solution supporting augmented analytics, predictive analytics, and enterprise planning Live connection (online) and data acquisition (batch) support Pre-built industry and line-of-business content SAP Data Warehouse Cloud Data management and decision-making cloud solution also enabling cross application analytics. Integrates with SAP LoB solutions, SAP Business Technology Platform services, partner solutions and open-source technologies. Complementary: SAP BW/4HANA with native integration to SAP Data Warehouse Cloud Key Characteristics Integration of local and remote data sources Model management Predictive and planning capabilities** *Also available: SAP Analytics Cloud, embedded edition, supporting the embedded analytics use case (cloud only). **Available with SAP Analytics Cloud Enterprise Edition. On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

71. Integration Domains Integration Styles Technology Mapping Analytics Integration Style Decision Table Template Integration Guidelines Integration Technology / Service Sample Values: 1) SAP Analytics Cloud 2) SAP Analytics Cloud, embedded edition 3) SAP Data Warehouse Cloud 4) Third party … Recommendation Degree Sample Values: 1) General Recommendation 2) Reasonable Alternative 3) Possible Exception 4) To be avoided … Description Optionally: refer to use case patterns Relevant Integration Domains User2OnPremise User2Cloud SAP Analytics Cloud General Recommendation For enterprise business intelligence, augmented analytics, predictive analytics, and enterprise planning (cross application analytics).   SAP Data Warehouse Cloud General Recommendation Data management and decision-making cloud solution enabling cross application analytics.   … … … This table allows you to define integration guidelines for the analytics integration style for your organization. Per row, you can add one integration guideline: In column 1 , you can select the relevant integration technology/service for which you want to define the guideline (e.g. SAP Analytics Cloud). In column 2 , you can define the recommendation degree that you would like to assign to the integration technology/service within your organization (e.g. General Recommendation). In column 3 , you can further describe your integration guideline, optionally by referring to the relevant use case patterns. Column 4 allows you to assign the integration technology/service to the relevant integration domain(s), e.g. User2Cloud or User2OnPremise. Important Note: The sample technology mappings shown in the table above are only illustrative examples that need to be aligned with your specific context and requirements. Also the inclusion of third party integration technologies / services is possible. How To Use

72. Analytics Integration Style SAP Analytics Cloud and SAP Data Warehouse Cloud SAP Data Warehouse Cloud and SAP Analytics Cloud are automatically integrated with each other. All three solutions provide connectivity to SAP and third party systems, both in the cloud and on premise, to access data with or without replication. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation Integration Domains Integration Styles Technology Mapping

73. Analytics Integration Style SAP Analytics Cloud and SAP Data Warehouse Cloud Embedded analytics is realized by embedding SAP Analytics Cloud into business applications using direct live access to primary data. Cross application analytics can be implemented in three different ways: Query b lending using SAP Analytics Cloud, data federation or data consolidation leveraging also SAP Data Warehouse Cloud. Further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes Integration Domains Integration Styles Technology Mapping Data Source Single LoB using live data access Multiple LoBs Federated live data models to LoBs, SAP and third party data sources Consolidated (and cross-LoB) models with periodic data extraction (w/ delta) Product Embedded SAP Analytics Cloud SAP Analytics Cloud SAP Analytics Cloud + SAP Data Warehouse Cloud SAP Analytics Cloud + SAP Data Warehouse Cloud Cross Analytics N/A Cross Analytics via filtering and navigation on linked dimensions Cross Analytics bulit into federated view modeling Cross Analytics built into consolidated data modeling Example Embedded analytics in SAP S/4HANA Cloud Touchpoint NPS in Sales and Service Financial analytics dashboard for SAC (also known as CFO dashboard ) Content: financial analytics dashboad for SAC (also known as CFO dashboard Cross Application Analytics & Planning Embedded Analytics Explanation * Restrictions may apply depending on source system type and use case

74. Analytics Integration Style Innovation Journeys for SAP BW Customers Integration Domains Integration Styles Technology Mapping SAP Data Warehouse Cloud, SAP BW bridge enables the transition to SAP Data Warehouse Cloud with the help of SAP BW-based data integration & staging with tool-supported move*. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation SAP Data Warehouse Cloud SAP BW bridge SAP BW/4HANA & Data Warehouse Cloud Hybrid Combine the strengths of SAP BW/4HANA with the innovation, openness , and self-service abilities of SAP Data Warehouse Cloud in a hybrid scenario SAP Data Warehouse Cloud, SAP BW bridge Re-use and integrate SAP BW-based data ingestion and staging (incl. ABAP code) in SAP Data Warehouse Cloud (tool-supported move*) SAP BW 7.X SAP BW 7.X SAP BW & BW/4HANA Cloud Private Edition 1 SAP Data Warehouse Cloud SAP BW & BW/4HANA Cloud Safe-guard investments by lifting existing landscape to the cloud – “RISE with SAP” SAP BW 7.X SAP BW & BW/4HANA Cloud Private Edition 1 * Check SAP Data Warehouse Cloud Roadmap rgd. plannned availability and features. 1   SAP BW/4HANA is fully supported until 2040 and can also be deployed on-premises if desired.

75. Integration Domains Integration Styles Technology Mapping Analytics Integration Use Cases Further Information Resource Link Description SAP Analytics - Business Intelligence, Statement of Direction Link Statement of direction regarding the SAP Analytics products such as SAP Analytics Cloud, SAP Business Objects BI Suite – including FAQ. SAP Analytics Cloud Link End-to-end SaaS solution that delivers all the analytics capabilities such as business intelligence, enterprise planning and augmented analytics. SAP Analytics Cloud, embedded edition Link Reusable business service for business intelligence (BI) on the SAP Business Technology Platform SAP Digital Boardroom Link Solution to design a real-time, interactive boardroom presentations based on SAP Analytics Cloud. SAP Data Warehouse Cloud Link Enterprise-ready data warehouse in the cloud that runs in multicloud environment, targeting different personas with different levels of technical expertise (IT, line of business / functional users and developers) SAP Data Warehouse Cloud, SAP BW Bridge Link SAP BW bridge is a function enhancement of SAP Data Warehouse Cloud. It allows customers who are running a SAP Business Warehouse or SAP BW/4HANA to reuse their existing models, transformations, and customizations in SAP Data Warehouse Cloud. SAP Product Roadmaps Link Access all product and solution roadmaps from SAP. You will also find latest roadmaps on all integration technologies and services mentioned in ISA-M. This slides provides links where you can find further information such as additional guidance, product information and roadmaps. How To Use

76. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

77. Integration Domains Integration Styles Technology Mapping User Integration Style Overview This section provides a decision table template that allows you to define integration guidelines for the user integration style for your organization including the highlighted integration domains. ISA-M is open to also include third-party integration technologies/services. The ISA-M template also includes examples on how to map this integration style to sample technologies/services from the SAP portfolio. Important Note: The sample technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific context and requirements. SAP also provides consulting services in case you need further support. How To Use On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

78. 1 Integration Domain(s) and Integration Style Integration Domains Integration Styles Technology Mapping User Integration Style Sample Technology Mapping: UI Integration 2 Sample Mapping to SAP Technologies / Services SAP Launchpad service Central point of access to cloud and on premise applications, tasks, and processes Common UX integration for SAP solutions (for example, SAP S/4HANA), custom apps and extensions following the SAP Fiori design guideline SAP Work Zone For branded digital workplaces with guided experiences, web content, document access, knowledge base and workspaces for collaborative knowledge sharing Offers workspaces, forums, document access, web content widgets, and MS Teams integration, Lines of Business specific content packages (e.g. SAP SuccessFactors´Work Zone) SAP Mobile Start Native app that serves as the mobile entry point to SAP’s integrated Intelligent Suite Native mobile version of the SAP Launchpad service that allows access to native or web-responsive (such as SAPUI5) business apps, data, and information SAP Mobile Services Development platform for enterprise mobile apps SDKs available for multiple devices (e.g. iOS, Android) Key Characteristics Role-based access Single sign on Session management Online / offline support (for mobile) On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

79. Integration Domains Integration Styles Technology Mapping User Integration Style Decision Table Template Integration Guidelines Integration Technology / Service Sample Values: 1) SAP Launchpad service 2) SAP Work Zone 3) SAP Mobile Services 4) Third Party … Recommendation Degree Sample Values: 1) General Recommendation 2) Reasonable Alternative 3) Possible Exception 4) To be avoided … Description Optionally: refer to use case patterns Relevant Integration Domains User2OnPremise User2Cloud SAP Launchpad service General Recommendation Central point of access to cloud and on premise applications, tasks, and processes   SAP Work Zone General Recommendation For branded digital workplaces with guided experiences, web content, document access, knowledge base and workspaces for collaborative knowledge sharing.   SAP Mobile Services General Recommendation Use to develop mobile apps (e.g. iOS and Android apps) and integrate them with backend applications (relates to the Mobile Integration use case pattern).   … … … This table allows you to define integration guidelines for the user integration style for your organization. Per row, you can add one integration guideline: In column 1 , you can select the relevant integration technology/service for which you want to define the guideline (e.g. SAP Launchpad service. In column 2 , you can define the recommendation degree that you would like to assign to the integration technology/service within your organization (e.g. General Recommendation). In column 3 , you can further describe your integration guideline, optionally by referring to the relevant use case patterns. Column 4 allows you to assign the integration technology/service to the relevant integration domain(s), e.g. User2Cloud or User2OnPremise. Important Note: The sample technology mappings shown in the table above are only illustrative examples that need to be aligned with your specific context and requirements. Also the inclusion of third party integration technologies / services is possible. How To Use *Check out product road map regarding supported applications.

80. User Integration Style SAP Launchpad service SAP Launchpad service provides SAP Fiori launchpad experience in the cloud, including related UX services such as branding, tasks, notifications and secure single sign-on.. Source and further Information: SAP Fiori Deployment Options and System Landscape Recommendations Explanation Integration Domains Integration Styles Technology Mapping

81. User Integration Style SAP Launchpad service and SAP Work Zone Integration Domains Integration Styles Technology Mapping SAP Work Zone extends the SAP Launchpad service with additional capabilities, such as: workspaces, end & key user content creation, knowledge base, web and document management, lean-collaboration capabilities, Lines of Businesses specific content packages (example: SuccessFactors Work Zone) Source and further Information Blog post SAP Portal, SAP Launchpad Service and SAP Work Zone Explanation UI Integration & Secure Access Business & Key User Authoring Personalized & role-based Experience Workspaces & Guided Experiences Knowledge & (Web) Content Management Customization & Extensibility SAP Launchpad service (foundation) SAP Work Zone (premium capabilities) Mobile experience: SAP Mobile Start / Work Zone Mobile Desktop (web) experience Business (Key) users Content Managers & Administrators (Citizen) Developers Content packages by LoB / Industries

82. Integration Domains Integration Styles Technology Mapping User Integration Style Further Information Resource Link Description SAP Launchpad service Link Establish a central point of access to SAP (e.g. SAP S/4HANA), custom-built, and third party applications and extensions, both on the cloud and on premise. SAP Work Zone Link For building digital workplace solutions with a centralized access to relevant business applications, processes, information, and communication. SAP Fiori Deployment Options and System Landscape Recommendations Link In this document, you can find the main SAP Fiori scenarios, the recommended system landscape setup, and the SAP Front-end server deployment options. This document also includes insights into SAP Fiori front-end server hub and embedded deployment and what aspects to consider. The FAQ section provides answers to common questions regarding the SAP Fiori deployment options. Relates to the “UI Integration” use case pattern. SAP Mobile Services Link Create and run native, hybrid and micro mobile apps with a mobile app development platform (Enterprise iOS and Android apps). Secure access to on-premise or cloud-based data sources, data-access features and offline OData synchronization. Relates to the “Mobile Integration” use case pattern. SAP Conversational AI Link Build enterprise-grade chatbots leveraging an end-to-end bot building platform as well as a digital assistant. Interactive SAP Roadmap Explorer Link Search for a SAP integration technology to find its planned innovations. To find information about planned integration scenarios select a product, process or industry, choose “More Filters” -> Focus Topics -> “Integration”. This slides provides links where you can find further information such as additional guidance, product information and roadmaps. How To Use

83. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

84. Integration Domains Integration Styles Technology Mapping Thing Integration Style Overview This section provides a decision table template that allows you to define integration guidelines for the thing integration style for your organization including the highlighted integration domains. ISA-M is open to also include third-party integration technologies/services. The ISA-M template also includes examples on how to map this integration style to sample technologies/services from the SAP portfolio. Important Note: The sample technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific context and requirements. SAP also provides consulting services in case you need further support. How To Use On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

85. 1 Integration Domain(s) and Integration Style Integration Domains Integration Styles Technology Mapping Thing Integration Style Sample Technology Mapping 2 Sample Mapping to SAP Technologies / Services SAP Internet of Things Embed IoT in business processes and industry applications to gain insights from previously unconnected devices Automate supply chains by leveraging auto ID technology Enable low latency, autonomous operations and cloud-based orchestration for mission-critical processes at the industrial edge Gain insights on the performance of industrial business processes in the factory and beyond, while overseeing asset availability, usage, and health Complementary: SAP Plant Connectivity Key Characteristics Onboarding and device management IoT specific protocol support (e.g. REST, MQTT, OPC-UA) Data ingestion, big data storage and time series management Edge-level ingestion, storage, and processing capabilities On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

86. Integration Domains Integration Styles Technology Mapping Thing Integration Style Decision Table Template Integration Guidelines Integration Technology / Service Sample Values: 1) SAP Internet of Things 2) SAP Plant Connectivity 4) Third party … Recommendation Degree Sample Values: 1) General Recommendation 2) Reasonable Alternative 3) Possible Exception 4) To be avoided … Description Optionally: refer to use case patterns Relevant Integration Domains Thing2OP Thing2Cloud SAP Internet of Things General Recommendation Solutions to extend existing SAP business processes by gaining information and insights from previously unconnected devices (e.g. machines, products, assets), thereby extending the value of existing SAP applications and processes.   SAP Plant Connectivity General Recommendation Software component to exchange of data between an SAP system and the industry-specific standard data sources of different manufacturers, for example, process control systems, plant Historian systems, and SPC systems   … This table allows you to define integration guidelines for the thing integration style for your organization. Per row, you can add one integration guideline: In column 1 , you can select the relevant integration technology/service for which you want to define the guideline (e.g. SAP Internet of Things). In column 2 , you can define the recommendation degree that you would like to assign to the integration technology/service within your organization (e.g. General Recommendation). In column 3 , you can further describe your integration guideline, optionally by referring to the relevant use case patterns. Column 4 allows you to assign the integration technology/service to the relevant integration domain(s), e.g. Thing2Cloud or Thing2OnPremise. Important Note: The sample technology mappings shown in the table above are only illustrative examples that need to be aligned with your specific context and requirements. Also the inclusion of third-party integration technologies / services is possible. How To Use

87. Thing Integration Style SAP I nternet of Things: Building Blocks and Process Flow SAP Internet of Things comprises three main capabilities in the cloud: IoT data management, modeling, and data processing, smart sensing based on auto-ID technology, analytics and intelligence. These building blocks are complemented by the “intelligent edge.” The intelligent edge includes capabilities to ingest and process IoT data and auto-ID events, which form part of SAP IoT, machine orchestration with SAP Plant Connectivity software, and the SAP Digital Manufacturing Cloud solution for edge computing. They provide the needed integration technology to embed IoT insights into SAP Digital Supply Chain solutions and SAP S/4HANA applications to enable data-driven business processes. Source and further Information: SAP Internet of Things Explanation Integration Domains Integration Styles Technology Mapping

88. This table provides links where you can find further information such as refined guidance, product information and roadmaps. How To Use Integration Domains Integration Styles Technology Mapping Thing Integration Style Further Information Resource Link Description SAP Internet of Things Link A complete set of microservices designed to build powerful apps and leverage data storage to deliver real-time insights. Industry 4.0 Link Entry page about SAP’s vision and portfolio for industry 4.0 which includes IoT applications and technologies. SAP Plant Connectivity Link Connect your machines to solutions such as SAP MII, manufacturing execution systems (MES), SAP EWM, and more. Deliver Industrial Internet of Things (IIoT) and machine-to-machine (M2M) connectivity to your business. Interactive SAP Roadmap Explorer Link Search for a SAP integration technology to find its planned innovations. To find information about planned integration scenarios select a product, process or industry, choose “More Filters” -> Focus Topics -> “Integration”.

89. Integration Technology Mapping Derive Integration Guidelines for Your Organization Integration Domains Integration Styles Technology Mapping Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

90. Integration Domains Integration Styles Technology Mapping Cross Use Cases Overview Cross Use Cases build a category for all use case patterns that complement one ore more of the five core integration styles. For example, API-Managed Integration provides full-lifecycle management for APIs that, e.g. can be leveraged in user- or process-centric integration scenarios. Workflow Management is an other example for a cross use case as it can spawn across process-, user- and data-centric integration scenarios. It also includes all other integration-related use cases such as business rules management or stream analytics. This section provides a decision table template that allows you to define integration guidelines for the cross use case category for your organization including the highlighted integration domains. ISA-M is open to also include third-party integration technologies/services. The ISA-M template also includes examples on how to map cross use cases to sample technologies/services from the SAP portfolio. Important Note: The sample technology mappings given in the next slides are only illustrative examples that need to be aligned with your specific context and requirements. SAP also provides consulting services in case you need further support. How To Use On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

91. 1 Integration Domain(s) and Integration Style Integration Domains Integration Styles Technology Mapping Cross Use Cases Sample Technology Mapping: API Managed Integration 2 Sample Mapping to SAP Technologies / Services API Management Capability within SAP Integration Suite Provides full lifecycle management for APIs Can be used in multiple integration domains and styles Examples Omnichannel access and mobile Open real-time B2B Integration Data access governance and monetization Key Characteristics API traffic management policies API security policies API analytics and monetization On-Premise Cloud Cloud2OnPremise Real World Objects User2OnPremise User2Cloud Thing2OnPremise Thing2Cloud Cloud2 Cloud User-Centric Applications S/4 C/4 X … Non SAP Cloud Apps S/4HANA Business Suite Non SAP Applications OnPremise2 OnPremise Private Cloud Business Partner Government Agency Analytics Integration Data Integration User Integration Thing Integration Process Integration Cross Use Cases

92. Integration Domains Integration Styles Technology Mapping Cross Use Cases Decision Table Template Integration Guidelines Integration Technology / Service Sample Values: 1) API Management capability of SAP Integration Suite 2) SAP Event Mesh 3) Third party … Recommendation Degree Sample Values: 1) General Recommendation 2) Reasonable Alternative 3) Possible Exception 4) To be avoided … Description Optionally: refer to use case patterns Relevant Integration Domains User2OP User2Cloud OP2OP OP2Cloud Cloud2Cloud API Management capability within SAP Integration Suite General Recommendation Use whenever you want to actively manage SOAP, OData or REST based APIs and/or like to enforce policies on the consumption of these APIs (such as security, traffic management, analytics and metering).      SAP Event Mesh General Recommendation Use to communicate in near real-time through asynchronous business events (list of SAP delivered business events: https://api.sap.com/content-type/Events/events/packages). Use together with SAP NetWeaver Add-On for Event Enablement for non-standard, custom business events.    … This table allows you to define integration guidelines for the cross use cases category for your organization. Per row, you can add one integration guideline: In column 1 , you can select the relevant integration technology/service for which you want to define the guideline (e.g. API Management). In column 2 , you can define the recommendation degree that you would like to assign to the integration technology/service within your organization (e.g. General Recommendation). In column 3 , you can further describe your integration guideline, optionally by referring to the relevant use case patterns. Column 4 allows you to assign the integration technology/service to the relevant integration domain(s), e.g. User2Cloud or Cloud2Cloud. Important Note: The sample technology mappings shown in the table above are only illustrative examples that need to be aligned with your specific context and requirements. Also the inclusion of third-party integration technologies / services is possible. How To Use

93. Integration Domains Integration Styles Technology Mapping Cross Use Cases Example: API Management capability of SAP Integration Suite The API Management capability of SAP Integration Suite provides a solution for the full lifecycle management of APIs. It enables use cases like omnichannel access, open real-time B2B Integration or data access governance and monetization. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes . Explanation

94. Cross Use Cases Sample Key Characteristics – API Management and Integration Layer Integration Domains Integration Styles Technology Mapping This slide shows some typical API policies and integration patterns that are best implemented in the API management layer or the integration layer. It provides guidance for integration architects on how to combine both offerings and can be extended/adapted to capture best practices in your organization. Source and further Information: Integration Architecture Guide for Cloud and Hybrid Landscapes Explanation

95. Integration Domains Integration Styles Technology Mapping Cross Use Cases Further Information Resource Link Description Integration Architecture Guide for Cloud and Hybrid Landscapes Link This guide follows the concepts of ISA-M and provides detailed guidance regarding SAP integration technologies. This also includes guidance on the complementary usage of the API Management. SAP Integration Suite Link SAP’s Integration Platform-as-a-Service (IPaaS): It simplifies integration by connecting people, processes, data, and devices everywhere by allowing people with different skills to leverage a wide variety of integration approaches, intuitive tools, and prepackaged content to achieve results faster and gain business agility with a versatile, dynamic, and enterprise-grade cloud integration platform. SAP Process Automation Link Citizen developer solution to adapt, improve, and innovate business processes with no-code workflow management and robotic process automation capabilities. SAP HANA Streaming Analytics Link Capture, analyze, and act on data streaming in from many sources with the highly scalable processing engine of SAP HANA. Digital Integration Hub Link The digital integration hub allows is a real-time digital access layer to insulate heterogenous transaction back ends using in-memory data grids and leveraging microservice-based architectures. This architecture enables a high-scale API-based access to system-of-record applications and data, while minimizing workload on these systems. Interactive SAP Roadmap Explorer Link Search for a SAP integration technology to find its planned innovations. To find information about planned integration scenarios select a product, process or industry, choose “More Filters” -> Focus Topics -> “Integration”. This slides provides links where you can find further information such as additional guidance, product information and roadmaps. How To Use

96. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

97. Interface Assessment Overview Interface Assessment User Integration Data Integration Thing Integration Cross Use Cases Process Integration A typical task in implementation projects is to blueprint integration scenarios between two applications. Typically, a business scenario is decomposed into technical interfaces. Next, each technical interface needs to be classified / assessed whether it is a process-, data-, analytics-, user- or thing-centric integration style. Based on the specific characteristics, the appropriate integration technology/service needs to be selected. ISA-M supports the classification of interfaces that will we shown on the next slides: in this example a business scenario is decomposed into three technical interfaces: Data Replication, A2A Integration, Mobile Integration. It is recommended to use the Integration Assessment capability within SAP Integration Suite for performing this task. How To Use Interface Decomposition Application 1 Application 2 Business Scenario Application 1 Application 2 ? ? Analytics Integration

98. Interface Assessment Sample Interface 2: A2A Integration Interface Assessment Integration Style & Use Case Pattern Matrix Analyze Business Scenario Identify Integration Style and Pattern Choose Integration Technology Option Integration Technology 1 Cloud Integration capability within SAP Integration Suite 2 … Decision Table * (Based on Customer Context) If not, decompose your business scenario into single interfaces for custom-built integration Business Scenario Application 1 Application 2 ? Cloud2OnPremise Domain If not, decompose your business scenario into single interfaces for custom-built integration Interface Decomposition Application 1 Application 2 1 3 A2A Integration 2 2

99. Interface Assessment Sample Interface 1: Data Orchestration Interface Assessment Integration Style & Use Case Pattern Matrix Analyze Business Scenario Identify Integration Style and Pattern Choose Integration Technology Option Integration Technology 1 SAP Data Intelligence 2 … Decision Table * (Based on Customer Context) If not, decompose your business scenario into single interfaces for custom-built integration Business Scenario Application 1 Application 2 ? Cloud2OnPremise Domain If not, decompose your business scenario into single interfaces for custom-built integration Interface Decomposition Application 1 Application 2 1 3 2

100. Interface Assessment Sample Interface 3: Mobile Integration Interface Assessment Integration Style & Use Case Pattern Matrix Analyze Business Scenario Identify Integration Style and Pattern Choose Integration Technology Option Integration Technology 1 SAP Mobile Services 2 … Decision Table * (Based on Customer Context) If not, decompose your business scenario into single interfaces for custom-built integration Business Scenario Application 1 Application 2 ? Cloud2OnPremise Domain Interface Decomposition Application 1 Application 2 3 Mobile Integration Mobile 1 2

101. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

102. ISA-M Cycle Phase 3: Define Integration Best Practices Objectives Govern and safeguard the implementation of integrations across your organization Achieve transparency about integration design and implementation Approach Define architecture blueprints for integration use case patterns complemented with decision criteria for choosing an architecture blueprint Define integration do’s and don’ts for common integration use cases or solutions Derive integration guidelines tailored to your organization’s technical and business requirements

103. Architecture Blueprints Overview Sample Architecture Blueprints B2B Integration Cloud2OnPremise UI Integration User2Cloud Event Based Integration Cloud2Cloud A2A Integration Cloud2OnPremise 1 4 7 A2A Integration Cloud2Cloud Data Orchestration Cloud2OnPremise UI Integration User2Cloud … 2 5 8 Master Data Integration OnPremise2OnPremise Embedded Analytics User2Cloud Digital Integration Hub Cloud2OnPremise/Cloud … 3 6 9 This slide shows sample architecture blueprints in regards of integration technologies. Architecture blueprints can be defined by combining integration use case patterns and integration domains. Choose the ones from the list of sample architecture blueprints which are relevant for your organization and define additional ones for your specific context as needed. How to Use Integration Domains I Integration Use Case Patterns 10

104. <Integration Style> <Integration Domain or Use Case Pattern> Public Cloud Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components Connectivity … Event Mesh Open Connectors API Management Smart Data Integration Cloud Integration SAP Data Intelligence … SAP Process Orchestration SAP Data Services Cloud Connector Firewall DMZ Firewall Firewall Architecture Blueprint Template Characteristics | Selection Criteria <Your defined content> Use this template for defining the architecture blueprints which are relevant for your organization. Reusing the SAP Business Technology Platform Solution Diagrams & Icons How To Use

105. Architecture Blueprint Samples Complemented with Integration Best Practices In this section, architecture blueprint samples for selected integration use case patterns are provided which are grouped per integration style. These are complemented with common integration do's and don’ts and a selection of characteristics/decision criteria. The architecture blueprints given in the next slides are only illustrative examples that need to be aligned with your specific customer context. Explanation Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

106. Process Integration - Architecture Blueprint Samples Complemented with Integration Best Practices Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

107. Process Integration General Integration Do’s and Don’ts Leverage integration packages (content) wherever possible Decoupling of applications via asynchronous messaging and events Usage of synchronous calls only in selected use cases Avoid direct integration (point-to point) and tight coupling of applications Prefer real-time distribution of data over batch oriented processes Avoid chaining as less as possible integration runtime components (operations, monitoring, …) Distribute integration logic and functionality in the most efficient way across the hybrid landscape … As part of an overall integration strategy, integration architects often define general integration guardrails / principles (what should be done – what should be avoided?). This slide contains some typical examples and needs to be adapted / extended to a specific customer context. How To Use

108. Process Integration Use Cases Decision Criteria Catalog - Legend Criteria / Capability Description Aligned APIs / Unaligned APIs Defines whether the sender and receiver application are using semantically and syntactically aligned APIs or not Pre-Packaged Content Availability of prepackaged content for a certain integration scenario (e.g. on SAP API Business Hub) Structure Mapping Maps message fields and hierarchies between two interfaces. Value Mapping Transforms field values that are exchanged between two applications Routing Used to determine, for a given message, a set of receivers based on static settings or message payload data Splitting / Aggregation Creates multiple messages out of a received message. Collects multiple inbound messages until a modelled threshold is reached. Protocol Mediation Covers the mediation between two different protocols used by sending and receiving applications (e.g. JMS, REST or SOAP). Exception Handling Technical capability to pick up and resolve errors during runtime Quality of Service Defines the QoS of the message transfer e.g. Exactly Once, Exactly Once in Order, Best Effort … … When defining a Hybrid Integration Platform (HIP), well defined decision criteria are required to select the appropriate integration services. This slide contains typical decision criteria that can be used in architecture blueprints. They have to be adapted/extended to a specific customer context. How To Use

109. Architecture Blueprint for the Process Integration Style Sample for A2A Integration (Cloud to On Premise) – Info Sheet Details Description Integration of on premise applications with cloud applications using a cloud based integration solution to enable business processes across an hybrid application landscape. The communication between the cloud based integration solution and the on premise application landscape and other cloud applications requires special security measures (e.g. via VPN, digital certificate based). The cloud based integration solution is operated by the provider. Involved SAP technology products SAP Connectivity service o r reverse proxy (see decision tree ) The following capabilities of SAP Integration Suite ( product documentation ): Cloud Integration Open Connectors (conditional) API Management (conditional) Integration Advisor (conditional) When to apply For exchanging transactional and master data between on premise and cloud applications in near real time which requires mediation capabilities such as mapping, routing and/or protocol adaptation. How to apply Cloud Integration as cloud based process integration solution leveraging prepackaged integration content ( SAP API Business Hub ) and/or implement custom integrations using Cloud Integration tooling ( SAP Discovery Center Mission ) SAP Connectivity service to establish a secure tunnel from SAP Business Technology Platform (cloud) to the on premise application landscape ( tutorial ) Open Connectors for simplified integration with third party cloud applications ( SAP Discovery Center Mission ) API Management to govern, protect and meter API access ( SAP Discovery Center Mission ) Integration Advisor for accelerating integration implementation (intelligent message and mapping proposal service) ( blog post ) Example SAP Cloud for Customer Integration with SAP ERP ( prepackaged integration content ) * 1

110. A2A Integration Cloud to On Premise 1 Characteristics | Selection Criteria Hybrid Traffic Unaligned APIs Pre-Packaged Content Structure Mapping Value Mapping Routing Splitting / Aggregation Protocol Mediation Techn. Exception Handling Quality of Service: Best effort, exactly once Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps | Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components SAP Business Technology Platform Cloud Connector 1 Secure tunnel SAP API Business Hub On Premise Application (SAP / Third Party) Cloud Application (SAP / Third Party) Cloud Integration Connectivity 1 Firewall DMZ Firewall Firewall 1 Or reverse proxy (see decision tree ).

111. Architecture Blueprint for the Process Integration Style Sample for A2A Integration (Cloud to Cloud) – Info Sheet Details Description Integration of on cloud applications with other cloud applications using a cloud based integration solution. The communication between the cloud based integration solution and cloud applications requires special security measures (e.g. digital certificate based). The cloud based integration solution is operated by the provider. Involved SAP technology products SAP Connectivity service or reverse proxy (see decision tree ) The following services of SAP Integration Suite ( product documentation ): Cloud Integration Open Connectors (conditional) API Management (conditional) Integration Advisor (conditional) When to apply For exchanging transactional and master data between on various cloud applications in near real time which requires mediation capabilities such as mapping, routing and/or protocol adaptation. How to apply Cloud Integration as cloud based process integration solution leveraging prepackaged integration content ( SAP API Business Hub ) and/or implement custom integrations using Cloud Integration ( SAP Discovery Center Mission ) Open Connectors for simplified integration with third party cloud applications ( SAP Discovery Center Mission ) API Management to govern, protect and meter API access ( SAP Discovery Center Mission ) Integration Advisor for accelerating integration implementation (intelligent message and mapping proposal service) ( blog post ) Example SAP Cloud for Customer Integration with SAP Marketing ( prepackaged integration content ) * 2

112. A2A Integration Cloud to Cloud 2 Characteristics | Selection Criteria Unaligned APIs Pre-Packaged Content Structure Mapping Value Mapping Routing Splitting / Aggregation Protocol Mediation Techn. Exception Handling Quality of Service: Best effort, exactly once Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. Internal On Premise Apps | Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components SAP Business Technology Platform SAP API Business Hub Cloud Integration Cloud Applications (SAP / Third Party) Firewall DMZ Firewall Firewall

113. Architecture Blueprint for the Process Integration Style Sample for Master Data Integration (On Premise to On Premise) – Info Sheet Details Description Integration of on premise applications with each other using an on premise integration solution (e.g. middleware, enterprise service bus) deployed and operated by the customer (or service provider). Involved SAP technology products SAP Process Orchestration software ( product documentation ) When to apply For exchanging master data between on various on premise applications in near real time which requires mediation capabilities such as mapping, routing and/or protocol adaptation. Common key characteristics of process integration can be found here. How to apply Deploy SAP Process Orchestration as integration platform for on premise applications (SAP, third party) Implement predefined integration content and/or develop custom integration scenarios ( product documentation ) Leverage embedded cloud integration runtime (as of release SAP NetWeaver 7.5) whenever possible Example SAP S/4HANA integration with SAP Transportation Management ( product documentation ) * 3

114. Master Data Integration On Premise to On Premise 3 Characteristics | Selection Criteria On Premise Traffic Pre-Packaged Content Structure Mapping Value Mapping Routing Splitting / Aggregation Protocol Mediation Techn. Exception Handling Quality of Service: Best effort, exactly once, exactly once in order Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps | Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components On Premise Applications (SAP / Third Party) SAP Process Orchestration Firewall DMZ Firewall Firewall

115. Architecture Blueprint for the Process Integration Style Sample for B2B Integration (Cloud to On Premise) – Info Sheet Details Description Exchange of business documents from internal on premise applications with external entities such as business partners (customers, suppliers). This integration is implemented with an on premise integration solution (e.g. Middleware, Enterprise Service Bus, B2B Gateway) which supports B2B specific capabilities such as business partner management, acknowledgement handling, different type system (e.g. EDIFACT, ANSI X.12) and B2B protocol standards (e.g. AS2, OFTP). The integration solution is managed by the customer (or service provider). Involved SAP technology products SAP Process Orchestration software ( product documentation ) SAP Process Orchestration, business-to-business add-on and/or secure connectivity add-on (blog post ) Integration Advisor capability of SAP Integration Suite (optional) ( blog post ) When to apply To exchange business documents (such as purchase orders, invoices) of an organization with business partners using classical B2B standards such as Electronic Data Interchange (EDI). How to apply SAP Process Orchestration acting as B2B gateway solution (for B2B communication only) or as integration solution for A2A and B2B integration ( product documentation ) SAP Process Orchestration, business-to-business add-on and/or secure connectivity add-on for supporting specific B2B protocol standards, type systems ( product documentation ) Integration Advisor for accelerating integration implementation (intelligent message and mapping proposal service) ( blog post ). Example Direct procurement of goods from suppliers using the ANSI X.12 standard and AS2 protocol. * 4a

116. B2B Integration Cloud to On Premise Characteristics | Selection Criteria B2B Traffic Trading Partner Management Structure Mapping (e.g. EDIFACT) Value Mapping Routing Routines Splitting / Aggregation B2B Protocol Mediation (e.g. AS2, OFTP) Techn. Exception Handling Acknowledgement Handling (techn. & func.) Quality of Service: Best effort, exactly once, exactly once in order Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components SAP Process Orchestration On Premise Application (SAP / Third Party) Business Partner 4a Firewall DMZ Firewall Firewall

117. Architecture Blueprint for the Process Integration Style Sample for B2B Integration (Cloud to Cloud) – Info Sheet 4b Details Description Exchange of business documents from cloud applications with external entities such as business partners (customers, suppliers). This integration is implemented with a cloud based integration solution (e.g. Integration Platform-as-a-Service) which supports B2B specific capabilities such as business partner management, acknowledgement handling, different type system (e.g. EDIFACT, ANSI X.12) and B2B protocol standards (e.g. AS2). Involved SAP technology products The following capabilities within SAP Integration Suite ( product documentation ): Cloud Integration Integration Advisor Trading Partner Management When to apply To exchange business documents (such as purchase orders, invoices) of an organization with business partners using classical B2B standards such as Electronic Data Interchange (EDI). How to apply Cloud Integration capability within SAP Integration Suite acting as B2B gateway solution (for B2B communication only) or as integration solution for A2A and B2B integration ( SAP Discovery Center Mission ) Integration Advisor for accelerating integration implementation (intelligent message and mapping proposal service) ( blog post ). Trading Partner Management for managing business transactions with multiple trading partners for the electronic exchange of business data ( blog post ) Example Exchange of purchase orders with suppliers using B2B standards such as EDIFACT or ANSI X.12 *

118. B2B Integration Cloud to Cloud Characteristics | Selection Criteria B2B Traffic Trading Partner Management Structure Mapping (e.g. EDIFACT) Value Mapping Routing Routines Splitting / Aggregation B2B Protocol Mediation (e.g. AS2, OFTP) Techn. Exception Handling Acknowledgement Handling (techn. & func.) Quality of Service: Best effort, exactly once Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components Business Partner 4b Cloud Apps (SAP / Third Party Cloud Integration Integration Advisor SAP Business Technology Platform Firewall DMZ Firewall Firewall Trading Partner Management

119. Data Integration - Architecture Blueprint Samples Complemented with Integration Best Practices Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

120. Data Integration Use Cases Decision Criteria Catalog - Legend When defining a Hybrid Integration Platform (HIP), well defined decision criteria are required to select the appropriate integration services. This slide contains typical decision criteria that can be used in architecture blueprints. They have to be adapted/extended to a specific customer context. How To Use Criteria / Capability Description Data Source (Connectors) Availability of connectors for source systems (e.g. DBs) of the integration scenario Data Target (Connectors) Availability of connectors for target system (e.g. DBs) of the integration scenario Data Orchestration Capability to orchestrate data flows (pipelining) Data Transformation Capability to transform data (e.g. aggregations, DB operations, …) Data Virtualization Provisioning of a virtual data layer by federation of queries to remote data sources without physical data movement. Data Replication Extract Transform Load (classical batch or real-time) … …

121. Architecture Blueprint for the Data Integration Style Sample for Data Orchestration ( Cloud to On Premise) – Info Sheet Details Description Integration of on premise data sources (e.g. from applications, databases) with cloud based applications (e.g. cloud data warehouse) using a cloud based data integration solution. Focus is on discovering, refining, governing and orchestrating data across heterogenous data sources. Involved SAP technology products SAP Data Intelligence Cloud ( product documentation ) SAP Connectivity service (conditional) The following capabilities within SAP Integration Suite ( product documentation ) Open Connectors (conditional) Further SAP integration solutions can integrate with SAP Data Intelligence Cloud such as SAP Data Services, SAP HANA Smart Data Integration, SAP Landscape Transformation Replication Server ( blog post ) When to apply Pipeline-driven data integration, operations and governance solution for disparate kinds of data (structured, unstructured, streaming etc.) for data lake, data warehousing or data science. How to apply SAP Data Intelligence includes can integrate and orchestrate data from heterogeneous data sources ( SAP Discovery Center Mission ). Deployment options: On SAP Business Technology Platform, public cloud Kubernetes service, private cloud, on premise installation (see PAM ). SAP Connectivity service to establish a secure tunnel from the SAP Business Technology Platform (cloud) to the on premise application landscape ( tutorial ) Open Connectors for simplified integration with third party cloud apps ( SAP Discovery Center Mission ) Example Data movement from SAP S/4HANA to SAP Data Warehouse Cloud * 5

122. Data Orchestration Cloud to On Premise 5 Characteristics | Selection Criteria Big Data Use Cases Data Intelligence Data Orchestration Data Sources and Targets (see supported connection types of SAP Data Intelligence, cloud edition) Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components SAP Business Technology Platform Data Warehouse (SAP / Third Party) Database (SAP / Third Party) On Premise Application (SAP / Third Party) On-Premise Integration Components SAP Data Intelligence Cloud 1 Cloud Connector 2 Secure tunnel Connectivity 2 1 Deployment options: On SAP Business Technology Platform, public cloud Kubernetes service, private cloud, on premise installation (see PAM ) Firewall DMZ Firewall Firewall

123. Analytics Integration - Architecture Blueprint Samples Complemented with Integration Best Practices Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

124. Analytics Integration Use Cases Decision Criteria Catalog - Legend When defining a Hybrid Integration Platform (HIP), well defined decision criteria are required to select the appropriate integration services. This slide contains typical decision criteria that can be used in architecture blueprints. They have to be adapted/extended to a specific customer context. How To Use Criteria / Capability Description Remote data & live data connectivity Allows to replicate data from a data source (e.g. business application) and/or to access the data source online. (Near) real time & historic analytics Ability to perform analytical queries on real-time or historical data. D ata modeling Ability to reuse existing data models from the data source or to create data models from scratch. Data preparation and data blending Ability to prepare the data and blend the same from multiple data sources Pre-built & custom built content Availability of pre-built analytical content for business applications and ability to create custom stories. ... …

125. Architecture Blueprint for the Analytics Integration Style Sample for Embedded Analytics (User to Cloud) – Info Sheet Details Description Provide analytical insights through reports or dashboards for custom built applications that run on the SAP Business Technology Platform or SAP business applications using SAP Analytics Cloud, embedded edition. For custom build applications you can expose business data to SAP Analytics Cloud, embedded edition, using a live data connection to the SAP HANA database of this application. Involved SAP technology products SAP Analytics Cloud, embedded edition ( product documentation ) SAP Connectivity service ( link ) When to apply For business intelligence needs of custom built applications on the SAP Business Technology Platform Embedded as part of SAP business applications (such as SAP S/4HANA Cloud, SAP Successfactors solutions) How to apply Configure your SAP Analytics Cloud, embedded edition tenant before building stories and embedding these stories into your business application ( getting started guide ) Embed an SAP Analytics Cloud story in a custom built web application ( tutorial ) Example Embedding SAP Analytics Cloud, embedded edition, into custom build applications which run on the SAP Business Technology Platform. * 6

126. Embedded Analytics User to Cloud Characteristics | Selection Criteria Business intelligence scenarios Expose data as charts, visualizations, text, and images Live data connectivity (Near) real time & historic analytics Data modeling to represent business data from source system Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. 6 On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components SAP Business Technology Platform On-Premise Integration Components SAP Analytics Cloud Desktop Mobile Metadata SAP HANA database Spatial Text and search Predictive Modeling SAP Analytics Cloud Rest story API URL API Permission API User and team management Your application Java or SAPUI5 Live connection Connectivity

127. User Integration - Architecture Blueprint Samples Complemented with Integration Best Practices Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

128. User Integration Use Cases Decision Criteria Catalog - Legend When defining a Hybrid Integration Platform (HIP), well defined decision criteria are required to select the appropriate integration services. This slide contains typical decision criteria that can be used in architecture blueprints. They have to be adapted/extended to a specific customer context. How To Use Criteria / Capability Description Single Sign On & Session Management Enables users to authenticate once, and then log on to all systems that operate in the single sign-on environment without further intervention Role Based Access Access is granted on the basis of common business roles. Such a role combines a selected set of permissions from business applications to bundle common responsibilities of a business user Integration of multiple application UIs Ability to integrate several application UIs into a single entry page (e.g. SAP Fiori launchpad) Navigation Context sensitive navigation across business applications within a single entry page Multi Channel Access Supports different access options (e.g. Internal, external, mobile) Offline / Online Support Supports online access to business application data and offline data synchronization without requiring a constant online connection to the backend applications Quality of Service Defines the QoS of the message transfer e.g. Exactly Once, Exactly Once in Order, Best Effort … …

129. Architecture Blueprint for the User Integration Style Sample for Mobile Integration (User to On Premise) – Info Sheet Details Description Consumption of on premise application data within a mobile application which is developed and operated in public cloud. The mobile application can be web based or device specific (iOS, Android). The communication between the cloud based mobile application and the on premise application requires special security measures (e.g. via VPN, digital certificates). Involved SAP technology products SAP Mobile Services ( product documentation ) SAP Gateway (conditional) ( product documentation ) SAP Connectivity service The following capabilities within SAP Integration Suite ( product documentation ): Cloud Integration capability of SAP Integration Suite (conditional) When to apply Exposing data from one or more data sources/applications on mobile devices. How to apply SAP Mobile Services mobile application development, configuration, and management ( SAP Discovery Center Mission ) SAP Connectivity service to establish a secure tunnel from SAP Business Technology Platform in cloud to the on premise application landscape ( tutorial ) SAP Gateway needed for SAP Business Suite and SAP S/4HANA to provision OData services to be consumed by the mobile app ( blog post ) Cloud Integration capability within SAP Integration Suite to provision OData services for third party data sources which are consumed by the mobile app ( SAP Discovery Center Mission ) Example Exposing SAP on premise application data as SAP Mobile Cards. Creating mobile applications with SAP SDK for iOS or Android. * 7

130. Mobile Integration User to On Premise 7 Characteristics | Selection Criteria Mobile Access Principal Propagation Online & Offline Support Real Time Integration Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components Connectivity 1 Cloud Connector 1 Secure tunnel Mobile Services Mobile Client SAP Gateway 2 1 For SAP Business Suite and SAP S/4HANA only. SAP Business Technology Platform Firewall DMZ Firewall Firewall On Premise Application (SAP) Data Source (Third Party) 1 Or reverse proxy (see decision tree ).

131. Architecture Blueprint for the User Integration Style Sample for UI Integration (User to Cloud) – Info Sheet Details Description Integration of custom build application UIs into a single point of entry including the consumption of cloud application data. The single point of entry can be accessed from a desktop or a mobile device. Involved SAP technology products SAP Launchpad service (Cloud Foundry) ( product documentation ) When to apply For integrating multiple application user interfaces exposing data from backend applications into a single point of entry. How to apply Create a launchpad site using the SAP Launchpad service (Cloud Foundry), and add applications to it ( SAP Discovery Center Mission ) Example Exposing custom SAPUI5 applications through SAP Launchpad service (Cloud Foundry). * 8

132. UI Integration User to Cloud (Custom App) 8 Characteristics | Selection Criteria Omni-channel access to cloud applications Integration of multiple application UIs into a single point of entry Role-based access (Near) Real time integration Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components Launchpad Cloud Apps (SAP / Third Party) SAP Business Technology Platform (Cloud Foundry) Firewall DMZ Firewall Firewall Desktop Mobile Integration content (local and remote) Custom apps and extensions (for example, SAPUI5) Help UI theme designer Related central services* Security and SSO *Further central services planned such as inbox, notifications.

133. Cross Use Cases Integration - Architecture Blueprint Samples Complemented with Integration Best Practices Process Integration A Data Integration B User Integration D Thing Integration E Cross Use Cases F Analytics Integration C

134. Architecture Blueprint for a Cross Use Case Sample for Digital Integration Hub (Cloud to On Premise and Cloud) – Info Sheet Details Description The Digital Integration Hub is an emerging architecture for implementing a large-scale, high-throughput access layer to business data by inserting a high performance in-memory data store layer between the frontend API service layer and backend app and data sources. Involved SAP technology products SAP HANA Database SAP Event Mesh SAP Connectivity service SAP HANA Smart Data Integration The following capabilities within SAP Integration Suite ( product documentation ): Cloud Integration API Management Open Connectors (conditional) When to apply Need for a large-scale, high-throughput and low-latency front-end API services (e.g. for user interfaces) For protecting back-end systems from excessive front-end APIs How to apply SAP HANA Database acts as a high-performance data store for caching the relevant subset of business data. Furthermore it provides a single consolidated view of entities which is stored in one or multiple business applications (cloud / on premise) and databases. Cloud Integration integrates apps (SAP/third party, cloud/on premise) with SAP HANA database and keeps the data in sync. Open Connectors for simplified integration of third party cloud applications. SAP HANA Smart Data Integration is needed when integrating data from databases with the SAP HANA and to keep the data in sync. SAP Event Mesh acts as an event broker for a loosely coupled event based integration between business applications. These publish their events to Event Mesh. Cloud Integration capability is the subscriber of these events and sends the data to the SAP HANA database for update. API Management enables a low-latency frontend API service connecting to SAP HANA database for read queries. Update calls can be performed directly on the business applications. (See blog post ) 9

135. Digital Integration Hub Cloud to On Premise and Cloud 9 Characteristics | Selection Criteria Need for responsive API access to data stored in business applications for large-scale/high performance scenarios Decoupling of business application data sources from front-end API by introducing an in memory data store layer In memory layer aggregate and synchronizes data with business applications by using event-based, request-based, and batch integration patterns Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components Cloud Integration API Management Cloud Connector Data Provisioning Agent Cloud Application (SAP / Third Party) SAP Fiori Desktop Mobile On Premise Application (SAP / Third Party) Database (SAP / Third Party) SAP HANA Database Your Application TCP Smart Data Integration (SDI) Read Write SAP Business Technology Platform Firewall DMZ Firewall Firewall Event Mesh Pub / Sub Pub / Sub Secure tunnel

136. Architecture Blueprint for a Cross Use Case Sample for Event Based Integration (Cloud to Cloud) – Info Sheet Details Description Loosely coupled integration of business applications (SAP/third party, cloud/on premise) using events. Business applications can publish event notifications on a business object's change in state. Consuming business applications are informed of the event and depending on the application logic defined, can read further details about the event and take appropriate action. Involved SAP technology products SAP Event Mesh The following capabilities within SAP Integration Suite ( product documentation ): Cloud Integration Open Connectors (conditional) When to apply Decoupling of applications, extensions or IoT data by messaging principles (publish & subscribe) Within a microservices based application architecture How to apply SAP Event Mesh acts as an event broker: Business applications can publish event notifications to queues within Event Mesh to enable an asynchronous and decoupled communication ( tutorial ) Cloud Integration capability within SAP Integration Suite acts as a subscriber to these events and routes the event data to receiving business application (s). If this application requires more information than provided with the event message more it actively requests more details using a read query from the event publisher ( blog post ). Open Connectors for simplified integration with third party cloud applications Example Notification on business partner change from SAP S/4HANA Cloud to a third party cloud application. 10

137. Event Based Integration Cloud to Cloud Characteristics | Selection Criteria Event based and driven integration Exchange patterns: Publish & subscribe, point-to-point, request/reply Decoupling of sender and receiver(s) Using standard protocols (AMQP 1.0, Webhook, REST, MQTT) QoS: Asynchronous Disclaimer: this slide shows an illustrative example that needs to be adapted to the specific customer context and requirements. It serves as a starting point for customers to model their hybrid integration use cases. On Premise Apps I Data I Users | Things Public Cloud Apps I Data I Users | Things Public Cloud Integration Components On-Premise Integration Components Event Mesh Cloud Integration Cloud Application (SAP / Third Party) Cloud Application (SAP / Third Party) 2. Read SAP Business Technology Platform 3. Lookup Firewall DMZ Firewall Firewall publisher subscriber 1. Expose Event Integration flows queues 10

138. SAP Integration Solution Advisory Methodology Template Overview & Terms of Use 1 Integration Roles & Governance 7 Integration Domains 2 Integration Styles & Use Cases Patterns 3 Technology Mapping 4 Interface Assessment 5 Architecture Blueprints 6

139. ISA-M Cycle Phase 4: Enable a Practice of Empowerment Objectives Establish integration as recognized discipline Position integration as a strategic differentiator Provide holistic view on integration Democratize integration delivery Establish knowledge sharing culture (best practices) Improve communication between teams / SIs Sample approach* Define and introduce integration roles Setup a dedicated integration strategy team Roll-out integration guidelines in your organization Establish an enterprise architecture board Rollout solution architecture blueprints Define areas for self-service integration * Highly depends on your organizational context

140. Integration Roles – Overview Sample Integration Roles and Responsibilities ISA-M includes frequently used integration roles in organizations, together with their typical responsibilities and some sample activities in the context of SAP. The concrete definition of integration roles depends on your specific customer context. You can use the outlined integration roles as a starting point and adapt/extend them to your specific needs. These roles, for example, can help you to establish an integration competency center within your organization and derive areas for self-service integration (e.g. simple integration tasks covered by citizen integrators). How To Use Integration Roles Enterprise Architect Business Domain Expert Integration Administrator Application/API Developer Integration Developer Citizen Integrator Integration Architect Business User Chief Integration Office

141. Integration Roles – Definitions I Sample Integration Roles and Responsibilities Integration Architect Definition of technical integration architectures with a focus on specific integration technologies / services Definition of technical specifications for integration scenarios based on business requirements Definition and communication of patterns, templates, and best practices Responsibilities Definition of development guidelines for SAP Integration Suite or SAP Process Orchestration Definition of best practices for integration flows using the Cloud Integration capability within SAP Integration Suite, Sample Tasks in SAP Context Enterprise Architect Definition, communication, and continuous improvement of an integration reference architecture based on an overall IT strategy Definition of integration standards and technology selection guidelines (cross-vendor, hybrid integration platform) Evaluation of new integration technologies / services Responsibilities Definition and rollout of company-wide technology selection guidelines using the ISA-M Roll-out of integration standards Review and adjustment of ISA-M content as part of the Integration Assessment capability within SAP Integration Suite Sample Tasks in SAP Context Integration Developer Implementation and test of integration scenarios based on technical specifications Implementation and extension of prepackaged integration scenarios Responsibilities Leverage Integration Assessment to determine the best fitting integration technology Implementation of integration flows in the Cloud Integration capability of SAP Integration Suite or SAP Process Orchestration Implementation of data orchestration flows in the SAP Data Intelligence solution Sample Tasks in SAP Context Integration Administrator Technical setup and operations of integration scenarios (for example, archiving or certificate management) Technical monitoring of interfaces, including root-cause analysis and technical error handling Responsibilities Technical monitoring of messages from SAP Integration Suite in SAP Solution Manager or SAP Cloud ALM Deployment of certificates in SAP Integration Suite. Sample Tasks in SAP Context Integration Roles

142. Integration Roles – Definitions II Sample Integration Roles and Responsibilities Business User Processing of workflow tasks Interacting with business applications (omni-channel access) Monitoring and error correction of messages in a specific business process domain or line of business Responsibilities Processing of workflow tasks, e.g. in SAP Workflow service. Error correction, canceling, or restart of messages in the SAP Application Interface Framework as part of SAP S/4HANA or SAP Business Suite applications Sample Tasks in SAP Context Business Domain Expert Specification of business requirements for a specific business process domain or line of business Semantic definition of interface customizations and messages mapping (together with an integration architect) Responsibilities Specify integration requirements from a business perspective leveraging the Integration Assessment capability within SAP Integration Suite Definition of customized B2B interfaces and mappings in the Integration Advisor capability within SAP Integration Suite. Sample Tasks in SAP Context Citizen Integrator Business user with the ability to perform some integration tasks independently (self-service) Elimination of need for deep integration knowledge Responsibilities Leverage Integration Assessment to determine the best fitting technology Implementation of simple integration scenarios by HR business users in the integration center of SAP SuccessFactors Integration of buyers and suppliers in the SAP Ariba Cloud Integration Gateway solution based on a self- service wizard approach Sample Tasks in SAP Context Application/API Developer Customization of enterprise applications Provisioning of customer-specific APIs Development of extension applications or mobile applications Responsibilities Customization of applications with SAP S/4HANA Development of extension applications on SAP Business Technology Platform Development of innovate, API-based applications (e.g. for fast innovation cycles, bimodal IT) Sample Tasks in SAP Context Integration Roles

143. Integration Roles – Definitions III Sample Integration Roles and Responsibilities Chief Integration Officer New emerging integration role Creates a strategy for successful business and technology integration Opens up an organization’s technical landscape to a wider ecosystem Leverages opportunities to collaborate and share digital assets beyond the company’s boundaries Facilitates the ultimate sharing economy Integration Roles A Chief Integration Officer is a new emerging integration role which is responsible for the strategic use of integration services to achieve immediate and impactful business outcomes. Source and further Information: . Integration as a Strategic Imperative – Part 5: Smart Lifecycle Management Explanation

144. Integration Center of Excellence Overview of Responsibilities Integration Strategy Definition I Execution Hybrid Integration Platform Design I Implementation Integration Best Practices Definition I Adoption Integration Coaching Enablement I Governance I Proof of Concepts Integration Center of Excellence Self-service integration based on well-defined standards Integration Developer Citizen Integrator API / Application Developer Virtual Integration Community Integration Center of Excellence Support an agile and decentral integration development approach by shifting from a traditional Integration Competence Center towards Integration Center of Excellence. An ICoE is responsible for applying ISA-M at an organization which also includes integration coaching of a virtual integration community. Source and further Information: Integration as a Strategic Imperative – Part 4: Integration Democratization Explanation

145. Integration Center of Excellence Supports a Holistic Integration Approach to Unlock Innovation Business Users Developer Experts Executive Managers Data Analysts Integration Center of Excellence Accelerators Data access Real-time synchronization Short-term support Executive reporting Data insights & intelligence Support & operations Established pathways to various data sources An Integration Center of Excellence based on agile building blocks can optimize tactical integration projects and empower strategic initiatives by also delivering data access, insights and intelligence.. Source and further Information: Unlocking Innovation Through Integration Explanation Integration Center of Excellence

146. Integration Governance Defining a Process for Integration Governance* *Simplified sample process definition Integration Governance You can also leverage accelerators of ISA-M along a governance process for integration developments. Integration developers can identify the right integration technology and approach leveraging integration best practices of ISA-M. If no existing integration technology can fulfill the requirements, the developer can consult the Integration Center of Excellence. Explanation

147. Tool Supported Integration Governance Approach Leveraging the Integration Assessment capability within SAP Integration Suite Business Domain Expert Specifies high level integration requirements from a business perspective by leveraging a business solution request Integration Developer Defines the integration scope from a technical perspective by processing an interface request Gets a proposal of the integration technology/ies with the best fit to the specified requirements Enterprise Architect M anage s ISA-M master data Maintains customer specific data and integration policies (e.g. for third party integration technologies) SAP Integration Suite Integration Assessment allows Integration Architects to define and document an integration technology strategy. You can leverage this tool to provide integration developers guidance about which integration technology/ies to choose for an integration scenario. Integration Assessment follows the concepts of ISA-M and therefore can cover all integration needs in heterogenous environments. It also aims at improving the collaboration across business and IT personas as part of integration projects. Explanation

148. Integration Governance API & Integration Governance Framework* *Simplified customer example The processes for integration governance have to be interconnected with the overall technology governance process of an organization. This includes defined responsibilities including escalation paths. Explanation Integration Governance

149. Integration Quality Assurance Agile Quality Assurance Process Objective: Introduce lightweight governance policies Type of quality requirements: Mandatory: Protect the organization from material damage by taking into account legal implications, business and technology risks Basic: Meet end user expectations Advanced (optional): Outperform end user expectations Governance: Supervised by the Integration Center of Excellence Integration Quality Assurance Complement your existing quality assurance (QA) process with a lightweight one for non-mission critical integration scenarios. For the latter ones you can implement a more agile and lean QA process which is still supervised by the Integration Center of Excellence. Full QA process still applies for mission critical and more complex integration scenarios. Explanation

150. Integration Quality Assurance Agile quality assurance process for integration developments (II) Approach: Questionnaire-based assessment owned by the Integration Center of Excellence Mandatory requirements Validation through self-declaration (possibly code reviews) + 3. Basic & advanced requirements Questions derived from defined integration best practices Provided as self service or interview-based with option for coaching Results documented through an auto-generated report Every developer is responsible for unit and scenario testing. Integration Quality Assurance Introduce a questionnaire based assessment approach for non-mission critical integration scenarios. These can be offered as self service to integration development teams / citizen integrators. The Integration Center of Excellence team shall also offer to run such assessments in an interview based style which will allow them to coach integration developers regarding quality requirements. Explanation