Real-Time step by step PO to CPI Migration

 As organizations move towards cloud-based integration platforms, migrating from SAP Process Orchestration (PO) to SAP Integration Suite (CPI) becomes essential. This blog will walk you through the key steps of this migration, focusing on:

●     Connecting SAP PO to SAP Cloud Connector And adding SAP PO in SAP Integration Suite (CPI)

●    Importing Message Mappings from SAP PO

●     Importing dependent objects of the Message Mapping, such as Imported Archives and Function Libraries

 

Step 1: Connecting SAP PO to Cloud Connector

Since SAP PO is an on-premise system, we use SAP Cloud Connector to securely connect SAP CPI (cloud) to the SAP PO environment. The Cloud Connector acts as a secure tunnel between cloud applications and on-premise systems without exposing them directly to the internet.

1.        Install SAP Cloud Connector on the same network as SAP PO (for testing install on your system).

2.        Connect Cloud Connector to your SAP BTP subaccount (SAP CPI tenant). Establishing a Connection Between Cloud Connector and Subaccount

3.        Login to the SAP Cloud Connector and select the subaccount and click on Cloud to On- Premises.   

  Add the SAP PO System Cloud Connector. Back-end Type:  ABAP System

    Protocol: HTTP

Internal Host: *PO Sytem Host Name without http://* Internal Port: *PO Sytem port*

Virtual Host: *Enter a desired virtual hostname. This will be used when connecting from Integration suite.*

Virtual Port: *Enter a desired port* Allow Principal Propagation: check 

Principal Type:Kerberos

Host in Request Header: Use Virtual Host Next ==> Next==>Check Internal Host: check Finish

  

 

  Add resources path by clicking on the + icon and enter / select Path and all Sub-Paths ==> Save. 

Check whether the added SAP PO system is reachable.

If it's not, cross-check the host and port. Ensure that both the SAP PO system and the Cloud Connector are accessible through the same network. 

Now we have successfully connected to SAP PO system from SAP Cloud Connector.

Step 2: Connecting SAP PO to SAP Integration Suite(CPI) Through SAP Cloud Connector

1.        Login to the Integration suite, Go tosettings ==> Integrations==> select System Tab==> click on + to add the SAP PO Sytem.

 

 

Enter the details of System Overview and Integration Directory.

In the Address box, enter the Virtual Host and Port with http://, as maintained in the Cloud Connector.

If your PO System uses the same address for both the Integration Directory and the ES Repository, check the corresponding checkbox       . Otherwise, specify them separately.

Test the connectivity between Integration suite and SAP PO system.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Now we have successfully connected to SAP PO system from Integration suite.

Step 3: Importing Message Mappings from SAP PO to SAP CPI

1.        Login to the Integration suite and go to your package and click on Add message mapping. Selcet ES Repository and select the added SAP PO System and connect.

2.       

3.   

Select the required message mapping and click on next.

4.       

5.   

To import Message mappings there are some prerequisites:

Based on your message mapping, you may have dependent resources such as a Function Library, Imported Archive, WSDL, or XSD.

WSDL and XSD files are imported automatically along with the message mapping. However, Function Libraries and Imported Archives must be imported separately.

 

After selecting the message mapping, you will be able to see the list of dependent resources. You must import the required resources (Function Library and Imported Archive) first; otherwise, the message mapping cannot be imported successfully.

4.

●     Importing Dependent Objects: Function Libraries

○     Create a function library artifact, click on "Upload," connect to the SAP PO system, select your function libraries, save, and then deploy.

○    

●  

Create a Imported Archives artifact, click on "Upload," connect to the SAP PO system, select your Imported Archives, save, and then deploy.

 

○    

○  

4.       Since the dependent objects have been imported, we can now import the message mapping. Add the message                                                      mapping artifact, select the ES Repository, choose the added SAP PO system, connect, select the message mapping,               click "Next," and then select the dependent objects that were imported as separate artifacts.

5.      Click on "Select" and choose the required function library artifact.

G. If the status shows "Already Existing," click on it and select "Reuse Existing Resource.

 

 

7. Next, click on "Select" and choose the required imported archive artifact. Then, click "Submit" to import the message                       mapping.

8.  Now the Message Mapping is successfully imported to Integration suite from SAP PO system.

 

 

Conclusion

Migrating from SAP PO to SAP CPI goes beyond a simple technical shift—it’s an opportunity to modernize integration landscapes, adopt cloud-first patterns, and leverage the flexibility of SAP BTP. By carefully setting up connectivity through the Cloud Connector, systematically migrating

message mappings, and addressing dependencies like archives and function libraries, you can ensure a smooth and reliable transition.

A phased migration approach, combined with thorough testing and best practices, will help minimize risk and maximize value. This journey not only preserves existing investments but also sets the stage for future-ready integrations.

Stay tuned for my upcoming blogs, where I’ll deep dive into adapter migration strategies and lessons learned from real project experiences.