Exploring Heterogeneous System Landscapes

Objective

After completing this lesson, you will be able to explain why heterogeneous system landscapes require integration and the role of SAP Integration Suite.

Course Scenario

Throughout this course, you will follow the integration challenges of a fictional company - Global Manufacturing AG, a precision manufacturing company. All technical product information refers to real SAP products; only the company and its specific scenario are fictional.

Global Manufacturing AG's landscape includes:

  • SAP S/4HANA (on-premise) - core ERP for production, procurement, and logistics
  • Third-party Quality Management System (QMS) (on-premise) - manages quality inspections
  • SAP Success Factors (cloud) - HR and employee management
  • Cloud - based logistics partner platform - for supply chain coordination with external partners
  • Legacy ERP (ECC 6.0) - still in operation in one manufacturing facility
  • SAP Process Orchestration (PI/PO) - the current on-premise integration middleware

The most critical integration challenge: exchanging quality inspection data between S/4HANA and the QMS. Both systems are on-premises, in the same private network. The data is subject to strict regulatory requirements - it cannot leave the company's private infrastructure. This ground-to-ground scenario cannot be routed through a cloud-based integration runtime. This is the key use case for Edge Integration Cell and a scenario you will revisit throughout this unit.

Introduction

Modern enterprise landscapes rarely consist of a single system. Typically, cloud applications, on-premise systems, legacy enterprise applications, third-party solutions, and partner systems operate in parallel. The result is a heterogeneous system landscape - a variety of applications, databases, and systems, each specialized for specific business or technical tasks.

This specialization enables organizations to address different business requirements with the most suitable solutions. At the same time, business processes frequently span multiple applications; data and information must therefore be exchanged between the systems involved.

But what happens when sensitive data must not leave an organization's own network? What happens when regulatory or architectural requirements prohibit integration scenarios from being routed through external cloud infrastructure? What happens when existing ground-to-ground scenarios from on-premise middleware need to be modernized but continue to run locally?

SAP addresses these requirements with Edge Integration Cell (EIC) - an optional hybrid integration runtime offered as part of SAP Integration Suite. EIC enables organizations to manage APIs and run integration scenarios within their private landscape, while design and monitoring remain in the cloud. It is Kubernetes-based and requires a customer-operated Kubernetes cluster.

To understand Edge Integration Cell, you first need the foundation: What are heterogeneous system landscapes? How does system integration work? What concepts does SAP Integration Suite use? What does it mean when the design environment and the execution environment are separated - and why is that exactly the model on which EIC is built? This course answers these questions step by step.

Heterogeneous System Landscapes and their challenges

A heterogeneous system landscape consists of different applications, databases, and services that operate in parallel, together supporting an organization's business processes. Such a landscape may include:

  • Cloud-based applications (e.g., SAP S/4HANA Cloud, SAP Success Factors)
  • On-premise systems (e.g., SAP S/4HANA on-premise, legacy ERP platforms)
  • Custom-developed applications
  • Specialized third-party solutions (e.g., quality management, logistics, CRM systems)
  • Partner and B2B systems (e.g., supplier portals, EDI networks)

The diversity of these environments results from deliberate decisions: each system was selected to address a specific business or technical requirement. Over time, as business needs evolve, new systems are added. Because these systems are developed and operated independently, they typically use different underlying technologies, distinct data models, varied communication protocols, and incompatible interfaces.

Complex Integration Landscapes

To see what this looks like in practice, consider our course scenario company, Global Manufacturing AG: SAP S/4HANA, the QMS, SAP Success Factors, a logistics partner platform, and a legacy ECC system all serve specific purposes - but they do not communicate natively. Without integration, each system becomes an isolated island of information, and every business process that crosses a system boundary requires manual intervention.

Challenges in Heterogeneous System Landscapes

The coexistence of multiple independent systems introduces recurring challenges. These are not theoretical risks - they are the daily operational reality for organizations running complex landscapes. Some of the key challenges organizations face include:

  • Data Silos: Each System Has Its Own View:

    When systems do not exchange data automatically, information accumulates in isolated repositories - commonly referred to as data silos. Each system holds its own version of a business object; there is no synchronized view across the landscape. At Global Manufacturing AG, for example, quality inspection data lives in the QMS, production data in S/4HANA, and employee data in SAP Success Factors - each potentially reflecting a different state of the same underlying business reality. Without integration, there is no single, authoritative source of information.

  • Manual Data Maintenance: Error - Prone and Slow:

    When the same data is required across multiple systems, organizations often rely on manual data entry or file exports to keep records consistent. In the case of Global Manufacturing AG, when a new material number is created in S/4HANA, someone must manually enter or import it into the QMS before it can be used for quality inspections. At scale, this creates a fragile, human-dependent process that leads to errors and delays.

  • Manual Process Handoffs: Latency and Lost Visibility:

    End-to-end business processes span multiple applications. Without automated connections, each system boundary requires a manual step - downloading a report from one system, uploading it to another, or triggering a downstream action by email. At Global Manufacturing AG, a production batch completion in S/4HANA currently requires a manual notification to the QMS team to initiate quality inspection. This introduces latency, increases error risk, and makes it impossible to track the real-time status of a business process.

  • Incompatible Data Formats: Every System Speaks a Different Language:

    Systems developed independently use different data formats and communication protocols. SAP S/4HANA might expose data via OData APIs; the QMS might accept only SOAP/XML; the logistics platform might use REST/JSON. Even when two systems agree to exchange data, the message must be transformed before the receiving system can process it.

