Sap Solution Manager 7.2 Cts+ Configuration
Environment.
For our example:
SAP PO on NetWeaver 7,5 (Client: 000)
Dual-stack SAP Solution Manager* 7.2 (Clients: 000 and default)
* SAP Solution Manager – Transport domain controller for CTS+
Resolution without CTS+
You can transfer non-abap objects in SAP PO via export/import* design objects (TPZs files)
* Export from Dev system, Import to QAS/PROD systems.
This resolution may be not applicable for many (especially for GMP-based) companies
Resolution with CTS+.
CTS+ provides an option to transport non-ABAP objects within a system landscape. This means, objects that have been created on the development system can be attached to a transport request (good management, clear footprint), which is then distributed through the system landscape to QAS and PROD systems.
Step 0. Architecture overview.
Describe our CTS+ architecture via such a blueprint
Let's implement this architecture in Steps
Step 1. Users and Roles preparation
1.1. Roles preparation in Solution Manager.
In Solution Manager (default client)
In transaction PFCG copy role SAP_BC_TRANSPORT_ADMINISTRATOR to ZSAP_BC_TRANSPORT_ADMINISTRATOR
and SAP_CTSDEPLOY to ZSAP_CTSDEPLOY
1.2. Create users in Solution Manager.
Create technical users in Solution Manager (default client) for example CTSSRVUSER.
Assign role ZSAP_BC_TRANSPORT_ADMINISTRATOR from step 2.1 to this user and user
CTSD_RFC. Assign role ZSAP_CTSDEPLOY from step 2.1 to this user.
1.3. Create users in SAP PO.
Create a technical user in SAP PO (DEV, QAS, PROD systems) for example CTSSRVUSER_PO
SAP NetWeaver Administrator -> Configuration ->Identity Managment
Create user:
CTSSRVUSER_PO
Roles:
SAP_XI_CMS_SERV_USER
SAP_XI_DEVELOPER_J2EE
SAP_XI_CONFIGURATOR_J2EE
Step 2. Configuring Transport domain controller for Non-ABAP System
Transaction – STMS (Transport Management System)
2.1. Goto Solution Manager (000 – client)
2.2. Open STMS transaction
2.3. Create Non-ABAP Systems (In our example – DEV, QAS and Production systems of SAP PO)
SAP PO DEV (Source System) Settings:
Activate Transport Organizer = checked
Target host – SAP PO Dev host
System/Client = Solution manager SID, default client in Solution Manager
SAP PO QAS/Prod (Target System) Settings:
Activate Deployment Service = XI/PI
Activate Transport Organizer = checked
System/Client = Solution manager SID, default client in Solution Manager
Target host = SAP QAS/Prod host
System No. = Instance number
Depending on the deployment methods selected, the system asks you for the users and passwords for the selected deployment methods. Enter here credentials from CTSSRVUSER_PO user from Step 1.3
2.4. non-ABAP Systems
Output example:
2.5. Configuration of non-ABAP systems in STMS transaction
Output example:
where:
TRANSDIR – Directory on Solution Manager host, for example,/sapmnt/trans/
COMMUNICATION_SYSTEM – Solution Manager <SID>
NON_ABAP_WBO_CLIENT – * (All Solution Manager clients allowed)
DEPLOY_DATA_SHARE – Directory on Solution Manager host, for example,/sapmnt/trans/data
DEPLOY_XI_URL – SAP PO host with port (port – 5<NN>00, where NN instance number)
WBO_GET_REQ_STRATEGY = SMART*
* – WBO_GET_REQ_STRATEGY= Control of automatically creating a transport request when you export an object, for example, from an SAP Enterprise Portal system or an SAP PI system. The system automatically creates a transport request (if no request has already been preselected) and flags it as the preselected request.
Links:
Parameters for Non-ABAP Transports
2.6. Create transport route in STMS transaction
Create transport route for example ZDPI
SAP PO Dev -> SAP PO QAS -> SAP PO Prod
Step 3. Activate and Test Services
Transaction – SICF (Activate and Maintain Services)
Solution Manager (000 or default client)*
* SICF is a cross-client transaction
3.1. Activate Services
Activate:
CTS_BROWSER
CTS_ORGANIZER
CTS_ORGANIZER_OBJECTLIST
CTS_ZENUI_TRANSPORTS
CTS_ZENUI_ENTITY_QUEUE
CTS_IMPORT_HISTORY
CTS_START_DEP_CHECK_APP
CTS_GENERAL_CONFLICTS_APP
CTS_FULL_CONFLICTS_APP
CTS_LOGVIEWER
CTS_OBJECTLIST_BROWSER
3.2. Test services
Test services from step 3.1
Step 4. Maintain Web service in Solution Manager
Prerequisite:
From NetWeaver 7.1 Logical Port CTSDEPLOY already preconfigured and there is no need to validate it in the transaction LPCONFIG (obsolete transaction)
4.1. Configuring the HTTP Connection
Goto Transaction SM59 in Solution Manager (default client)
Create HTTP Connection to External Server (Type – G)
RFC Destination – CTSDEPLOY
Target Host – For our dual-stack system target host = the hostname of the current system.
Service No – 5<NN>00, where NN – instance number for Solution Manager, Java Stack
Logon & Security – Credentials from user CTSD_RFC from Step 2.2
Step 5. Settings in SAP PO systems
5.1 Create Destinations in SAP NetWeaver Java System (DEV, QAS, Prod systems)
SAP NetWeaver Administrator -> Configuration -> Destinations
Connection and Transport:
RFC Destination – sap.com/com.sap.tc.di.CTSserver
Target Host – Solution Manager host
System – Solution Manager ABAP instance
System ID – Solution Manager <SID>
Gateway Host – Solution Manager host
Gateway service – sapgwNN, where NN instance number
Logon Data:
Credentials from CTSSRVUSER from Step 1.2
Output must be:
Ping Destination -> Successfully connected to <SID> as user CTSSRVUSER
5.1 Configure CTS+ parameters for SAP PO System (Dev, QAS, Prod systems)
SAP NetWeaver Administrator -> Configuration ->Infrastructure-> Java System Properties
Tab – Services
Filter – *XPI*
Select service XPI Service. All Config Service and check/add properties:
com.sap.aii.ibrep.core.cts.enableCITransport = true
com.sap.aii.ibrep.core.cts.enableTransportWizard = true
com.sap.aii.ibdir.core.cts.enableTransportWizard = true
com.sap.aii.ibdir.core.cts.enableRequestSelection = true
Step 6. Test CTS+ with real business example
Real business example.
The dataType for Materials was changed in SAP PO Development System.
Сhanges must be transferred to QAS and PROD systems
6.1. SAP PO / Enterprise Services Builder. New TR
Open ESR.
Tools – Open CTS Transport Organizer
(in web browser interface)
Create New Request
Specify TR
6.2. SAP PO / Enterprise Services Builder. Export
Open the desired DT and select Export Design Object.
Set mode – Transport Using CTS
Individual objects – DT/MT with changes
Assign Objects with Transport Request
Summary output:
6.3. SAP PO / Enterprise Services Builder. TR Release
Tools – Open CTS Transport Organizer
Specify the desired TR and release it
6.4. SAP PO / Enterprise Services Builder. TR Import
Goto Solution manager (default client)
Transaction – STMS
System – QAS/PROD SAP PO Systems
Import Request
Troubleshooting.
Problem:
The CTS+ option is disabled or it is not visible in Tools -> Export Design Objects
Resolution:
1739340 – ESR/ID Export Using CTS+ option is disabled
Problem:
Error during "Open CTS Transport Organizer in SAP PO ESR"
Resolution:
- Incorrect file association on the local machine with ESR. Check ESR on another machine.
Problem:
Error retrieving JCO destination (check stacktrace for details) [DESTINATION_ERROR_CHECK_STACKTRACE]
Resolution:
1563107 – Error releasing activities to CTS+ (Transport View)
Problem:
java.io.IOException: Cannot create temporary directory./temp/CTS/XXXXX
during TR import
Resolution:
2343548 – CTS+: java.io.IOException: Cannot create temporary directory
and
2453088 – Deploy fails with "access is denied" error
Conclusion.
SAP BASIS Routine task with examples from real life was provided
In Part 2. Configure CTS+ for SAP HANA systems. SolMan 7.2 as a domain. Step by step guide (coming soon)
Links.
1540191 – Application types: Handling and reservation mechanisms
1003674 – Enhancement for non-ABAP systems in CTS
1540191 – Application types: Handling and reservation mechanisms
Transporting Non-ABAP Objects in Change and Transport System
Configuration Guide for CTS+
How To… Implement CTS+ for Your Application
Enhanced Change and Transport System
Transporting Objects from SAP NetWeaver XI by Using CTS
Security for the Enhanced Change and Transport System (CTS+)
Sap Solution Manager 7.2 Cts+ Configuration
Source: https://blogs.sap.com/2020/10/07/configure-cts-for-sap-po-system.-solman-7.2-as-a-domain.-step-by-step-guide/