SAP PI to Cloud Integration migration report

SAP PI to SAP BTP/Integration Suite/Cloud Integration migrations is a hot topic many customers are looking at now or will do in the coming years. We have made our investment into the field of supporting SAP PI to Cloud Integration/CPI migration with our migration tool to help you migrate.

We also wanted to give you an overview of your migration process to understand what is going on, and if there is integration, you need to handle it differently.

SAP is currently also working on an assessment report to give users an understanding of the migration effort for each integration. I will recommend you check that report out also.

Over the last few releases of the Figaf Tool, we have been improving the report. Our goal is to better understand your integration and the information you need to decide which integrations can be migrated.

Assessing your migration with Figaf

The assessment from Figaf will give you information about what kind of setup you have in your landscape.

  • Systems involved in the integration should give you an understanding of what is happening.
  • Adapter types that are used
  • The Adapter Modules so you can see what, if any, special handling is taking place.
  • Our best guess of the scenario type like BE or Async-sync bridge
  • Which operation mappings are used
  • Which types of mappings are used for each interface? Is it message mappings, XSLT, java or ABAP
  • Number of messages processed on a given interface in the current or last month(best estimate)

The tool supports both Receiver Determination and ICO objects. This makes it quite useful for people using older versions of SAP PI/PO. We should support most cases from 7.1.

Here is an example of the report (CSV file):

Once you start the migration, you can see which integrations have been migrated and moved into production.

The Report is a part of the Figaf DevOps Suite. A free 30-day trial period will allow you to create the report and understand the tool’s value.

And once you have installed the tool, you may also thy the migration capabilities to covert an ICO to an iFlow, since it is just a click away.

I have tried to let it be up to you as an architect or developer to understand what can be migrated and the effort involved in each scenario.

Creating the report

It will probably take you 20 minutes to install the Figaf Tool on your laptop and get the report created.

  1. First, you will need to sign up for the Figaf DevOps Suite. (Start here)
  2. Then you need to install it on your local PC
  3. Then Connect to your SAP PI/PO system as an agent.
  4. Then you need to synchronize everything, which will download all artifacts
  5. Then you need to connect to an SAP CPI system. You just need to create an agent it does not need to work. The report is designed to be used for a migration effort.
  6. Go to the migration configuration page, then add your PI and CPI system
  7. Go to the migration overview page.
  8. Select generate report

Question

Which information would you find useful when judging a migration and its effort? Please share below so we can find a way to improve it.