Transport Management with in the SAP cloud solutions has been one of the pain point during implementations. Though solution profile copy is provided by SAP to move the business configuration across tenants for C4C implementations, it doesn’t provide uniform approach for other objects like page layouts, extension fields business roles, form templates etc., Implementation partners/System integrators are often facing challenges to move the implementation content and developments across tenants within the project environment. This has been addressed by SAP by providing transport management capability where in admins are now able to create transport requests that allows movement of development objects and application specific content between tenants. Though it is not exhaustive solution that supports all objects currently, we can expect the same in future releases.
Transport Management was introduced in C4C in 1805 release as Beta version and as of 1808, below objects are supported for Transport Management.
- Adaptation changes
- Local Form Templates
- Language Adaptations
- Business roles
- Add-on solutions – currently Beta version is available and this will be available in the next release. Some of the important considerations are given below
- Solutions which are assembled in advance in the Cloud Applications Studio are available for selection.
- Users with PDI developer role are only allowed to activate and transport add-on solutions.
- The Add-on solution in the target system must be on a lower version than the Add-on solution in the source system
Below table provides some of the inclusions/exclusions.
|01 – Adaptation changes||
Below subtypes are supported
· 101 = Extension Fields
· 102 = Layout Changes
· 103 = Page Layouts
· 104 = Instance Types
· 105 = Code List Restrictions
· 106 = Analytical Content
· 107 = UI Components
|06 – Business Roles||
Exceptions: Below data is not supported as of now
· UI Switches
· Extension Field Restrictions
· Notes History
· Responsible Identity
· Restriction rule 99
· User Assignment
Steps for Transport Management
1. Create Transport Route
Select Create Transport Route under Service Control Center. By default, system will take the login system as the source and select the target system to create the Transport Route.
2. View Transport Routes
Click on the System ID to view the existing transport routes for the system. If the selected system is currently logged on system then all the systems connected to the system are displayed.
3. Create Transport Request
The path to create transport request is Administrator>Transport Management
Select NEW to create Transport Request as shown below
Select Transport objects
Add selected/All transport objects from available list
Select Target Systems
Perform Assemble and Release actions for TR
Actions> Assemble to trigger a background job and collect all the active objects and package it in the transport request. The status of TR changes from NEW to ASSEMBLED.
Actions> Release to trigger the transfer of the transport request to the target system. Here the status changes from ASSEMBLED to IMPORTED
4. Activate the TRs in the target tenant
Log on to the target system as an administrator. Find and open the transport request that you previously created (in the source tenant) under Transport Requests Ready for Activation.
Select the TRs and Click Activate under Actions. This triggers the deployment of the changes in the target system in a background job. The Transport Status now changes to Activated.
5. Check the logs under Transport Logs under TR
Finally check the TR status and transport logs to see the Log Item Severity and the Log Messages. The Transport Content tab displays the zipped content of all transported changes.
For your quick reference, statuses of Transport Requests are given below
|Status values for local Transport Requests||Status values for Transport Requests that are not local (Target System)|
New – Indicates a new transport request (target systems and transport objects may have already been assigned, but the assembly has not yet started)
Assembly Started – Indicates that the assembly process has started and is currently running as a background job
Assembled – Indicates that the content of the assigned transport objects is collected and packaged in the transport object
Assembly failed – Indicates that an error occurred during the assembly process. The transport log lists the details of the error.
Released – No further changes can be made to this transport. Transport is released to a target system. However, you can still add additional target systems and the assembled content is sent to those systems as well.
Assembled with Warnings – Indicates that only some of the assigned transport objects were successfully assembled. The transport log lists the details
Imported – Indicates that the transport request is received from the source system and is created in the target system
Activation Started – Indicates that the activation process has started and is currently running as a background job
Activation Failed – Indicates that an error occurred during the activation process. The transport log lists the details of the error.
Partially Active – Indicates that only some of the assigned transport objects were successfully. The transport log lists the details.
Activated – Indicates that the activation is successful.