SAP PO 7.5 Migration

“To migrate or not to migrate, that is the question.”

Table of Contents

Migration to SAP PO 7.5 should be a key activity on every IT infrastructure roadmap.

One of the most important reasons to migrate to SAP PO 7.5 is that SAP support for SAP NetWeaver PO/PI versions 7.1x, 7.3x, and 7.4 ends on 31^st December 2020. Failure to migrate will result in new technologies being unsupported and security vulnerabilities being exposed.

SAP PO 7.5, on the other hand, has support until 2027 with an extended maintenance period until 2030. Security vulnerabilities and bugs found in previous versions fixed, new integration protocols supported, and the latest security technologies (TLS12, new Cipher Suites etc.) also supported.

Advantages of SAP PO 7.5

Single Stack Java Architecture – SAP PO 7.5 provides a simplified IT landscape and performance boost by running only on single-stack Java. Higher throughput of messaging is achieved without an increased requirement of resources.

Simplified Development, Configuration, and Monitoring. All Tools in One Box. With PO 7.5 you can use the B2B addon, BPM, BRM, JAVA Gateway, REST Adapter, and centralized monitoring tools:

B2B add-on – SAP’s B2B adaptors remove the need for 3^rd party adaptors or EDI solutions. Internal trading partner management simplifies certificate and SLA management.

Business Process Management and Business Rules Management allowing for the automation/flexing of processes and integrations where possible.

SAP PO Migration Options

There are two options for migration: Upgrade or Migrate/Fresh Install

Upgrade of the existing system from PO 7.4 to 7.5
Migration/Fresh Install is a new single stack installation that carries out transport operations, integration migration and end-to-end tests.

Conclusion

Our recommendation is to migrate via Fresh Install and is aligned with SAP's own advice for migration to PO 7.5

By running the migration step-by-step, you have a better control of the scenarios that you plan to set live, and always the possibility to rollback once you face major issues on the new environment.

Risk reduction, downtime, project timelines, etc. can be handled easier.
This way you run a lower risk than the big-bang approach.
Naming convensions; It doesn’t take long for a PI implementation to become a complete mess if standards are not put in place before development occurs. To avoid this confusion, it is important that the naming is in a certain format.
Opportunities & Standardizations; SAP PI has evolved over time and the platform name has changed over the years since starting out as XI. Our guidelines for object naming incorporate changes up to the current version of SAP PI and are being updated for the newly christened version 7.50 of SAP PO.
Optimizations; Integrations in the system are examined one by one. Integrations that affect the performance of the system are analyzed. The integrations that can be fixed are corrected, and if necessary, the process is redesigned in an optimal way.
No Database Reorganizations needed.