Technical Articles
New ISA-M version introducing the analytics integration style and more
I am pleased to inform you about the availability of a new version (3.4) of the SAP Integration Solution Advisory Methodology (ISA-M) template. With this update we have added some of the integration concepts of SAP’s integration strategy in the context of the intelligent enterprise to our integration methodology. Furthermore, new incorporated new topics which are being introduced with the openSAP course about the SAP Integration Solution Advisory Methodology into the latest ISA-M template version. Let’s take a look at the enhancements and updates in detail.
Enriching ISA-M with technologies of the suite qualities
As outlined by the whitepaper Intelligent Enterprises are Integrated Enterprises SAP aims at delivering an intelligent suite with an end-to-end business process integration following an holistic integration approach: Integrated processes and data accelerates the speed of innovation while reducing complexity at the same time. Distinct suite qualities were introduced that facilitate an out-of-the box integration of SAP applications (see figure 1).
Figure 1: Suite qualities
With the new ISA-M template version 3.4 we have added concepts of selected suite qualities to the integration methodology:
Change | Integration Style / Use Case Pattern / Technology Mapping | Related suite quality |
Updated | Technology mapping of the master data integration use case pattern (process integration style) | Aligned domain models |
New | Analytics integration style with the integration use case pattern embedded analytics and cross product analytics | Embedded and cross product analytics |
Updated | Technology mapping of the UI integration use case pattern (user integration style) | Seamless user experience |
Master data integration use case pattern (updated technology mapping)
With the suite quality “aligned domain models” SAP intends to deliver business objects such as master data, value types and code lists which are aligned across SAP application. This results in the SAP Domain Model which makes it easier to exchange and synchronize this data between SAP applications. The SAP Master Data Integration service of SAP’s Business Technology Platform leverages the SAP One Domain Model and provides scalable and robust technical means for creating, updating and deleting master data objects following a hub and spoke mechanism in cloud. If you are interested in learning more about the SAP Master Data Integration service you may check out the blog SAP Master Data Integration – sharing and synchronizing master data in the integrated Intelligent Suite.
With the new SAP Master Data Integration service we updated the technology mapping of the Master Data Integration use case pattern as follows (see figure 2):
Figure 2: Technology mapping for master data integration and management
In addition to the “master data integration” use case pattern also a guidance regarding master data management is given: The recommended solution is still SAP Master Data Governance which provides master data management capabilities such as duplicate checks, data quality monitoring, master data consolidation and more. This solution can also interact with the SAP Master Data Integration service.
A more detailed explanation of the technology mapping is also available with the new Integration Guide for Cloud And Hybrid Landscapes (p. 34 ff).
Analytics integration style (new)
With the suite quality “embedded and cross application analytics” SAP plans to provide a holistic 360° business and customer view on enterprise data. As a first step SAP Analytics Cloud is embedded into SAP applications enabling a seamless user experience which is also consistent across SAP’s intelligent suite. In a second step cross application analytics scenarios are being supported by leveraging SAP Analytics Cloud or SAP Data Warehouse Cloud. Following this strategy, we have introduced an analytics integration style to ISA-M comprising out of two use case patterns which are “embedded analytics” and “cross application analytics”. For realizing the latter one, three different architecture options are in place (see figure 3).
Figure 3: Technology mapping for embedded and cross application analytics
The ISA-M template also offers an architecture blueprint sample for the “embedded analytics” use case pattern leveraging SAP Analytics Cloud, embedded edition. You can use this edition for embedding SAP Analytics Cloud into applications which you built on the SAP Business Technology Platform.
Figure 4: Sample architecture blueprint for embedded analytics
For more information about the analytics integration style including recommended SAP technology you may look at the new Integration Guide for Cloud And Hybrid Landscapes (p. 64 ff).
UI integration use case pattern (updated technology mapping)
With the help of the suite quality “seamless user experience” SAP aims to deliver a harmonized look & feel and navigation patterns across SAP applications. This suite quality refers to several design and technology concepts. For the ISA-M template version 3.4 we have introduced the concept of the central point of access for users to various SAP and also third-party applications leveraging the SAP Launchpad service. The sample architecture blueprint of the “UI integration” use case pattern has been updated to using the SAP Launchpad service.
Guidance regarding SAP Data Integration Solutions (enhanced)
SAP offers a comprehensive portfolio of enterprise information and data management solutions which also include data integration tools. These were either organically built or added through acquisitions over the years (see figure 5).
Figure 6: SAP enterprise information and data management solutions
Due to the choice of data integration tools the technology mapping of the data integration use case patterns has been fine-tuned: Often several SAP data integration tools can support a particular use case pattern. Therefore, the technology mapping has been enriched with further details (e.g. related to the type of data sources and targets) which makes it easier for you to identify the right SAP data integration tool for your needs.
ISA-M use case “enable a practice of empowerment” (enhanced)
With the openSAP course about the SAP Integration Solution Advisory Methodology we expanded the scope of the last use case of ISA-M which covers all non-technical aspects of enterprise integration. The organizational dimension and “human” factor of integration are quite important as these are key to bring your enterprise integration strategy to life and to success. As part of the course we introduced the new role of the Chief Integration Officer, the new Integration Center of Excellence (see figure 7) and also looked at examples for introducing integration governance and quality assurance in an agile environment. These topics have now also been added to the ISA-M template.
Figure 7: Integration Center of Excellence
When applying the fourth use case of ISA-M “enable a practice of empowerment” at an enterprise it is recommended to watch the videos of the fourth week of the openSAP course: These explain the new concepts in more detail and also delivers some real life examples. I described the scope of the openSAP course at the blog openSAP course about the SAP Integration Solution Advisory Methodology.
Curious about these news and further updates of the ISA-M template? You can find the latest ISA-M template (version 3.4) available for download at the SAP Integration Architecture Community. Not yet a member? Just simply send a mail to isam@sap.com and you will be invited to join the community.
What is the reasoning for making use-case "Master Data Integration, API-based exchange of master data across business applications." a Process Integration style, and not keeping it as a Data Integration style?
Hello Morten,
the rationale is that most master data integration scenarios more fit to the key characteristics of the process integration style (such as a process level integration with a message based exchange in near-realtime) rather than the ones of the data integration style (which is typically more a data level integration, often scheduled batch processing). This also applies to the integration technologies used in a SAP context which is the cloud integration capability of SAP Integration Suite and SAP Master Data Integration.
Best regards,
Katrin
Hi Katrin
We see many API based master data synchronizations that are batch based, and not process related (in non-SAP space).
I presume it can be argued to belong in either.
Best Regards
Morten
Hi Katrin, SAP has changed the official name for ‘SAP Cloud Platform Enterprise Messaging’ to ‘SAP Event Mesh’ in order to highlight the increased importance of event-centric scenarios in the SAP cosmos - quote from https://blogs.sap.com/2021/02/22/please-welcome-sap-event-mesh-new-name-for-sap-cloud-platform-enterprise-messaging/
When will ISA-M be updated to reflect this change and what will be the impact of the increased importance of event-centric integration on ISA-M?
Thanks and best regards
Hello Martin,
you are right regarding the outdated product name: We are currently updating the ISA-M template which will also include latest product name version. Event-centric scenarios belong to the integration use case pattern "event based integration". The integration use case pattern of ISA-M are not ranked regarding importance as it depends on the requirements and needs which use case pattern to choose. But you are right, in the SAP universe the amount of event based integration scenarios may increase. You may also check out the SAP Community Call "Discover Event-Driven Integrations with SAP" which not only covers SAP Event Mesh but also the support of event driven integrations by SAP S/4HANA.
Best regards,
Katrin
Hello Martin,
we are currently working on updating the ISA-M template in order to reflect the latest SAP product name changes. Event centric scenarios are represented by the integration use case pattern "event based integration" of ISA-M. These use case pattern are not classified according their importance as this may also depend on the customer context. For instance for some customers EDI based B2B integration is "dead" as these for instance leverage API management solutions for using public APIs to exchange data with suppliers and customers. In contrast to this for other customers EDI based integration is crucial for their business (e.g. just-in-time delivery in the automotive industry). However, it is likely that we will see more event based integrations in context of SAP application integration scenarios. You may also check out the SAP Community Call "Discover Event-Driven Integrations with SAP" which not only covers the use of SAP Event Mesh but also the adoption of event driven integrations by SAP S/4HANA.
Best regards,
Katrin