A few weeks ago we added an option to monitor your SAP PI/PO repository content, so you could see what was changed in any objects. And based on the changes you registered you could test the scenarios.
We have also enabled users to test SAP Cloud Integration so it made a lot of sense also to monitor the content so we could support full cycle development. So we can now monitor all changes to the content. So you can see what was changed in a script and what areas were changed in an iflow. The output may be a little technical but it will allow you to see that something was changed.
We also have the ticket content that allows you to register the changes that you are doing and ensuring that you are testing all of the changes that you are making. It is a way to ensure that enables you to document the changes in a better way than using Word documents for the information. You can then link your existing ticket/helpdesk system to the IRT tickets as an extra data source.
You can see a short demo here.
There is some features that we will improve in the comparison, so you can see the message mappings content and see the part that was changed. And also improve the comparison of scripts. It will come in a future release.
If you have other wishes to future development do let us know.
We just released IRT 2.3. That had two big additions. One was our ability to monitor your full SAP PI/PO/CPI development process. In this post, I’ll share the other which is much better support for cloud integration.
In 2.2 we add the first option to run cloud integration tests. We were able to use the new trace functionality for cloud integration to get messages at all stages. This made our test easy to perform without any changes to the setup.
In this, we have added some more functionality
We can run regression test for both HTTP and now SOAP adapter. This means that it will use your existing iflow to process the test message in.
If you use other adapters or scheduled tasks IRT is able to create a new flow that looks like the original one, except it starts with an HTTP adapter. IRT can record the message from the existing flow.
We have an oss note with SAP that the latest release meant we were getting some problem when setting an iflow into Trace mode.
You can watch the demo video here.
It is pretty simple to setup. Just signup at http://figaf.com/irt then login with the password you will get. Here you can also find the manual. Download the jar file, start it. In the configuration enter your host url, Suser and password, then you can synchronize the list of iflows and start setting up test cases.
https://figaf.com/wp-content/uploads/2018/05/SAP-Cloud-IntegrationTesting.png400700dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2018-05-17 11:37:122018-05-17 11:37:12Update to testing on SAP Cloud Platform Integration (CPI)
If you just purchased SAP PI/PO there is a lot of things to consider. This post will help you in the process of figuring out what is interesting.
The thing is you don’t know too much but it will have the greatest impact on what is set up. So it would be a good idea to have an architecture workshop where you will get all the insight into how you can create a solution that matches what you want to achieve. So it is an ideal time to get help.
I have created a mindmap video where I cover some of the most important things about the process. Watch the video below.
Architeture
A big thing is to get the architecture to match what you want in your organization. There a lot of things to consider like naming conventions and how to create interfaces. This should you would hopefully get a few sample interfaces that show how the things would look and how to monitor them. You should also consider how to make documents required for it both mapping documents if required and documentation.
It may be a good idea to have a secondary consultant to help you in the process that is on your side because you don’t know as much about what you can expect.
Testing
Testing is one of the important things in the process. If you “just” replace middle where you have the ability to get input and output document. If you use the Figaf IRT for SAP PI/PO testing then you will be able to perform the tests to verify that messages look identical. This way you can save some time for testing the application together with business experts.
If are doing a greenfield implementation of SAP S/4 ERP then you will have to change the interfaces on both sides. You will still have to setup testing so you can ensure that the process works correctly even when you have to apply support packs.
Migration
A good place to start is also my migration guide. It is much the same things, except that you have more free hands with what you want to do and the changes that you must make.
There are some of the things here that can be applied to the list of attributes to collect from each interface. You can find it in the slides. If you can get the information it may be a lot easier for a partner to do a good estimation of the project. You may add data like a number of fields in each interface to give better information about required mapping size maybe group it in to bucket like 1-20 , 20-100, 100+ fields that need to be mapped.
In this blog, we have not been covering any of the SAP platforms that may be interesting and save some time on integration. There is the SAP Cloud Platform Integration (CPI aka HCI) which is a solution that is quite simply to PI but cloud-based and more flexible. It contains a lot of prebuild content that will speed up and integration, so it may be used in some scenarios. You may also be able to run this type of interfaces on your new SAP PO system. For some integrations, it may be beneficial to use because of the flexibility and the availability of adapters.
Other advice:
I ask the question what people would like to have known before they started on the SAP PI/PO project a long time ago and I did get some interesting answers that may be quite in line with what you are looking for. There was a lot of ideas about making better guides for what should be implemented. You can read all suggestion here.
Good luck on your new platform. I promise it will be an adventure.
https://figaf.com/wp-content/uploads/2018/01/How-to-start-with-SAP-PI.png400700dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2018-01-19 09:55:022018-01-19 09:55:02How to start from scratch for using SAP PI/PO
