SAP PI (Process Integration) is an enterprise integration platform that provides seamless integration between SAP and non-SAP applications within the organization A2A (Application to Application) or even outside the organization B2B (Business to Business). It allows organizations to exchange information between internal softwares within the company and external systems outside the company.
The SAP PI full form is Process Integration.
SAP PO (Process Orchestration) is a tool for automation and optimization of business processes. It combines features of SAP Business Process Management (BPM), SAP Process Integration (PI), and SAP Business Rules Management (BRM). In other words, SAP Process Orchestration is a more advanced version of SAP PI and has all the tools required to integrate applications.
The SAP PO full form is Process Orchestration.
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.
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 these four phases.
Next in this SAP PI tutorial, we will learn How SAP PI/PO works.
SAP PI performs three basic functions
Next in this SAP PO , we will learn about SAP PI PO architecture.
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
It is a central information provider in a system landscape. SLD contains two types of information, “Component Information (Installable & Installed) and Landscape description.”
It is a tool-set which contains a set of tools for accessing and editing integration objects
It is a central processing engine of the PI. All messages are processed using this server.
With the help of this monitoring of PI domain is done, and “workbench” is the tool that is used for monitoring.
It acts as a connector to connect the integration engine to SAP systems and other systems.
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.
Process Integration (PI) uses integration repository to design message structure
Integration Directory (ID) is used to configure technical parameters for objects created in IR ( Integration Repository)
Once the IDOC is activated in SAP system, PI takes in charge and convert messages into XML format for its internal processing
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.
There are four types of Adapters used in SAP PI
Other interfaces supported by adapter framework are
For messages, SAP PI provides the message level security for XI message protocol, for the SOAP adapter, for the RosettaNet protocol, for mail adapter, for the CIDX protocol and for connectivity with WSRM (Web Service Reliable Messaging) enabled systems. In SAP PI message level security enabled through the use of encryption, digital signature, SAML Assertion, Username token, Certificate token, etc. Authentication methods supported by WS infrastructure for transport level includes basic authentication (Password and Username), SAP assertion ticket, and HTTP over SSL.
To connect with WSRM enabled system you use a communication channel of adapter type WS.
Add-on for SAP PI: Secure Connectivity add-on (SGTP Adapter, PGP module) & B2B add-ons (OFTP adapter, AS2 adapter, EDI separator, EDI XML converter etc.)