Documenting your SAP PI/PO scenarios

Documentation is a part of all IT practices. It is there to ensure we document what has been created. This is to ensure that some people later will be able to help support the process. This is also true for SAP PI/PO projects. Documentation is something that does cost a lot to produce, so you need to get value from it and automate it.

I have a problem with the way we normally are documenting your scenarios. In many cases, the requirement for documentation have been small adjusted based on what some people from other departments wished and the types of the object used. It has been a manual process to update all of this documentation. Since I started with XI 3.0 in 2004 one of the things that I have always considered and worked with was how to make the documentation process much better. It has resulted in a host of tools that can create the documentation.

One of the big problems have always been it was almost impossible to create and maintain some documentation so you could keep your previous history. This is the same if you autocreate the documentation or if you make it manually. The Word document will be placed in some repository and then never be touched. I recond that you have seen some thing like the following change history, that will never changed.

The change history of only an inital entry

I wanted to keep the histroy and link it with a business requirmeent for the change. We have added the Ticket concept in Figaf IRT, here you can create a object that look like a Service Request, Request for Change or what jira ticket. The function allow you to handle all your processing in just one application and assign changes to the objects that is affected by a changed. We are working to make this even more connected with your CTS+ transport system, so you can registere all objects in the ticket easier.

When you then generate the documentation after some time you will see what was changed on the ICO, or any linked objects. So if somebody has changed a message mapping used by the ICO then you will it in the list. That way you know when it was changed. If you then later want to drill into what object you can open the link and see the full ticket information. All information in the document will only reflect what is the current values for it.

What is changed for an Integration Sceanrio

An example of what the full file will look like:

We still have some way to go with it. We can go into all Repository Objects, fetching and show the most interesting values from the channels, and get documentation from the different objects. We are looking for customer requierments and feedback to see what should make sense in the process.

You can try this out on your own system with the Free part of the Figaf IRT tool, though it will not create the full documentation for you. Then you will need to have a licensed version.

What is the test coverage of your SAP PI message mappings

On a customer demo I got asked what is the test coverage of the tool. We do show in the UI how many ICO’s you have test for but how about message mappings and also modules used in your landscape and how many times they was run.

We already build a report that showed how many times a message mapping was run in a given period based on the data in the PI monitor. So it was just about combining the two sources to give users a good view of what is going on.

For each integration flow we added the number of test cases created with the IRT tool. Then number if then propaged down to each message mapping so we can show how many message mappings is tested and more important which is not.

We also added a tab with the modules used in your landscape and how they performed. Probably we also need to add the IRT test cases to this. But it also depend on how people want to with our with our our modules.

Check out the demo and then try it for free on your own system

You can try it out on your own system. Just download the Figaf IRT tool run it on your laptop and you will be able to see the data after the landscape have been downloaded.

The testing solution from SAP to test PI/PO called PIT

Friday the 8 of March was the day that SAP finally released SP 14 of SAP PI/PO 7.5. The big promise was the new testing solution that allowed users to test SAP PI message process. It is called PIT.

“TL;DR the testing solution from SAP has some good features for testing. If you are serious with your testing and want full coverage then try out the Figaf IRT tool. “

As a vendor with a similar product, I have been interested in knowing what was going on with it and how it was working. I had seen some initial working of it but did not know where it would end. If it was going to be a killer product then it would remove part of my market. No customers can see the solution and judge if it will be useful for their use cases.

The key takes away is that testing is an important part of your it process where it is upgrading/patching, development or change of your interfaces. It is something that customer have expected and would like to see improved.

It is also good to know that SAP is taking the same approach as we have for fetching and running test cases.

Let’s start with the good part.

The Good part of PIT

  • It is a part of your license so you do not have to pay separately for it.
  • It removes the excuse that you cannot run any tests because you can always set it up
  • It supports fetching test data from dual-stack systems so you can test when you are performing upgrades for the systems. You will need to apply some ABAP notes to allow the recording.
  • You don’t need to install extra systems to run it the testing application.
  • It has a shared repository of data that all developers with the right role can access.
  • You can configure comparison of attachments
  • There are batch jobs running message processing and validation.
  • It is standard software following SAP delivery and support method.
  • Messages can be stopped before reaching the adapter and thereby not send it to the receiver.
  • That no changes need to be made to your landscape except you need to switch logging on for a period of time for the interfaces you want to collect data from.
  • It gives a good overview over how many messages that are affected by a change in one element
One overview i like. In just one screen you can see where the differences are structure across the testing result

I have not seen any roadmaps of the tool and how much resources and new features will be delivered but it looks like there will be more effort in it. So this is all based on the initial release.

Check out the video that I recorded that show my first look at what the tool can do.

My first experience with the tool and what is possible.

