IM IntegrationMapper

SAP Integration Suite

Your integration landscape, finally visible.

Turns a complex integration landscape into a clear workspace — to understand dependencies, flows, impact and operations.

Nothing installed in your environment · Your iFlows stay untouched · The connection is read-only

The tunnel view of the map: legacy systems on the left, SAP Integration Suite in the middle and the ERP on the right, with the integrations running across — The tunnel view: legacy systems on one side, SAP Integration Suite in the middle, the ERP on the other — and every line crossing it is an integration that exists today.

See it in two minutes

Two videos, narrated in Portuguese: one shows how the map is built from your environment, the other follows an error in the middle of the night all the way to a ticket opened with the right team.

It reads your environment. It does not touch it.

The connection is read-only: the product does not deploy, does not edit iFlows and does not reprocess messages. The only writes to your SAP environment are the ones you ask for — turning the Trace of an iFlow on and off, and enabling External Logging if you adopt real-time ingestion.

SAP Cloud Integration Packages, iFlows, the internal design of each flow, deployment status, runtime endpoints and the message processing log.

SAP API Management The published API proxies and the specification of each one, with their paths and declared responses.

SAP Event Mesh Queues and subscriptions, with the topic pattern and the depth of each queue.

Map

Packages, iFlows, API Management proxies, Event Mesh queues and the external systems at each end, redrawn on every sync. The same environment, seen in different ways depending on the question.

“What stops working if this system goes down?”

The map with a dependency path highlighted, linking the Event Mesh queue to the iFlow in Cloud Integration and to the endpoint in the ERP

Focus — an entire dependency path highlighted: what feeds it, what passes through and what depends on it.

Document

Each integration becomes a document: the architecture, what triggers the flow, the outbound calls with the address already resolved, the schema and the numbers for the period. A whole package produces one PDF per interface.

“Does the documentation we have still match what is running?”

The Document Flow: the scheduled trigger, the iFlow on SAP BTP and the four target systems, each with its protocol — From what triggers it, through the SAP BTP subaccount, to the target systems — with the protocol of each call.

The PDF it produces

The cover of the generated document: the interface name, the package, the environment and when it was generated — Cover — interface, package, environment and generation date.

The architecture page: the source system, the iFlow on SAP BTP and the target systems, with the protocol of each call — Architecture — the source, the iFlow and every system it calls, with the protocol.

The monitoring page: runs, failures, error rate and p95 latency per period — Numbers — runs, failures, error rate and p95 per period.

Seven pages per interface, generated from the live environment: overview, architecture, how the flow is triggered, the outbound calls with the resolved address, the numbers for the period and the open tickets. From the map, a whole package produces one document per interface, all downloaded as a single file.

Explore

The same truth as a list, with filters by type, protocol and status — and a diagram of the chain each integration follows, from sender to receiver.

“How many SOAP interfaces are still here?”

The Explorer screen: iFlows grouped by package, with protocol filters and the chain diagram — The Explorer, with the protocol filters and the chain diagram of the selected integration.

Monitor

Exceptions grouped by iFlow and by error class, separating real failures from ExceptionSubprocess. With Trace on, the step-by-step execution is kept with the payload of each step, before SAP discards it.

“At which step of the flow did the message break, and with what content?”

The Trace waterfall: each step of the iFlow with its duration and the payload of the selected step — Trace lays out the execution step by step, with the duration of each step and the payload that went through it.

Analyze

Volume over time, latency distribution and a summary by status, across everything that was processed — with free-text search and export.

“Is today’s volume out of the ordinary?”

The Analytics panel: processing timeline, latency distribution and summary by status — The processing timeline and the latency distribution, with the average, p95 and p99.

The Analytics status panel: the split between completed, failed and ExceptionSubprocess, and the iFlows with the most errors — The breakdown by status: completed, failed and ExceptionSubprocess, with the weight of each — and the iFlows that fail the most in the period.

The screenshots above show the shape of the product, not the fine print. To see the interface at full size, watch , narrated in Portuguese — or spend in your own environment.

19,776 messages processed in 24 hours

16 s p95 processing time — 95% finish within 16 seconds

821 of 1,196 errors that were ExceptionSubprocess, not real failures

Numbers from a real environment, over 24 hours. Separating failures from ExceptionSubprocess — the error the flow itself already handled — is what stops the on-call team from chasing what is not a problem.

Delivered as a service

Nothing to install on your side — and nothing left loose on ours. What keeps it running, in detail.

Multi-tenant architecture Each environment — development, quality assurance, production — has its own address and an isolated space in the database. Access is checked on every request, and what you are not entitled to see does not appear.

Nothing to install No open ports on your network and no address exposed to scanning. All communication goes from the product to the APIs you have authorized.

Credentials in a vault AES-256-GCM with the master key in OCI Vault, read using the identity of the machine itself — no API key stored on disk.

Encrypted before it leaves you The secret is encrypted in your browser, in an RSA-OAEP envelope with an ephemeral key per call. Neither the network edge nor the traffic logs see the value in plain text.

SSO and MFA Single sign-on (SSO) via SAML 2.0 and provisioning via SCIM 2.0, validated with Microsoft Entra ID. Deactivating someone in your identity provider ends their sessions and blocks the next sign-in. To save or delete a credential, the product asks for the password and MFA again — even when you are already signed in.

Backups that have been proven An encrypted copy of the database every six hours, stored off the machine. Every week the restore runs in a disposable environment and is checked — a backup that has never been restored is not a backup.

Personal data masked In error text, authorization tokens, email addresses, Brazilian tax IDs (CPF and CNPJ) and phone numbers are masked before being stored.

Want to see it in your environment?

We show you the product running and what it finds in your SAP Integration Suite. A thirty-minute conversation is all it takes.