In this last episode of the Integration Podcast, I’m talking about something that will probably affect you next year. I know a lot of companies are planning migration projects. Therefore does it make sense to talk about it here, so you can get my views on the topic.
I’m covering my views on
- Dual stack to Single stack migration
- Should you upgrade if you have a single stack 7.31/7.4 system to 7.5 and what you will get
- Third Party to SAP PI/PO
- Using of Cloud Integration Content
- Seeburger migration
I created a video while recording the podcast.
At Figaf we are working on improving the IRT tool, so you can use it to gain an understanding of your SAP Integration. So you can see how many times a given message mapping, Java or XSL mapping has been executed. I think it will make it a lot easier to understand who big your integration effort will be. It should also be able to recognize which Message Mappings is using the Seeburger Message format.
Once you have a plan and an overview it is easier to start estimating the number of resources and developers you need for the project. Can you do it with your existing developers or do you need more consultants. It also depends on the number of hours you need to spend on the migration.
Business Case for a migration
Nobody cares about you running your Migration Project, and the business would probably prefer you did not do it. Because you will not be able to deliver new integration for a period of time. The big cust will though be if you don’t do it and are stuck on an unsupported version of the SAP PI system. Also, it will be more difficult to make new development and if you have to create ccBPMs that need to be converted at some point in the future to a bigger cost.
If they are going to be involved because of the testing, it may be an idea to get the Figaf IRT application to perform business test so the business doesn’t need to spend time on it.
You can get a list of all my resources at and be notified