I believe that PIT will probably run more tests that my tool because the availability of the tool and customers it is simple to install the system.

What are the requirements

The test system must be installed on a 7.5 sp 14 or above. It can only run a test on the system with that SP level.

PIT  is able to collect test data from AEX system 7.31+ that have been updated within the last 2 years (It requires this note 2650265, which seems to have been backported to all service packs on 7.31+).

PIT can also collect messages from ABAP based systems here you need to apply some more support packages to allow the system to read data.

Read more on

I still see some areas where we have advantages over the SAP tool. (Okay, I may be a little biased, but if you try it out you will hopefully too.)

Why you still need to buy my tool

  • It enables you to test your modules that way you are ensuring that it is also covered as a part of the test.
  • We have a number of options for testing including using the SAP logging, but unlike SAP we du support all 7.31+ releases because we have web scraping to get messages. It is not an ideal solution but allows you to create test data on your old system without having to patch them. Because then you will have to do testing.
  • The speed of recording multiple test cases is a lot faster with the IRT tool because it can handle a lot of configuration needed. You can select multiple iflows and record them at the same time.
  • We do have a graphical overview to view differences and add ignoring of certain elements like time stamps that you do not want to cover.
  • Figaf support patterns not covered by PIT like Async-sync, Sync-async, EDISeperator and pattern is determinated automatically
  • Comparison not only in XML but also JSON, X12, EDIFACT, Text, and Binary
  • Simple data anonymization. You can select your input payload and then with a few clicks analyze everything and insert random names or number on different locations. This allows you to test with sensitive data and comply with GDPR.
  • Allow you to run multiple jobs and test cases when you want or scheduled
  • Excel report of all results so you can show how it worked
  • Connection with our DevOps solution so you can ensure that you are testing all interfaces that are affected by your change. It also allows you to document what was changed.
  • For customers the ability to get new features or functions delivered in days.
  • And so on… I could probably find a few more areas that we cover better.

Will we integrate the Figaf IRT tool with PIT

Since SAP will have a lot of test cases running in the tool we may be able to add some additional benefits of running tests with it. There may be something that can be implemented. We can leverage the way SAP is processing messages if you don’t want to get the test messages into the adapter. We could also use the ability to send a message directly to the message processing without creating an XI30 message.

We cloud probably also leverage the SAP part about downloading messages from dual-stack systems, and use them in our landscape.

IT will probably depend on when customers are adopting 7.5 sp14.

Your take away

If you have a plan to apply 7.5 sp 14 in the near future to your landscape do evaluate it. And see how it fits your plan and idea for working with the tools.

If you want to tool that can help you set up test cases faster, give you full tracking of what is being developed then try out the Figaf IRT tool? And we do support CPI also in the same approach.

You can check out the tool and see if it will suit your testing capabilities better. Check it out at Figaf.com/IRT


How to build a business case

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 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 through this process. Therefore I thought about helping them out, so you don’t have to start from scratch.

I have created an IRT-ROI-business-case 2019.

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.

News for Figaf IRT – January 2019 Improving SAP CPI and PI development and monitoring

Enhanced SAP CPI Monitor, Web integration and PI create test form error

So, lately I have been working with development of Figafs Integration Regression Tool, and I think the new stuff is pretty cool. Hopefully, it will be something that is useful for you to improve the ability to develop and run SAP CPI/PI content even faster and give you less support. If you have ideas for improvements I’ll like to hear.

Improved SAP CPI monitoring

We have improved the logging of errors. So it will download the attachments for the failed flows. Then it will be a lot easier for you to monitor and process the alerts. We have also improved the OData filter, so you can specify filters for messages that do not fail. So if you are using sender and receiver information you can setup a filter like Sender = ‘Salesforce’ and Receiver = ‘LOG’ that way you can get the payloads even if there are no errors on the CPI flow.

Support tool with webhooks

The IRT Support desktop is not the only one in your organization. This way you can setup integration with Jira, Paparduty or Solution manager. We configure to receive Jira notifications in about 1 hour with the information we got from the rules using zapier.com but you can use SAP PI/CPI for it.

 

Used Mappings report

Understand what is used on your SAP PI system of mappings, we have now added an option to show also Java Mappings, XSLT and also Message Mappings. Just use the Excel export of your configuration scenario.

In December 2018 I published a blog about this topic: SAP PI/PO Used message mapping.

Create a test case from a failed message

If your message fails because of a message mapping, you can set up a new test case to cover that case. This way it becomes a lot faster to validate that you have fixed the mapping once you have fixed the problem.

 

Want to ease your work?

I do believe that these improvements will make your work a lot easier. If you want to learn more please watch this video:

 

The last details

I also cover my newest insight about IRT in this slideshow:

 

You can try the features now on your own SAP PI/CPI system.