Skip to Content
Author's profile photo Anil Veepuri

SAP tool to migrate dual stack ID objects to Integrated Configuration Objects (ICO) – PI 7.3 EHP1, SP07

Here comes the revolutionary tool from SAP that can migrate all your dual stack ID objects to Java only ICO objects. Yes, really a true hassle free business converting the dual stack configuration objects to java only objects.

This is possible only from SP07 of PI 7.3 EHP1.

In order to access the tool, PI instance has to be SSL enabled in the first place.

SSL enabling of your PI 7.31 Server.

Secondly, 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/

You end up arriving at the below screen.


Scenario Migration

This is basically used to migrate all the objects that correspond to a complete Configuration Scenario.


This is used to configure the Systems that are used in the integration and the Renaming rules that you want to use to rename the objects like Communication Channels, Business Components, Party and Routing Expressions etc.

Channel Migration

Used for migrating the communication channels.

Let’s how the migration is being done in each of the above cases.

Scenario Migration

The complete Configuration Scenario Migration is done based on the Sender Agreement (Receiver Determination if a Sender Agreement doesn’t exists as in the case of IDOC or PROXY). The tool gets all the objects of the complete configuration scenario by traversing through the Sender Agreement (Receiver Determination) till the Receiver Agreement of the respective configuration scenario.

Once you enter Scenario Migration, you will get the below screen in which you find the corresponding steps to be carried out.


In System Selection, you need to select the source system (in which you have all your classical dual stack based configuration objects) and the target system (in which you want to create the ICO objects for the respective source ID objects).

After providing the details, you move on to Scenario Selection where you need to select a Sender Agreement / Receiver Agreement (individually or all that exist in a particular configuration scenario). After migration, the respective IDOC AAE and the SOAP AAE will be created automatically.

Once you move on to the next option, Scenario Matcher, the tool validates whether all the involved objects can be migrated to an ICO in the target system.

Next is the Preview and Renaming. Here you can preview all the corresponding objects.  You can rename the objects if you want using the renaming rules that we create as part of the Configuration migration. You can also check the adapter engine for the communication channels as part of this task. And as a result, all the ABAP based receiver communication channels will be transformed to JAVA based communication channels (ABAP IDoc to JAVA IDoc, ABAP XI to JAVA SOAP and ABAP HTTP to JAVA HTTP).

And finally, Object Creation. This creates all the objects and will be associated to a change list. You can view this change list in the target system’s integration Directory and can activate the same.

Configuration Migration

Configuration Migration is used to configure the systems that can be used as the source systems (you can select the available systems or you can add manually) and also to create any renaming rules for renaming the objects like Communication channels, Business components, Party, and Routing expressions.


Renaming the business systems still depend on the transport targets that were defined in the SLD.

Channel Migration

We go for this option when we want to migrate many channels from one system to another.


Populate the source and destination system details and move on to the next step.

Choose all the communication channels that you want to migrate. And click on Next.

In the Object Creation, you will confirm to create the objects in the target system. All the objects will be created and associated with a change list in the target system. Log into the target system, change the details and activate them.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Diego Gabriel
      Diego Gabriel

      Thanks for sharing, Anil.

      A really helpful tool!!!


      Author's profile photo Ravi Prakash Raika
      Ravi Prakash Raika

      Nice Blog.

      Author's profile photo Michal Krawczyk
      Michal Krawczyk

      hi Anil,

      SAP has already posted the same document a few months back

      with a bit more details - any chance you could change your article to show maybe only non document things in the previous one ?

      Thank you,


      Michal Krawczyk

      Author's profile photo Anil Veepuri
      Anil Veepuri
      Blog Post Author

      Hi Michal,

      I dint notice this and I was very excited about the new feature of SP07 and hence I had created this blog. I think there is nothing much I can update on this front as the previous blog has already provided detailed info. But, I can add the reference of the SAP blog in mine.


      Anil Kumar Veepuri

      Author's profile photo Rashmi Joshi
      Rashmi Joshi

      Nice blog Anil..Let me tell u wat i got frm this blog...correct me if i'm wrong..

      This blog explains tht we cn migrate dual stack objects like in ESR or ID objects into stigle i.e. java stack...right??Can u please tell me why one will want to migrate dual stack objects in to java stack??and wat is ICO objects??



      Author's profile photo Evgeniy Kolmakov
      Evgeniy Kolmakov

      Hi Rashmi!

      With the integrated configuration you specify the configuration settings in which the message from the Advanced Adapter Engine are to be processed.

      In this case you can specify all configuration settings simply in one single object.

      In case of ICo Integration Engine is not involved - all processing takes place in AAE.

      Regards, Evgeniy.

      Author's profile photo Rasav Malhotra
      Rasav Malhotra

      Hi Anil,

      Earlier SAP has mentioned that it won't work for scenarios those don't have sender agreement like idocs and XI adapter. but u have mentioned that we can work using receiver determination.

      have you tried that also ? Is it working fine ?

      And how we can deploy this tool and is there any connection required between 7.10 to 7.31 ??

      Author's profile photo Former Member
      Former Member

      We are currently on PI 7.11 and have a new parallel system installed with PI 7.4 single stack only. I see no tool or wizard to move Dual stack PI 7.11 objects to PI 7.4. So do I need to upgrade to PI 7.31 EHP1 and then move objects from 7.31 EHP1 to NW 7.4 via the tool provided in NW 7.31 EHP1

      Author's profile photo Andreas Job
      Andreas Job

      Not necessary to go so complicated.

      You should find the tool on your 7.4 system. You always run the tool on the target system for the migration. It should be available in all 7.4 SPs.

      Author's profile photo Srikanth E
      Srikanth E

      I recently did our migration from PI 7.11 to a new parallel system installed with PI 7.4 single stack. Just follow the link mentioned in the blog https://<host>:<port>/webdynpro/resources/ you'll be directed to Migration Tool Integration Directory page. For there move Communication channels 1st and then Configuration Scenario's.

      Author's profile photo Anis Pasha
      Anis Pasha

      Please provide document as we are going to migrate from SAP PI 7.31 to SAP PO

      Author's profile photo Former Member
      Former Member

      Thanks for sharing,'s  helpful to me