Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

SAP PI 7.0 by Mind Map: SAP PI 7.0
0.0 stars - 0 reviews range from 0 to 5

SAP PI 7.0


runs in ABAP stack

based on SAP Workflow

also called Integration Process

designed in the Integration Repository

belong to a Software Component

Once designed, needs to be imported into the Integration Directory

define Business Systems connecting to process


can be automatically updated from another SAP system

ABAP Systems: via RZ70

Java Systems: via Data Supplier Service

Business Systems

can be associated to 1+ comms channels, mandatory for Receiver channels, optional for Sender channels (HTTP adapter can be used to bypass)

groups can be used to associate Business Systems across multiple SLDs, e.g. group ERP_DEV and ERP_PRD into a group called ERP., This is useful for transporting objects

1 to 1 mapping to Technical Systems, exception: ABAP systems; each has its own Business System and Technical System, ability to down-select installed products

Ability to associate to an integration server, used to align system landscapes with PI, landscapes are defined separately in the SLD

define transport sources & targets

Integration generally occurs between 2 Business Systems

Technical Systems

defines, hostname, Products, linked to Software Component Versions, Software Components can be assigned selectively, SID (for ABAP systems)

Product Catalogue

defines, Products, Linked to Technical Systems, Software Component Versions

does not contain Business Services

these are defined in the Integration Directory only

single-instance services without the ability to have a landscape (i.e. dev, test, prod)

Receiver Determination

part of logical routing

defines either

Sender Service

Receiver Service


this information is taken from the envelope of the message received by PI

Message Split

duplicate incoming message and forward to 1 or more receivers

routing based on, content, envelope information

creates new entries in SXMB_MONI

Content-based Routing

significant performance impact

XPath logic, multiple conditions, logical AND, OR, etc.

best starting point for trouble shooting

central part of an interface

good end to end visibility

Adapter Framework

Message Interface

located in the Integration Repository

highest-level component of an interface

PI interfaces go from one Message Interface to another


direction, inbound, outbound

interface pattern, synchronous, asynchronous

Message Type

can be built from external definitions

modifiable, XSD, DTD

not modifiable (need re-import), IDoc, RFC, WSDL

uniquely identified by

Business System

Message Interface name

Namespace, any valid URI

Integration Builder

Runs in Java stack

Integration Repository

design-time environment, reusable objects, data types, etc., Enterprise Services Repository in PI 7.1

organised by Software Component Version

contains, Message Types, Data Types, Message Interfaces, Mapping Programs, imported IDocs, imported RFCs, Integration Scenario, graphical high-level view of integration process, ARIS integration possible, BPEL compatible, BPEL4WS, BPEL4PEOPLE coming in PI 7.1

Integration Directory

configuration-time environment

organised by, object type, namespace, configuration scenario

contains, Configuration Scenario, logical collection of Directory objects, can be cross-namespace, useful for transporting objects together, Value mapping table tool, Communication channels, Receiver Determinations, Interface Determinations, Sender Agreements, Receiver Agreements, Business Services, not transportable, not in the SLD, cannot define landscapes - single service, useful for external web services, Party, each external B2B partner should be set up here, can define unique partner IDs, Duns & Bradstreet number (DUNS), EAN, assigns, Business Services, Business Systems, Integration Processes

Message Type

highest-level XML document for an interface

can be imported from an XSD

contains one or more Data Types

based on standard XSD data types

can contain other Data Types, for nested XML, i.e. complex Data Type

can be Context Objects, XPath variables based on other XML documents, reusable


7.0 version

ABAP Stack

Integration Server

ccBPM/Workflow Engine

Internet Connection Manager (ICM)

Java Stack

Integration Builder tools

Runtime Workbench

Mapping engine, except for ABAP mapping programs and XSLT (ABAP)

Adapter Engine, can be run on a separate server with a Java Stack


Java schema

ABAP schema

Runtime Workbench

End to End monitoring


Cache monitoring

Message monitoring

Performance monitoring

statistics, throughput (messages/hour), latency (between receive and send)

includes adapter engines

can link to other ABAP systems if proxies defined

Alert Inbox


structure mapping

transforms one XML document into another

change field names or hierarchial structures

value mapping

modification of values in message fields

can use value mapping tables, manually created & updated in Integration Directory, uploaded through HTTP adapter, visible in Runtime Workbench

generally performance impact

implemented in

Graphical mapping program

XSLT, can run in Java or ABAP stack, Java stack is more standards-based, XSLT 1.0 only



Communication Channels

Alert Framework