Automatic Migration of SAP PI/PO

SAP PI migrations are important if you are not on 7.5, you have 16 months to complete it.
For the last year, we have been building components that could help in the process. Now we are taking steps to bundle it all together so you as a user will get full support of the process.

Today I held a webinar to show what we have been working on, and get feedback if it was the correct direction. We did not get to show the full process, but it is not long before we can show it.

The goal is to be able to handle the processing of the full migration process automatically. There will be areas where you need to take and handle the processes your self.

  • Create test cases on your old landscape
  • Migrate Repository and Directory to the new landscape
  • Configure channels and ICOs in full landscape
  • Run testing in the new landscape
  • Manage the process

You can watch the replay of the presentation webinar

Want to try it

If you think this is interesting then your first step is to try out the Figaf IRT testing part of the application. You can try it for free on https://figaf.com/IRT. You will anyway need to create test cases on your old SAP PI system.
We currently support 7.31-7.5 and have a number of different ways to create and run tests. All are pretty easy to setup.
Download it for free now.
Then in a few weeks, we will show the first version of the tool.

Here are the slides

Making Seeburger Migration faster

3 years ago I saw the challenges of migration Seebuerger Message Mappings on SAP PI to use B2B Add-on. It was a different structure that people needed to use and it would cause a lot so problems to get it working.

I got an idea for a project to make the process automated. I found a developer that could create a Proof of Concept for it and it did work. We could take a Seeburger Message Mapping on our SAP PO system and update the mapping to use B2B Add-on. It was not a really pretty operation in the beginning and it did strike as a PoC. SMT was working and customers could try it. We have been able to convince some customers to use it have they have used it convert 300+ mappings using the tool. They have just started using the tool, so they have 1000 more planned.

You can see a video of the tool here to see what it can do.

What is new

Now it was time to a version 2.0. We had learned quite a lot about the tool worked and what customers problems were with it. We have made improvements to the following areas

  1. Licensing. Before users needed to get us to sign licenses request before they could convert the tool. It was not a really easy process that caused a lot of manual wor on our and the customer’s side. So now we just give users a license they can use when they start the application. Then it will count each license. Customers can then see the licenses they have used in a document
  2. Test driven approach: The original application was developed as a PoC that was then extended with bug fixes. It meant that we did not have a good way of testing how a change would impact, so it was a lot of manual testing to try to figure out how it can be improved. We had taken some examples that we got bug reports from and created test cases based on it. After it, we could rewrite our code to be simpler and every time validate that we did not cause more problems. So we could rewrite the code so it was easier to add rules and functions.
  3. VDA: 28 days ago one of our customers was trying to convert a VDA mapping. It failed because our algorithms did not know how to convert the mappings. It is now possible to convert VDA. We have also got a request for Tradacom, and it will not take that long to implement, with the current architecture
  4. UI: We had just created a simple application that could help convert mappings. It was not optimal and difficult to use. We now went for a UI5 approach just like with our Figaf IRT tool. It is not possible to search for mappings and schemas, so the conversion process should be a lot faster.

You can see how the UI has changed to be a lot easier to use.

Old UI
New UI using OpenUI5

I want to try

If you have Seeburger Mappings and want to convert them fast then try the Seebuger Migration tool. The first 10 conversion is on us.

SAP PI/PO Migration

There many companies working on migration or planning a migration of their SAP XI/PI to SAP PI/PO 7.5 systems. Over the years I have created a number of resources that make a lot of sense if you are in the process of considering a migration. Here is one place that you can find all my best resources on the topic.

Timeline

One of the drivers for migration is that the support of everything but 7.5 will end in December 2020. That is currently in 20 months time. Not a long time if you need to plan a project, get funding and running the upgrade. I would assume that the minimum time for a migration is 6 months once you got people working on the project. If you need to get the funding you know your companies budget process, so you better get started.

As I read the note 1648480 extended support will not be possible for the Java stack.

Options for upgrading

There are a number of options that you can use when upgrading your landscape. Product manager of PI/PO Alexander Bundschuh has written a list of the different options (13) that you have depending on where you are at the moment. What options for Upgrading SAP PI/PO

My recommendation is to go for a single stack system because the dual stack is not developed anymore. It will also improve your next upgrade because of a simpler architecture. You will have to covert your ABAP Mappings.

Your different options

There is also the option to migrate to SAP CPI, which is the cloud-based tool for Process Integration. It has some areas where it can replace a PI and BPM solution, but there are patterns that are not fully optimal yet. It will no doubt be the place where SAP is focusing their development, so you will see a number of improvements there.

If you are not planning to use PO functions like B2B Add-on, BPM/BRM then it is probably best to keep at current license but move to an AEX, Java only version of your system. The only reason they would be to run CPI content on your PO system. If you have a few ccBPM probably consider moving them to CPI or Cloud Workflow.

If you are using B2B Add-on or want to run CPI content locally the PO is the way to go.

There is the concept Stack split that I have heard some customers use. The idea is to upgrade your 7.31 dual stack system to 7.5 with dual stack. In 7.5 they cannot share a system ID so one of the systems will get a new System ID. You will then be able to delete the ABAP system. So you only have a single stack system. It does require that you are using ICO’s for all your integration. I’m not sure if this is a supported process and how it works. Maybe your consultants know how it works.

Outlook

SAP PI/PO 7.5 will be in maintenance until 2024. SAP has announced there will be a new version of SAP PI/PO in 2022. The goal of this version is to support a newer Java version and latest Databases. The release will depend on when drivers for databases and Java is availabe from vendors.

There is a roadmap for the SAP PI/PO you need to search for Process Orchestration and then login to see the roadmap.

