SAP PIPO Guru99 Tutorials2
SAP PIPO Guru99 Tutorials2
Web
Must Learn
Big Data
Live Project
AI
But this was a technical aspect of SAP PI, but to understand this better we will
see the example of implementation of SAP Process Integration.
Prior to SAP PI, business would connect with each other through point-to-point
communication. But this process is not used for multiple and complex processes. For
smooth communication between multiple businesses, Mediated communication or
Integration broker is used, and SAP PI adapts this system very well. It enables
interconnection of a different process via a central location known as Integration
Broker, unlike the point to point connection which is more like a spider web. The
integration broker or server is an integral part of mediated communication consist
of Java based Advanced Adapter Engine (AAE) and an integration engine for routing.
Mediated communication is based on an integration broker which is executed by
exchanging XML messages.
SAP PI/PO
SAP PI PO Overview
Let see how SAP PI handles the XML messages by the help of Integration Broker. The
exchange of data or message in SAP PI occurs in this four phases.
Next in this SAP PI tutorial, we will learn How SAP PI/PO works.
How SAP PI/PO works
SAP PI is not a single component responsible for the integration of SAP and Non-
SAP application, but it is a cluster of components that together make SAP PI
functional. This architecture of SAP PI or components is used during design time,
configuration time and at run time. The various components of SAP PI include
System Landscape Directory
It is a central processing engine of the PI. All messages are processed using this
server.
Central Monitoring
With the help of this monitoring of PI domain is done, and “workbench” is the tool
that is used for monitoring.
Adapter Engine
It acts as a connector to connect the integration engine to SAP systems and other
systems.
Message Processing Technique by PI
To access data from SAP and Non-SAP application this technique is used. SAP PI uses
an intermediate document like IDoc to Flat files to transfer their data.
Design
Once the IDOC is activated in SAP system, PI takes in charge and convert messages
into XML format for its internal processing
Message Monitoring
The messages can be monitored and traced using “Run Time Workbench”. This tool can
be useful in monitoring sender and receiver adapters, Outgoing and Incoming
messages, End to End monitoring of complete scenario and error traces.
Connectivity: Proxy Framework & Adapter Framework
Adapter Framework
SAP PI connects with any external systems (SAP or Non-SAP) using the Adapter
Framework. The adapter framework is based on the AS Java runtime environment and
the connector architecture (JCA) version. The adapter framework consists of two
default module chains if message processing is to be executed entirely within the
adapter, default module chain for the adapter can be used.
The data is received from the wire through a receive location that is listening
for messages at certain protocol at a specified address
After the message is received by the receive location, a message is sent to the
adapter. It creates a new BizTalk message, attaches the data stream to the message.
It adds any meta-data pertaining to the end-point over which the data was
received and then the message is submitted to the message engine
Message engine sends the message to the receive pipeline where the data is
transformed into XML, here the message sender is authenticated, a message is
decrypted and the XML is validated
Next, the messaging engine published the message to the message box. The
message box is a Microsoft SQL table containing messages to be processed
The messaging engine sends the message to either the orchestration or send
port.