Posts

SAP PI/PO change tracking tool is now free

I love getting ideas on how to easier to complete a boring task for SAP PI/PO developers.
I believe quite a few of you remembered the PIDocumenter that I created ten years ago. It was a PHP application that could generate an Excel document with the mapping. This function is now standard with Netweaver Developer Studio, though I would say my version was better formatted. That solution became deprecated because the method to get the XMI file was blocked.
One and a half year ago I started working on a tool to make the testing easier on SAP PI/PO. One of the functions we had could make a comparison of XML documents and read the directory API to understand the landscape. It would be simple to combine the two function to compare a directory comparison function.

I have been working at different places where there was a requirement to document what was transported. And I thought it was difficult(too manual) and time-consuming. But there was not a system in place to handle it so things could be changed so it was out of sync. So I wanted to make a tool that could help in the process.

It became the Change Tracking Tool(CTT).

CTT is a tool that will allow you to find what is changed on any objects, like which switch is changed.
In the Swing tool or NWDS, you can see the different versions of an object. It is though difficult to see which specific field was changed in a change. That is one of the use cases CTT helps with.

The other problem is about registering which change is affecting which objects. This way you can have an easy overview of the changes that are happening in your landscape. So you can register the changes on your change number, so you can easily track the changes together with what happened.

It has was given as a bonus to people buying IRT (Integration Regression Tool). It did though not match which what those organizations were looking for. So now you can get it for free. CTT is a part of the installation IRT so once installed you will have access to both functions. IRT is still a licensed product; you can obtain a trial license to try it out.

Take it for a spin and let me know what you think.

Nb. we will add Repository information later this year.

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

The risk pyramid and SAP PI/PRO projects

I took my car to the mechanic recently, and on the wall of the shop I saw a sign that said, ‘We can do two of three things!” On it, there was a graphic of a pyramid with three levels: ‘Low Price’, ‘Short Time’, and ‘Quality’. Then the message, ‘We can do two of these but not three’. Clearly, the idea was that you could have, for instance, a low price and a quick turnaround time, but not good quality.

Project perspective parameters

I think often it’s the same with Integration work. We have these same three parameters when we are working on a project, and we can adjust which parameter takes priority, depending on what our clients prefer to have. Of course, they want all three, but, like the mechanic told me they can’t have all three.

I was presenting Figaf’s integration regression testing tool (IRT) for SAP PI/PRO and one thing that came up was risk of the project.  The thing is, the mechanic’s pyramid is missing the ability to adjust for the very important element of risk. Risk is different from quality — quality is what you get after the project is complete, while risk is a factor you want to mitigate. When we are working on a project, we have risk we want to minimize. In an integration project a risk could be that our mappings will not work with the partners and we need to test more with them. Or that the new technology we try to use does not work. We ask ourselves questions like, how can we complete the project on time? Will it work when we go into production? How many variables are we testing?

I think that a lot of the time, as Integration professionals, we don’t put enough energy into minimizing risk. If you pick up any project management book, one of the big topics it covers is risk. The goal is to teach project managers to ask how they can mitigate and measure the risk they are taking with a given project. Measuring the risk gives the project manager lots of important information that will allow him to lower the risk so that it will be easier to include all the components of a project in less time, with fewer problems and higher quality.

Our SAP regression tool helps achieve all three of the factors in the pyramid by mitigating the risk. First, IRT enables you to set up a certain set of test cases. This reduces risk by ensuring that you’ve run the same test cases every time, and that they’ve passed without any problems. Second, better and more consistent testing raises the quality of the project overall, giving your client a better final product. Then of course, streamlining the testing process reduces the time spent, and allows delivery of the project to the client that much sooner. This is a big deal since most integration professionals work and bill on an hourly basis. And finally, of course, fewer billable hours means a reduced cost to the client.

So, I just wanted to remind you that whenever you are doing integration work, there is a tool that will help you mitigate the risk you’re taking with the project to help you deliver on time and within budget, while still meeting the requirements of your project.

You can check out the Figaf integration regression tool at: http://figaf.com/irt

P.s. We are now going to do a demo of the tool for the client, so they must have linked it.