From what I can see on the roadmap it does not look like BPM and BRM function will be improved. You probably need to find another solution for BPM process. It could be the SAP Cloud Platform Workflow or CPI that will allow you to run it. The place where you will see most development is on running CPI content on SAP PO.

Process

The process for migration is pretty simple. It is just something about planning what to do. It does make a lot of sense to get an understanding of how you want to migrate so you can get started and know how it will work. I think it will give you some information to start the migration from. It can be improved and need to be adapted to your model. There are two areas that you need to focus on.

  • Planning: In this, you try to understand what you should be doing with regards to migration. This is where you need to figure out how to upgrade certain elements. This should be considered before you scale up the team. In this phase, you will also be able to see how you automate the solution.
  • Execution: In this part is about making the migration as fast as possible and keep the risk low. Here is where you make a migration of a single interface, test it and then move it to production.

You can read the full post and see all slides and the replay at the link below.

Automation of the process

We have been making a lot of tools for the SAP Platform and they do make a lot of sense to apply in any migration project. The more you can automate the easier the process will be. Here are some of the things you can consider for your project.

Understanding your current integration

To understand what part of your current integration and message mappings, we have created a free tool that allows you to see what is going on. It can give you information about which message mappings you have used and how many times they have been executed in the last month. It can also give you information about which modules you have and how they are used. It is a free part of the Figaf IRT application so it is just to try it out, so you can plan your migration.

Seeburger Migration

If you have Seeburger and are considering what options you have for migration then we have a path for it. We have created an automated tool that can take your Seeburger Message mapping and convert it to a B2B Add-on mapping with a few click. You can then save many hours in the migration process. You just select which mapping you want to convert and which B2B structure you want to use. Then the application will take care of the rest. It will cost you a fixed fee per mapping.

You can read more on the application at Seeburger Migration tool or at how the seeburger migration works.

Testing your migration

If you are doing any upgrade or change of your landscape it is really useful to perform test to validate that it works correctly. I have in some cases seen that after an upgrade something on the mappings had changed behavior. It is, therefore, a good idea to be able to test that nothing is affected.

You have the following options to Test SAP PI.

  • Manual testing requires a lot of resources
  • SAP PIT a free tool from SAP to test from 7.5 sp14.
  • Figaf IRT a tool build to make it a lot easier to test SAP PI/PO. Is our tool designed to make upgrade testing faster
  • INT4 Iftt a ABAP tool made for testing interfaces. It is good for testing result in the ABAP tables

Comparison of the two testing tools, I would recommend the Figaf tool because it makes the testing a lot faster to create and allow you to test your first upgrade. It also contains more patterns for testing and is able to test modules which is important with B2B Add-on.

Automation of the migration process

SAP have a tool that allows you to migrate channels and ICOs. It is a part of the PI system and you just link the two systems together and can then migrate scenarios or channels.

Figaf is currently working on a tool to automate the full migration process. The goal is to make the process a lot easier and enable users to see if they have tested and performed configuration in the full landscape.

Anything missing

Is there something missing let me know.

If you any questions on your migration, sent a email to info@figaf.com.

Make better regression test cases with Figaf Seeburger Migration tool

The Figaf Seeburger Migration Tool (SMT) allows you to migrate your existing Seeburger BIC solution to a native B2B Add-on solution. It helps to update your message mappings to use the new schemas created with the B2B Add-on. It makes your migration process a lot faster and has reduced risk. Some of the benefits of using the tool look as follow:

  • The new solution from SAP has a lot of advantages making it a lot more flexible and supports the newest schemas. It includes all EDIFACT, X12, Tradacom and EANCOM messages that you want to be using, so you don’t need to pay for each message.
  • It is also simpler to transport since they don’t require the use of the BIC to make the one to one mappings
  • It contains all the same adapters with some new features
  • The price of the solution is also included in your standard SAP PI price so you don’t need extra licenses to make sure you can communicate with EDI for your partners. So you can save money on the maintenance of the Seeburger solution.
  • You have the option to use the Trading Partner Management solution making it a lot easier to maintain many partners and the information from them

When facing the migration there are some challenges that you must figure out how to solve.

  • Schemas are different so everything needs to be remapped
  • Test nothing happens with the output messages.
  • Budget and planing

Do you want to try a package with 10 free mapping? Then check out https://figaf.com/tools/seeburger-migration-tool/

Blogs about Seeburger Migration

Do you want more information about SMT? Then please check out the blog posts below:

SAP PI Migration webinar

Migrating Seeburger to SAP B2B Add-on the fast way

Migrate from Seeburger to SAP PI B2B Addon webinar

SAP XI/PI dual stack to SAP PO/PI single stack migration

 

SAP PI Migration webinar

So, on January 15. 2018 I held a webinar I webinar about SAP PI Migration. In the webinar, I talked about my 7 step plan for migration of SAP PI to a single stack. The 7 steps look as following:

  • Goals
  • Current integrations
  • Pattern mappings
  • Resource consumption
  • Migration phases
  • Development
  • Testing

The plan covers an initial assessment on your landscape and an idea of where you want to move your landscape.

Here you can watch the replay on the webinar:

If you want to know more you can also take a look at the blog post 7 steps PI PO migration, which was published on September 25., 2017.

You can also take a look at the slideshow: SAP PI/PO migrations – How to save time and lower risk on your projects:


Lastly, when you are interested in migration, you might want to take a look at this:

  • Seeburger Migration Tool The Figaf Seeburger Migration Tool (SMT) allows you to migrate your existing Seeburger BIC solution to a native B2B Add-on solution.
    It helps update your message mappings to use the new schemas created with the B2B Add-on. It makes your migration process a lot
    faster and have a reduced risk