🚀 Configure and Test Cloud Transport for SAP CPI – Step-by-Step Guide

Cloud Transport Management Service (TMS) in SAP BTP provides a structured, secure way to transport CPI (Cloud Integration) artifacts across different environments such as Development, Test, and Production. In this blog, you’ll learn how to configure TMS and test the transport of an integration flow (iFlow) between subaccounts.

🧭 Prerequisites

• Access to SAP BTP Cockpit
• Two Subaccounts: One for Source (Dev) and one for Target (Test/Prod)
• SAP Integration Suite (Cloud Integration) is enabled in both subaccounts
• Entitlement and service plan for Transport Management Service (TMS) is available

🌐 Step 1: Understand the Use Case

Tutorial Reference

SAP TMS supports CPI transport scenarios where artifacts are moved between:

• Source Subaccount (Developer creates the artifact)
• Target Subaccount (Used for testing or production)
• Cloud Transport Management Subaccount (CTMS) (Manages transport centrally)

🛠 Step 2: Set Up the Source Subaccount

Tutorial Reference

1. Enable the following in the Source Subaccount:
   • Cloud Integration
   • Transport Management Service
2. Create a TMS Instance (with service plan default)
3. Assign required roles to your user:
   • AuthGroup.Administrator
   • IntegrationDeveloper
4. Generate a Service Key from the TMS instance

🎯 Step 3: Set Up the Target Subaccount

Tutorial Reference

1. Enable Cloud Integration in the Target Subaccount
2. Assign necessary roles such as IntegrationDeveloper
3. Create a Cloud Integration Service Instance if needed
4. Ensure both source and target subaccounts are linked to your global account

🔗 Step 4: Connect Source and Target via Transport Management

Tutorial Reference

1. In the TMS UI, create Transport Nodes for:
   • Source (Dev)
   • Target (Test)
2. Create a Transport Landscape and a Sequence (e.g., Dev ➡ Test)
3. Assign the nodes to the sequence

🌉 Step 5: Create CTMS Destination in Source Subaccount

Tutorial Reference

1. In the Source Subaccount, go to Connectivity > Destinations
2. Create a new destination named: TransportManagementService
   • Type: HTTP
   • Authentication: OAuth2ClientCredentials
   • Use credentials from the TMS service key
   • Set the correct URL and Token Service URL

✅ Step 6: Enable Transport in Source CPI

Tutorial Reference

1. Open SAP Integration Suite (Source)
2. In your Package or iFlow, click on Configure Transport
3. Choose:
   • Transport Type: MTAR (recommended)
   • Landscape and Node: As defined in Step 4
4. Save the configuration

🧪 Step 7: Test the Transport

Tutorial Reference

1. In Source CPI, export the artifact using the transport option
2. Open Transport Management UI
3. Navigate to the Import Queue for the target node
4. Select the artifact and click Import
5. Confirm that the iFlow/package appears in the Target CPI system

🎉 Conclusion

With this setup, you’ve established a complete transport pipeline for your CPI artifacts using SAP’s Cloud Transport Management. You can now:

• Move artifacts across subaccounts in a structured manner
• Enable lifecycle management for your integrations
• Maintain audit trails and version control

Happy transporting! 🚛💨

Have questions or tips? Share them in the comments below or connect with me on LinkedIn.

Click here to read – Upgrade Your Integration Strategy in BTP