This presentation shows you all the concepts of developing with SAP Process Integration (PI) and SAP Process Orchestration (PO). You will learn about the architecture. The way the different datatypes both external definition and message and datatypes can be constructed to create a Service Interface. How the message mappings is connected with the operation mappings. The presentation also cover the System Landscape Directory and how it must be integrated with the runtime of the system. You will see how the objects is configure so the messages can be processed. Get up to speed on how the adapters is developed and can be used. If you want to know more goto http://picourse.com to start the free program, or sign up to one of the affordable SAP PI courses or learn how to use BPMN on SAP PO. The presentation covers the first module of the course.

1. Module 1 Getting Started
Daniel Graversen
PI Course

2. Goal
• Give you a basic idea of how SAP PI works.
• If you want to see the video of this go to http://PICourse.com
and you will be able to see the full presentation

3. Agenda
• Basics
• Architecture
• Components
• Objects

4. PI focus area
 Enterprise Services Bus
 The PI platform is focused on integrating system
 Excellent for integrating with SAP systems

5. Main project groups
 A2A Application to Application
 B2B Business to Business
 ETL Extract, Transform, load
 Managed File Transfer

6. Why use SAP PI
 Easy way to use mappings
 Connection to multiply system/protocols
 Native SAP Integration with all types of
protocols
 PI is designed to be really good at processing
single messages.

7. When not to use SAP PI
 ETL
 Data load
 When making huge date imports

8. Loosely Coupling of System
 SOA Service-oriented Architecture
 Make it possible to decouple one system and replace it with
another
 Sound good in practice, but in real life I have only seen it a
couple of times.

9. Components
SLD
ESR
-Builder
-Content
Directory
-Builder
-Content
Adapter
Engine
BSystem
PI Single Stack

10. Architecture

11. Dual Stack

12. Single Stack

13. Adapter
 Java based
 Make sure the system can communicate
 Receives message from connected system
 Send messages to connected systems
 Development will take the used adapter into
consideration. So you must know the used
adapters.

14. Adapter Architecture

15. Sender / Receiver Concept
 Confusion takes longtime to understand
 Relating to the system communicating with SAP PI
 Sending System
System sending the message
Outbound Service Interface
 Receiver System
System receiving the message
Inbound Service Interface

16. XML
 Is used for all message inside SAP PI
 Has different for formats defined by XSD (DTD)
 Make it easy to share and agree on formulas
 Contain business information agreed on by
involved parties, standards organization or
government

18. Mapping
 Take one data format and translate it to an new format
 Most often the graphical mapping
 But also XSL(T) and JAVA
 Before we also had ABAP and ABAP XSL

19. Graphical mapping
 Lots of build in functions
 It looks real easy to perform mappings.
 The queue/context function is a must that you
master
 Can add your own Java functions to improve
the functionality.

21. Business Understanding
 Business cannot give the full mapping
information
 You as a developer therefore has to take some
for the responsibility
Get as much help as possible from the business
But don’t rely on them having all the answer

22. Objects
 Have lots of interactions
 They all relate of specific functions
 There is a lot of different objects that you must know

23. Object Placement
 Namespaces is a place where the
files can be saved
 Can use syntax like urn::picourse-
com:project1
 Or http://picourse.com/project1

25. Repository and Directory
Repository
 Structural information
 Mapping
 Processes
 Lots of governing
 Developed once and then
identical in all systems
Directory
 Is different on each system.
 Configure connections
 Flows

26. Business Example
• Inventory update file
• Send an XML file from Warehouse to SAP ERP
• We want to send a file with information on the inventory of
the stock in the Warehouse system. We want to send this to
ERP where the data will be read by a program to update the
business information.

27. Repository Objects

28. Directory

29. System Landscape Directory

30. Next
•Go to http://picourse.com and
optin to get the video of this
presentation and a tutorial on
how to make your first file 2 file
scenario