Skip to Content
User Experience Insights
Author's profile photo Suresh Gunji

Changing i-flow name permanently in SAP CPI/HCI


In this blog post you will learn how to change the i-flow name permanently in CPI. I am sharing my inputs which I had gone through while I was doing this.

Let’s consider that you have an i-flow and you want to change the i-flow name. There are two ways to change the i-flow names. So, that in UT & SIT(Unit & System Integration Testing) also flow name will be changed permanently.

Let’s have a look on both ways


Consider you have a package “Test123” and in that package we have an i-flow named “Technical_Data_Integration”. Now, click on Actions


After that click on metadata then you will see the below screen

Now, click on Edit to change the i-flow name

After changing the name we can do save/save as version of the i-flow

Now we are able to see that i-flow name have changed successfully.

But when we deploy/test this i-flow the ID will not be changed. See, the below screenshot of i-flow name and Id is different. You can check as I have highlighted the ID. But this both needs to be same to perform the UT/SIT.

To change the ID also to i-flow name we have another process that is 2nd way. Let us see that now


Go to the i-flow and click on Actions. Now click on Download option. When we have clicked on download option. It will show a dropdown to download as per need. But, always we have to select Merged Configured and Default Values and then we have to click on download.

Now a ZIP folder will be downloaded as shown below.


Next, we have to go to the folder location and we need to rename the folder to the i-flow name which we wants to change. So, I have renamed it as per need.


Now without extracting that ZIP file open it. After that go to META-INF folder


In that META-INF folder, we have MANIFEST.MF file. Open that file with whether Notepad or Notepad++ or WordPad or any supported app on your PC. I’m opening it with Notepad.


Once you opened the MANIFEST.MF file we need to change the flow name at 4 places which I have highlighted in the below screenshot and changed it as per need.



After changing the names save that file with the existing name in any other folder. Later copy that file and paste it under META_INF folder.



When we try to paste that MANIFEST.MF file it will show like above. We have to select Copy and Replace option. After copying that file under META_INT folder click (Ctrl+S) to save it in that folder/ZIP file.

After this open your package and click on Add dropdown and now click on Integration flow. Now, we need to select Upload option and click on Browse and should upload that Renamed ZIP file.



After uploading the ZIP file click on OK. Now, the i-flow name have been changed successfully. Now Deploy/Test this i-flow. You can see now the ID and deployed i-flow name is same. So, to change the both i-flow name and technical id permanently we have to follow this process.




So to conclude this blog post helps you in changing the i-flow name & technical ID in SAP CPI.

If you have any queries please feel free to ask a question in comments. I would request everyone to provide your feedback and like if this blog post finds helpful for you.


Thanks & Regards,



Assigned Tags

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

      Great Suresh! We would like to see more blogs from you. All the best!

      Author's profile photo Suresh Gunji
      Suresh Gunji
      Blog Post Author

      Sure, Thanks Abhishek.

      Author's profile photo Avinash Paul
      Avinash Paul

      Thank you Suresh for the insightful blog. Keep posting

      Author's profile photo Suresh Gunji
      Suresh Gunji
      Blog Post Author

      Sure, Thanks Avinash

      Author's profile photo Barath Vivekanandan
      Barath Vivekanandan

      Thanks for the blog! Nice to know this trick.

      What's wrong/con in below way?

      Click on the actions tab of the iflow and click on copy and rename it and then delete the old one. In this case, you will have both name and id changed.





      Author's profile photo Pavan G
      Pavan G

      Hi Barath Vivekanandan ,

      I was curious after reading your comment a couple of days back. I tried it out and didn't face any issues in doing so.

      I did even create TRs using TMS. But the TR failed with the uniqueness and ended with a Fatal Error as below:


      CTS+ process failed. Error: "Content deployment for module "<PackageName>" to resource "process_integration_transport_instance_mtls" failed: CPI deployment failed: "


      I could find 2 resolutions to fix this Fatal error:

      • Performing the activities as suggested by Suresh Gunji  in this blog in the lower environment and creating transporting them
      • Deleting the artifacts in the higher environment and reimporting the TRs in TMS

      I think in most cases, the second option is the least preferred one.

      I hope this helps.