In this presentation, you will see some of the problems SAP PI/PO upgrades, Support Packs, and Patches. You will learn some of the problems about applying them and how to get it fixed. The best way to ensure you are testing it is to use an automated tool to setup the test cases and run them. There is a demo on using Figaf IRT to setup the tests in it. You can try the tool self at https://figaf.com/IRT

1. Testing in SAP PI/PO
Developer version
How to test SAP PI/PO after
an upgrading
© Figaf 2018

2. © Figaf 2018
• Upgrades and the challenges
• How to test
• Automating the testing
• Try it your self
Agenda

3. Daniel Graversen
Worked with SAP Integration for
13+ years
Owner of Figaf
Did not like the manual steps often
associated with XI/PI development
Me

4. New functions
Vs
Stability
The fragile nature of software systems

5. ● SAP deliver all changes in columunative packages that contain all
fixes until now
● Many software component that have dependencies between them.
● Patches contains all fixes
● Support Pack contains new features + all fixes up to release
● Both add a lot of new functions that could affect your operations of
the PI/PO system
● If you have not upgraded for a long period it becomes deficult
Is a Patch or Support Pack the same

6. One potential user of IRT wanted to install try our new feature of non-
invasive data collection.
They had 7.5 SP7 and needed Messaging System patch level 1.
Could only download patch 60, which depended on a lot of other
components.
It would almost be the same effort to upgrade to SP11 and get new
functions.
Example of what an upgrade requires

7. ● You are using some function to the edge that is being changed.
● Message mapping behaves differently
○ Complex algorithm and mapping leverage the cases
○ Seen it on multiple occasions
○ Only specific cases where a specific rules is used changes some times 1-2%
of mappings
● Adapters have been changed
○ I have seen adapter namespace change
● Modules and EDI Conversions
What is the risk

8. © Figaf 2018
• Many developer find it enough to test the message mappings.
• Testing message mapping is a good unit test it ensure that mappings
works.
• But it does not test
• More of the flow Routing, Modules and Dynamic Attributes
• Comparing of result is mostly just looking at the document, it may be difficult
to understand if something else if affected
• Test with multiple documents
• Have limited set up test cases
Myth: Message Mapping test is enough

9. ● End to End test where business is asked to create all documents and
verify that they are received correct
○ Often Simple test and few variants
Normal way to test that it works
● Developer test, where developers will send fetched
messages thru system and validate they look the same
○ Manual tasks to find documents and reprocess them
○ Compare XML and see if it is okay

10. ● Time
● Developer time
● Business time
● Will fix this error cause other errors
Problems with upgrades

11. IRT tool
Automation is the way

12. Idea
• Physiotherapy
• Adapter modules
• PoC
• Get development team
• Challenged to make tool simpler
• Create some versions of the tool
© Figaf 2018

13. ● Automated way to collect test cases from production system
● Get data with 10 clicks
● Run the tests on development system
● Easy configuration of test cases
● No programming
What can IRT

14. ● IRT module to be inserted in the flows
● Use the Standard SAP Logs (if you have patched after may 2017)
○ Either use the SAP modules
○ or the ICO logging
● IRT will automatically update the configuration if possible
What IRT does

15. Demo

16. ● Patterns
○ Async, Sync, Bridges Sync-Async/Async-Sync, EDISeperator
● Comparisons
○ XML, Json, Text, Binary, EDIFACT, X12
Support

17. An Iflow can go into Trace mode, this will allow IRT to capture all
messages stages.
When testing IRT can also use the same Iflow or create a similar one
with a HTTP adapter.
How SAP validate Cloud Integration

18. Start using IRT
© Figaf 2018

19. 80 USD/hour
200 ICOs
16.000 USD if you
can test each in just
1 hour
How much does an upgrade cost you?
Time required
pr instance Number of ICOs Pr year Cost pr year
Normal PI testing
Test an interface when changing mapping 120 1 300 48,000
Support packs installations testing 60 200 2 32,000
Total 80,000
Testing with IRT
IRT server 30,000
IRT installation and configuration 5,000
IRT create test cases 10 200 1 2,667
Test an interface when changing mapping 5 1 300 2,000
Support packs installations testing 2 1,600
Total with IRT 39,667

20. © Figaf 2018
• Java 8 application running on
• Spring boot/ Tomcat application
• Comes with built in H2 database to easy start
• For production use databases like PostgreSQL, Oracle, DB2, MS SQL
Server
Deployment options

21. ● Get started in 15 minutes
Just go to Figaf.com/IRT
● Free version upto 10 interfaces
● IRT runs with it own server and database, can run on most laptops.
○ Server options also available.
● If you have patched SAP PI/PO after May 2017 you don’t need to
change anything
● Otherwise a small module needs to be installed on the PI system
Installation

22. Versions
• Free
• 10 ICO
Single User
• Run on local PC and use
Postgresql
• 100 ICO, 3000 Messages for test
cases
• Max size of messages 10 MB
• Comparisons: XML, Text, JSON
• Support
• Price: 5000 EUR, 3500 EUR
following years
© Figaf 2018

23. Enterprise versions
Pro
• 10 Users
• Run on standalone, support all major
databases
• 1000 ICO, 20.000 Messages for test
cases
• Max size of messages 40 MB
• Comparisons: XML, Text, JSON, X12,
EDIFACT, Binary
• Price 30.000 EUR, 20% in
maintance/support
Enterprise
• Pro +
• Unlimited users, Test cases and
message size
• Run test on multiply systems
• Change Tracking
• Tickets
• Support
© Figaf 2018

24. IRT: a simple tool
- that tests complex scenarios
© Figaf 2018
Learn more at figaf.com/IRT