Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
This post is intended for all the Consultants working on Upgrade/Migration of SAP PI/PO systems and looking for things to be considered and technical checklists.


There are multiple reasons why customers are not going for the latest releases:

  • It is too difficult to get the system upgraded.

  • They are licensed differently.

  •  Don't want to take the risk with an existing stable system.

  • Downtime during the upgrade.

  • Timelines and cost involved and so on...

Why Upgrade?

We all know that the mainstream maintenance for SAP NetWeaver releases 7.1x, 7.3x, and 7.4 is coming to end by 2020. It’s time to start planning for an upgrade/migration project to move to release 7.5.
There are many advantages to have the latest updated system:

  • Latest Release: With the new Functionality available in the latest Support Pack can be used to enhance your scenarios without having to do any workarounds.

  • Security: With the latest release, all the security bugs can be fixed from time to time.

  • SAP Support: During implementation, we might face problems in the software that we need SAP to fix.

  • It would be much easier to maintain the code by implementing available standard functionality than having custom code/workaround.

  • We will be getting the SAP support with the latest release as SAP has a limit on support time for each release.

Available options for Upgrade/Migration:

  • Either upgrade or migrate to PO 7.5

  • Either upgrade or migrate to AEX 7.5

  • Either upgrade or migrate to PI dual usage type 7.5

  • Migrate AEX to PO 7.5

  • Migrate PI to AEX 7.5

  • Migrate PI to PO 7.5

For more Details:

All the integration content has to be moved to the latest versions during upgrade/migration.
We can make use of the Migration Tool to avoid the transports for this PI instance that has to be SSL enabled.
The user should have the roles SAP_XI_API_DISPLAY_J2EE, SAP_XI_API_DEVELOP_J2EE in source and target system respectively.
Once it is SSL enabled, access the tool using the URL https://<host>:<port>/webdynpro/resources/

For more Details:

The below list of functionalities might impact partially or even completely.

  • Connectivity:
    *RFC Destinations
    *HHTP Destinations
    *Communication Channel

  • Mapping:
    *ABAP Mappings

  • Routing:
    Switching to Integrated Configurations

  • BPM:
    * Redesign BPMs by using adapter modules and replace ccBPMs by BPM process

  • BASIS:
    *NWDS for BPM
    *CTS+ Transport Mechanism
    *User Management Engine for roles are now locally connected to AD

  • Monitoring:
    *PIMONI replaces SXMB_MONI for messages monitoring

  • Alerting:
    *Message-based alerts can be configured in NWA

  • Backend Systems:
    *ABAP Proxy pints to adapter engine via RFC Destination.
    *IDOC_AAE uses RFC Destination of T type for IDOC port connections.

  • SLD:
    *PO system should point to central SLD

  • ESR:
    *Need to check the source system during Migration

  • ID:
    *Migration of objects using Migration tool or redesigning of objects.

  • NWA:
    *Need to redefine the objects like Destinations, Key-store, Alert configurations, etc.,

Activities during upgrade/migration:

  • PI system URL working or not

  • SLD Checks

  • ESR and ID Application Checks

  • CTS+ Transport Organizer Checks

  • RWB: Message Monitoring; Channel Monitoring; IDoc Monitoring

  • Migration Tool for ID objects conversion.

  • NWA: RFC, HTTP Destinations, inbound and outbound Resource Adapters, Certificates and Keys, Alert Configurations, Adapter Services.

  • In case of Dual usage Type Upgrade:
    *All the PI codes need to be checked.
    *RFC destination from PI system to Target Destinations.

I have tried my best to list out a few issues which might occur during upgrade/migration.

  • Unable to access ESR and ID :

    • Disable SAPLOCALHOSTFULL parameter.
      In /dir URL -> Administration -> Parameters. Repository -> Exchange Profile. Click on Parameters.

  • ESR and ID don’t have the latest 7.5 version configurations:

    • BASIS need to run the wizard

  • Adapters not opening in ID:

    • SLD sync issues, BASIS needs to refresh the SLD cache.

  • URL error popup Messages while saving an object:

    • Cache Refresh Issue

  • RFC connections error between ECC and PI:

    • User locked, password issues, BASIS needs to check the connection and update passwords if required.

  • SXMB_IFR from PI ABAP stack routes to different URL - /sap/public/myssocntl/?sap-client=100 after dual split usage:

    • SXMB_IFR is not available after dual stack split.

  • HTTP connection to http://<host>:<port>/sap/xi/cache?sap-client=100 returns status code '404' (Not Found) in response:

    • {SAP Note2273975 }- PI CTC: Inappropriate ABAP HTTP Port proposed by Split Wizard

  • File channels Error with permission issue:

    • Permission issue {SAP Note-2464888}

  • SFTP Advantco Channels Error:

    • License issues might occur.

  • SOAP channels Error:

    • The adapter needs to be restarted in RWB {SAP Note-1347828}

Also, we can make use of automated testing tools for SAP Integration like INT4 to reduce the manual test effort.

Based on my recent upgrade project experience, I have tried my best to consolidate the checklists required during the upgrade/migration of SAP PI/PO systems. I hope this post will give some insight into activities involved during the upgrade/migration of the SAP PI/PO system.

References :
Labels in this area