0% found this document useful (0 votes)
15 views4 pages

SAP PIPO Guru99 Tutorials2

SAP PI (Process Integration) is an enterprise integration platform that facilitates seamless information exchange between SAP and non-SAP applications, while SAP PO (Process Orchestration) enhances this by automating and optimizing business processes. The document explains the architecture, functions, and components of SAP PI/PO, including message transformation, routing, and connectivity through various adapters. An example illustrates how SAP PI can unify competing dairy industries to standardize pricing and share profits through integrated communication.

Uploaded by

Bharath
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views4 pages

SAP PIPO Guru99 Tutorials2

SAP PI (Process Integration) is an enterprise integration platform that facilitates seamless information exchange between SAP and non-SAP applications, while SAP PO (Process Orchestration) enhances this by automating and optimizing business processes. The document explains the architecture, functions, and components of SAP PI/PO, including message transformation, routing, and connectivity through various adapters. An example illustrates how SAP PI can unify competing dairy industries to standardize pricing and share profits through integrated communication.

Uploaded by

Bharath
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP

Web

Must Learn

Big Data

Live Project

AI

SAP PI/PO Tutorial: What is Process Integration & Orchestration


By :
Olivia Turner Olivia Turner
Updated
July 3, 2024
What is SAP PI?

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.


Table of Content:

What is SAP PO?

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.


Understanding SAP PI/PO with an Example

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.

Understanding SAP PI/PO with an Example


Example

To understand the concept of SAP PI more clearly, we take an example of a large-


scale Dairy Industry, which is operating in a large portion of a state and
dominating the region. But there is some small-scale dairy industries operating in
the same region, parallel to the large-scale industry which is not making a profit
due to their price variation compare to large-scale industry. So to avoid the
pricing conflict and maintaining the same price all over the region, large scale
and small scale industry decide to link together, with the help of SAP PI. They
interconnect with each other with the help of SAP PI and started to work as a
single unit. Now, through SAP PI they are able to exchange all the information
pertaining to dairy industry, including pricing and share an equal amount of
profit.
SAP PI connects different platforms like

SAP and Non-SAP systems


B2B and A2A Scenarios
Asynchronous and Synchronous Communications
Cross-component business process management

Why SAP PI/PO?

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.

Message Transformation: During message exchange, it transforms the structure of


the business data
Message Routing: Forwarding a message sent by a sender system to one or more
receiver systems
Connectivity Adapters: Connecting the integration broker and receiver system,
the adapter will transform the incoming message into an inbound message and later
convert it to the format of the receiving system at the other end
Integration Processes: Cross component Business Process Management (ccBPM)
consists of functions for enhanced service orchestration.

Next in this SAP PI tutorial, we will learn How SAP PI/PO works.
How SAP PI/PO works

SAP PI performs three basic functions

Connect: SAP PI has an ability to integrate with all application regardless of


whether it is an application from a 3rd party or from the SAP. It uses the adapter
framework to integrate 3rd party solutions.
Co-ordinate: It can define a path/workflow for each business transaction that
is integrated. It ensures that each message is correctly delivered from the source
to the target destination
Communicate: It can translate files into any format whether an internal file
format or any business to business integration standard.

Next in this SAP PO tutorial, we will learn about SAP PI PO architecture.


SAP PI/PO Architecture
SAP PI/PO Architecture

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
System Landscape Directory

It is a central information provider in a system landscape. SLD contains two types


of information, “Component Information (Installable & Installed) and Landscape
description.”
Integration Builder

It is a tool-set which contains a set of tools for accessing and editing


integration objects
Integration Repository

To develop, design and maintain data types, message structures, mappings,


interfaces, integration processes and integration scenarios independently of system
landscape, integration repository is used.
Integration Server

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

Process Integration (PI) uses integration repository to design message structure


Configuration

Integration Directory (ID) is used to configure technical parameters for objects


created in IR ( Integration Repository)
Message Processing

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.

One for the sender direction


One for the receiver direction

There are four types of Adapters used in SAP PI


File adapters: It exchanges files with external systems
JMS adapters: It communicates with a messaging system
SOAP adapters: It communicates with providers and clients of web services
JDBC adapters: It is an extended pack for SAP PI

Other interfaces supported by adapter framework are

Configuration Services ( API and Adapter metadata xsd)


Administration Services
Various service APIs provided by Adapter framework- Thread Manager, Transaction
Manager)
Adapter framework includes a message audit log API. The API can be used for the
technical trace and logging to write trace statements that describes the execution
of the code.

How adaptor framework works?

Adaptor Framework Works with SAP PI/PO

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.

You might also like