Testing async/sync sync/async bridges in SAP PI

I this week we have added a new functionality for testing your SAP PI/PO interfaces.

IRT is a custom build application that works with SAP PI/PO to make sure you can record messages from your production system and run them on your development system. All with a few clicks in the application.

Watch the video to see more about the application

We got a client request to support async-sync bridges without BPM, and then we added support also for sync-async bridges. The system will then figure out what type of pattern that you are using. Based on the pattern modules and recording will then happen with data.

The other feature is to make sure you can limit the number of test cases you have. For instance, you may have different order types on your orders. And they each follow a different rule set and is mapped differently. If you have recorded 100 messages in total but only 5 for one type and 95 for the other type. You may just want to test with five messages for each, so verify that your interface. Then you can use the new trim functionality to delete all the other 90 test cases, so you just have 5 for each type.

You can get a free 30 day trial at http://figaf.com/irt

Building a business case for testing SAP PI/PO interfaces

For any business investment you must to is to build a business case so you can show a positive ROI. Otherwise, money can spend on something else that has a better output.

The same applies if you want to get a better SAP PI/PO testing up and running. And all of my customers of Integration Regression Tool(IRT) must go thru this process. Therefore I thought about helping them out, so you don’t have to start from scratch.

I have created an Excel document with the business case you can find it there.

There are obviously a lot of assumptions that I have made in it. The assumptions are for a medium SAP PI/PO customer based on my experiences. I have tried to explain them in the video that I have made.

In this case, normal usage of testing would cost around 80.000 EUR a year.
If you go for IRT the first year, it will only cost around 40.000 EUR. The second year would be even better because you have made all the initial investment in the testing.
I was trying to see whether you really should be testing. This part had some nasty consequences like have system or factory down for 2 hours or losing a relationship with a customer. Here the price was 85.000 EUR. It had big fluctuations if you depending on how if your system was down every year or every second year.

Do let me know in the comments if there are ways this can be improved.

Easier configuration of SAP PI/PO test tool IRT

The other day I was going thru the customer journey of my IRT(Integration Regression Tool) application that allows you to test SAP PI/PO interfaces fast.

For my potential customers to see the value in IRT they need to create test cases quickly. There were some steps in the process from them wanting to try IRT to running their first test that could take some time.

The user had to go thru installation where SCA files are deployed on the java system with your favorite deployment tools like SUM, telnet or Netweaver Developer Studio.

Configuration was also one of the points where you had to read the manual to make sure you created users accurate and with roles. It was simple, but if you had not worked with user administration, it could take some time. I wanted to make this much faster and I though of creating a wizard for the full process.

So now you can configure IRT to run you your local system in 2 minutes. I designed it so even my girlfriend would be able to configure it, even though she did not have any experience with SAP user administration.

In the video, I’m also showing how to setup your first test case.

If you want to try it out, you can get a free 30-day trial and test it out on your system.
http://figaf.com/irt

new IRT feature: Compare SAP PI/PO messages as JSON or Binary/Hex values

This video describes the new feature with the SAP PI/PO testing tool.

IRT Integration Regression Tool allows you to fetch messages from your SAP PI/PO productive system and compare how they work on your Test system. IRT allows you to compare XML, EDIFACT, X12, Text files and now also Binary/HEX and JSON files.
You can get a free trial at
http://figaf.com/irt

Tool to get BPM context data from a SAP PO BPM

One of the benefits to having a team of developers at your disposal like I do to create my SAP PI/PO test tool is, the ability to create cool applications to solve problems. So I’m really happy that I can give a free tool away to the people that have the same challenge as I ran into.

I have a client where we were using BPM to have some user actions in. Sometimes they wanted to restart the BPM process with the same data or minor changes. I could see the payload in the BPM monitor as on below.

This did not give any information about how I could download the message. I know if the process is failed I’m able to edit the payload of a message, but this is obvious, not true if the process is completed.

There was no API for getting the data from my research at the point.

So we had to create our own tool to handle the queries.

We found the table in the database that housed the Context Data and then started understanding how it worked. The context data was encoded in an XML structure with base64. Then it was just to build a simple user interface on top of it.

It should be easy to find the correct document and so we added a function to make xpath in the data to get the correct data. So we ended up with the following UI.

 

If you want to get it. You can get it for free at http://figaf.com/tools/figaf-bpm-extractor/.

The build includes sources so you can optimize it your self.