The Goldilocks Zone of Change management for SAP PI

Setting the correct change management procedure can be challenging. You need to capture the right things and not too much.

For one SAP PI/PO client, I just had to do development in Dev, and then move to production to test. I was really uncomfortable doing this.
Another client requires a lot more effort to do the transportations needed. Here is multiple checks and validations to do transports. Here it takes too long time to do something.

That is the reason I believe there is a Goldilocks zone for change management you need to do not too little and not too much.

In many places, people are just trying to implement the same changes that they have to do ERP changes. Which is probably not ideal for transporting SAP PI/PO objects. I have been spending a lot of time making documentation that was not ideal.

In my example where I had to change a field in the XML formats it would be nice if I could mark the changes and then use it. The more manual work you are going to do the more difficult it will be to make the documentation and ensure it is correct. And how do you find it when it is necessary. So at the client, I worked where we had a lot of documentation we could just capture a few lines text about what we had done on the interface. Finding it again would be difficult because how did you find the message mapping information.

 

For SAP PI/PO we are working to improve our Change Tracking tool that allows you to do better change management on your landscape. We have currently been looking at just directory objects, but in the next, release we will also have documentation of repository objects. This will allo you to assign a ticket and a description of why something was changed. You can then see for a message mapping when something was changed in it and why. You can also do an easy comparing between the versions to find the differences.

Read more at http://figaf.com/ctt

 

IRT 2.0 released you can now test SAP PI/PO for free

Ever since I started with developing SAP PI/PO testing was a big thing. There has not been any tool provided by SAP for it.

Over the last two years, we at Figaf has been working on creating a testing tool for testing SAP PI/PO. We got some customers using it, and it is improving their operations. Both when applying support packs or when checking that their new transports work as expected.

I thrilled to announce that we now support a free version of our testing tool. I guess it is also kind of scary to give away something that has cost this much to develop for free. There is some limitation on this free version but you will be able to test some of your interfaces and ensure they work. You can only test 10 ICO(Integration Objects) and save 100 test cases.

IRT is a tool that allows you to collect messages from your productive SAP PI/PO system and then process them on your development system. This is the fastest way to create a validation that your scenarios work.

See a short demo of IRT below.

It is fairly simple to install and run IRT. Install an SCA file on the SAP PI/PO system, create a user and you are ready to run it.  You can get it working in 1 hour if you got the access required.

Download IRT today and start testing your SAP PI/PO systems.

 

IRT 2.0 Release event. Taking SAP PI/PO Testing to the next level

If I had a big marketing department this invitation would probably look like the unveiling of the new Samsung phone. But since I’m the marketing department it is just some fact. And no cool graphics. I do hope you want to join anyway.

Testing SAP PI/PO is not really fun. It takes way too much time and is challenging. That is the reason I created Figaf IRT. I got the idea for IRT two years and it is time for a new release. We are ready to IRT 2.0 Simpler, Easier and Everywhere.

One of the big challenges has been the deployment of the IRT testing application and the difference between different Java and Netweaver that gave different results. We have therefore spent 3 months planning and rewriting the application to be able to run standalone so customers will be able to run IRT if they have 7.31+.

This enables us to create different models for deployment and license options.

We have a release party on February 8 ( which coincidently also is Daniels birthday).

I will be sharing some of the new features and what it means for licensing models.

You can join by clicking the button below.

And as with all good events, there is a surprise. I’m burning to share this with you also but want to keep the suspense.

IRT 1.4 Testing big messages in SAP PI/PO

You asked for it. Or our customers asked for it so now we have created it. IRT, our tool to make SAP PI/PO testing easy, has now been upgraded.

I created the following video

We had a customer that requested that we could process 400Mb messages and verify that they worked. We found that the messages about 10Mb were stuck, so we had to find a way around it. The JMS queue we are using, the build into SAP PI/PO has some limits for external clients. So we try to ZIP the payload, and if that is not enough, we save the message in the database on the agent. We can then fetch the message with a web service call later.
The comparison algorithms were using a lot of memory, so we had to refactor them to be able to compare bigger files. For comparing two 1Mb Text documents, it was using 100Mb, so that did not scale. Now the comparison algorithm has been updated to support messages of 200Mb depending on the hardware. Let’s see if the bigger also works with the memory consumption. If the compare fails it will only be on your development system, so no real problem.
We still have one improvement on the UI to show the big files, but it will come in one of the next releases. For now, you can see it in the Excel reports.

The other improvement was about creating unique numbers in each message. Here we are leveraging the option to use the number range module from the B2B Add-on because it enables good flexibility.

Learn more on how you can test your SAP PI/PO better https://figaf.com/irt

7 steps to a SAP PI to PO migration

Some time ago I created a webinar about SAP PI to PO migrations. I wanted to use the content and share it because it is quite useful for everybody working on a migration. I can see that it is some of the questions that I got on my latest webinar was also about the process. I do hope that this gives a better understanding of what is happening.

As with all things, there are 7 steps to make a good SAP Migration. So if you are in the process this is the steps that I would recommend that you take. It is assumed that you will migrate to a new system because it will make it easier to migrate a single interface at the time. If things does not work you will always have a backup plan.

The 7 steps are the following:

  1. Goals
  2. Current integrations
  3. Pattern mappings
  4. Resource consumption
  5. Migration phases
  6. Development
  7. Testing

The process should be very iterative because you learn a lot in the process that you can use to migrate other interfaces. I the current integration you are going to map out all your existing interfaces together with what types of pattern they are using. This information will then be used in the migration phase and how it is going you may get input on how the next interfaces can be migrated.

You can view this in two different ways. Either you can watch my Screen recording video of it.

Or view the slides here and download them if you want to be using them.

I have also created a longer article about some of the SAPs you need to consider more in details in the blog SAP XI/PI to PO migration.  It is not the same and the two have a lot in common.