The Role of SAP Integration Suite as an Integration Platform

Integration platforms support the connection of different applications and systems. They enable the exchange and processing of data and messages between the components involved. As a result, integration scenarios can be centrally modeled, managed, and operated.

Why an Integration Platform Is the Right Answer

The instinctive response to these challenges is to build connections between systems directly - one interface at a time. This works for the first two or three connections, but it does not scale. Every custom, point-to-point connection you build is another interface to develop, test, monitor, and maintain. The landscape quickly becomes a tangle of custom code - expensive to maintain and fragile in production. (Lesson 2 explores this further in the context of integration topologies.)

The right answer is to centralize: to have one governed layer that handles all connectivity, transformation, and routing between systems. This is what an integration platform provides. An integration platform acts as a central layer that handles:

  • Message routing - moving data from the source system to the target system
  • Data transformation - converting data from the source format to the format the target expects
  • Protocol mediation - translating between different communication protocols (e.g., HTTP to RFC)
  • Lifecycle management - versioning, deployment, and monitoring of integration content

With an integration platform, adding a new system means configuring one new connection to the platform - not connections to every other system. Monitoring and troubleshooting happen in one place. Governance is centralized.

The Role of SAP Integration Suite

SAP's enterprise integration platform is SAP Integration Suite - an iPaaS (integration Platform as a Service) provided as part of SAP Business AI Platform. It gives organizations a single, governed environment for designing, deploying, and monitoring all their integration scenarios, accessible through a web-based interface called the SAP Integration Suite Cockpit.

SAP Business AI Platform: Positioning of SAP Integration Suite

Note

SAP Integration Suite is part of SAP Business AI Platform.

SAP Business AI Platform (BAIP) is the unified enterprise AI foundation announced at Sapphire 2026. It brings together SAP Business Technology Platform (BTP), SAP Business Data Cloud (BDC), and SAP Business AI under a single governed platform. SAP BTP remains the technical foundation for integration, extension, and development - including the services used by Edge Integration Cell. In this course, we refer to the platform as SAP Business AI Platform.

SAP Integration Suite bundles multiple integration capabilities on a single platform. The capabilities relevant to this course are:

CapabilityPurpose
Cloud IntegrationDesign and execute integration flows across cloud, on-premise, and hybrid landscapes for A2A, B2B, and B2G scenarios. This is the most relevant capability to this course.
API ManagementCreate, publish, govern, secure, and monitor APIs for controlled and standardized access to system functions and data.
Event MeshEnable asynchronous, real-time event distribution and event- driven architectures across applications.
Integration AdvisorAccelerate B2B/EDI integration using machine learning and crowdsourced content to generate interfaces and mappings.

These are not the only capabilities of SAP Integration Suite. Additional capabilities include Open Connectors, Trading Partner Management, Graph, OData Provisioning, Data Space Integration, Integration Assessment, and Migration Assessment. For a complete overview, see: Capabilities of SAP Integration Suite - SAP Help Portal.

Cloud Integration is the capability within SAP Integration Suite that is most relevant to this course. Edge Integration Cell is one of the runtime options for Cloud Integration - and the central topic of this course.

Key Takeaways

In this lesson, you identified the core integration challenges in heterogeneous system landscapes: data silos, manual data maintenance, manual process handoffs, and incompatible data formats. You learned that an integration platform centralizes connectivity, transformation, and governance - and that SAP Integration Suite is SAP's iPaaS for exactly this purpose, running on SAP Business AI Platform. You also encountered Global Manufacturing AG's S/4HANA-to-QMS scenario, a ground-to-ground integration that cannot be routed through an external cloud runtime. This challenge defines the use case for Edge Integration Cell.

In Lesson 2, you will explore the architectural models - topologies - that define how systems connect with each other and discover where Edge Integration Cell fits in the topology landscape.

Modern organizations operate heterogeneous system landscapes that require integration scenarios. SAP Integration Suite supports the structured implementation of such scenarios. Not all scenarios can be handled via the cloud - Edge Integration Cell addresses exactly these cases. This course builds the necessary understanding step by step.