This is the first blog of a series to check what SAP can offer to do a migration SAP PI/PO interfaces to Integration Suite.

This weekend (21st of January 2023) SAP released the Beta of the Migration Assessment and we decide to try it. We are preparing an SAP PI/PO system with less number of interfaces but keeping a good representation of the different possible scenarios that our customers will face to check how accurate the Migration Assessment is based on our Integration Suite experience to develop this interfaces from scratch.

1.1         Activate Migration Assessment

Before you can use Migration Assessment (Beta), you must activate the capability in SAP BTP cockpit.
    1. In your subaccount in SAP BTP cockpit, navigate to Services -> Instances and Subscriptions.
    1. Under Subscriptions, choose Integration Suite. The Integration Suite application launches.
    • Choose Add Capabilities.
    • In the step Select Capabilities, select the checkbox for Assess Migration Scenarios.
    • Choose Next: A list of the capabilities that are to be activated is displayed.
    • Choose Activate: The Overview tab displays the activation progress.

1.2                       Configure User Access

Before users can access the application, you need to assign the relevant role collections to them.

Prerequisites

You’re subscribed to SAP Integration Suite in your subaccount. You’re assigned to the Subaccount Administrator role in the Security section of your subaccount There are two role collections available for Migration Assessment (Beta) that cover different personas and responsibilities:
    • PIMAS_Admin performs administrative tasks, like configuring system settings
    • PIMAS_IntegrationAnalyst performs executive tasks, like reading and running evaluations as well as downloading results

Procedure

    1. In your subaccount in SAP BTP cockpit, navigate to Security  Role Collections.
    1. Select the role collection you want to assign and choose Edit.
    • In the Users section, enter the ID of the user you want to assign the role collection to.
For each additional user, choose + Add a User and enter their ID.
    • Choose Save.

1.3  Create a technical user in SAP PI/PO

We created a technical user with the following roles:
    • SAP_XI_API_DISPLAY_J2EE
    • SAP_XI_API_DEVELOP_J2EE
    • SAP_XI_MONITOR_J2EE

1.4  Configure the Cloud Connector

Open the cloud connector, in the server where you have it installed open the url: http://localhost:8443/ And configure new connection:
    1. Backend Type SAP Process Integration
    • Protocol HTTP
    • Internal Host/Port
    • Virtual Host/Port
    • Allow principal propagation
    • Principal type -> Kerberos
    • Host in Request Header -> Use Virtual Host
    • Create a resource for the Connection
    • The URL Path should be just /
    • The Access Policy should be Path and all sub-Paths.

1.5  Create Destination in the BTP Cockpit

We need to create a destination in the BTP Cockpit for this purpose

1.6  Extract information

Procedure

    1. In the Migration Assessment application, navigate to Request -> Data Extraction.
    1. Choose Create.
    1. Enter a Request Name and select the System you want to connect to.
    1. Choose Create.
The data extraction starts. Once the extraction finishes, the new request appears in the list of data extraction requests with status Completed.
    • Choose Log to view the data extraction log, which provides you with details about the data extraction.

1.7  Scenario evaluation

There is a Dashboard that shows the following, classifying the effort for the migration in T-Size measures (S, M, L and XL) and we can also see how many Sender and Receiver adapters we do have per type. We have another tab where we can see per ICO the complexity and if the interface requires adjustments or is ready to migrate.
Also the scenario evaluation compose an pdf, that can be a good tool to show to the customers what is the effort estimated by this tool, and the effort in Person/days for the technical migration.
Most but the most useful export, could be an excel sheet that contains all the information about the interfaces in different Excel sheets.
In the next blogs we will analyse if we agree with the estimations for a set of different interfaces, and the final objective will be to check how the automatic migration tool will handle all the possible scenarios. We believe, based not only on the Migration Assessment tool  that a big number of complex scenarios will require reimplementation, and in some cases this could be a good opportunity to rethink the process and use the best practices. These were our key insights for your SAP PI/PO to Integration Suite Migration assessment.
Related Post
Understanding PEPPOL Integration Standards: A Comprehensive Guide

Navigating the PEPPOL Network: Embracing Integration Standards for Efficiency The EU defines PEPPOL (Pan-European Public Procurement On-Line) as a standard Read more

SAP Azure SAS Integration: Effective File Transfer with PI/PO REST Adapter to Azure Storage

SAP Azure SAS Integration: AzureBLOB Authentication Business scenario / Requirements For the SAP Azure SAS Integration, you must actively transfer, Read more

Migration to Cloud Integration: Is now the moment?
Cloud Integration conceptional image with Code10 logo in the middle of the cloud being the main character of the concept.

Migration to Cloud Integration: Is now the moment? Almost two and a half years ago, I was sitting in front Read more

The mandatory KSeF e-invoicing implementation has been postponed
KSeF postponement post picture

Poland initially aimed to introduce mandatory e-invoicing on July 1, 2024. However, on January 19, Finance Minister Andrzej Domański declared Read more

4 Responses

  1. Hi,

    Thanks for the blog i had configured as suggested and tested connection and showing successful but while executing request getting below error.

    Extraction request returned an unexpected result. Code: 400 Bad Request 500 Internal Server Error.

      • Hello ,

        while the test connection is working successful but while executing data extraction I am getting below error either at OM_Details extraction or MM_Details extraction.

        xtraction request returned an unexpected result. Code: 400 Bad Request 500 Internal Server Error.

        could you please help.

Leave a Reply

Your email address will not be published. Required fields are marked *