How – define the iPaaS migration scope

Scope of the project is crucial for proper planning and monitoring of the project execution – both vital for successful project delivery time and finance wise. It can be hard to define if the interface master list is not maintained properly. Even if you have such list you need to check it against reality, to make sure you are not missing anything.

Int4 Shield can quickly produce list of the integration on SAP PO system giving you initial input for scope definition. Let me show you how you can define the scope with Int4 Shield.

Now you know that the scope definition can be quickly generated from the Int4 Shield based on the real data. Knowing the scope, you can properly plan and split scope into releases or sprints which you can effectively monitor during the transition.

In the Int4 Shield there are two applications prepared specifically for the SAP PO to SAP Cloud Integration migration: PI Interface import and Migration Cockpit.

In the PI interface import you can define your source environment, for example production and you can define some additional selection criteria. When you execute it, the scope is loaded to the Migration Cockpit.

Let’s open the migration cockpit, where you have the whole list of integrated configurations from your SAP PO system. Here you can see the migration status of the interface, you can remove it from scope, mark as completed or run SAP PO or SAP CPI test cases or even
export the list to the Microsoft Excel.