Analyze Your SAP PI/PO System Before a Migration to Integration Suite

[DG]

Before you can create any SAP PI/PO migration you need to plan and budget for a migration project. It is not an easy to do task and there are a lot of factors you should consider.

SAP has their migration assessment tool, that you can trigger to fetch data about your current system and landscape. I strongly encourage you to run it and get the details from it. The more perspectives you have on your integration, the better.

At Figaf we also have our report over your landscape. It does not come with any timeline on how long it should take to process each migration. It is something that is up to you to process with your landscape.

How Figaf collects data

Once you install Figaf and it connect to your SAP PI/PO system it collects a local version of all objects. Then it links all objects to so we got a tree of the objects. This is the same as SAPs tool does.

You can use our free migration edition, which will also help you test the migration and allow you to try our migration tool. You can install Figaf on a laptop for a PoC or on BTP for productive usage.

Figaf report

Once data is collected, you can generate a report like the following with all data.

You will need to go through and find:

• The different types of adapters used. It is mainly the first time you connect with an adapter that it will cost you time.

• Number of different modules you need to support and how critical it is

• Number of EDI interfaces

• Find problems that cannot be migrated

Once you have gone thru the list it becomes easier for you to estimate how many interfaces you need to migrate.

The small differences

With the projects we have been working with we have found that it is small details that makes or breaks if a migration will work. Some of the recent challenges we have come up with are:

1. Local function in a message mapping that are using Imported Archives

1. Message mapping that links to an Imported Message. Something we have only seen in old mappings.

 And you will probably find a lot of other cases

In our latest release (2402) of Figaf we have created a option to callow you to create your own rules via Xpath or Regex. Then it will find all objects in your ESR or Directory that matches this. On a call we should the team in about 5 minutes how to create a new rule to cover checking for the second case. Then we could see less than 10 mappings were affected so no need to automate a workaround. If it was 20-50 we may have considered improving to fix this case.

For 1. Figaf allows you to extract the UDF to a groovy script as we do for Function Libraries. This gives you a way to edit and manage the content much more accessible.

To create a new rule check the following guide

I hope this will be a part of your migration toolbox.

Pilot project

The assessment is not something that can stand alone. Running a pilot project where you migrate some integrations with the different options SAPs, Figafs or manual migration will give you much more data about how to get started.

Also consider the effort of moving it into production and all the steps involved, like testing and go live considerations.