Skip to content
Last updated:

Glossary

The words Integration Mapper uses, and what each one means on screen.

API proxy : An API in SAP API Management. Shown with its flows and policies.

Environment : One SAP Integration Suite tenant connected to Integration Mapper, such as development, quality or production. Its code (DEV, QAS, PRD) appears next to the organisation’s name in the header.

ERP / HCM : Groups for external systems that are recognised with certainty: ERP for systems such as SAP S/4HANA, HCM for systems such as SuccessFactors or Workday.

ExceptionSubprocess : An error that an iFlow caught and handled in its Exception Subprocess. The message did not fail in SAP, but something went wrong on the way.

External systems : Every system that appears in a design but is not synced and not recognised as ERP or HCM.

iFlow : An integration flow in SAP Cloud Integration.

Package : The SAP Cloud Integration package an iFlow belongs to. On the map, the card that holds its iFlows.

Platform : A product that Integration Mapper syncs: SAP Cloud Integration, SAP API Management or SAP Event Mesh. Each platform is a column on the map.

Queue : A queue in SAP Event Mesh.

Revision : In Audit, one version of an iFlow’s content. A new revision is recorded when the content changes, whatever version number SAP reports.

Sync : Integration Mapper reading SAP. The Discovery sync reads the inventory and designs; the Monitoring sync reads messages and errors.

Template : Rules that decide where each group sits on the map and how its items are laid out.

Type : In Explorer, what something is: iFlow, API Proxy, Queue, Topic, or an interface (ERP, HCM, external or unclassified). It comes from what Discovery found, not from a label someone assigned.

Contract : In Schema, the request and response payload registered for an interface. Shared by everyone in the environment.

Incident : Integration Mapper’s record that a recurring error needs follow-up, opened from a signature. With ServiceNow connected, it also becomes a ticket.

Signature : In Monitoring, one recurring error of one iFlow: its occurrences grouped by the error the sync recorded, ignoring the parts that change every time, such as IDs and timestamps.

Version : In Projects, one delivery: V1 is the implementation, each improvement is a new version. Only the open version accepts changes.