Skip to Content
avatar image
Former Member

Migrating/Upgrading from PI 7.0 to PO 7.4

Dear All,

We are currently running SAP PI 7.0 and are required to go to PO 7.4 (dual stack).

The reason for the move is because SAP PI 7.0 goes out of support at the end of this year.

We have about twenty interfaces spread over a handful of third-party systems. Outgoing interfaces tend to be either from ABAP Proxy to SOAP or File. Incoming interfaces tend to be SOAP, File or HTTP to IDoc or ABAP Proxy. Some interfaces use ccPBM.

We have been given two options on doing this:

1. Clone the current environment and perform upgrade from 7.0 to 7.4 on the clone.

1. Fresh installation of 7.4 on a parallel environment and "migrate" the interfaces from 7.0 to 7.4

In both cases, the existing system will be replaced.

If option 1 is done, I presume all the interfaces will appear in 7.4 after the upgrade, but there may be some configuration changes required to the interfaces in 7.4 afterwards?

If option 2 is done, is this done via a migration tool, or is the migration tool only used when going from dual stack to single stack?

If the migration tool isn't an option, I presume we would have to manually export SLD, IR and ID content from 7.0, and import them into SLD, ESR and ID in 7.4?

What tasks would be required once the interfaces are migrated/exported/imported?

I have had a look at the document "Decision Making Factors when Moving to SAP NetWeaver Process Integration 7.3 - Upgrade or New Installation with Phase-out"

Many Thanks,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • May 11, 2017 at 03:30 PM

    Hello Gareth,

    If you really wanted to upgrade from PI 7.0 to PO 7.4 double stack, then I would suggest a classical upgrade with no migration of interfaces needed.

    The SAP Directory Content Migration Tool is for PI double stack to PO singe stack migrations, where you would have to install a new PO system and then migrate the interfaces. Also, if you did not have too many PI interfaces relying on ccBPM, then I would really consider the more future proof migration to PO single stack.

    Best regards


    Add comment
    10|10000 characters needed characters exceeded

  • May 12, 2017 at 07:41 AM

    Hi Gareth,

    The migration tool can be helpful for dual stack as well is you want to migrate the classical configuration to the ICO object, this kind of configuration is better than the classical way. I have worked in the two kind of migrations, for PI developer perspective is quicker the first option, however when you have all the SLD, ESR and ID objects migrated you have to test all your scenarios. The main problems can be the User defined functions, java mappings and the XSLT mappings. The jvm changes and the XSLT mapping in PI 7.0 was done with SAP API and in Pi 74 is better to do it the proper java API. Depending the migration, you can have problems with firewalls, https certificates and so on. Also, you should check the effort of adaptation the old scenario, for example, i had scenarios with SFTP that i've done with java mapping, but in PI 7.4 there is an adapter for this, therefore it was better to change the entire scenario.

    Hope this helps.


    Add comment
    10|10000 characters needed characters exceeded

  • Sep 18, 2017 at 08:38 AM

    I kinda second Frank here when voting for PO or AEX (Java Only PI). When you "only" have to deal with approx 20 interfaces this would well worth considering.

    On the other hand, giving that low footprint of your integration landscape you are probably still on a volume based contract and might be better off financially staying on that. PO will then be a more expensive offer because licensing there is offered on a per CPU model. PO probably being more future proof but offering stuff that you probably would not need anyways (like B2B adapters or BPM and BRM).

    PI AEX might be a sweet spot product for you there but you will need to discuss licensing with your sales rep first, to make sure you have all the information first before making a decission



    Add comment
    10|10000 characters needed characters exceeded