Home / Guides / SAP Integration Landscape Diagram: How to Map It

SAP Integration Landscape Diagram: How to Map It

ECC or S/4HANA in the middle, everything else around it — a clear way to map an SAP landscape using recognisable SAP icons instead of generic boxes.

6 min read · Free, no sign-up · Updated 2026-09-05

SAP landscapes tend to have one thing in common regardless of industry: a core ERP (ECC or S/4HANA) in the middle, with a ring of integration middleware, satellite systems, and reporting layers around it. A diagram that makes that structure obvious — rather than a flat list of every system — is what actually helps someone new to the landscape.

The systems worth naming specifically

Vague labels are the biggest weakness in most SAP diagrams. "The middleware" could mean PI/PO, a third-party iPaaS, or a hand-rolled interface layer — and each behaves completely differently during an incident. Be specific:

• Core ERP — SAP ECC or S/4HANA, named explicitly (they have different integration patterns).
• Integration layer — SAP PI/PO, a third-party iPaaS (MuleSoft, Boomi, Informatica), or direct point-to-point calls if that's genuinely what exists.
• Reporting/analytics — SAP BW, SAP Datasphere, or a non-SAP warehouse being fed via extraction.
• Satellite systems — the non-SAP applications that exchange data with the core: Salesforce, a WMS, a homegrown portal.
• Interface mechanism per connection — IDoc, RFC, OData, BAPI, or a flat-file exchange over SFTP. This detail matters enormously for anyone troubleshooting a broken interface.

Building it step by step

1. Open FlowDiagrams and go to ☰ → Starter templates → Integration landscape as a starting layout, or begin from a blank canvas if your landscape doesn't fit a hub-and-spoke shape.
2. Open the library (grid icon, top right) and filter to the ERP category. Drag in SAP ECC or S/4HANA as the anchor system, placed centrally.
3. Add satellite systems around it — search the library for Salesforce, Workday, or whatever else is in your landscape; they're organized under SaaS, Data, and Cloud categories.
4. Place the integration layer between the core and its satellites — SAP PI/PO has a built-in icon; for a third-party iPaaS, search the Integration category.
5. Label every connector with the actual interface type — IDoc, RFC, OData, SFTP flat file — rather than a generic "integration" label.
6. If reporting is part of the landscape, add SAP BW or SAP Datasphere downstream of the core, with the extraction mechanism labelled (SAP SLT for real-time replication is common enough to have its own icon).

A note on landscape complexity

Real SAP landscapes are frequently large enough that a single diagram covering everything becomes unreadable. When that happens, it's usually better to draw one landscape-level overview diagram (systems and major integration paths only) plus separate, more detailed diagrams per major interface — rather than trying to force interface-level detail into the same picture as the landscape overview.

Frequently asked questions

What SAP systems have built-in icons?

SAP, S/4HANA, SAP BW, SAP PI/PO, SAP ECC, SAP HANA, SAP Datasphere and SAP SLT are all built in under the ERP and Data categories, alongside the non-SAP systems that typically sit around them — Salesforce, Workday, Oracle EBS, and most common middleware and integration tools.

Can I add a custom or niche SAP module that isn't in the library?

Yes. The library panel has an Import an official logo option for adding your own SVG or PNG, and any generic shape can simply be relabelled — so a module that isn't in the built-in set can still be represented clearly.