PUBLIC

Document Version: Draft – 2023-12-18

Change Control Management

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Change Control Management - Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Initial Setup for the SAP Solution Manager System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1 Master Data in SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Authorizations and Business Roles, Security Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

3 Change Control Management User Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.1 Change Management Launchpad Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Change Control Management in the WebClient UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Using the Search Function in the WebClient UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
The “My Messages” Widgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Including Custom Fields in the WebClient UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Change Request Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

4.1 Basic Terms and Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Roles in Change Request Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Transaction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Task List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.2 Processing Change Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Processing Requests for Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Processing Normal Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Processing Urgent Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Processing Standard Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Processing Defect Corrections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Processing Administrative Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Processing General Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Processing Git-enabled Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Processing Continual Cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Processing Phase Cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Processing Release Cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Withdrawing Change Documents with Solution Documentation Elements. . . . . . . . . . . . . . . . . 112
4.3 Functions in Change Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Specifying the Processor in Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Assigning Reference Objects (IBase). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Adding Text and Reusing Text Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Managing Transport Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Performing Transport-Related Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Monitoring the System Landscape, Transport Status and Transport Risks. . . . . . . . . . . . . . . . . 166

Change Control Management

2 PUBLIC Content
 PPF Actions in Change Request Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Changing the Transaction Status with PPF Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Sending E-Mails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
Processing Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
Application Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Warnings and Errors in Change Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Creating Follow-Up Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Copying Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Time Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Solution Documentation Assignment Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Test Management Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Assigning SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Using Checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Opening the IT Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Project Management Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Configuration Check for Change Cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Creating Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Redefining a Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Closing Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Editing Job Scheduling Change Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
4.4 Advanced Features of Change Request Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Adapting the WebClient UI: Personalization and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 280
Rule Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Approval Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
E-Mail Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Multilevel Categorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Administration Cockpit for Change Request Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Dual Landscape Synchronization (Retrofit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Downgrade Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Cross-Reference Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Assigning a Change Document to Transport Requests Created Outside SAP Solution Manager
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Import Strategies: Standard, Status-Dependent, and Selective. . . . . . . . . . . . . . . . . . . . . . . . 396
Managing Changes for Non-ABAP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Change Control Management Using Central CTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Change Control Management Using SAP Cloud Transport Management . . . . . . . . . . . . . . . . . . 448
Configuring Git-enabled CTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .455
Release Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Customizing Solution Documentation Integration for Upgrades. . . . . . . . . . . . . . . . . . . . . . . . 462
Configuring the Notification Framework of SAP CRM for Change Request Management. . . . . . . 470
Linking IMG Projects to Change Cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .473

Change Control Management

Content PUBLIC 3
4.5 Configuring Change Request Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
4.6 Reporting in Change Control Management - Change Request Management. . . . . . . . . . . . . . . . . . 476

5 Quality Gate Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

5.1 Change Management Using Quality Gate Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479
Phases in Quality Gate Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Quality Gate Management Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
5.2 QGM Scenario Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Setting Up Quality Gates and Assigning Phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Checking the Quality Gate Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Change Cycles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .493
Changing the CTS Status Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Application Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Using the Search Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
5.3 QGM Data for a Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Calendar View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Landscape View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Risks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Transport Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Overview of Scheduled Import Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .530
Transport-Related Checks in QGM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Opening the IT Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
5.4 Closing Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
5.5 Administration Cockpit for Quality Gate Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Task Lists Tab for Quality Gate Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Landscape Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .541
Defining Critical Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Creating Cross-System Object Lock Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Cross-Reference Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Transport Analysis Tab for Quality Gate Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Scheduled Import Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
5.6 Dual Landscape Synchronization (Retrofit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Retrofit Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .554
Retrofit Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Additional Functions in Retrofit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Performing the Retrofit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Tool-Assisted Retrofit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Setting Up Retrofit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Standalone Retrofit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571

Change Control Management

4 PUBLIC Content
 SAP S/4HANA Upgrade Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
5.7 Downgrade Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Cross-System Object Lock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Downgrade Protection System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Release Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588
Reassign Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Predecessor Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .591
Imminent Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Delta Downgrade Protection Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Import Groups in Downgrade Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Conditions for Ignoring Transport Conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Using the CTS Plug-In Management Web UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
5.8 Managing Changes for Non-ABAP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .608
5.9 Change Control Management Using Central CTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Central Change and Transport System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
5.10 Enhanced Transport Functions with Central CTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

6 System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658

Change Control Management

Content PUBLIC 5
1 Change Control Management - Overview

Change Control Management provides a comprehensive workflow to control and document changes in system
landscapes. You can request changes, implement, and test them. You can perform change control activities
across technology stacks and application components.

You access the Change Management launchpad group on the SAP Solution Manager launchpad in your web
browser.

Features

In Change Control Management, you use either Change Request Management or Quality Gate Management
(QGM) to manage the change control process and provide the user interfaces. For both options, the Change
and Transport System provides the technical infrastructure.

Change Request Management

Allows you to process your projects universally in SAP Solution Manager: From change management and
project planning, through resource management and cost control, to the physical transport of the changes
from the development environment into the production environment.

Quality Gate Management

Provides a phase-based overview of the status of your software changes. Each of the phases ends with a quality
gate. When a quality gate is released, the import lock is removed and an import into subsequent systems is
possible.

Change and Transport System

Moving developments and changes across a system landscape requires the management of transport. In
response to this need, SAP offers the Change and Transport System (CTS) for ABAP transports and the
Enhanced CTS (CTS+) for non-ABAP as well as non-SAP applications.

The evolution from CTS to the enhanced CTS (CTS+) for non-ABAP and non-SAP content led to the
requirement to manage transports across technology tracks, which is supported by a new central transport
foundation layer known as central CTS (cCTS). The central Change and Transport System provides enhanced
flexibility functions in Change Control Management. If you activate central CTS for your change cycle, several
functions in Change Request Management and Quality Gate Management have enhanced features. For each
new change cycle, you can decide whether you want to use CTS or central CTS.

Change Request Management also supports the Git-enabled Change and Transport System (gCTS), with
which you can use Git as version control system for your ABAP system landscape. Note that Git-enabled CTS
does not support central CTS.

SAP Cloud Transport Management

SAP Cloud Transport Management is the lifecycle management tool for SAP Cloud development. It controls the
content transport between different tenants.

Change Control Management

6 PUBLIC Change Control Management - Overview
Related Information

SAP Fiori Launchpad

Change Request Management [page 21]
Quality Gate Management [page 478]
Change Control Management Using Central CTS [page 399]
Change Control Management Using SAP Cloud Transport Management [page 448]

Change Control Management

Change Control Management - Overview PUBLIC 7
2 Initial Setup for the SAP Solution
Manager System

After the basic setup for SAP Solution Manager, you need to perform certain steps to enable Change Control
Management.

Prerequisites

• You have the necessary authorizations.

• On the SAP Solution Manager system and the managed systems, the required releases and support
packages are installed.
• On the SAP Solution Manager system, the Transport Management System (TMS) has been configured.
• The managed systems are registered on the System Landscape Directory (SLD).
• The service connection to SAP Support Portal has been set up.
• In SAP Solution Manager Configuration (SOLMAN_SETUP), you have performed the setup procedures
System Preparation, Infrastructure Preparation, Basic Configuration, and Managed Systems Configuration.
• The standard background jobs are scheduled.

Context

In SAP Solution Manager Configuration (SOLMAN_SETUP) scenario Change Control Management, you perform
the following setup procedures:

• To configure Change Request Management, perform the setup procedure Change Request Management for
the SAP Solution Manager system.
• To configure Quality Gate Management, perform the setup procedure Quality Gate Management for the
SAP Solution Manager system.

Regardless of using Change Request Management or Quality Gate Management, perform the setup procedure
Managed Systems Setup for each managed system.

Procedure

1. Check the prerequisites and results of the basic setup.

a. Check the activation of the piece list.
b. Set the client for Change Request Management or Quality Gate Management.
c. Maintain number ranges.

Change Control Management

8 PUBLIC Initial Setup for the SAP Solution Manager System
2. Implement the Collective Note.
3. Optional: Configure Downgrade Protection and Retrofit.
4. For Change Request Management, execute the following steps:
a. Copy and adjust transaction types.
b. Activate the categorization schema.
c. Configure the Webclient UI and master data:
• Business roles and business partners
• Installed Base (iBase) components
• Number ranges
d. Set up reporting.
5. Configure the search infrastructure.
6. Optional: For Change Request Management, you can integrate additional functions and use cases, such as
the following:
• Solution Documentation
• SAP Portfolio and Project Management (SAP PPM)
• Job Management
• My Inbox SAP Fiori app

Related Information

Configuring Change Request Management [page 473]

Downgrade Protection [page 360]
Dual Landscape Synchronization (Retrofit) [page 338]
Multilevel Categorization [page 289]
Assigning Reference Objects (IBase) [page 115]
The “My Messages” Widgets [page 17]

2.1 Master Data in SAP Solution Manager

Before you can start using Change Control Management, you must set up master data such as business
partners, IBase components, and number ranges.

Business Partner

Business partners identify persons, groups, and organizations. Each business partner can have one or more
roles assigned. During the change process, only certain business partner functions, such as “developer” or
“tester”, are authorized to perform defined activities.

Change Control Management

Initial Setup for the SAP Solution Manager System PUBLIC 9
Installed Base (IBase)

IBase components identify objects for which a service is offered, for example, the production system and
client into which the transport request of a normal change must be imported, but also devices, machines,
and software. In total, the IBase describes the system landscape. You can assign business partners to IBase
components to enable the automatic determination of partner functions.

Number Ranges

The number range interval determines the sequential numbers assigned to newly created transactions. Before
you can use specific transaction types, a number range must be defined for these transaction types.

Related Information

Configuring Business Partners

Authorizations and Business Roles, Security Concept [page 10]
Roles in Change Request Management [page 23]
Assigning Reference Objects (IBase) [page 115]

2.2 Authorizations and Business Roles, Security Concept

Business roles and authorizations define which user can see certain UI elements or execute defined activities.

Each user in a business scenario has specified tasks to execute. These business user definitions are mapped to
use case IDs, and authorization roles are defined for the defined tasks. You can use the delivered standard user
roles as templates for your own authorization concepts.

Respecting the principle of segregation of duty, each user in a system gets exactly the authorizations they need
for the tasks they are to execute.

SAP Solution Manager differentiates between users who perform the following actions:

• Configure the SAP Solution Manager scenario

• Administer an SAP Solution Manager system
• Use SAP Solution Manager to manage other systems.

For more information about the user and roles concept, see User and Roles Concept in SAP Solution Manager.

Authorizations for many functionalities and for the WebClient UI are based on CRM business roles. For more
information about the authorization concept and authorization objects, see CRM Authorization Concept in SAP
Solution Manager.

Business roles such as SOLMANPRO determine how the WebClient UI looks like for the user. Authorization
roles (also called PFCG roles) such as SAP_SOCM_DEVELOPER are used to implement a comprehensive

Change Control Management

10 PUBLIC Initial Setup for the SAP Solution Manager System
security concept and protect the SAP system against unauthorized access at database, network, and front-end
level.

 Recommendation

To ensure that changes aren't overwritten during an upgrade, copy the standard business roles and the
authorization roles into the customer namespace.

Learn more about the security concept in the Help Portal for SAP Solution Manager on https://help.sap.com/
viewer/p/SAP_Solution_Manager under Implement Security .

Related Information

Roles in Change Request Management [page 23]

Including Custom Fields in the WebClient UI [page 19]

Change Control Management

Initial Setup for the SAP Solution Manager System PUBLIC 11
3 Change Control Management User
Interfaces

The main user interfaces for Change Control Management are the the Launchpad and the WebClient UI.

The SAP Solution Manager Launchpad ist the common entry point for SAP Solution Manager. In the the
WebClient UI, you perform and document the change process.

For some configuration and for customizing activities, you use the classical SAP GUI to access transactions
such as SPRO (SAP Reference IMG).

Related Information

Change Management Launchpad Group [page 12]

Change Control Management in the WebClient UI [page 15]

3.1 Change Management Launchpad Group

This Launchpad group is the central access point for all the information and functions you need to control
changes in system landscapes in a comprehensive workflow.

Use

The launchpad group comprises different tiles, in which you create requests for change, edit them if necessary,
and implement changes. You can perform the change request management activities across technology stacks
and application components.

Change Control Management

12 PUBLIC Change Control Management User Interfaces
Features

By default, the launchpad group consists of the following tiles:

Tile Description

Change and Release Management You can access the WebClient UI for Change Request Management.

For more information, see Change Control Management in the WebClient UI [page 15].

Administration Cockpit - Change You can access all administrative activities for Change Control Management.
Control Management
For more information, see Administration Cockpit for Change Request Management
[page 291] and Administration Cockpit for Quality Gate Management [page 535].

Change Control Management - You can view and analyze the status of requests for change and change documents in
Analytics the Change Request Management application area.

For more information, see Reporting in Change Control Management - Change Request
Management [page 476].

Quality Gate Management You can monitor all software change processes, distribute software across systems and
technology stacks, and gain an integrated and consistent overview of the implementa-
tion of changes to your SAP software solution.

For more information, see Quality Gate Management [page 478]

Approve Q-Gates and Urgent You can pass, not pass, and reset Q-Gates or approve or reject urgent changes.
Changes
For more information, see Approve Q-gates and Urgent Changes.

License Management - System You can access the distribution of licenses and maintenance certificates maintained in
Overview your system landscape.

System Recommendations You can manage the SAP Notes and support package patches that are not yet imple-
mented and installed on your managed systems.

For more information, see System Recommendations.

SAP Readiness Check You get a pre-conversion overview, useful for identifying current system landscape
preparation steps, well in advance of your SAP S/4HANA system conversion project
start date.

For more information, see SAP Help Portal at http://help.sap.com and search for “User
Guide - SAP Readiness Check for SAP S/4HANA” .

Scope and Effort Analyzer - You can analyze the scope of activities and effort before you start the physical deploy-
Upgrade Planning ment of Enhancement Packages (EHP) and support packages stacks (SPS).

For more information, see Scope and Effort Analyzer.

Change Control Management

Change Control Management User Interfaces PUBLIC 13
Tile Description

Maintenance Planner - SAP You can plan and maintain systems in your landscape. You can plan complex activities
Support Portal like installing a new system or updating existing systems. All changes can be scheduled
to be deployed at a convenient time to minimize downtime.

For more information, see SAP Help Portal at http://help.sap.com and search for “Main-
tenance Planner - User Guide” .

Download Service - Maintenance You can directly fetch the installation archives that you have calculated with the mainte-
Planner nance planner to update, upgrade, or newly install software in your system landscape.

Cross Build Analytics You can trace the whole lifecycle of your projects, IT requirements, change requests and
change documents, test plans and test cases, as well as defects. For more information,
see Cross Build Analytics, under Test Execution Analytics.

The following tiles are not displayed by default:

Tile Description

IT Service and Change You can view the corresponding status of incidents, problems, and changes, so you can
display and analyze the behavior of incidents, problems, and changes in one panel.
Management - Dashboard
For more information, see Reporting in Change Control Management - Change Request
Management [page 476].

Configuration - Change You can perform mandatory and cross-scenario configuration, which are implemented
Management as guided procedures. A scenario consists of several steps. Each step groups a number
of activities to be performed together. While some activities run automatically, other
manual activities require you to execute them.

For more information, see Configuration

Configuration - Dashboard Builder You can display large amounts of information in a concise form. The Dashboard Builder
is a browser-based tool that enables you to quickly create tile-based dashboards in
order to visualize data for analysis.

For more information, see Dashboard Builder

Related Information

SAP Fiori Launchpad

Change Control Management

14 PUBLIC Change Control Management User Interfaces
3.2 Change Control Management in the WebClient UI

The WebClient UI provides general and specific functions for Change Control Management. Your user role
determines what you can access in the navigation bar.

Use

You can start the WebClient UI in the following ways:

• Call transaction SM_CRM

• On the SAP Solution Manager launchpad, in the Change Management launchpad group, select tile Change
and Release Management or Quality Gate Management.

Prerequisites

You have the required authorizations.

Features

You can use the following general WebClient UI functions:

• My saved searches
• Search function
• Start page
• Worklist
• Calendar
• Inbox
• Master data

The following functions are available specifically for Change Request Management:

• Search for change transactions (change documents, requests for change, templates for requests for
change, and change cycles)
You can use various search criteria, for example, the creator, status, document type, or installation.
• Create change transactions (change documents, requests for change, change cycles, and templates for
requests for change)
You can create new transactions and templates directly from the search screen.
• Edit change transactions
• Configure and personalize the WebClient UI

Change Control Management

Change Control Management User Interfaces PUBLIC 15
  Note

Archived objects are not visible in the WebClient UI. For more information about archiving, see the Overview
table in Archiving of Objects.

Related Information

CRM WebClient UI
Functions in Change Transactions [page 113]
Adapting the WebClient UI: Personalization and Configuration [page 280]
Change Management Launchpad Group [page 12]
Getting Started with the WebClient UI

3.2.1 Using the Search Function in the WebClient UI

Use

You can search for messages, change transactions, and requirements on the Search screen of the WebClient
UI. The result of your search is displayed in the result list. A series of search operators is available for the
search. Input help or search help in certain fields also assists you in your search.

You can find general information about the search function on SAP Help Portal at http://
help.sap.com/crm <release> Application Help Getting Started with the WebClient UI Searches .

Features

• Search for All Objects (SAP Netweaver Enterprise Search)

Use this option to search for any kind of transaction type (and its attachments) that is used on the
WebClient UI. From the results lists, you can directly access the object.
This search option uses SAP Netweaver Enterprise Search. For more information, in SAP Help Portal at
http://help.sap.com/crm , search for Enterprise Search.
Configure this search option in SAP Solution Manager Configuration (transaction SOLMAN_SETUP) for the
relevant scenario.
• Central Search
The central search function displays the search menu containing the objects for which you can search.
For example, you can search for messages created on a certain date or for change documents that have a
specific status.
By default, if you combine several search parameters of the same attribute, the system links the search
parameters using logical OR combinations.
• My Saved Searches

Change Control Management

16 PUBLIC Change Control Management User Interfaces
 Use this function to access search queries that you created on the central search screen. To call up your
saved searches, use the My Saved Searches widget.
If "Saved Searches" is set up as the default search option, you can can switch between "All Objects" and
"Saved Searches" and can delete a saved search with the trash bin button on the top right. For more
information, see KBA 2662724

 Note

A saved search is only available to the user who has saved the search; other users cannot see it.
To share your searches with other users, organizational units, positions, or business roles, use the
central sharing tool. For more information, see SAP Help Portal at http://help.sap.com/crm <SAP
Enhancement Package 1 for SAP CRM 7.0 and above> Application Help WebClient UI
Framework Generic User Interface Functions Central Sharing Tool .

• With My Involvement
You can search for objects that have your involvement.
The search retrieves transactions that you are currently processing, have processed previously, or have
created or changed. When you select this search criterion, enter an interval that defines the time of your
involvement.

3.2.2 The “My Messages” Widgets

The “My Messages” widget provides information that is relevant to you specifically, for example, because you
need to take action.

The widgets support object types from Requirements Management (business requirements, IT requirements),
ITSM (support notifications, service requests, incidents, problems), and Change Control Management
(requests for change, change documents, tasks). During configuration, you can select the object types required
for your scenario.

You find the widget on your Home screen in the WebClient UI. Depending on your role, the following widgets are
available:

• My Messages – Assigned To Me: Processors see the messages that are waiting for their action.
• My Messages – For Dispatching: Dispatchers see all messages assigned to their team, and can dispatch
them to a processor.
• My Messages – Action Required By Me: End users see messages that are waiting for their action.
• My Messages – Reported By Me: End users see the messages that they’ve submitted.
• My Messages – Reported By My Organization: A head of a team sees all messages reported by their team.

In each widget (except My Messages – Reported By My Organization), you can assign a colleague as your
substitute, or assign yourself as someone else's substitute.

 Tip

In Change Request Management, you can use My Messages – Assigned to Me as your workflow inbox. The
items are assigned to you when they’ve reached a process status that requires your action.

When you update the status of a change transaction and save it, the business partner is automatically
assigned as Current Processor (SDCD0004) for the new status as defined in the Customizing (transaction

Change Control Management

Change Control Management User Interfaces PUBLIC 17
 SPRO). If a business partner other than you (the current user) has already been assigned as current
processor, this business partner remains the current processor after you save the change transaction.

The current processor can be changed manually. When you open a change transaction in change mode,
you can also specify the current processor.

For example, in a normal change with status In Development, a business partner with the role developer
is assigned as current processor and must take action. When the developer saves the normal change with
status To Be Tested, a business partner with the role tester is assigned as current processor and must take
action.

 Note

For SAP Solution Manager 7.2 SPS 5, the widget displays the existing change documents and requests
for change after they were saved for the first time.

Prerequisites

• You have configured the filters for the widgets in SAP Solution Manager Configuration (transaction
SOLMAN_SETUP) for your scenario, under step Configure User Interface Configure WebClient UI , in
activity Define Filters for My Messages Widgets.
• For Change Request Management: For each status of a transaction type, you have defined which business
partner role has the business partner function “current processor” (SDCD0004). You can do this in
SAP Solution Manager Configuration (transaction SOLMAN_SETUP) under Change Control Management
Change Request Management Configure User Interface Configure WebClient UI Define Current
Processor for My Messages Widgets .

 Note

Per default, field Overwrite has the value "unknown". To assign the responsible person automatically
according to document status, set the value "true".

If you use the Customizing activity Copy Transaction Types in SAP Solution Manager Configuration
(transaction SOLMAN_SETUP) under Change Control Management Change Request Management
Copy Transaction Types step, the Customizing is done automatically.
• To dispatch items that are assigned to a team, you have the role SOLMANDSPTCH and you have assigned
team members to your development teams (for more information, see KBA 2710246 ).
• To display items for your organization, the following is required:
• The administrator has enabled the messages of your organization to be displayed on your home
screen (see SAP Note 1256661 ).
• For My Messages – Reported By My Organization: You have a business partner relationship to your
organization. The default relationship is Is the Employee Responsible for (BUR011).
• For My Messages – Assigned To Me: You have a business partner relationship to your organization. Your
business partner function Current Processor (SDCD0004) has the business partner function category
0008 - person responsible.

Change Control Management

18 PUBLIC Change Control Management User Interfaces
  Note

When you’ve updated to SAP Solution Manager 7.2 SPS 5 or higher, assign the business partner
function Current Processor (SDCD0004) to the business partner function category 0008 - person
responsible. You can do this in Customizing for SAP Solution Manager (transaction SPRO) under
Capabilities (Optional) Change Control Management Transactions Partner Determination
Procedure Define Partner Functions .

• Optional: The business partner relationship and the partner functions can be customized (see SAP
Note 1256661 ).

Related Information

Specifying the Processor in Transactions [page 114]

Substitution [page 285]
Changing the Transaction Status with PPF Actions [page 169]

3.2.3 Including Custom Fields in the WebClient UI

You can enhance the WebClient UI to suit your business needs using the application enhancement tool.

Use

Any customer-specific UI elements you have created for your change transactions, messages, or requirements
are displayed in the Custom Fields assignment block. You can add these custom fields to the Details
assignment block using the UI configuration tool.

 Note

By default, the Custom Fields assignment block is hidden in the WebClient UI. To display it, choose
Personalize and move the assignment block to the list of displayed assignment blocks.

You can rename the Custom Fields assignment block using the UI configuration tool.

Prerequisites

You are authorized to add new UI elements to the WebClient UI.

Change Control Management

Change Control Management User Interfaces PUBLIC 19
More Information

For general information about the WebClient UI framework, see http://help.sap.com/crm <Release>
Application Help <Language> WebClient UI Framework .

For information about adapting the user interface to your business needs, see Application Enhancement Tool
and UI Configuration Tool.

Related Information

Adapting the WebClient UI: Personalization and Configuration [page 280]

Change Control Management

20 PUBLIC Change Control Management User Interfaces
4 Change Request Management

Change Request Management enables you to manage maintenance and implementation projects from end to
end: From change management and project planning, through resource management, to physical transports of
changes from the development environment into the productive environment.

Use

Ongoing software and configuration changes, as well as large implementations, are ongoing challenges for
managing data consistency and secure project control. Change Request Management enables you to control
changes within a system landscape from a central SAP Solution Manager system. It integrates SAP CRM
business transaction functionality for managing requests for change, and in a process-oriented fashion extends
and documents project control by integrating project planning from the processing of requests for change to
the actual transport into productive systems.

Change Request Management includes a predefined set of workflows and processes which are all compliant
with the recommendations provided by the IT infrastructure library (ITIL). This supports you when setting up
an ITIL-compliant change management process in your company.

The processes supported by Change Request Management include urgent changes for implementing fast and
direct changes in the productive environment, and activities for maintenance and implementation projects.
Cross-system and cross-component changes are supported.

Change Request Management offers you the following benefits:

• Increased maintenance and project efficiency

• Minimized costs for project management and IT
• Reduced risk of correction and project failure
• Shorter correction, implementation, and going-live phase
• Efficient maintenance of customer developments and implementations
• Transparency and documentation of the change process from approval of a request for change to the
transport of changes into follow-on systems

 Note

For each change cycle, you have the option to activate the central Change and Transport System (central
CTS) which provides a technical infrastructure for the enhanced flexibility functions in Change Control
Management. For more information, see Change Control Management Using Central Change and Transport
System [page 399].

 Tip

When setting up Change Request Management in an existing system that contains previously created
transports, continue to use the existing transports, and create new Change Request Management projects
in parallel. After some time, the old transports will be finished, and your system will contain only new
projects and transports. CTS projects are not mandatory during the transition.

Change Control Management

Change Request Management PUBLIC 21
  Note

From SAP Solution Manager 7.1, you can create and edit requests for change and change documents
using the WebClient UI. We recommend that you finish maintaining all previously created requests and
documents using the SAP GUI. New requests and documents should be created and edited only using the
WebClient UI.

For more information about requests for change in the SAP GUI, see the SAP Solution Manager
documentation for earlier releases at help.sap.com/viewer/p/SAP_Solution_Manager.

Integration

Change Request Management is a scenario of SAP Solution Manager, and contains interfaces to the following
SAP solutions:

• CRM service transactions for creating and managing requests for change (optional)
• SAP Portfolio and Project Management for managing project planning (optional)
• Job Request Management
• Test Management
• System Integration

Features

• Distribute software changes of ABAP and non-ABAP objects (for example, Java archives)
For more information, see the online documentation for Change and Transport System and Transporting
Non-ABAP Objects in Change and Transport System.
• Management of maintenance and implementations spanning multiple logical components
• Powerful service request management plus project management for controlling, planning, designing,
developing, testing, and going live
• Comprehensive, workflow-driven management of distributed activities, including planning, development,
maintenance, and go-live
• Powerful project change tracking

 Recommendation

We recommend that, apart from using the phase control, you initially use Change Request
Management to manage your urgent changes and continual cycles; you can then benefit from
additional functionality for managing large change projects.

Change Control Management

22 PUBLIC Change Request Management
4.1 Basic Terms and Concepts
The following sections explain basic terms and concepts of Change Request Management.

Related Information

Roles in Change Request Management [page 23]

Transaction Types [page 24]
Task List [page 53]

4.1.1 Roles in Change Request Management

Roles define what a user can do during the change process. In Change Request Management, the template
users determine the user roles.

Change Request Management uses the following template roles for distinct purposes. Technically, they are a
composite of several assigned roles. For more information about that, see the Application-Specific Security
Guide regarding Users and Roles Change Request Management.

Roles in Change Request Management

User Role Purpose

Requester Asks for a change to be made

Change Manager Approves or rejects the requested change, defines the

scope, validates, prioritizes and monitors the change proc-
ess.

Change Advisory Board Steering committee that approves the budget and scope

Developer Implements changes and passes them to the tester

Tester Tests changes and confirms the status in the change docu-
ment

Administrator Advances the phases of the change cycle and imports

project-related changes

IT Operator Takes care of software logistics

 Note

Based on the authorization, you must adjust the key values according to your requirements. For example,
copy a transaction type to custom name space (Z...), which you cannot include in standard roles. For this
purpose, you use the template user roles instead.

For more information on user roles in Change Request Management, see SAP Solution Manager
Configuration (transaction SOLMAN_SETUP) scenario Change Control Management Managed System
Setup Create User Master Data Create Managed System Template Users .

Change Control Management

Change Request Management PUBLIC 23
4.1.2 Transaction Types

By default, Change Request Management offers several transaction types to handle and document all change
processes with SAP Solution Manager. You can also define custom transaction types.

Related Information

Request for Change [page 24]

Change Documents [page 26]
Change Cycles [page 28]

4.1.2.1 Request for Change

A request for change is a change transaction that you use to request a change of your software or a company
system, for example, an enhancement or change to a function.

Use

The standard change transaction type for requests for change is SMCR.

 Note

You can use the default transaction type supplied by SAP or define your own in Customizing: Copy the
transaction type and adapt it to your requirements. For more information, see SAP Note 1493264 .

There are several ways to create a request for change, for example, from a template, or from a problem
message. A request for change passes through a series of defined statuses which document the activities of
the users that are involved.

A request for change usually contains one or more scope items which document the implementation of the
change.

The requested change must pass an approval process before a change can be made. After a change manager
(or another designated employee) has approved and released the change for implementation, the related
change documents are created from the scope items, and linked to the request for change.

Structure

The request for change consists of assignment blocks, which you can customize as you need them.

The Status Overview indicates the current step in the process.

Change Control Management

24 PUBLIC Change Request Management
Header Level (Details Assignment Block)

In the header details, you enter general data that is valid for the entire request for change. This includes, for
example, the following data:

• General data, for example, description, requester, change manager, and ID

• Processing data
• Data for change planning, for example, approval procedure and change cycle data
• Relationships, for example, related problem and related event

Assignment Blocks

In the other assignment blocks, you record additional data for the request for change, for example:

• Scope
• Approval
• Attachments
• Solution documentation
• Test management

Integration

Change Request Management uses variants of the SAP CRM service transaction for the processing of change
transactions in SAP system landscapes.

For more information about integration and the required settings, see the Customizing in SAP Solution
Manager Capabilities (Optional) Change Control Management .

The execution of a request for change can be planned in detail and, if necessary, can be integrated with other
processes and functions. If a knowledge article was used to complete a request for change, this knowledge
article can be attached to similar requests for change as a source of useful information.

Related Information

Change Documents [page 26]

Processing Requests for Change [page 56]
Functions in Change Transactions [page 113]
Assigning Reference Objects (IBase) [page 115]

Change Control Management

Change Request Management PUBLIC 25
4.1.2.2 Change Documents

Change documents are change transactions that reflect the change process during development, testing, and
implementation. They pass through a series of defined statuses and document the activities of the users that
are involved, for example, developers, testers, and system administrators.

Use

Depending on what should be changed, you select the appropriate change document type. If one or more
change document types were defined in the scope of a request for change, the change documents are created
automatically when the request for change is released to development.

By default, the following change document types are available in Change Request Management:

Type Use More Information

SMMJ For changes in your maintenance land- Processing Normal Changes [page 68]
scape and to implement features in
your development landscape.

SMGH For changes that use the Git-enabled Processing Git-enabled Changes [page 99]
CTS.

SMSG For low-risk changes that are uncritical Processing Standard Changes [page 89]
and can be implemented without fur-
ther approval.

SMHF For fast implementation of changes in Processing Urgent Changes [page 81]
your production system.

SMAD For changes by an administrator that do Processing Administrative Changes [page 95]
not have to be transported with a trans-
port request.

SMCG For changes that do not require a con- Processing General Changes [page 97]
nection to the SAP Change and Trans-
port System.

SMTM For correcting defects that were iden- Processing Defect Corrections [page 92]
tified during the “Build” and “Test”
phase.

 Note

You can use the default transaction types supplied by SAP or define your own transaction types for change
documents in Customizing. You can copy the transaction types and adapt them to your requirements.

Structure

A change document consists of assignment blocks, which you can customize and personalize as needed.

Change Control Management

26 PUBLIC Change Request Management
The Status Overview indicates the current step in the process.

Header Level (Details Assignment Block)

In the header details, you enter general data that applies to the whole change document. This includes, for
example, the following data:

• General data, for example, description, developer, tester, and ID

• Processing data
• Change cycle data, such as the change cycle, the change control landscape, and the branch
• Relationships, such as a related request for change
• Reference object: the installed base (IBase) component that represents the production system where the
change is to be implemented

Assignment Blocks

In the other assignment blocks, you enter more data that controls further processing. You can use the following
assignment blocks, for example:

• Texts
• Documents
• Information about test management
• Processing log
• Information about transport requests, tasks, and the system landscape
• Solution documentation

Integration

Change Request Management uses variants of the SAP CRM service transaction for the processing of change
transactions in SAP system landscapes.

For more information about integration and the required settings, see the Customizing in SAP Solution
Manager Capabilities Change Control Management . Execution of a change document can be planned in
detail and, if necessary, can be integrated with other processes and functions.

Related Information

Adapting the WebClient UI: Personalization and Configuration [page 280]

Functions in Change Transactions [page 113]
Changing the Transaction Status with PPF Actions [page 169]

Change Control Management

Change Request Management PUBLIC 27
4.1.2.3 Change Cycles

A change cycle is a type of change transaction that defines the system landscape (change control landscape
and branch) and the transport tracks for change documents. Each change cycle has a defined set of phases,
depending on its type. The phases define which activities are permitted as part of change control.

There are three types of change cycle:

• Continual cycles (transaction type SMAI)

• Phase cycles (transaction type SMIM)
• Release cycles (transaction type SMRE)

For more information about when to use which cycle, see the documentation for each cycle type.

Use

A change cycle controls the following activities in change control management:

• Requests for change and the resulting changes in the systems that are used in your solution landscape
• Transports of changes to the follow-on systems
• Change logistics, that is, which transports can be transported into the follow-on systems at which point in
time

You use change cycles to control which change activities are permitted in which phase. The phases determine
the sequence of tasks in task lists.

When the transport features of the CTS or central CTS are to be used, you must assign a change control
landscape and a branch to a change cycle. This enables SAP Solution Manager to identify the technical
systems.

You can create change cycles in the WebClient UI. Release cycles can be created from the release planning
function.

Structure

By default, a change cycle contains the following assignment blocks:

• Status Overview: Displays the phases of a change cycle. The current phase of the cycle is highlighted. To
change the phases and therefore the status of the cycle, use the respective Actions.
• Details: Contains general administration data for the change cycle, such as when and by whom it was
created, and the current cycle phase.
• Text: For more information, see Texts and Text Templates [page 117].
• Transport-Related Checks: For more information, see Performing Transport-Related Checks [page 150].
• Landscape: For more information, see Landscape Assignment Block [page 166].
• Related Transactions: Contains links to the task list and all change documents that use this cycle.
• Application log: For more information, see Application Log [page 251].

Change Control Management

28 PUBLIC Change Request Management
Integration

Change cycles are the basis for Change Request Management because they define the system landscape and
transport tracks via the change control landscape assignment. It is up to you to decide how flexible you want to
manage the change cycle assignment in your request for change. You can specify at what point in your request
for change process you want to assign a change cycle or whether you intend to assign a change cycle at all.

Per default, SAP standard requests for change (transaction type SMCR) must be assigned to a change cycle at
the latest when they are in status To Be Approved.

To enable a flexible management of change cycles, call transaction SOLMAN_SETUP (SAP Solution Manager
Configuration), go to Change Request Management Configure User Interface Configure WebClient UI
and adjust the settings in activity Assign Flexible Change Cycle.

Related Information

Task List [page 53]

Continual Cycle [page 29]
Phase Cycle [page 35]
Release Cycle [page 44]
Release Planning [page 456]
PPF Actions in Change Request Management [page 168]
Processing Requests for Change [page 56]

4.1.2.3.1 Continual Cycle

A continual cycle is a type of change cycle that is used for development without specific phases for build and
test. All implementation and testing happens in the main phase Active.

Use

Use a continual cycle to manage your changes and developments without phase control. You can perform
phase-independent and individual imports.

In contrast to a phase cycle, a continual cycle has a defined start. However, since maintenance is an ongoing
process, the continual cycle can be repeated time and again.

Continual cycles support all change document types except defect corrections, which aren’t needed without
designated test phase.

The standard transaction type for continual cycles is SMAI.

Change Control Management

Change Request Management PUBLIC 29
Structure

By default, a continual cycle has the following phases:

• Created (E0001)
• Active (E0002)
• Completed (E0008)
• Withdrawn (E0012)

Integration

Each continual cycle has a dedicated task list.

 Note

If the task list was created before SAP Solution Manager 7.2 SPS 6 and you want it to support normal
changes and standard changes, redefine the landscape or perform a cycle switch.

If you close or withdraw a continual cycle, the behaviour depends on the status of the change documents:

• The cycle contains open change documents and you want to create a successor cycle: The new cycle is
assigned to the original task list and takes over all open change documents.
• If the cycle contains only finished change documents, you can choose to create a successor cycle linked to
the original task list: If you close or withdraw the cycle without successor, the task list is closed as well.

Related Information

Processing Continual Cycles [page 106]

Change Documents [page 26]
Task List [page 53]
Redefining a Landscape [page 275]

4.1.2.3.1.1 Defined Actions for Continual Cycles

These are the actions that are delivered with the standard Customizing for each phase of a continual cycle
(SMAI).

There are no such defined actions in phases Completed and Withdrawn.

Note that there are further actions that can be triggered independently of a phase.

* The actions to release transport requests also check whether it is possible to create transport of copies
(ToC).

Change Control Management

30 PUBLIC Change Request Management
 Created

Active
Action Description

Administrative Change AD_CREATE Create Administrative  

Change

AD_REASSIGN Reassign Administra-  

tive Change

Correction CORR_TRANSFER Move Transport Re-  

quests of Open Correc-
tions

General Change GC_CREATE Create General Change  

GC_REASSIGN Reassign General  

Change

Git-enabled Change GH_CREATE Create Git-Enabled  

Change

GH_DEP_PROD Git-Enabled Change:  

Deploy into Production

GH_DEP_TEST Git-Enabled Change:  

Deploy into Test Sys-
tems

GH_TR_ASSIGN Git-Enabled Change:  

Register Transport Re-
quests

GH_TR_CREATE Git-Enabled Change:  

Create Transport Re-
quest

GH_TR_DECOUPLE Git-Enabled Change:  

Decouple Transport
Request

GH_TR_RELEASE* Git-Enabled Change:  

Release Transport Re-
quest

GH_TT_CREATE Git-Enabled Change:  

Create Transport Task

IT Requirement ITR_CREATE Create IT Requirement  

Normal Change RC_CREATE Create Normal Change  

Change Control Management

Change Request Management PUBLIC 31
 Created

Active
Action Description

RC_IMP_TEST Normal Change: Im-  

port into Test Systems

RC_PRELIM_IMP_PRO Normal Change: Pre-  

D liminary Import into
Production

RC_PRELIM_IMP_TES Normal Change: Pre-  

T liminary Import into
Test

RC_REASSIGN Reassign Normal  

Change

RC_TR_ASSIGN Normal Change: Regis-  

ter Transport Requests

RC_TR_CREATE Normal Change: Cre-  

ate Transport Request

RC_TR_DECOUPLE Normal Change: De-  

couple Transport Re-
quest

RC_TR_RELEASE* Normal Change: Re-  

lease Transport Re-
quest

RC_TT_CREATE Normal Change: Cre-  

ate Transport Task

Request for Change RFC_CREATE Create Request for  

Change

Standard Change SG_CREATE Create Standard  

Change

SG_IMP_PROD Standard Change: Im-  

port into Production

SG_IMP_TEST Standard Change: Im-  

port into Test Systems

SG_REASSIGN Reassign Standard  

Change

SG_TR_ASSIGN Standard Change: Reg-  

ister Transport Re-
quests

Change Control Management

32 PUBLIC Change Request Management
 Created

Active
Action Description

SG_TR_CREATE Standard Change: Cre-  

ate Transport Request

SG_TR_DECOUPLE Standard Change: De-  

couple Transport Re-
quest

SG_TR_RELEASE* Standard Change: Re-  

lease Transport Re-
quest

SG_TT_CREATE Standard Change: Cre-  

ate Transport Task

Task List SM_IMP_PROD Schedule Manager: Im-  

port into Production

SM_IMP_TEST Schedule Manager: Im-  

port into Test Systems

SM_TR_RELEASE* Schedule Manager:  

Release Transport Re-
quest

SM_TR_DECOUPLE Schedule Manager:  

Decouple Transport
Request

Defect Correction TM_CREATE Create Defect Correc-  

tion

TM_IMP_PROD Defect Correction: Im-  

port into Production

TM_IMP_TEST Defect Correction: Im-  

port into Test Systems

TM_REASSIGN Reassign Defect Cor-  

rection

TM_TR_ASSIGN Defect Correction:  

Register Transport Re-
quests

TM_TR_CREATE Defect Correction: Cre-  

ate Transport Request

Change Control Management

Change Request Management PUBLIC 33
 Created

Active
Action Description

TM_TR_DECOUPLE Defect Correction: De-  

couple Transport Re-
quest

TM_TR_RELEASE Defect Correction: Re-  

lease Transport Re-
quest

TM_TT_CREATE Defect Correction: Cre-  

ate Transport Task

Urgent Change UC_CREATE Create Urgent Change  

UC_IMP_PROD Urgent Change: Import  

into Production

UC_IMP_TEST Urgent Change: Import  

into Test Systems

UC_TR_ASSIGN Urgent Change: Regis-  

ter Transport Requests

UC_TR_CREATE Urgent Change: Create  

Transport Request

UC_TR_DECOUPLE Urgent Change: De-  

couple Transport Re-
quest

UC_TR_RELEASE Urgent Change: Re-  

lease Transport Re-
quest

UC_TT_CREATE Urgent Change: Create  

Transport Task

Related Information

Continual Cycle [page 29]

Statuses and Phases That Allow Reassigning Change Transactions [page 144]

Change Control Management

34 PUBLIC Change Request Management
4.1.2.3.1.2 Using Change Cycles Without a Task List

Use

You can use this function if you want to manage your changes in your solution landscape using Change Request
Management independently of transport management. This function is available for continual cycles and for
phase cycles.

You create a change cycle and assign a change control landscape and a branch to it. Once the cycle is in
the Created phase, you assign it to a general change or an administrative change, and change the solution
documentation within this document.

When assigning a change cycle to a change transaction, you can search for change cycles with or without task
lists.

Related Information

Change Cycles [page 28]

Reassigning Change Transactions [page 141]
Processing Administrative Changes [page 95]
Processing General Changes [page 97]

4.1.2.3.2 Phase Cycle

A phase cycle is a type of change cycle that supports phase-driven development and independent import of
changes.

Use

Phase cycles support all change document types.

The standard transaction type for phase cycles is SMIM.

Structure

By default, a phase cycle has the following phases:

• Created: Initial status

• Scope: Transport requests can be generated but not released. Use this phase if developments are not to be
transported to the test system straight away.

Change Control Management

Change Request Management PUBLIC 35
• Build: This phase is initiated by the change manager or the change advisory board. You can release
transport requests and import them into the test system for developer tests. Use defect corrections to
eliminate errors that occurred during import.
• Test: After changes have been imported into the test system, this phase can start and integration testing
can commence. New change transactions can no longer be created for the project. Use defect corrections
to eliminate errors that occurred during testing.
• Withdrawn: To withdraw a phase cycle, make sure that no change has been executed and transported. This
means that all dependent change documents must also be withdrawn.
Transport requests directly created from a task list must be empty of transport objects. When you
withdraw, the task list is closed automatically and the empty transport request is deleted.
• Go Live: All changes that were tested successfully are imported into the production system.
• Being Completed: This phase doesn’t allow you to go back to the previous phase.
• Completed

Integration

Each phase cycle has a dedicated task list. The task list is closed when the following conditions are fulfilled:

• The transport requests have been imported into the production system.
• All change documents have been completed.
• The phase cycle has been closed.

If the system detects any open change documents or transport requests when you close the cycle, they’re
assigned to a new phase cycle, and the task list is continued.

 Note

For changes that are not linked to the transport management system, you can use change cycles without a
task list.

Related Information

Processing Phase Cycles [page 108]

Using Change Cycles Without a Task List [page 35]
Task List [page 53]

4.1.2.3.2.1 Defined Actions for Phase Cycles

These are the actions that are delivered with the standard Customizing for each phase of a phase cycle (SMIM).

There are no such defined actions in phases Completed and Withdrawn.

Note that there are further actions that can be triggered independently of a phase.

Change Control Management

36 PUBLIC Change Request Management
* The actions to release transport requests also check whether it is possible to create transport of copies.

Being Completed
Created

Go Live
Scope

Build

Test
Action Description

Administra- AD_CREATE Create Ad-      

tive Change ministrative
Change

AD_REASSI Reassign      
GN Administra-
tive Change

F4 Help CHECK_PRO Check      

JECT whether ac-
tion F4 help
is allowed
for this
phase

Correction CORR_TRAN Move Trans-      

SFER port Re-
quests of
Open Cor-
rections

General GC_CREATE Create Gen-      

Change eral Change

GC_REASSI Reassign      
GN General
Change

Git-Enabled GH_CREATE Create Git-      

Change Enabled
Change

GH_DEP_PR Git-Enabled      
OD Change:
Deploy into
Production

GH_DEP_TE Git-Enabled      
ST Change:
Deploy into
Test Sys-
tems

Change Control Management

Change Request Management PUBLIC 37
 Being Completed
Created

Go Live
Scope

Build

Test
Action Description

GH_TR_ASS Git-Enabled      
IGN Change:
Register
Transport
Requests

GH_TR_CRE Git-Enabled      
ATE Change:
Create
Transport
Request

GH_TR_DEC Git-Enabled      
OUPLE Change:
Decouple
Transport
Request

GH_TR_REL Git-Enabled      
EASE* Change: Re-
lease Trans-
port Re-
quest

GH_TT_CRE Git-Enabled      
ATE Change:
Create
Transport
Task

IT Require- ITR_CREAT Create IT      

ment E Require-
ment

Normal RC_CREATE Create Nor-      

Change mal Change

RC_IMP_TE Normal      
ST Change: Im-
port into
Test Sys-
tems

Change Control Management

38 PUBLIC Change Request Management
 Being Completed
Created

Go Live
Scope

Build

Test
Action Description

RC_PRELIM Normal      
_IMP_PROD Change:
Preliminary
Import into
Production

RC_PRELIM Normal      
_IMP_TEST Change:
Preliminary
Import into
Test

RC_REASSI Reassign      
GN Normal
Change

RC_TR_ASS Normal      
IGN Change:
Register
Transport
Requests

RC_TR_CRE Normal      
ATE Change:
Create
Transport
Request

RC_TR_DEC Normal      
OUPLE Change:
Decouple
Transport
Request

RC_TR_REL Normal      
EASE* Change: Re-
lease Trans-
port Re-
quest

RC_TT_CRE Normal      
ATE Change:
Create
Transport
Task

Change Control Management

Change Request Management PUBLIC 39
 Being Completed
Created

Go Live
Scope

Build

Test
Action Description

Request for RFC_CREAT Create Re-      

Change E quest for
Change

Standard SG_CREATE Create      

Change Standard
Change

SG_IMP_PR Standard      
OD Change: Im-
port into
Production

SG_IMP_TE Standard      
ST Change: Im-
port into
Test Sys-
tems

SG_REASSI Reassign      
GN Standard
Change

SG_TR_ASS Standard      
IGN Change:
Register
Transport
Requests

SG_TR_CRE Standard      
ATE Change:
Create
Transport
Request

SG_TR_DEC Standard      
OUPLE Change:
Decouple
Transport
Request

SG_TR_REL Standard      
EASE* Change: Re-
lease Trans-
port Re-
quest

Change Control Management

40 PUBLIC Change Request Management
 Being Completed
Created

Go Live
Scope

Build

Test
Action Description

SG_TT_CRE Standard      
ATE Change:
Create
Transport
Task

Task List SM_IMP_PR Schedule      

OD Manager:
Import into
Production

SM_IMP_TE Schedule      
ST Manager:
Import into
Test Sys-
tems

SM_TR_ASS Schedule      
IGN Manager:
Register
Transport
Requests

SM_TR_CRE Schedule      
ATE Manager:
Create
Transport
Request

SM_TR_DEC Schedule      
OUPLE Manager:
Decouple
Transport
Request

SM_TR_REL Schedule      
EASE* Manager:
Release
Transport
Request

SM_TT_CRE Schedule      
ATE Manager:
Create
Transport
Task

Change Control Management

Change Request Management PUBLIC 41
 Being Completed
Created

Go Live
Scope

Build

Test
Action Description

Defect Cor- TM_CREATE Create De-      

rection fect Correc-
tion

TM_IMP_TE Defect Cor-      

ST rection: Im-
port into
Test Sys-
tems

TM_REASSI Reassign      
GN Defect Cor-
rection

TM_TR_ASS Defect Cor-      

IGN rection:
Register
Transport
Requests

TM_TR_CRE Test Mes-      

ATE sage: Cre-
ate Trans-
port Re-
quest

TM_TR_DEC Defect Cor-      

OUPLE rection: De-
couple
Transport
Request

TM_TR_REL Defect Cor-      

EASE rection: Re-
lease Trans-
port Re-
quest

TM_TT_CRE Defect Cor-      

ATE rection:
Create
Transport
Task

Change Control Management

42 PUBLIC Change Request Management
 Being Completed
Created

Go Live
Scope

Build

Test
Action Description

Urgent UC_CREATE Create Ur-      

Change gent
Change

UC_IMP_PR Urgent      
OD Change: Im-
port into
Production

UC_IMP_TE Urgent      
ST Change: Im-
port into
Test Sys-
tems

UC_TR_ASS Urgent      
IGN Change:
Register
Transport
Requests

UC_TR_CRE Urgent      
ATE Change:
Create
Transport
Request

UC_TR_DEC Urgent      
OUPLE Change:
Decouple
Transport
Request

UC_TR_REL Urgent      
EASE Change: Re-
lease Trans-
port Re-
quest

UC_TT_CRE Urgent      
ATE Change:
Create
Transport
Task

Change Control Management

Change Request Management PUBLIC 43
4.1.2.3.2.2 Using Change Cycles Without a Task List

Use

You can use this function if you want to manage your changes in your solution landscape using Change Request
Management independently of transport management. This function is available for continual cycles and for
phase cycles.

You create a change cycle and assign a change control landscape and a branch to it. Once the cycle is in
the Created phase, you assign it to a general change or an administrative change, and change the solution
documentation within this document.

When assigning a change cycle to a change transaction, you can search for change cycles with or without task
lists.

Related Information

Change Cycles [page 28]

Reassigning Change Transactions [page 141]
Processing Administrative Changes [page 95]
Processing General Changes [page 97]

4.1.2.3.3 Release Cycle

A release cycle is a type of change cycle that is used within release management for phase-driven changes that
depend on the release plan.

Use

Release cycles can be created directly from the release planning function. The release planning function in
SAP Solution Manager is used to plan major and minor releases, specify go-live dates, and assign the release
planning data to change control landscapes and branches.

 Note

For a selected change control landscape, at least one release cycle must be available. It’s used as a copy
template for the cycle to be created. The the Go-Live dates and other data of the release cycle are adjusted
automatically.

If there’s no release cycle for a change control landscape, you must create the first cycle manually.

Release cycles support all change document types.

The standard change transaction type for release cycles is SMRE.

Change Control Management

44 PUBLIC Change Request Management
Structure

By default, a release cycle has the following phases:

• Created
• Scope
• Build
• Test
• Deploy
• Hypercare
• Operate
• Retired

Release management uses a predecessor – successor relationship. A successor release can be imported into
the production system only after the predecessor release has been imported. This means that a successor
release cycle can be shifted to the Build phase only after the Deploy phase of the predecessor release cycle is
finished.

Related Information

Release Planning [page 456]

Processing Release Cycles [page 110]

4.1.2.3.3.1 Defined Actions for Release Cycles

These are the actions that are delivered with the standard Customizing for each phase of a release cycle.

There are no such defined actions in phase Retired.

Note that there are further actions that can be triggered independently of a phase.

* The actions to release transport requests also check whether it is possible to create transport of copies.

Change Control Management

Change Request Management PUBLIC 45
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

Adminis- AD_CREAT Create Ad-       

trative E ministra-
Change tive
Change

AD_REASS Reassign       
IGN Adminis-
trative
Change

F4 Help CHECK_RE Check       

LEASE whether
action F4
help is al-
lowed for
this phase

Correction CORR_TRA Move       

NSFER Transport
Requests
of Open
Correc-
tions

General GC_CREAT Create       

Change E General
Change

GC_REASS Reassign       
IGN General
Change

Git-Ena- GH_CREAT Create       

bled E Git-Ena-
Change bled
Change

GH_DEP_P Git-Ena-       
ROD bled
Change:
Deploy
into Pro-
duction

Change Control Management

46 PUBLIC Change Request Management
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

GH_DEP_T Git-Ena-       
EST bled
Change:
Deploy
into Test
Systems

GH_TR_AS Git-Ena-       
SIGN bled
Change:
Register
Transport
Requests

GH_TR_CR Git-Ena-       
EATE bled
Change:
Create
Transport
Request

GH_TR_DE Git-Ena-       
COUPLE bled
Change:
Decouple
Transport
Request

GH_TR_RE Git-Ena-       
LEASE* bled
Change:
Release
Transport
Request

GH_TT_CR Git-Ena-       
EATE bled
Change:
Create
Transport
Task

IT Re- ITR_CREA Create IT       

quirement TE Require-
ment

Change Control Management

Change Request Management PUBLIC 47
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

Normal RC_CREAT Create       

Change E Normal
Change

RC_IMP_T Normal       
EST Change:
Import
into Test
Systems

RC_PRELI Normal       
M_IMP_PR Change:
OD Prelimi-
nary Im-
port into
Produc-
tion

RC_PRELI Normal       
M_IMP_TE Change:
ST Prelimi-
nary Im-
port into
Test

RC_REASS Reassign       
IGN Normal
Change

RC_TR_AS Normal       
SIGN Change:
Register
Transport
Requests

RC_TR_CR Normal       
EATE Change:
Create
Transport
Request

RC_TR_DE Normal       
COUPLE Change:
Decouple
Transport
Request

Change Control Management

48 PUBLIC Change Request Management
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

RC_TR_RE Normal       
LEASE* Change:
Release
Transport
Request

RC_TT_CR Normal       
EATE Change:
Create
Transport
Task

Request RFC_CREA Create Re-       

for TE quest for
Change Change

Standard SG_CREAT Create       

Change E Standard
Change

SG_IMP_P Standard       
ROD Change:
Import
into Pro-
duction

SG_IMP_T Standard       
EST Change:
Import
into Test
Systems

SG_REASS Reassign       
IGN Standard
Change

SG_TR_AS Standard       
SIGN Change:
Register
Transport
Requests

Change Control Management

Change Request Management PUBLIC 49
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

SG_TR_CR Standard       
EATE Change:
Create
Transport
Request

SG_TR_DE Standard       
COUPLE Change:
Decouple
Transport
Request

SG_TR_RE Standard       
LEASE* Change:
Release
Transport
Request

SG_TT_CR Standard       
EATE Change:
Create
Transport
Task

Task List SM_IMP_P Schedule       

ROD Manager:
Import
into Pro-
duction

SM_IMP_T Schedule       
EST Manager:
Import
into Test
Systems

SM_TR_AS Schedule       
SIGN Manager:
Register
Transport
Requests

Change Control Management

50 PUBLIC Change Request Management
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

SM_TR_CR Schedule       
EATE Manager:
Create
Transport
Request

SM_TR_DE Schedule       
COUPLE Manager:
Decouple
Transport
Request

SM_TR_RE Schedule       
LEASE* Manager:
Release
Transport
Request

SM_TT_CR Schedule       
EATE Manager:
Create
Transport
Task

Defect TM_CREAT Create De-       

Correction E fect Cor-
rection

TM_IMP_T Defect       
EST Correc-
tion: Im-
port into
Test Sys-
tems

TM_REASS Reassign       
IGN Defect
Correction

TM_TR_AS Defect       
SIGN Correc-
tion: Reg-
ister
Transport
Requests

Change Control Management

Change Request Management PUBLIC 51
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

TM_TR_CR Test Mes-       

EATE sage: Cre-
ate Trans-
port Re-
quest

TM_TR_DE Defect       
COUPLE Correc-
tion: De-
couple
Transport
Request

TM_TR_RE Defect       
LEASE Correc-
tion: Re-
lease
Transport
Request

TM_TT_CR Defect       
EATE Correc-
tion: Cre-
ate Trans-
port Task

Urgent UC_CREAT Create Ur-       

Change E gent
Change

UC_IMP_P Urgent       
ROD Change:
Import
into Pro-
duction

UC_IMP_T Urgent       
EST Change:
Import
into Test
Systems

Change Control Management

52 PUBLIC Change Request Management
 Hypercare

Operate
Created

Deploy
Scope
Descrip-

Build

Test
Action tion

UC_TR_AS Urgent       
SIGN Change:
Register
Transport
Requests

UC_TR_CR Urgent       
EATE Change:
Create
Transport
Request

UC_TR_DE Urgent       
COUPLE Change:
Decouple
Transport
Request

UC_TR_RE Urgent       
LEASE Change:
Release
Transport
Request

UC_TT_CR Urgent       
EATE Change:
Create
Transport
Task

4.1.3 Task List

A task list is a structured group of tasks, which are executed periodically by one or more users, to complete a
certain process, such as the handling of changes.

Structure

The task list is displayed as a structure tree. It contains tasks relevant for the process and defines which
processes can be performed for a change, depending on the change cycle to which it is assigned.

Change Control Management

Change Request Management PUBLIC 53
For more information, you can select the following tabs:

• Monitor: List of application logs for a task. This corresponds to the Application Log assignment block of the
associated change cycle in the WebClient UI.
• Daily overview for the tasks that are executed or planned on a daily basis.
• Transport request overview for a task list
• Transport landscape graphic

Integration

You create task lists in the WebClient UI, depending on the assigned change cycle.

From a change document and from a change cycle, you can call up the relevant task list by choosing More
Open Task List .

In the administration cockpit, you can manage your task lists on the Task Lists tab.

At your request, the system generates the task lists based on the settings for the change cycle (such as change
control landscape and branch).

Customizing provides the tasks that are generated for each system, depending on the system role type. You
can change the Customizing settings under the following paths:

• SAP Solution Manager Capabilities (Optional) Change Control Management Schedule Manager
Define Additional Tasks for Task Lists
• SAP Solution Manager Capabilities (Optional) Change Control Management Schedule Manager
Create Customer-Specific Header and Footer Tasks

If you make changes to the change cycle or in Customizing, these changes apply to all new task lists that are
generated from then on.

 Note

For Change Request Management, the task list also contains the status switch job that automatically
updates the status of change documents after they are imported into a target system.

Related Information

Change Control Management in the WebClient UI [page 15]

Creating Task Lists [page 273]
Managing the Task List [page 294]
Updating Change Document Status After Import of Transport Requests [page 132]

Change Control Management

54 PUBLIC Change Request Management
4.1.3.1 Task List Variants

Use

A change cycle defines the system landscape (change control landscape and branch) and the transport tracks
you use in Change Request Management. Each change cycle has a defined set of phases depending on its type.
The phases define which activities are permitted as part of change control. The transport tracks are defined in
the Transport Management System (TMS).

If you use Change Request Management, your systems are set up in such a way that you can only perform
the transport tasks (create, release, and import transport requests) in Change Request Management. This is
determined by the Central Transport System (CTS) project assigned to the transport requests, and the CTS
status switch which defines that you cannot create, release, or import transport requests using transactions
SE09 and STMS. Only the Change Request Management programs can perform these functions based on the
task list assigned to every change cycle.

Features

There are two SAP standard task list variants that determine the import strategy of changes:

• SAP0: Standard import strategy (recommended)

Distinguishes between two types of import:
• Normal changes are always imported into the system together (that is, all transport requests for a CTS
project in the import buffer) in the order of their release. The transport requests are then removed
from the import buffer.
You can perform a preliminary import of normal changes to accelerate the transport process. In this
case, the transport requests of the normal change stay in the import buffer.
• Urgent changes are transported separately and as quickly as possible. After import, the transport
requests of the urgent change stay in the import buffer. They are imported with other related CTS
project transport requests in the order of their release, and only deleted from the buffer during the
mass import.

 Note

You must ensure consistency between urgent changes manually, that is, you must ensure that
the import sequence of urgent changes matches the release sequence, especially, if they are
interdependent.

Because normal and urgent changes are imported together as part of the CTS project import based on
their release sequence, any inconsistencies caused by urgent changes may be repaired.

• SAP1: Deletion of import buffer strategy

All imports are handled like urgent changes, but the transport requests are removed from the import buffer
after import. If you do not import in the release sequence, inconsistencies can occur. You cannot repair
these by performing the CTS project import because the buffer entries no longer exist.

 Caution

Use this import strategy with caution. Use it only if you are making small changes that are not
interdependent. Note that only the developer can determine which transports are to be determined

Change Control Management

Change Request Management PUBLIC 55
 if there are interdependencies. In such a case, import the transport requests separately using this
import strategy, and not as part of a CTS project import.

By default, you have the following selection options for the task list variant:

• For phase cycles or release cycles:

Select SAP0 or a customized task list variant
• For continual cycles:
Select SAP1 or a customized task list variant

If you want to have different selection options for the task list variant for a change cycle, you can overwrite this
default selection option for the change cycle in the customizing table /TMWFLOW/TLVARCY.

More Information

Preliminary Import of Normal Changes [page 71]

4.2 Processing Change Transactions

SAP provides default process flows for processing request for changes and the follow-up change documents to
deploy the changes.

Learn how to request a change, to validate, approve and implement different kinds of changes, and to manage
the implementation process with change cycles.

4.2.1 Processing Requests for Change

Use this process to create, edit, approve, and implement requests for change. This process documents all
related tasks and helps to find out at any time where a request originated, who implemented it and when the
change was implemented in a production environment.

Prerequisites

• You have configured the settings in Customizing (SPRO) under SAP Solution Manager Capabilities
(Optional) Change Control Management .
• The users in the change management process have the necessary authorization, that is, system
administration has created user roles that include these authorizations and assigned these roles to
the users. These roles were created in SAP Solution Manager and in the managed systems. For more
information, see the Security Guide for Change Control Management on SAP Help Portal at https://

Change Control Management

56 PUBLIC Change Request Management
 help.sap.com/viewer/p/SAP_Solution_Manager <current release> Security Application-Specific
Security Guide Change Control and IT Service Management Scenarios .
• You have created a change control landscape in SAP Solution Manager, activated Change Control
Management, and created a change cycle.

Context

Change Control Management

Change Request Management PUBLIC 57
Procedure

1. A user working in a production system discovers something that should be changed, for example, an error
or a missing function. The user creates a message directly from the transaction, describing the situation
and requesting a change.
2. The message appears in the worklist or the widget of a service employee who processes the message
and creates a request for change. The processor can create the request for change from scratch, from a
template, or create a follow-up document from an incident or a problem.
3. The request for change appears in the worklist of the change manager. The change manager reviews the
existing data, prioritizes the request for change according to its impact and specifies for which systems the
change is relevant. In the assignment block Scope, the change manager defines the scope by inserting one
or more change document types.

The change manager can also assign a change cycle, solution documentation elements, test cases, and
additional information relevant to the change process, such as which business process is affected. When
validation is finished, the change manager releases the request for change for approval.
4. The request for change must be approved before a change document can be created. Per default, the
change managers are assigned as approvers. If desired, you can also enter an additional business partner,
such as the change advisory board.
5. After approval, one or more change documents are created automatically. In the following work steps, the
change document is the operational basis for developers, testers, and IT administrators.

An approved request for change can still be changed, for example, to extend the scope by adding further
change documents.
6. The change document appears in the worklist of a developer, who implements the change and releases
it for testing. After successful testing, the change is transported through the system landscape to the
production system.
7. The change manager completes the request for change.

If all assigned change documents have been fully processed, the request for change is also closed.

Related Information

Creating a Request for Change [page 59]

The “My Messages” Widgets [page 17]
Change Documents [page 26]
Change Cycles [page 28]
Solution Documentation
PPF Actions for SMCR Request for Change [page 172]
Assigning Reference Objects (IBase) [page 115]

Change Control Management

58 PUBLIC Change Request Management
4.2.1.1 Creating a Request for Change

A problem has been detected, and you want to request a change to fix it.

Prerequisites

You have the role SAP_CM_REQUESTER.

Context

There are several ways to create a request for change based on predecessor documents.

In all cases, the new request for change is assigned to a change manager. It is in the change manager's worklist
with status Created, waiting for validation.

Creating a Request for Change from a Template

Prerequisites

A template has been created. For more information, see Creating Templates for Requests for Change [page
66].

Procedure

1. In the WebClient UI, select New Request for Change New from Template

The system displays the search help for templates for requests for change.
2. Select the template you want to use.
3. Enter the required information and save your entries.

Creating a Change Transaction from a Roadmap

Procedure

1. In transaction RMMAIN, select a project with a roadmap assigned to it.

Change Control Management

Change Request Management PUBLIC 59
2. Select a workpackage.

The roadmap structure is displayed, and the selected workpackage is marked.

3. Under Service Messages, select Create Change Transaction .

4. Choose the change transaction type you want to create and add a description.

The change transaction is saved automatically. It’s displayed under Service Messages.

The change transaction is available for processing in the WebClient UI.

Creating a Request for Change from a Job Request

Context

You can create administrative changes based on job requests.

Procedure

1. In the Job Management, select an existing job request for which you’re the processor, and select Edit.

You see the job request document.

2. Select Actions Create Request for Change .

3. To create the request for change with data from the job request (for example, the description and the
processor), select Save.

The request for change has the scope Administrative Change, and its predecessor is the original job
request.

The request for change is available for processing in the WebClient UI. You can add more details as
required.

Related Information

Editing Job Scheduling Change Documents [page 278]

Creating a Request for Change from an Incident

Procedure

1. In the incident in the WebClient UI, select Create Follow-Up Request for Change .

Change Control Management

60 PUBLIC Change Request Management
 A request for change is created, containing data from the incident. For example, you see the incident ID
under Relationships and the installed base as configuration item under Scope.
2. Complete the request for change with more details.
3. Save the request for change.

Creating a Request for Change from System

Recommendations

Context

For more information, see System Recommendations (http://help.sap.com/solman_fiori ).

Creating a Request for Change from a Project Management

Project Task

Context

For more information, see Creating a Request for Change in a Project Management Project Task

Related Information

The “My Messages” Widgets [page 17]

Assigning Reference Objects (IBase) [page 115]

4.2.1.2 Validating a Request for Change

Prerequisites

• A request for change has been created that documents the problem.
• You have the role SAP_CM_CHANGE_MANAGER.

Change Control Management

Change Request Management PUBLIC 61
Context

Change managers validate every request for change, that is, they review the information, define the scope and
submit it for approval. Alternatively, they can reject the request.

Procedure

1. Select the request for change that you want to validate.

The system opens the request.

2. In the assignment block Details, select Edit and set the request for change to status Validation.
3. Review the data that has already been entered for the request, and prioritize the request according to its
impact.

You can choose further subcategories to be more exact, depending on the category. For more information
about the available customer-specific categories, ask the person responsible for your system.
4. In the assignment block Scope, insert one or more change documents and the associated configuration
items.

To define the scope, you select one or more types of change, such as a normal change, urgent change, or
general change. You can assign several change documents to the same request for change. For example, if
a change affects several production systems of a change control landscape, you can record all changes in
one request for change.

For low-risk changes, select transaction type "standard change" and activate the checkbox Standard
Change. You must be authorized to select this option. If the scope contains change types other than
standard changes, the value of the Standard Change checkbox in assignment block Details can’t be
changed.

 Note

As of SAP Solution Manager 7.2 support package stack 3, you can use a standard request for change
without inserting entries in the Scope assignment block. For such a request for change without scope
items, the system doesn’t create change documents.

To allow using requests for change without scope items, open SAP Solution Manager Configuration
(transaction SOLMAN_SETUP) and go to Change Request Management Employ Additional Use
Cases Enable Optional Scope Items .

For each change document, you must select a configuration item to specify the production system for
which a change is requested.
• For a normal change, urgent change, standard change, and defect correction, you can choose from
the configuration items only of those production systems that are on a transport track of the selected
change cycle.
• For an admin change, you can choose from the configuration items of all production systems on all
tracks of your system landscape, regardless of change cycle.
• For a general change, you can choose from the configuration items of all production systems, including
the additional systems as defined in the selected change cycle, regardless of transport track or
landscape.

Change Control Management

62 PUBLIC Change Request Management
  Note

If necessary, you can extend the scope later.

The system displays the assigned transaction types and their current status.
5. You can add more information, for example, the change cycle to which the request for change is
associated. Assigning the change cycle establishes the relationship to the CTS project for the request
for change and all follow-up documents and transport requests.

If there’s only one change control landscape for the cycle, the change control landscape is displayed
automatically. If there are several change control landscapes, select the relevant one from the search help.
6. As required, add further information like relationships to Solution Documentation or knowledge articles.
7. When you are finished with validation, release the request for change for approval.

The request for change proceeds to status To Be Approved.

Next Steps

Approving a Request for Change [page 63]

Rejecting a Request for Change [page 66]

Related Information

Assigning Reference Objects (IBase) [page 115]

4.2.1.3 Approving a Request for Change

To create follow-on change documents, the request for change must be approved.

Prerequisites

• A request for change has been created that documents the problem. It has been validated and has the
status To Be Approved.
• All business partners that are supposed to approve the request for change have been inserted into the
Approval assignment block.
• You have the SAP_CM_CHANGE_MANAGER role.

Change Control Management

Change Request Management PUBLIC 63
Context

A request for change, for example, for an urgent change, has been validated by a change manager, who has also
added more information to it.

Before any change can be made, all approvers must review and approve the request. Alternatively, they can
reject it or decide that the change is not relevant.

Procedure

1. Choose a request for change that is assigned to you for approval.

2. Review the contents of the request for change and make sure all mandatory fields are filled out.
3. In assignment block Approval, under column Activity, select the value Approved.

 Note

Only if all approvers approve their respective assigned steps, the requested change is approved.

If one approver rejects the assigned step, the whole request is rejected. For more information see SAP
Note 190688 .

If all approvers choose Not Relevant, the request for change keeps the status To Be Approved.

4. Save the request for change.

Results

The request for change has the status Approved.

Next Steps

To release the request for change for further processing, choose Edit, and then Actions Release for
Development .

The request for change now has the status Being Implemented and the associated change documents are
created.

Related Information

Approval Procedures [page 282]

Rejecting a Request for Change [page 66]

Change Control Management

64 PUBLIC Change Request Management
Change Documents [page 26]

4.2.1.4 Extending the Scope of a Request for Change

During the implementation, the change manager can add more change documents to a request for change to
document that the scope is extended.

Prerequisites

• A request for change has been created that documents the problem. It has been validated and has the
status Being Implemented or Implemented.
• All business partners that are supposed to approve the request for change have been inserted into the
Approval assignment block.
• You have the SAP_CM_CHANGE_MANAGER role.

Context

When you notice during the implementation that the original scope of a request for change is not sufficient, you
can extend the scope.

Procedure

1. In the WebClient UI, open the request for change in edit mode.
2. Execute the action Extend Scope.

The request for change proceeds to status Extend Scope.

3. In assignment block Scope, add the required change documents.
4. Start the approval process for the new scope elements.

Related Information

Approving a Request for Change [page 63]

Change Control Management

Change Request Management PUBLIC 65
4.2.1.5 Rejecting a Request for Change

Prerequisites

• A request for change has been created that contains information about the what should be changed.
• You have the SAP_CM_CHANGE_MANAGER role.

Context

A request for change has been created. In your position as change manager, you have decided that the change
should not be made. You are going to to reject the request.

Procedure

1. In the Approval assignment block, go to the step that needs approval.

2. Review the contents of the request.
3. In the Activity column, choose the dropdown list and select the entry Rejected. You can add comments to
explain the reasons for the rejection.
4. Save the request for change.

Results

The request for change has the status Rejected.

4.2.1.6 Creating Templates for Requests for Change

Prerequisites

In SAP Solution Manager Configuration (transaction SOLMAN_SETUP), scenario Change Control Management
Change Request Management Define Change Process Define Copy Control Define Copy Control , you
have defined the copy control so that the transaction type SMCT can be copied to SMCR:

Change Control Management

66 PUBLIC Change Request Management
• You have specified SMCT as source transaction type.
• You have specified SMCR as target transaction type.

Context

If you often create requests for change with the same data, it is useful to create templates with the data that is
always contained in your requests for change. This minimizes the time needed to create a request for change.

 Note

Similar to requests for change and change documents, templates for requests for change are also based
on business transactions. The default transaction type for the request for change template is SMCT. Your
settings are the same as those for the request for change (SMCR), but there is a separate status profile and
a separate date profile, so that the validity of a request for change can be specified.

Procedure

1. In the navigation bar of the WebClient UI, select Change Request Mgmt Request for Change
Templates .

On the following screen, you can search for existing templates or create a new template.
2. Choose New.

The system displays a blank input screen for a request for change.
3. Give your template a name and enter all the data that is supposed to be part of your template, for example,
the change manager, the change advisory board, and standard documents.
4. In the Dates assignment block, specify the validity of the template.

5. Choose Actions Release Template .

Later you can edit the template, invalidate it temporarily, or close it completely.
6. Choose Save.

Results

You have created a template for requests for change and you can use it now (or when the validity period starts)
to create requests for change.

You can find it in the search for templates for requests for change.

Change Control Management

Change Request Management PUBLIC 67
Related Information

Creating a Request for Change [page 59]

4.2.2 Processing Normal Changes

Use this process to make normal changes in your maintenance landscape and to implement features in your
development landscape.

Prerequisites

• A request for change has been approved and released for development, creating a change document of the
type Normal Change.
• The assigned change cycle must be in a phase that allows the required activity.

 Recommendation

To check whether the assigned change cycle is in a valid phase, assign and maintain consistency
checks.

To change the settings, call transaction SOLMAN_SETUP (SAP Solution Manager Configuration) and
select Change Request Management Define Change Process Copy Transaction Types Improve
Normal Change Process .

 Note

More information on change management-related roles and profiles: SAP Note 834534
and the security guide for Change Control Management on SAP Help Portal at https://
help.sap.com/viewer/p/SAP_Solution_Manager <current release> Security Application-Specific
Security Guide Change Control and IT Service Management Scenarios .

Context

A normal change is an implementation of a request for change: a new functionality, a new feature in an existing
functionality, or a corrective activity for a minor defect in an existing functionality. This change document type
supports the development, testing, and approval of changes within an overall release strategy for the landscape
and for one or more production systems.

 Caution

Users must not be permitted to create, maintain, or release transport requests or tasks directly in the
Transport Organizer. This is because Change Request Management cannot identify transport requests that
were created outside of Change Request Management as belonging to a scenario.

Change Control Management

68 PUBLIC Change Request Management
Procedure

1. In the Web Client UI, the lead developer, who heads a team of developers, opens the change document and
sets the status In Development.
2. Via the Transport Management assignment block, the lead developer creates a transport request in the
development system. The lead developer adapts the relevant data, for example, the description for the
transport request and whether it’s a workbench or a customizing request. The lead developer additionally
creates a task for each of the developers in the team.
3. The developers log on to the development system via the Landscape assignment block. In the development
system, they implement the requested features and save their work to the tasks assigned to them by the
lead developer.
4. Once the features are implemented, the developers release their tasks in the transport requests in the
development system with the transport organizer transaction (SE09).

Change Control Management

Change Request Management PUBLIC 69
5. The lead developer hands over the change document to testing and saves the change document.

The status of the change document proceeds to To Be Tested.

6. In the SAP Transportation Management infrastructure of the managed landscape, this triggers the creation
and release of a transport of copies (ToC), with the content of the original transport request.

 Note

Transports of copies are useful when the objects are changed several times: Test transports are
imported only into the test system. Only the original transport request is queued in the buffer of the
production system. Therefore, the production buffer is not filled up with erroneous transports that
will never be imported into the production system. The only transport requests that are added to the
production buffer are those that are to be imported into the production system. When you activate the
parameter AIC_TOC_DELTA_SWITCH, transports of copies are created only for transport requests that
have been changed. For more information, see SAP Note 3158273 .

 Note

If you don’t want to import the changes immediately, replace the COPY_ALL_ENH action with the
COPY_ALL action in Customizing for SAP Solution Manager (transaction SPRO) under Capabilities
(Optional) Change Control Management Change Request Management Framework Make Settings
for Change Transaction Types . If you want to use the COPY_ALL_ENH action, see SAP Note
2445103 .

7. After the transport of copies was imported into the test system, the tester logs on to the test system via
the Landscape assignment block and starts testing the change.
8. In the change document, the tester indicates the test result:

• If the test was not successful, the tester returns the change document to the developer. The change
document returns to status In Development.
• If the change fulfils the test criteria, the tester confirms successful testing. The change document
proceeds to status Successfully Tested. This releases the transport requests associated with the
change document for import to the test system and delivery to the production system import buffer.
9. After successful testing, there are two options to proceed:

• The tester requests the preliminary import of the normal change. If this request is approved, the
transport requests associated with the change document can be imported immediately, independent
of any mass import into the follow-on system. This accelerates the import process for normal changes.
• The change manager sets the production status without preliminary import. The IT operator triggers
the import manually from the task list. All transport requests are imported into the test system and
then into the production system. To do this, the change cycle must be in the correct phase, that is, Go
Live, Deploy, or Active (depending on cycle type).

Next Steps

Preliminary Import of Normal Changes [page 71]

Change Control Management

70 PUBLIC Change Request Management
Related Information

Change Cycles [page 28]

Starting an Import: Scheduling [page 130]
Creating Transports of Copies (ToC) [page 123]
PPF Actions for SMMJ Normal Change [page 212]

4.2.2.1 Preliminary Import of Normal Changes

To accelerate the import process for normal changes, you can request the preliminary import of a normal
change into a follow-on system. This means that the import of the transport requests associated with the
normal change is carried out at once, independent of any mass import into the follow-on system.

Prerequisites

You have configured the preliminary import function.

The status of the normal change is Successfully Tested, that is, all transport requests have been released.

Context

 Note

• The preliminary import of a normal change (or the import of an urgent change) doesn’t remove the
transport requests from the import buffer of the systems where the transport requests are imported,
waiting to be imported again from a mass import. The downgrade protection conflict of transport
requests (cross-system object lock and release check) is also not removed. For details, refer to SAP
Note 1826789 .
• The preliminary import action can be carried out despite a lock in the task list. By default, in the normal
change process, if the development system is locked in the task list, you cannot create a transport
request. However, with the preliminary import function, you can trigger a preliminary import even when
the whole task list is locked.
• For central CTS-enabled cycles, the preliminary import function supports “uneven” cluster tracks, that
is, not all system clusters in the cluster track contain the same number of systems with the same roles.

Change Control Management

Change Request Management PUBLIC 71
 Overview: Preliminary Import Process

Procedure

1. The tester requests preliminary import.

The status of the normal change proceeds to Preliminary Import Requested.

2. The change manager approves the preliminary import.

 Note

The change manager who approves the preliminary import request should not be the user who set the
status to Successfully Tested.

The transport request for the normal change is automatically imported into the assigned follow-on system.

If the import was successful, the status of the normal change proceeds to Testing for Preliminary Import.
3. After successful testing, the tester confirms successful test.

The transport request of the normal change is automatically imported into the next system in the
landscape.

When the transport request is in the import queue of the production system, the normal change proceeds
to status Tested for Production Import. Otherwise, it keeps status Testing for Preliminary Import.

Change Control Management

72 PUBLIC Change Request Management
4. When the normal change is in status Tested for Production Import, the change manager can authorize the
transport request for import to production.

The status proceeds to Authorized for Import.

5. Finally, the IT operator imports the normal change into production.

In the back-end system, the transport requests are imported into the production system.

The status of the normal change proceeds to Imported into Production.

Related Information

Downgrade Protection [page 360]

System Cluster [page 403]
Configuring the Preliminary Import Function [page 73]

4.2.2.1.1 Configuring the Preliminary Import Function

Use

To use the preliminary import function, you can adapt your existing system configuration for the normal
change process.

 Note

This procedure is only relevant if you have been using the normal change process in your SAP Solution
Manager system before the preliminary import function was introduced, by copying the standard normal
change transaction type into your namespace.

When you create a new user status, the system generates a new technical number. In the SAP standard
delivery, the preliminary import function introduces four new user statuses, with technical numbers ranging
from E0011 to E0014. As these numbers might already be in use by your customer-specific user statuses, you
must adapt the user status profile manually.

In the SAP standard delivery, the preliminary import function is a side-process starting in the standard user
status Successfully Tested and returning to the user status Imported into Production. You must analyze the
equivalent user statuses in your user status profile, as they are the start and end point in your process.

 Note

The preliminary import function must be triggered after the transport request is released in the normal
change. Therefore, you should not configure it in the user status Successfully Tested.

Change Control Management

Change Request Management PUBLIC 73
Procedure

Step 1: Create new authorization keys (optional)

If you use your own authorization keys in your customer-specific user status profile for the normal change,
create four new authorization keys.

1. In Customizing (transaction SPRO), select SAP Solution Manager Capabilities (Optional) Change
Control Management Transactions Status Management Define Status Profile for User Status .
2. Select Environment Authorization Key and change to edit mode.
3. Select the authorization keys SMMJ_04, SMMJ_05, SMMJ_06, and SMMJ_07.
4. Choose Copy.
5. Adapt the standard authorization keys to your namespace.

Step 2: Add preliminary import user statuses to user status profile

1. In Customizing (transaction SPRO), choose SAP Solution Manager Capabilities (Optional) Change
Control Management Transactions Status Management Define Status Profile for User Status .
2. Select your normal change status profile, and choose Details.
3. Insert four new user statuses, based on the SAP standard preliminary import user statuses, as follows:
1. The preliminary import user statuses should have a status number between the start and end user
status numbers identified in the process, so they should be between the user statuses for Successfully
Tested and Imported into Production.
2. In the Status field, enter the same values as in SAP standard.
3. In the Lowest, field enter the user status number of the In Development user status (or the equivalent
customer-specific user status).
4. In the Highest field, enter the number of the next preliminary import user status, to only reach the next
user status. The last user status, Authorized for Import, should have the status number of the Imported
into Production user status (or customer-equivalent user status).
5. Add the newly created authorization keys to the user statuses.
4. Save your entries.

 Note

The system automatically creates new EXXX status numbers for your new user statuses. You can display
them in table TJ30, in transaction SE16. In the STSMA field, enter the name of the normal change status
profile. The system displays all technical user statuses for the status profile.

The following table shows the placeholders for the customer-specific user status, as used in this
documentation:

SAP Standard User Status SAP Standard User Status Placeholder for Customer- Authorization Key
Description Specific User Status

Preliminary Import E0011 <EXXX1> <Transaction type>_X1

Requested

Testing for Preliminary Import E0012 <EXXX2> <Transaction type>_X3

Change Control Management

74 PUBLIC Change Request Management
SAP Standard User Status SAP Standard User Status Placeholder for Customer- Authorization Key
Description Specific User Status

Tested for Production Import E0013 <EXXX3> <Transaction type>_X4

Authorized for Import E0014 <EXXX4> <Transaction type>_X5

Step 3: Adapt roles in authorization object B_USERSTAT

Adapt the roles in authorization object B_USERSTAT, in transaction PFCG.

User status Authorization key Role

<EXXX1> <Transaction type>_X1 All roles used in Change Request Man-

agement

<EXXX2> <Transaction type>_X2 Change Manager, System Administra-

tor

<EXXX3> <Transaction type>_X3 Tester, System Administrator

<EXXX4> <Transaction type>_X4 IT Operator, System Administrator

Step 4: Create PPF actions and conditions

1. To create the PPF actions that set the user statuses, and to adapt old PPF actions, in
Customizing (transaction SPRO), choose SAP Solution Manager Capabilities (Optional) Change
Control Management Transactions Actions Change Actions and Conditions Define Action Profiles
and Actions .
2. Create the PPF actions in the table with HF_SET_STATUS implementation, container element
USER_STATUS, and the values listed in the table. You can also copy another PPF action with the
HF_SET_STATUS implementation, but the texts in all languages are copied with it.

Action Definition Sets User Status (in Further PPF Container Ele- Definition of Container El-
PPF container element ment ement
USER_STATUS)

<Transaction type>_RE- EXXX1

QUEST_PRELIMINARY_MJ

<Transaction type>_AP- EXXX2 PRELIMINARY_APPROVE 1. In the container editor,

PROVE_PRELIMINARY_MJ (used for authorization) choose

PRELIMINARY_APPRO
VE.

2. Under D. Type

ABAP Dict. Data

Type , enter CHAR1

in the Type Name field.

Change Control Management

Change Request Management PUBLIC 75
 Action Definition Sets User Status (in Further PPF Container Ele- Definition of Container El-
PPF container element ment ement
USER_STATUS)

<Transaction type>_CON- EXXX3

FIRM_SUCC_TEST_MJ

<Transaction type>_AU- EXXX4

THORIZE_PRE_IMPORT_MJ

<Transaction E0009 (equivalent to

type>_CANCEL_PRE- Successfully Tested status)
LIMIN_IMPORT_MJ

<Transaction EXXX2
type>_DIRECT_PRLIMI-
NARY_APPR_MJ

(not relevant for SAP Solu-

tion Manager 7.1 SP07 and
above)

<Transaction E0002 (equivalent to In PREDOC_STATUS (used to 1. In the container

type>_SET_BACK_TO_DE- Development status) set the request for change editor, choose

VELOP_MJ to E0005) PREDOC_STATUS.

(not relevant for SAP Solu- 2. Under Initial Value

tion Manager 7.1 SP07 and ABAP Dict. Data

above) Type , enter E0005.

<Transaction type>_IM- E0006 (equivalent to

PORT_NC_INTO_PROD_MJ Imported into Production
status)

3. You can compare your Customizing entries to the standard action (SMMJ_...in the PPF action
SMMJ_ACTIONS action profile).

 Note

Since SAP Solution Manager 7.1 SP07, action <transaction type>_DIRECT_PRLIMINARY_APPR_MJ

has been replaced by <transaction type>_APPROVE_PRELIMINARY_MJ, and
<transaction type>_SET_BACK_TO_DEVELOP_MJ has been replaced by <transaction
type>__TESTED_AND_NOT_OK, by adopting the PPF conditions of the replacing PPF actions.

4. In Customizing (transaction SPRO), choose SAP Solution Manager Capabilities (Optional) Change
Control Management Transactions Actions Change Actions and Conditions Define Conditions .

Change Control Management

76 PUBLIC Change Request Management
5. Choose Schedule Conditions, and make the following entries:

PPF Condition Schedule Condition

<transaction type>_REQUEST_PRELIMINARY_MJ &CRM Service Process.User Status& [*] E0009+

+MJHEAD

and &CRM Service Process.ErrorFreeFlag& = X

(or equivalent user status for Successfully Tested)

<transaction type>_APPROVE_PRELIMINARY_MJ • Up to SAP Solution Manager 7.1 SP06:

&CRM Service Process.User Status& [*] EXXX1+
+MJHEAD
and &CRM Service Process.ErrorFreeFlag& = X
and &PRELIMINARY_APPROVE& = X
(or equivalent user status for Successfully Tested)
• From SAP Solution Manager 7.1. SP07:
&CRM Service Process.User Status& [*] E0009+
+HEAD
or &CRM Service Process.User Status [*] E0011+
+HEAD
and &CRM Service Process.ErrorFreeFlag& = X
and &PRELIMINARY_APPROVE& = X

<transaction type>_CONFIRM_SUCC_TEST_MJ &CRM Service Process.User Status& [*] EXXX2+++

+HEAD

and &CRM Service Process.ErrorFreeFlag& = X

<transaction type>_AUTHORIZE_PRE_IMPORT_MJ &CRM Service Process.User Status& [*] EXXX3+++

+HEAD

and &CRM Service Process.ErrorFreeFlag& = X

<transaction type>_CANCEL_PRELIMIN_IMPORT_MJ &CRM Service Process.User Status& [*] EXXX2+++

(not relevant for SAP Solution Manager 7.1 SP07 and +HEAD
above)
or &CRM Service Process.User Status& [*] EXXX3+++
+HEAD

or &CRM Service Process.User Status& [*] EXXX4+++

+HEAD

<transaction type>_DIRECT_PRLIMINARY_APPR_MJ (not &CRM Service Process.User Status& [*] E0009+++

relevant for SAP Solution Manager 7.1 SP07 and above) +HEAD

and &CRM Service Process.ErrorFreeFlag& = X

(or equivalent user status for Successfully Tested instead

of E0009)

Change Control Management

Change Request Management PUBLIC 77
 PPF Condition Schedule Condition

<transaction type>_SET_BACK_TO_DEVELOP_MJ &CRM Service Process.User Status& [*] EXXX2+++

+HEAD

and &CRM Service Process.ErrorFreeFlag& = X

<transaction type>_IMPORT_NC_INTO_PROD_MJ &CRM Service Process.User Status& [*] EXXX4+++

+HEAD

and &CRM Service Process.ErrorFreeFlag& = X

<transaction type>_TESTED_AND_NOT_OK_MJ Starting with SAP Solution Manager 7.1 SP07:

or &CRM Service Process.User Status& [*] E0004+

+MJHEAD

or &CRM Service Process.User Status& [*] E0012+

+MJHEAD

6. Make the following entries for the PPF start conditions:

PPF Condition Start Condition

<transaction type>_REQUEST_PRELIMINARY_MJ No

<transaction type>_APPROVE_PRELIMINARY_MJ No

<transaction type>_CONFIRM_SUCC_TEST_MJ No

<transaction type>_AUTHORIZE_PRE_IMPORT_MJ No

<transaction type>_CANCEL_PRELIMIN_IMPORT_MJ No
(not relevant for SAP Solution Manager 7.1 SP07 and
above)

<transaction type>_DIRECT_PRLIMINARY_APPR_MJ (not No

relevant for SAP Solution Manager 7.1 SP07 and above)

<transaction type>_SET_BACK_TO_DEVELOP_MJ No

<transaction type>_IMPORT_NC_INTO_PROD_MJ No

Step 5: Assign Change Request Management actions and conditions

1. To create the relevant Change Request Management settings for the preliminary import function, in
Customizing (transaction SPRO), choose SAP Solution Manager Capabilities (Optional) Change
Control Management Change Request Management Framework Make Settings for Change Transaction
Types , select your normal change transaction type and open Assign Actions.

Change Control Management

78 PUBLIC Change Request Management
 Transaction Type Status Profile User Status Sequence Action Logic

<your normal <transaction <EXXX1> 10 SAVE_PARTNER Inserts current

change transac- type>HEAD user's business
tion type> partner in a part-
ner function

<your normal <transaction <EXXX2> 10 SAVE_PARTNER Inserts current

change transac- type>HEAD user's business
tion type> partner in a part-
ner function

<your normal <transaction <EXXX2> 20 PRM_NEXT_IMP Synchronizes

change transac- type>HEAD transports in test
tion type> systems

<your normal <transaction <EXXX1> 10 PRM_NEXT_IMP Synchronizes

change transac- type>HEAD transports in test
tion type> systems

2. To register the relevant Change Request Management action as executed late, after the consistency checks
have been executed, in Customizing (transaction SPRO), choose SAP Solution Manager Capabilities
(Optional) Change Control Management Change Request Management Framework Make Settings for
Change Transaction Types , select your normal change transaction type and open Define Execution Time
of Actions.
3. Make the following entries:

Transaction Type Status Profile User Status Sequence Action Time

<transaction <transaction <EXXX2> 20 PRM_NEXT_IMP Execute After

type> type>HEAD Checks

4. To create the relevant Change Request Management conditions for the preliminary import
function, in Customizing (transaction SPRO), choose SAP Solution Manager Capabilities (Optional)
Change Control Management Change Request Management Framework Consistency Checks Assign
Conditions to Status Values and make the following entries:

Trans.Type Status User Sta- Seq. Condition Applica- Message MT User Sta-
Profile tus Status tion Area tus
Transition

<trans.type <trans.type <EXXX1> 10 PRELIM_P Cancel E0009

> >HEAD RD_NOT_I (equivalent
MP to
Successfull
y Tested)

Change Control Management

Change Request Management PUBLIC 79
 Trans.Type Status User Sta- Seq. Condition Applica- Message MT User Sta-
Profile tus Status tion Area tus
Transition

<trans.type <trans.type <EXXX2> 10 SAME_USE AI_CRM_C 069 Warning E0009

> >HEAD R M_MESSAG (equivalent
E to
Successfull
y Tested)

<trans.type <trans.type <EXXX2> 20 PRELIM_P Cancel E0009

> >HEAD RD_NOT_I (equivalent
MP to
Successfull
y Tested)

<trans.type <trans.type <EXXX3> 10 PRELIM_T Cancel EXXX2

> >HEAD R_IN_PRD
_BUF

Step 6: Specify status attributes

1. In Customizing (transaction SPRO), choose SAP Solution Manager Capabilities (Optional) Change
Control Management Change Request Management Framework Make Settings for Change Transaction
Types .
2. For your normal change transaction type and status profile (<Transaction type>HEAD), make the following
entries under Specify Status Attributes:

User Status System Role Type Type Sequence

EXXX1 Test System Processing Phase 1

EXXX2 Test System Processing Phase 1

EXXX3 Test System Processing Phase 1

EXXX4 Test System Processing Phase 1

Step 7: Save partner Customizing settings

1. To create the relevant partner settings for the preliminary import function, in Customizing (transaction
SPRO), choose SAP Solution Manager Capabilities (Optional) Change Control Management Change
Request Management Framework Make Settings for Change Transaction Types .
2. For your normal change transaction type and status profile (<transaction type>HEAD), make the following
entries under Specify Partner Assignment and Check. You can either enter the SAP standard partner
functions or your specific partner functions.

Change Control Management

80 PUBLIC Change Request Management
 User Status Partner to Partner from

EXXX1 SMCD0001 SDCR0002

EXXX2 SDCR0002 SMCD0002

4.2.3 Processing Urgent Changes

Use this process to make urgent changes that are not part of a project plan, for example, to fix an error
in existing functionality that could jeopardize a production environment. The change is transported into the
production system faster than a normal change.

Prerequisites

• A request for change has been approved and released for development, creating a change document of the
type Urgent Change.
• If you have been using SAP Solution Manager before, you have configured the dialog window to create
transport requests.

Context

 Caution

Users must not be permitted to create, maintain, or release transport requests or tasks directly in the
Transport Organizer. This is because Change Request Management cannot detect that transport requests
that were created outside of Change Request Management belong to a scenario.

Change Control Management

Change Request Management PUBLIC 81
 Processing Urgent Changes

Procedure

1. In the web client UI, the lead developer, who heads a team of developers, opens the change document and
sets the status to In Development.
2. The developer creates a transport request and one or more tasks with the following options:

• Create several tasks at once

• Create tasks for other users
• Create Customizing or Workbench requests
3. The lead developer enters the relevant system and client and, if necessary, assigns the transport request to
another developer.
4. The developers log on to the development system via the Landscape assignment block. They implement
the requested features in the development system and save their work to the tasks assigned to them by
the lead developer.
5. The developer releases the transport request manually in the Transport Management assignment block.

A code inspector check is run.

Change Control Management

82 PUBLIC Change Request Management
 The original transport is exported from the development system.
6. The developer hands over the urgent change to testing and saves the change document.

The status of the change document proceeds to status To Be Tested and the original transport is imported
into the test system.
7. The IT operator opens the change document and assigns it to a tester.

 Note

The current processor can be assigned automatically if the tester is maintained as a business partner
in the system.

The change document appears in the tester's worklist.

8. The person assigned as tester logs on to the test system via the Landscape assignment block and starts
testing the urgent change.
9. In the change document, the tester indicates the test result:

• If the test was not successful, the tester returns the change document to the developer. The urgent
change returns to status In Development.

 Note

Urgent changes don’t support test transports. Because the original transport request was already
released before, the developer needs a new transport request to correct the implementation and
hand it over to testing again. This is repeated until the changes are tested successfully.

For central CTS-enabled cycles, the preliminary import function supports “uneven” cluster tracks,
that is, not all system clusters in the cluster track contain the same number of systems with the
same roles.

• If the change fulfills the test criteria, the tester confirms successful testing. The urgent change
proceeds to status Successfully Tested and can be imported into the production system.
10. After successful testing, the change manager approves the urgent change for import into the production
system.

The urgent change proceeds to status Authorized for Production.

11. The IT operator opens the change document and starts the import of the urgent change into the
production system.

 Tip

To make sure that your parallel test and production systems are consistent, you can synchronize the
import of urgent changes with a task in the task list.

The urgent change proceeds to status Imported into Production.

12. The change manager confirms that the change has been made as desired.

The urgent change proceeds to status Confirmed.

13. To lock the urgent change for editing, the change manager must set the change document to final status
Completed.

Change Control Management

Change Request Management PUBLIC 83
Results

When all change documents related to the request for change are in their final status, the request for change
automatically proceeds to status Implemented.

After the transport request of an urgent change is imported into the test and production systems, the transport
request remains in the import buffer. This makes sure that the changes are not overwritten by other transport
requests in the normal change cycle.

Next Steps

 Note

If you want to set multiple change documents to the next status (for example, from Authorized for
Production to Imported into Production), execute the batch job CRM_SOCM_SERVICE_REPORT. To set all
change documents assigned to a change cycle to the next status, specify the change cycle ID. You can also
specify other selection criteria. For example, you can select the urgent changes as the transaction type and
specify a change cycle ID to set all urgent changes of the change cycle to the next status. You can also use
this report to import all changes at a scheduled time, into the follow-on systems.

Caution: Using this report for a batch import of multiple documents may lead to issues:

• The dependencies of different change documents are not foreseeable. As a result, the system cannot
process the import order automatically.
• If multiple imports are triggered simultaneously, the program might be impacted due to interferences.

If you have implemented the Business Add-In CRM_ORDER_STATUS, your implementation will not be called.

For more information about Change Request Management-related roles and profiles, see SAP Note 834534
and the security guide for Change Control Management on SAP Help Portal at https://help.sap.com/
viewer/p/SAP_Solution_Manager <current release> Security Application-Specific Security Guide
Change Control and IT Service Management Scenarios .

Related Information

Change Cycles [page 28]

Continual Cycle [page 29]
System Cluster [page 403]
Reverting Changes [page 149]
Synchronizing Urgent Changes in Parallel Systems [page 317]
PPF Actions for SMHF Urgent Change [page 201]

Change Control Management

84 PUBLIC Change Request Management
4.2.3.1 Using the Code Inspector in Urgent Changes

In urgent changes, you can use the code inspector to check your programs and other objects.

Context

 Note

If you change an urgent change to status To Be Tested, the transport request is released automatically,
without the code inspector checking the request. To trigger the code inspector, you must release the
transport request manually.

Procedure

1. In the WebClient UI, in the Transport Management assignment block, choose a transport request and select
Release Transport Request.

A dialog box displays the result in the Code Inspector column.

2. Check the result of the code inspector check.

• “Passed” (green traffic light): You can release the transport request.
• “Not passed” (red traffic light): You must fix the errors before you can release the transport request.

a. To see the details of the failed check, go to the managed system in which the transport request was
created, run the code inspector locally, and display the transport request details.
b. Correct the errors reported by the code inspector.
3. Release the transport request in the WebClient UI.

Related Information

Releasing Transport Requests [page 125]

4.2.3.2 Distributing Urgent Changes

Use

If an urgent change you have made in a production system is also relevant for other, parallel production
systems or for another productive client in the same change control landscape, you can distribute it to them

Change Control Management

Change Request Management PUBLIC 85
with the ”Distribute change” action. The system creates a new urgent change containing the data of the
original urgent change, and transports the corrections to the specified system.

Prerequisites

• To activate this functionality for the SAP standard transaction type for urgent changes (SMHF), make the
following settings:
• In Customizing for SAP Solution Manager, under Capabilities Change Control Management
Transactions Actions Change Actions and Conditions Define Action Profiles and Actions ,
remove the Inactive flag for the action definition SMHF_DISTRIBUTE.
• In Customizing for SAP Solution Manager under Capabilities Change Control Management
Implementation of Dialog Boxes in the WebClient UI Assign Dialog Box to a PPF Action , activate
the action definition SMHF_DISTRIBUTE.
• In Customizing for SAP Solution Manager under Capabilities Change Control Management
Change Request Management Framework Make Settings for Change Transaction Types , assign the
following Customizing settings for consistency checks to the user statuses of your process.

User Status Sequence Consistency Application Area Message Num- Message Type
Check ber

To Be Tested 60 DISTRIBUTOR CHM1_AC- 057 Information

TION_LOG

Successfully 60 DISTRIBUTOR CHM1_AC- 057 Information

Tested TION_LOG

Authorized for 60 FATHER_IS_PRO- CHM1_AC- 063 Cancel

Production DUCTIVE TION_LOG

Authorized for 60 DISTRIBUTOR CHM1_AC- 057 Information

Production TION_LOG

 Note

DISTRIBUTOR consistency check: The system checks the condition to see whether a transaction
that is to be distributed is assigned to the urgent change. If this condition finds a distributed
change, the system displays the message CHM1_ACTION_LOG 057.

FATHER_IS_PRODUCTIVE consistency check: The system checks whether the transport request of
the urgent change from which the distributing urgent change was created has been imported into
the production system. If so, the system displays the message CHM1_ACTION_LOG 063.

• To activate this functionality for your customer-specific urgent change transaction type, make the following
settings:
• If you have copied your urgent change transaction type from the standard transaction type before SAP
Solution Manager 7.1 SP08, create a PPF action in the PPF action profile, with the same settings as

Change Control Management

86 PUBLIC Change Request Management
 the SMHF_DISTRIBUTE action. The name of your new PPF action must contain the character string
DISTRIBUTE, for example, ZMHF_DISTRIBUTE_NEW.
• If you have copied your urgent change transaction type from the standard transaction type
in SAP Solution Manager 7.1 SP08 or higher, the system automatically copies the action
SMHF_DISTRIBUTE, to [XX]HF_DISTRIBUTE. Activate this PPF action in Customizing for SAP Solution
Manager, under Change Control Management Implementation of Dialog Boxes in WebClient UI
Assign Dialog Box to a PPF Action .
• In Customizing for SAP Solution Manager under Capabilities Change Control Management
Change Request Management Framework Make Settings for Change Transaction Types , assign the
following Customizing settings for consistency checks to your customer transaction type to the user
statuses of your process.

User Status Sequence Consistency Application Area Message Num- Message Type
Check ber

To Be Tested 60 DISTRIBUTOR CHM1_AC- 057 Information

TION_LOG

Successfully 60 DISTRIBUTOR CHM1_AC- 057 Information

Tested TION_LOG

Authorized for 60 FATHER_IS_PRO- CHM1_AC- 063 Cancel

Production DUCTIVE TION_LOG

Authorized for 60 DISTRIBUTOR CHM1_AC- 057 Information

Production TION_LOG

Activities

1. When an urgent change has status “Successfully tested”, you can choose the “Distribute change” action.
2. The system displays all production systems into which the change can be distributed.
3. After selecting a production system, the system confirms that the change has been distributed. The IBase
and the data for developer, tester, IT operator and change manager are copied into the new urgent change.

 Note

When the action triggers the import of the distributed urgent change, a downgrade check is performed. For
more information, see Downgrade Protection [page 360].

Change Control Management

Change Request Management PUBLIC 87
4.2.3.3 Configuring the Dialog Window for Creating
Transport Requests in Urgent Changes

Use

When an urgent change is set to “In development”, the system displays the Create Transport Requests dialog
window.

 Note

If you are a new customer with SAP Solution Manager 7.2, the Customizing for this function is copied
automatically in the SAP Solution Manager configuration. In this case you can ignore this documentation.

If you have been using change request management with SAP Solution Manager before, and copied your
transaction types already in an earlier release or Support Package, you have to customize this functionality
for your customer-specific transaction type.

Procedure

The configuration procedure consists of two steps:

Step 1: Create a PPF container element in the PPF action which sets the user status 'In Development'

1. In Customizing for SAP Solution Manager under Capabilities Change Request Management
Transactions Actions Change Actions and Conditions Define Action Profiles and Actions , select your
action profile for the urgent change (for example, ZMHF_ACTIONS).
2. Choose Action Definition to display the actions assigned to the profile.
3. Select the action ZMHF_IN_PROCESS (or your copy from the original action SMHF_IN_PROCESS and
choose Save.
4. Choose Processing Types.
5. Choose Change Definition.
6. Choose Create Transport.
7. Choose Create.
8. Create a new container element using the following data:
• Element: CREATE_TRANSPORT
• Name: CREATE_TRANSPORT
• Short Description: CREATE TRANSPORT
• Object Type: ABAP class, CL_AIC_PPF_CONT_ASSIGN_TRANSP
9. Save your entries.

Step 2: Create an entry in the Dialog Window Framework to register the dialog window 'Create Transport
Requests' to the PPF action

1. In Customizing for SAP Solution Manager under Capabilities Change Request Management
Implementation of Dialog Boxes in WebClient UI Assign Dialog Box to a PPF Action. , select your action
profile for the urgent change (for example, ZMHF_ACTIONS).

Change Control Management

88 PUBLIC Change Request Management
2. Select SMHF_IN_PROCESS and choose Copy as...
3. Adapt the entry to your transaction type, action profile and action.
4. Save your entries.

Optional Step: Add a filter value for a Business Add-In implementation

If the name of your PPF action does not end with “..._IN_PROCESS”, you have to add a filter value for a Business
Add-In (BAdI) implementation, so that the system can call the BAdI. The filter calls all PPF actions ending with
'IN_PROCESS'. If your action has another name, you have to add the filter value in the BADI implementation
calling the dialog window.

 Note

If you do not have a developer key, you cannot add the filter value. In this case, copy the PPF action and the
condition and use the name ending with “..._IN_PROCESS”.

1. In Customizing for SAP Solution Manager under Capabilities Change Request Management
Implementation of Dialog Boxes in WebClient UI Implement BADI Methods for Dialog Box , enter the
name of the BAdI definition AIC_POPUP_ON_CLOSE_EVENT.
2. Choose Display.
3. Under the BAdI definition, choose Implementations and select the implementation
AIC_CREATE_TRANSPORT_REQ.
4. Select the implementation AIC_CREATE_TRANSPORT_REQ by double-clicking it.
5. Add the additional filter value PPF_ACTION = <your PPF action name>.

Result

When in your system an urgent change is set to “In development”, the system displays the Create Transport
Requests dialog window.

4.2.4 Processing Standard Changes

Use this process for frequent changes that have no technical impact, such as adding a new currency or
location. Standard changes are no-risk or low-risk changes and can therefore be processed without approval.

Prerequisites

• Standard changes can only be used in ABAP systems.

• The change cycle has a task list.
• In the managed development system, you have implemented SAP Note 2402504 .
• In the managed development system, you have installed the most recent Solution Tools Plug-In (ST-PI).
The required minimum version is ST-PI 2008_1_7xx SP 16 or ST-PI 740 SP 6, respectively.

Change Control Management

Change Request Management PUBLIC 89
• In the Administration Cockpit, on the Landscape Overview tab, you have selected the On option in the
Upon-Saving Checks column for the systems in which changes are to be made.
• If a request for change exists, in assignment block Details, the option Standard Change is selected.

 Note

Requirements Management: If you work with IT requirements, you can use standard changes as well.
The Standard Change checkbox is unnecessary for an IT requirement, because IT requirements are
based on projects and were already approved via a business requirement.

• Objects can only be saved on the transport request of a standard change if they are on the allowlist.
Otherwise, you receive an error message. In that case, either you add the relevant objects to the allowlist,
or you reassign the transport request to a normal change or to an urgent change.
You can define the allowlist objects in the Administration Cockpit on the Allowlist Objects tab. Developers
can also request that objects are added to the allowlist.

Context

Change Control Management

90 PUBLIC Change Request Management
Procedure

1. If the scope of the request for change contains no other change document type than standard change,
the request for change proceeds directly from status Validation to Being Implemented without further
approval. This is the characteristic feature of a standard change process.

One or more standard changes are created automatically.

2. In the Web Client UI, the developer opens the change document and sets the status to In Development.
3. In the development system, the developer creates a transport request via the Transport Management
assignment block.
4. When the features are implemented, the developers release their tasks in the transport requests in the
development system, in the transport organizer (transaction SE09).
5. The developer hands over the standard change to testing and saves the change document.

 Note

A transport-related check makes sure that only allowlist objects are assigned to the transport request.
If not, the standard change can’t proceed to testing. The developer can either request to add the
missing objects to the allowlist or select another transport request that is assigned to a different
change document type. The change manager can process the requested allowlist objects in the
Transport-Related Checks assignment block or in the My Inbox SAP Fiori app. After processing, the
system enters your action as a text log in the standard change itself.

The change document proceeds to status To Be Tested.

6. In the SAP TM infrastructure of the managed landscape, a transport of copies (ToC) with the object
content of the original transport request is created and released. The ToC is added to the import buffer of
the next test system and is imported automatically into the test system.
7. The tester logs on to the test system via the Landscape assignment block and starts testing.
8. In the change document, the tester indicates the test result:

• If the change can be imported into the production system, the tester confirms successful testing.
The change document proceeds to status Successfully Tested. This releases the transport requests
associated with the change document. Transport requests are ready to be imported from the task list
into the test systems.
• If the test was not successful, the tester returns the change document to the developer. The change
document returns to status In Development.
9. After successful testing based on the ToC, import into the productive system happens in two steps:
a. A scheduled background job imports the original transport request into all test systems.
b. From the test systems, a scheduled background job imports the original transport requests into the
productive system.

The change document proceeds to status Imported into Production.

10. When all standard changes related to the request for change have reached the status Imported into
Production, the status of the request for change is automatically set to Implemented.
11. The requester completes the request for change by setting its status to Confirmed.

Change Control Management

Change Request Management PUBLIC 91
Next Steps

 Note

For more information on change management-related roles and profiles, see: SAP Note 834534
and the security guide for Change Control Management on SAP Help Portal at https://
help.sap.com/viewer/p/SAP_Solution_Manager <current release> Security Application-Specific
Security Guide Change Control and IT Service Management Scenarios .

Related Information

Processing Requests for Change [page 56]

Requirements Management
Performing Transport-Related Checks [page 150]
Defining Allowlist Objects [page 329]
Creating Transports of Copies (ToC) [page 123]
Importing Transport Requests [page 127]
PPF Actions for SMSG Standard Change [page 222]

4.2.5 Processing Defect Corrections

Use this process to make corrective changes during the Build and Test phase of a phase cycle or release
cycle, or during the Active phase of a continual cycle. In these phases, no new normal changes can be created
because this would change the specified and approved project scope.

Prerequisites

You are in the Build or Test phase of a phase cycle or release cycle, or in the Active phase of a continual cycle.

Context

A defect correction isn’t related to a specific change document or request for change: Defect corrections are
used in integration testing, and this testing is based on all changes.

Defect corrections don’t need approval because the project scope was approved in change transactions during
earlier phases of the change cycle.

Change Control Management

92 PUBLIC Change Request Management
 Processing Defect Corrections

Procedure

1. A tester wants to bring an identified error to the attention of a developer. In the WebClient UI, the tester
creates a defect correction and describes the symptoms.
2. The IT operator forwards the defect correction to the developer responsible, who sets the status of the
change document to In Correction.
3. The developer creates one or more transport requests assigned to the defect correction, and corrects the
error in the development system.
4. The developer submits the change document for another test. The scheduled import job imports the
transport requests of the defect correction into the appropriate system.

When the import is completed, the defect correction automatically proceeds to status To Be Retested.
5. The tester checks the functions and confirms successful testing.

The defect correction proceeds to status Successfully Retested.

Change Control Management

Change Request Management PUBLIC 93
6. When the change cycle proceeds to the correct phase (that is, Go Live or Deploy), the import into the
productive system takes place and sets the defect correction to status Imported into Production.

Related Information

Phase Cycle [page 35]

Release Cycle [page 44]
Use Case: Creating Defect Correction from Defects [page 94]
PPF Actions for SMTM Defect Correction [page 227]

4.2.5.1 Use Case: Creating Defect Correction from Defects

Use

As an option, you can create a defect correction from a defect of a test system. SAP supports this use case
by delivering standard Customizing. In the standard process, you can create a defect correction as a follow-up
document from an incident because from a technical point of view, an incident and a defect are identical.
The only difference is that the incident targets the production system, whereas the defect targets the quality
system.

Process

1. Copy the SAP standard incident transaction type SMIN to your customer namespace and rename it
"defect".
2. To create the copy Customizing from your customer defect correction to the "defect", copy the SAP
standard Customizing from the standard incident to the defect correction and adjust the names of the
transaction types.

More Information

Processing Defect Corrections [page 92]

Change Control Management

94 PUBLIC Change Request Management
4.2.6 Processing Administrative Changes

Use this process to make a change that doesn't have to be transported with a transport request, for example,
an account number or number range change in a system. Administrative changes typically are initialized by an
IT operator or administrator.

Prerequisites

• A request for change has been approved and released for development, creating a change document of the
type Administrative Change.
• The installation for the relevant production system is assigned to the request for change.

Change Control Management

Change Request Management PUBLIC 95
Context

Processing Administrative Changes

Procedure

1. In the WebClient UI, the IT operator opens the administrative change and sets the status In Process.
2. In the development system, the processor logs on to the Landscape assignment block and makes the
requested change.
3. In the WebClient UI, the processor sets the administrative change to status Completed and saves the
change document.
4. The IT operator confirms that the change was made as requested and sets the status Confirmed.

Change Control Management

96 PUBLIC Change Request Management
 The change document is locked for editing.

Related Information

Request for Change [page 24]

PPF Actions for SMAD Administrative Change [page 181]

4.2.7 Processing General Changes

Use this process to make a change that does not need a connection to the SAP Change and Transport System.
It could be, for example, a repair of a printer or computer in your organization, or a change to a mobile device.

Prerequisites

• A request for change has been approved and released for implementation, creating a change document of
the type General Change.
• The change document is assigned to a change cycle.
• The object affected by the change is maintained in the system with an installation.

Change Control Management

Change Request Management PUBLIC 97
Context

Procedure

1. Depending on the type of change, the processor opens the change document in the worklist or in the Web
Client UI, sets status In Process and saves the change document.
2. After making the change, the processor sets the change document to status To Be Tested.

Change Control Management

98 PUBLIC Change Request Management
3. After successful testing, the processor sets the change document to status To Be Documented and enters
the requester as the next processor. If the change is not ready, the processor can reset the document to In
Process and test it again later.
4. After documentation, the requester sets the change document to status Change Analysis and checks
whether the changes were made as requested.
5. If the change was successful, the requester confirms the general change.

The change document proceeds to status Confirmed and the process is complete.
6. If the change was not successful, the requester sets the change document to status Failed.

• The processor can search for another solution and set the change document to status Restore Source.
• Alternatively, the processor can close the failed change and set the change document to status
Canceled.

Results

In status Confirmed and Canceled, the change document is locked for editing.

Related Information

PPF Actions for SMCG General Change [page 187]

4.2.8 Processing Git-enabled Changes

Use this process to make changes in the development system for your landscape and then transport the
change into production system with Git-enabled CTS.

Prerequisites

• Git-enabled CTS has been set up. For more information, see Configuring Git-enabled CTS [page 455].
• On the development and test system, the same branch (“feature branch”) is active, on the production
system, another branch (“main branch”) is active.
• On the managed systems, you have installed SAP S/4HANA 2020 or higher releases.
• A request for change has been approved and released for development, creating a change document of the
type Git-enabled Change.
• The assigned change cycle must be in a phase that allows the required activity.

 Recommendation

To check whether the assigned change cycle is in a valid phase, assign and maintain consistency
checks.

Change Control Management

Change Request Management PUBLIC 99
Context

 Caution

Users must not be permitted to create, maintain, or release transport requests directly in the Transport
Organizer. This is because Change Request Management cannot identify transport requests that were
created outside of Change Request Management as belonging to a scenario.

The procedure is largely the same as for normal changes, just that the code is pulled from the Git server and
then deployed into the target system. Note that Git-enabled changes don't use the cross-reference check, and
the DGP predecessor check and imminent check.

Change Control Management

100 PUBLIC Change Request Management
Procedure

1. In the Web Client UI, the lead developer, who heads a team of developers, opens the change document and
sets the status In Development.
2. The lead developer assigns a Git repository to the change document.
3. Via the Transport Management assignment block, the lead developer creates a transport request in the
development system. The lead developer adapts the relevant data, for example, the description for the
transport request and whether it’s a workbench or a customizing request. The lead developer additionally
creates a task for each of the developers in the team.
4. The developers log on to the development system via the Landscape assignment block. In the development
system, they implement the requested features and save their work to the tasks assigned to them by the
lead developer.
5. Once the features are implemented, the developers release their tasks in the transport requests in the
development system with the transport organizer transaction (SE09).

 Note

When the transport task is released, the related code change of the features is pushed to the Git
repository that is linked to the development system.

6. The lead developer hands over the change document to testing and saves the change document.

The status of the change document proceeds to To Be Tested.

7. In the Change and Transport System infrastructure of the managed landscape, this pulls the code change
from the Git repository and deploys the content of the latest commit into the test system.
8. After the code change was deployed into the test system, the tester logs on to the test system via the
Landscape assignment block and starts testing the change.
9. In the change document, the tester indicates the test result:

• If the test was not successful, the tester returns the change document to the developer. The change
document returns to status In Development.
• If the change can be imported into the production system, the tester confirms successful testing.
The change document proceeds to status Successfully Tested. This releases the transport requests
associated with the change document on condition that all tasks have been released.
10. After successful testing, the change manager authorizes the deployment into the production system:

To merge the feature branch into the main branch of the Git repository, a pull request is created and
directly approved.
11. The IT operator triggers the deployment into production system.

In the Change and Transport System infrastructure of the managed landscape, this pulls the code change
from the Git repository and deploys the code change into production system.

Results

The current commit, merged to the main branch, is deployed: All changes that were done before this change
are deployed together.

Change Control Management

Change Request Management PUBLIC 101
An import feedback job shifts the other change documents to production status.

Related Information

PPF Actions for SMGH Git-Enabled Change [page 194]

4.2.8.1 Processing Git-enabled Changes with Emergency

Mode

Use this process to make emergency changes that are not part of a project plan, for example, to fix an
issue in an existing functionality that could jeopardize the production environment. The changes are directly
transported to the production system via a dedicated emergency branch while the project development in
another branch is on hold.

Prerequisites

• You have set up Git-enabled CTS. For more information, see Configuring Git-enabled CTS [page 455]
• On the development and test systems, the same branch (for example, development) is active, but on the
production system, another branch (for example, main) is active.
• On the managed systems, you have installed SAP S/4HANA 2020 or a higher release.
• You have upgraded the component UIBAS001 to the latest release for your managed systems.
• The latest piece list AI_CUSTOMIZING has been activated on the production environment of your SAP
Solution Manager system and the custom transaction type for Git-enabled changes has been updated in
report AI_CRM_CPY_PROCTYPE.
• No other unfinished Git-enabled change with emergency mode enabled exists for the Git repository. In
addition, the creation of new Git-enabled changes is not possible for the Git repository, which includes
unfinished Git-enabled changes with emergency mode enabled.
• You have run report /TMWFLOW/GCTS_GIT_REPO_MIGRATE on your SAP Solution Manager system at least
one time after you have upgraded to SAP Solution Manager 7.2 SPS 17 or higher.
• You have updated the authorizations for the administrator user to the latest user role.
• You have assigned parameter AIC_GCTS_ENHANCE with value X in view AIC_WORK_CUSTOM.
• You have created a dedicated branch (for example, emergency) based on the main branch for emergency
mode.

 Note

We recommend that you to create the emergency branch from the main branch in the Git platform (for
example, GitHub).

• You have released all transport tasks for Git-enabled changes with the development branch assigned.

Change Control Management

102 PUBLIC Change Request Management
  Note

Release transport tasks to push the code changes to the Git repository. Otherwise, the code changes
are overwritten and lost when switching the active branch to the emergency branch.

• A request for change has been approved and released for development, creating a change document of the
type Git-enabled Change.
• The assigned change cycle must be in a phase that allows the required activity.

Context

 Caution

Users must not be permitted to create, maintain, or release transport requests directly in the Transport
Organizer. This is because Change Request Management can't identify when transport requests that were
created outside of Change Request Management belong to a scenario.

The procedure is almost the same as for standard Git-enabled changes. The difference is that the emergency
branch is assigned manually and then automatically set as the active branch for a development system and
test system after saving the change document.

Change Control Management

Change Request Management PUBLIC 103
Procedure

1. On the WebClient UI, the lead developer, who heads a team of developers, opens the change document and
sets the status to In Development.
2. The lead developer assigns the Git repository that needs an emergency fix to the change document.
3. On the WebClient UI, the administrator opens the change document and marks the Emergency Mode
checkbox.
4. The administrator selects the emergency branch for the Git repository and saves the change document.
Then, the emergency branch is active for both development system and test system.

Change Control Management

104 PUBLIC Change Request Management
  Note

After the emergency mode has been enabled for a Git-enabled change, the following changes are
made: The code changes from the development branch are undeployed from the development system
and test system, and the code base from the emergency branch is deployed instead. This means that
the code changes from the development branch do not exist in the systems. All unfinished Git-enabled
changes with a development branch assigned are not editable and it is not possible to create a new
Git-enabled change for this Git repository.

5. Via the Transport Management assignment block, the lead developer creates a transport request in the
development system. The lead developer adapts the relevant data, for example, the description for the
transport request and whether it’s a workbench or a customizing request. The lead developer additionally
creates a task for each of the developers in the team.
6. The developers log on to the development system via the Landscape assignment block. In the development
system, they implement the emergency fixes and save their work to the tasks assigned to them by the lead
developer.
7. When the emergency fixes are implemented, the developers release their tasks in the transport requests in
the development system with the Transport Organizer transaction (SE09).

 Note

When the transport task is released, the corresponding code change of the features is pushed to the
Git repository that is linked to the development system.

8. The lead developer hands over the change document to testing and saves the change document. The
status of the change document is set to To Be Tested.
9. In the Change and Transport System infrastructure of the managed landscape, this pulls the emergency
code change from the emergency branch of Git repository and deploys the content of the latest commit
into the test system.
10. When the emergency code change is deployed to the test system, the tester logs on to the test system via
the Landscape assignment block and starts testing the change.
11. The tester indicates the test result in the change document:
• If the test is not successful, the tester returns the change document to the developer. The change
document returns to status In Development.
• If the change can be imported into the production system, the tester confirms the successful test.
The change document moves to status Successfully Tested. This releases the transport requests
associated with the change document on condition that all tasks have been released.
12. After successful testing, the change manager authorizes the deployment into the production system. This
merges the emergency branch into the main branch of the Git repository
13. The IT operator triggers the deployment into the production system. In the Change and Transport System
infrastructure of the managed landscape, this pulls the emergency code change from the main branch of
the Git repository and deploys the content into the production system. After this action, the emergency
changes are deployed into the production system.
14. When the emergency code is deployed into production, the change document moves to status Deployed
into Production. See SAP Note 3313529 for required actions for your Git repository.

 Note

When you have completed the required actions in the SAP Note above for the Git repository, the
following changes are made: The code changes from the development branch are deployed into the

Change Control Management

Change Request Management PUBLIC 105
 development system and the test system. All unfinished Git-enabled changes with a development
branch assigned are editable. The project development in the development branch can be continued.

Related Information

PPF Actions for SMGH Git-Enabled Change [page 194]

Processing Git-enabled Changes [page 99]

4.2.9 Processing Continual Cycles

Use continual cycles to implement changes without having to use specific phases.

Prerequisites

 Recommendation

To ensure consistency, activate Cross-System Object Lock and Downgrade Protection because many
change documents might be transported individually.

Context

This cycle type supports normal changes, Git-enabled changes, standard changes, urgent changes,
administrative changes, and general changes. Continual cycles have no designated test phase, thus no defect
corrections.

You edit continual cycles in the WebClient UI under Change Request Management Change Cycles .

Procedure

1. System administrators or technical project leads create a continual cycle and set the phase to Active.

The system displays the guided procedure for creating task lists.

 Note

To import normal changes and standard changes, schedule an import job, for example, in a task list.

Change Control Management

106 PUBLIC Change Request Management
2. In phase Active, developers carry out all development activities for the change: Transport requests and
tasks can be created, released, and imported.

 Recommendation

Perform an impact analysis from the documents that are ready to go live. See also Business Process
Change Analyzer (BPCA).

3. Close the continual cycle by setting the status to Completed.

Results

A dialog box displays all open change documents or open requests for change.

• If there are no open change documents or open requests for change and you don’t create a new cycle, the
system sets the status of the cycle to Completed. Also the CTS projects are released and the related task
list is closed.
• If there are open change documents or requests for change, you must create a new cycle. A successor
cycle linked to the original task list is created and the open items are taken over.

 Note

This system behavior also applies if you set a continual cycle to Withdrawn.

Next Steps

You can create a new continual cycle.

Related Information

Continual Cycle [page 29]

Creating Task Lists [page 273]
Downgrade Protection [page 360]
Cross-System Object Lock [page 363]
PPF Actions for SMAI Continual Cycle [page 236]
Defined Actions for Continual Cycles [page 30]

Change Control Management

Change Request Management PUBLIC 107
4.2.10 Processing Phase Cycles

Use phase cycles to implement changes in defined phases.

Context

This cycle type supports normal changes, Git-enabled changes, standard changes, urgent changes,
administrative changes, general changes, and defect corrections.

You edit phase cycles in the WebClient UI under Change Request Management Change Cycles .

Procedure

1. System administrators or technical project leads create a phase cycle to control all change activities in the
solution landscape using Change Request Management.
2. They switch the phase to Scope.

 Recommendation

Do not use this phase in normal changes, because developers will not be able to import changes into
the test system, for example, the changes from the transport of copies.

The system displays the guided procedure for creating a task list. For changes that are not linked to the
transport management system, you can use change cycles without task lists.

In this phase, features can be developed and transport requests and tasks can be created but not exported.

To define the scope of a change, you create requests for change. In assignment block Details you see which
change cycle is assigned. The subsequent change documents are assigned to the phase cycle.
3. When the change manager switches the phase of the phase cycle to Build, transport requests can be
released from within a normal change.

The administrator has the following options to import change documents into the test system:

• Import a specific change document from the WebClient UI, using the preliminary import function
• Import all released changes whose phase matches the import strategy of the cycle, using the task list

 Tip

Transports of copies can be imported only from the task list.

During the Build phase, use defect corrections to resolve the errors that were reported by testers.

 Recommendation

Perform an impact analysis before the Test and Go Live phase. See also Business Process Change
Analyzer (BPCA).

Change Control Management

108 PUBLIC Change Request Management
4. The change manager sets the phase of the phase cycle to Test.

 Note

In a phase cycle, the test phase refers to a real test period (for example, acceptance tests or scenario
tests). It does not refer to the test phase of a change document.

During the test phase, use a defect correction to resolve the errors that were reported by testers.

If there are any normal changes whose status has not been set to Successfully Tested, the system issues
a warning. The change manager can release or withdraw such changes. Unresolved changes are excluded
from the current phase cycle and transferred to the next cycle.
5. In the Go Live phase, the entire content of the buffer is imported into the production system.

The project buffer is now empty, and there are no open transport requests.
6. You close the phase cycle by setting the phase to Being Completed.

This phase does not allow you to go back to the previous phase.
7. When you set the phase to Completed and the phase cycle contains unfinished change transactions, a new
phase cycle is automatically created.

Results

The unfinished change transactions and the task list are reassigned to this new phase cycle.

 Note

The system also checks whether change transactions that are assigned to an SAP PPM project can be
reassigned to the next cycle. If the project does not allow the change transaction to be reassigned, you get
an error message.

You see all unfinished change transactions and whether a change transaction has an SAP PPM integration.
To reassign such change transactions, they must be decoupled from the particular project. The dialog box
informs you about the associated project and the project manager so you can request the decoupling.
When all unfinished change transactions have been decoupled from assigned projects, the phase cycle can
be closed.

Next Steps

The new cycle is displayed on the WebClient UI and you can navigate to it.

Related Information

Phase Cycle [page 35]

Change Control Management

Change Request Management PUBLIC 109
PPF Actions for SMIM Phase Cycle [page 239]
Creating Task Lists [page 273]
Using Change Cycles Without a Task List [page 35]
Processing Normal Changes [page 68]
Creating Transports of Copies (ToC) [page 123]
Project Management Integration [page 269]

4.2.11 Processing Release Cycles

Use release cycles to implement changes in phases based on the release plan.

Prerequisites

For a selected change control landscape, at least one release cycle must be available. It’s used as a copy
template for the cycle to be created. The the Go-Live dates and other data of the release cycle are adjusted
automatically.

If there’s no release cycle for a change control landscape, you must create the first cycle manually.

Context

This cycle type supports normal changes, Git-enabled changes, standard changes, urgent changes,
administrative changes, general changes, and defect corrections.

You edit release cycles in the WebClient UI under Change Request Management Change Cycles .

Procedure

1. The release manager creates a release cycle based on a release, and enters the relevant data.
2. The change manager sets the phase of the release cycle to Scope.

The system displays the guided procedure for creating task lists.

To define the scope of the change, you create requests for change. The corresponding change documents
are assigned to the release cycle.
3. To start development, the change manager sets the phase to Build.

When the planned activities are carried out for a release during this phase, requests for change and change
documents are created and assigned to release cycles. To resolve errors that were reported during testing,
use a defect correction.

Change Control Management

110 PUBLIC Change Request Management
  Recommendation

Perform an impact analysis before the Test and Deploy phase. See also Business Process Change
Analyzer (BPCA).

4. When the change manager sets the phase to Test, all change documents assigned to this release cycle
should have the status Successfully Tested.

If there are change documents that are not successfully tested, the system displays a warning. You can
reassign these change documents manually to a successor release. To resolve errors that were reported
during testing, use a defect correction.
5. When a release is going live, that is, when the change manager sets the phase to Deploy, the changes that
have been successfully tested are imported into the production system.
6. When the change manager sets the phase to Hypercare, the following happens:

Any unfinished change documents are reassigned to the successor release cycle. A change document is
finished when it is withdrawn or completed, and doesn’t contain any open transport requests in the buffer
of the production system.

The system checks whether change transactions that are assigned to an SAP PPM project can be
reassigned to the next cycle. If the project does not allow the change transaction to be reassigned, the
system displays an error message.

 Note

The following rules automatically determine the successor release:

• Change documents of a minor release – for example, 1.4 – are reassigned to the next minor release
1.5 that is in the same system landscape and branch (if this next minor release already exists).
• If minor release 1.5 is planned, but does not have a release cycle assigned yet, a new release cycle
is created automatically as a copy of previous minor release change cycle 1.4.
• If the successor of minor release 1.4 is major release 2.0, which is not in the same system
landscape and branch, the change documents are reassigned to the next minor release – for
example, 2.1 – that is performed in the same branch as the minor release 1.4.

At the cutover point from the development branch to the maintenance branch, make sure that any
changes made to objects using change documents assigned to minor release 1.4 are also implemented
in major release 2.0. To do so, either use the retrofit feature or manually adjust the changed objects.

7. Change documents that were created in, or assigned to, the release cycle after the switch to Hypercare are
displayed in a dialog box.

You can decide to transfer them to the successor release. The same applies when the release cycle is set to
Retired.

Related Information

Release Cycle [page 44]

Creating Task Lists [page 273]
Release Planning [page 456]
Reassigning Change Transactions [page 141]

Change Control Management

Change Request Management PUBLIC 111
Dual Landscape Synchronization (Retrofit) [page 338]
Project Management
PPF Actions for SMRE Release Cycle [page 243]

4.2.12 Withdrawing Change Documents with Solution

Documentation Elements

A change document can only be withdrawn if there are no changed Solution Documentation elements.

Context

You use change documents to record changes in the assigned Solution Documentation elements.

Procedure

1. In the Change Request Management UI, navigate via a release check from the change document to the
solution documentation.
2. In the Changed elements overview, select either Discard or Move to other change document for changed
solution documentation elements.
3. When all the changed solution documentation elements are removed, you can withdraw the change
document.

Related Information

Solution Documentation Assignment Block [page 256]

Change Recording [page 259]

Change Control Management

112 PUBLIC Change Request Management
4.3 Functions in Change Transactions
The WebClient UI contains a range of integrated functions and information options that you can use in requests
for change, change documents, and change cycles.

Features

These are some of the functions you can use in a change transaction:

• Use Actions, for example, to change the status or phase

• Start the Business Process Change Analyzer (BPCA) with Actions Create BPCA Analysis .
Solution, branch, and transaction ID are copied from the transaction, and displayed in the BPCA. The
system analyzes the changes made in the change transaction.
• See the statuses or phases of change transactions in the Status Overview assignment block, for example,
In Development or Successfully Tested. The current status of the transaction is highlighted. Statuses that
are not (or not yet) in use are grayed out.
• Prioritize and categorize the change transaction in the Details assignment block, under Category.
• Identify reference objects, such as customer installation and configuration elements, under Reference
Objects in the Details assignment block
• Use Texts and Text Templates
• Test Management Integration
• Solution Documentation Integration
• Upload and download attachments
• SAP Notes
• Time Recording
• Error log and error handling

Configuration

You can make settings for the following assignment blocks:

• Details
• Test Management
• Scope
• Transport Management

To customize the Status Overview assignment block or hide statuses that you never use, implement BAdI
AI_CRM_CM_UI_ROADMAP.

 Example

You can restrict the editability or visibility of UI elements via authorization objects. For example, only
administrators are allowed to decouple or assign transport requests. Change managers and developers
inform them about the content, and the administrator does the actual decoupling or reassignment.

Change Control Management

Change Request Management PUBLIC 113
You can specify the visibility and usage of some fields in change transactions, depending on the user status
and the authorization in the change transaction. In SAP Solution Manager Customizing (transaction SPRO),
choose SAP Solution Manager Capabilities (Optional) Change Control Management Change Request
Management Framework Configure status-dependent UI element control .

Related Information

Changing the Transaction Status with PPF Actions [page 169]

Analyzing Business Processes Affected by Changes
Multilevel Categorization [page 289]
Assigning Reference Objects (IBase) [page 115]
Adding Text and Reusing Text Templates [page 117]
Test Management Integration [page 262]
Solution Documentation Assignment Block [page 256]
Assigning SAP Notes [page 264]
Time Recording [page 255]
Warnings and Errors in Change Transactions [page 252]

4.3.1 Specifying the Processor in Transactions

As a processor, you can specify the current processor when a change transaction or message is opened in
change mode.

 Note

In messages, the support team linked to the business partner is also automatically entered.

You can define global settings and user-specific settings.

Global Settings

In Customizing (transaction SPRO), go to SAP Solution Manager Capabilities (Optional) Change Control
Management Transactions Specify Settings for Automatic Assignment of Processor .

Parameters to Assign the Processor

Parameter System Behavior

No entry No automatic entry in the Current Processor or Message

Processor fields

AUTO_NONE_POPUP (default setting for change transactions) The system automatically enters the current user as current
processor or message processor, regardless of the previous
contents of the field.

Change Control Management

114 PUBLIC Change Request Management
Parameter System Behavior

AUTO_POPUP_NO2READONLY A dialog box asks you whether you want to assign your busi-
ness partner as the processor.

If you choose No, the entry in the respective field remains

unchanged, and the transaction is in display mode.

AUTO_POPUP_NO2EDIT (default setting for messages) A dialog box asks you whether you want to assign your busi-
ness partner as the processor.

If you choose No, the entry in the respective field remains

unchanged, and the transaction is in change mode.

User-specific settings
Prerequisite: In the global settings, you have entered either the parameter AUTO_POPUP_NO2READONLY or
AUTO_POPUP_NO2EDIT.

By default, the system displays the dialog box. For each user, you can specify that the system enters the
processor automatically without displaying the dialog box:

In the user profile (transaction SU3), under Parameters, enter parameter ID AI_CRM_POPUP_PROC with value X.

4.3.2 Assigning Reference Objects (IBase)

You can assign reference objects to your change transaction or message. A reference object represents a
product or an installation in the customer’s system landscape for which a service or change is requested.

Prerequisites

An IBase is available.

Features

• You can specify the following reference objects in change transactions and messages:
• Configuration item
Entity or system that is identified and changed in Change Request Management or IT Service
Management. Configuration items are objects in the Landscape Management Database (LMDB) or
Configuration Management Database (CMDB). They vary in complexity and size from a single module or
small component, to an entire system. Configuration items can, for example, contain the following:
• Hardware (such as technical systems, databases, hosts, routers)
• Software
• Services

Change Control Management

Change Request Management PUBLIC 115
 • Documentation
• In Change Request Management, the IBase component is displayed that relates to the selected
configuration item.
• For Change Request Management: If you enter a value in the Configuration Item field, the Component field
is filled automatically.
• For Change Request Management: When you search for a configuration item (and if a change cycle has
been assigned to the change transaction), the result list shows only those objects that belong to the
change cycle that is assigned to the request for change or to the change document. Depending on the
transaction type, the following systems are displayed:
• Normal change, urgent change, defect correction: only productive systems of the system landscape
• Administrative change: all systems of the system landscape
• General change: all possible configuration items
• You can enter and process reference objects in the following assignment blocks:
• Requests for change: Scope assignment block
You can also enter the product ID of the configuration item.
• Change documents: Details assignment block
The system fills the Reference Objects fields automatically with the data from the Scope assignment
block in the associated approved change request.
• Messages: Assignment blocks Details and Reference Objects

 Note

Depending on the transaction type and status of the transaction, you can edit the reference objects.
For example, if a normal change is already being implemented, you can no longer change the reference
object.

• You can use the reference object as a criterion to search for change transactions or messages.

Related Information

Installed Base
Change Documents [page 26]
Request for Change [page 24]

Change Control Management

116 PUBLIC Change Request Management
4.3.3 Adding Text and Reusing Text Templates

You can save recurring information as personal text templates and insert it into your change transactions,
messages, and requirements at the press of a button.

Use

Recurring information could include a signature or telephone numbers, for example. The system administrator
can also create system templates with standard texts, which are available to all staff (for example, standardized
prompts to indicate which information must be entered in a request for change, message, or requirement).

Prerequisites

• If you don't want to use the default text types and text determination procedures, you have made the
following settings in Customizing (transaction SPRO):
• For Change Control Management, choose SAP Solution Manager Capabilities (Optional) Change
Control Management Transactions Text Management .
• For IT Service Management, choose SAP Solution Manager Capabilities (Optional) IT Service
Management Text Determination Procedure .
• For Requirements Management, choose SAP Solution Manager Capabilities (Optional)
Requirements Management Transactions Text Management Text Determination Procedure .
• If you want to use Rich Text Format, you have configured the Customizing activity Activate Text Formatting.

Features

• Text entry according to the selected text type (for example, internal note or response). The available text
types are defined in Customizing.

 Note

The visibility of a text in the system depends on the text type. An internal note can, for example, only be
seen by your own support team.

• Creation of personal text templates for specific users and insertion into the Texts assignment block
• Creation of system templates for all users and insertion into the Texts assignment block. The system
templates are edited in Customizing for text management.
• Text log: Documentation of all texts created. You can filter the display for the content by text type.
In change transactions, the system also shows all status changes, authorizations, and changes to the
transaction.
• Rich Text Format (RTF)

Change Control Management

Change Request Management PUBLIC 117
 You can edit texts using RTF features, for example, by using fonts, copy and paste functions, and text
alignment.
• Rich Text Format (RTF) Integration in CRM WebClient UI
In the assignment block Notes, the CRM WebClient UI supports a rich text edit control, which allows users
to paste screenshots directly into the long text. You must perform customizing to enable this. This function
is only available within the CRM UI. The system does not send rich text from the new editor through
external interfaces, such as the incident exchange interface with SAP or the external service desk interface,
etc. The Fiori apps and other user interfaces outside the CRM WebClient UI do not support the display or
the creation of rich text. Furthermore, the text types “CRM Rich Text enabled” are deactivated and cannot
be selected.
For more information about integration between IT Service Management and SAP Customer Relationship
Management, see the SAP Library for SAP Customer Relationship Management.

4.3.4 Managing Transport Requests

In change documents connected to the Change and Transport System, the Transport Management assignment
block offers functions from the Transport Management System to carry out and monitor transports between
SAP systems.

Features

• Display and create transport requests, test transports, and tasks

• Release transport requests and test transports
• Display information on transport requests, such as the status, whether they contain critical objects, or
whether there are conflicts.
The transport requests can have the following statuses:
• Changeable: The transport request is either modifiable or modifiable and protected.
• Releasing
• Released
• CTS Project Changed
• For Git-enabled changes: See the number of commits for the transport request, a list of all commits, and
the overview of the deploy status for the latest commit.
• If there’s a retrofit system for the relevant system landscape, you can display the retrofit status and start
the retrofit process.
You see the retrofit status for released transport requests. For unreleased transport requests, the retrofit
status isn't displayed because no retrofit data is available.
The following retrofit statuses are possible:
• Retrofit data created - Process retrofit
• Retrofit successful - Retrofit manual
• Retrofit successful - Retrofitted
• Retrofit successful - Retrofit not relevant
• Retrofit successful - Retrofit rejected

Change Control Management

118 PUBLIC Change Request Management
 • Error while creating retrofit data
• Retrofit data not created - Status not available
As soon as the change document (urgent change or normal change) or the change cycle is authorized for
production (and in the following phases), you can start the retrofit process under More Start Retrofit .
• Display tasks for a selected transport request under Display Details
• Navigate to transport requests in connected systems
• See the latest import status for the transport request and its transport of copies, for example, "Import
successful", "No import" and "Error"
• Display the transport log
• To see transport logs in the WebClient UI, select Import Status
• To see transport logs in the managed system, select Display Log
• Decouple and reassign transport requests

 Note

The transport logs displayed when you choose the Import Status icon are collected via the
import feedback mechanism. If you want to remove the obsolete data here, check the parameter
CM_IMPORT_FEEDBACK_RETENTION_DAY in SAP Note 1483276 . You can select the transport ID in the
transport log popup to remotely display the transport logs on the respective managed systems or in the
SAP Cloud Transport Management service.

Related Information

Creating Transport Requests [page 119]

Creating Transport Tasks [page 122]
Approving and Exporting Critical Objects [page 147]
Decoupling Transport Requests in Change Request Management [page 134]
Assigning Transport Requests [page 135]
Performing the Retrofit [page 345]
Central Change and Transport System [page 400]
Transport Management Functions in the Administration Cockpit [page 302]

4.3.4.1 Creating Transport Requests

In SAP Solution Manager, you can create transport requests from a change document, or from a task list.

Prerequisites

• A task list exists with the status Active.

Change Control Management

Change Request Management PUBLIC 119
• In the Solution Manager system, you have the role SAP_CM_DEVELOPER_COMP or
SAP_CM_OPERATOR_COMP.
• If you want to create a transport request from within the task list: In the managed system, you have the role
SAP_CHANGEMAN_OPERATOR.
• For Git-enabled changes: You have assigned the Git repository.

 Note

For urgent changes, only one open workbench and one open Customizing request are permitted at any
time.

Context

The transport requests are created for the development system where your software changes are recorded.
The transport requests are connected to the CTS project created from the change cycle used in the change
document and the task list. The transport requests get the transport request attributes SAP_CTS_PROJECT
(which contains the CTS project ID) and SAP_TMWFLOW (which contains the task list ID of your task list).

 Caution

For non-ABAP developments, see the Strategy for User Collaboration in Non-ABAP Development.

Creating Transport Requests from a Change Document

Procedure

1. In the WebClient UI, select the change document.

2. On the Transport Management assignment block, choose New Transport Request.
3. By default, your user is the owner and there is a single task for your user, and a generated short
description.
a. You can change the owner and short description.
b. You can also add developers to whom you want to assign transport tasks within this request.
4. Select the type of transport request you want to create (workbench or Customizing request for an ABAP
system, workbench for non-ABAP systems).

Results

In the selected development system, a transport request is created for the specified owner and developers.

Change Control Management

120 PUBLIC Change Request Management
Creating Transport Requests from a Task List

Procedure

1. In the administration cockpit, choose Task Lists.

2. Choose the change cycle or urgent change.

By default, you get a list of the task lists with the status Active. To select or activate task lists with other
statuses, change the status of the task list.
3. Select the track for which you want to create a new transport request.

4. Under the task node of the development system, select Create Transport Request Execute .
5. By default, your user is the owner and there is a single task for your user, and a generated short
description.
a. You can change the owner and short description.
b. You can also add developers to whom you want to assign transport tasks within this request.
6. Select the type of transport request you want to create (workbench or Customizing request for an ABAP
system, workbench for non-ABAP systems).

Results

In the selected development system, a transport request is created for the specified owner and developers.

After the transport request has been created, the task list is displayed again.

You can check the status of your task. If you need more information about the task, check the application log in
the Daily overview of the task list.

In the selected development system, a transport request is created for the specified owner and developers.

Related Information

Changing the Status of Task Lists [page 299]

Strategy for Collaboration in Non-ABAP Development

Context

In non-ABAP developments, you can have only one modifiable transport request per change document. This
ensures consistency in software distribution. Also, in non-ABAP developments, you cannot create tasks under
a transport request.

Change Control Management

Change Request Management PUBLIC 121
If you want to collaborate with other non-ABAP developers in the same transport request, you can preselect all
developers involved to enable them to use this particular transport request. This is the only way to guarantee
that non-ABAP content is transported in the correct order and to avoid downgrade.

Procedure

1. Call transaction STMS (Transport Management System).

2. On the menu bar, choose Transport Organizer Web UI and select the system.
3. Select the transport request for which you want to preselect users.
4. Under Details of Transport Request, find the Preselection tab.
5. You can search and add preselected users. To add more names, add another row.
6. Save your entries.

4.3.4.2 Creating Transport Tasks

Use

You want to create new transport tasks for an existing transport request. This may be necessary, for example, if
additional developers need to take part in the development, or if old tasks have already been released.

Prerequisites

• A task list exists with the status Active.

• You have been assigned the SAP_CM_DEVELOPER_COMP role in the SAP Solution Manager system.
• A transport request has been created for your user.

 Note

If you want to create transport tasks in the administration cockpit, you must have the
SAP_CHANGEMAN_OPERATOR role in the managed system.

Procedure

Creating Transport Tasks from a Change Document

To create transport tasks from within a change document, proceed as follows:

1. In the Transport Management assignment block, select a transport request and choose New Task.

Change Control Management

122 PUBLIC Change Request Management
2. In the dialog window, specify the users who need a transport task in this transport request.

Creating Transport Tasks from a Task List

To create transport tasks from within a task list, proceed as follows:

1. In the administration cockpit, choose Task Lists.

2. Select the relevant change cycle.
3. Click the task list for which you need to create new transport tasks.
4. Under the task node of the development system, select Create Transport Task and start the action by
clicking Execute task.
5. On the screen that appears, enter or select the request number and the names of the developers for whom
you want to create new tasks.
After the transport tasks have been created, the task list is displayed again.
6. Check the status of your task. If you need more information about the task, check the application log in the
Daily overview of the task list.

Result

In the selected development system, new tasks have been created in the specified transport request for the
specified developers.

4.3.4.3 Creating Transports of Copies (ToC)

With transports of copies, you can transport your software changes to the consolidation system without having
to transport them automatically to other systems in your transport track. The objects are transported with the
version they have in the current SAP system. The original location of the objects remains unchanged.

Prerequisites

• A task list exists with the status Active.

• The tasks associated with the transport request have been released.
• In the SAP Solution Manager system, you have the role SAP_CM_DEVELOPER_COMP.
• To release transport requests from the task list, you have the role SAP_CHANGEMAN_OPERATOR in the
managed system.

Context

You can create transports of copies (ToC) in the WebClient UI (normal change or standard change), or from a
task list.

Change Control Management

Change Request Management PUBLIC 123
Can I create a ToC?
Change Transaction In Webclient UI From Task List

Request for Change (SMCR)  

Normal Change (SMMJ)  

Administrative Change (SMAD) n/a n/a

General Change (SMCG) n/a n/a

Standard Change (SMSG)  

Urgent Change (SMHF)  

Git-enabled Change (SMGH)  

Defect Correction (SMTM)  

Creating Transports of Copies (ToC) in the WebClient UI

To create a transport of copies from within a normal change or standard change, you have the following
options:

• On the Transport Management assignment block, select a transport request and choose New Transport of
Copies.
Transports of copies are released and imported automatically into the consolidation system.
• Set the change document status To Be Tested.
Transports of copies for the existing transport requests are created and exported automatically.

Creating Transports of Copies (ToC) from a Task List

To create a transport of copies from within a task list, proceed as follows:

Procedure

1. In the administration cockpit, go to Task Lists and select the change cycle and task list for which you want
to create a transport of copies.
2. In structure tree of the selected task list, find the track of the development system for which you want to
create a transport of copies.

3. Expand the task nodes of the development system and select Create Transport of Copies Execute
Task .

A dialog box lists the available original transport requests.

 Note

The available transport requests are from the change transactions (except for urgent changes,
standard changes and Git-enabled changes) assigned to the CTS project that is connected to the
cycle.

4. Select one or more original transport requests for which you want to create transports of copies.

After the transports of copies have been created, you return to the change cycle's task list.

Change Control Management

124 PUBLIC Change Request Management
5. Check the status of your task.

For more details, check the application log in the Daily Overview of the task list.

Results

For each selected transport request, the object list is used to create a new transport of copies. Transports of
copies are released and added to the import queue of your consolidation system. Now, you can import these
transport requests for testing.

 Note

Transports of copies are not included in the CTS delivery mechanism, so they aren’t transported across
your system and are, therefore, not imported into your production system.

If the tests of your transports of copies are successful, you release the original transports, which can then be
transported across your landscape.

The transports of copies are provided with transport request attributes SAP_CTS_PROJECT (which contains
the CTS project ID) and SAP_TMWFLOW (which contains the task list ID of your task list).

Related Information

Processing Normal Changes [page 68]

Processing Standard Changes [page 89]
Managing the Task List [page 294]

4.3.4.4 Releasing Transport Requests

You can release the transport requests that are part of your changes from the Solution Manager system in the
WebClient UI and in the Administration Cockpit.

Prerequisites

• A task list exists with the status Active.

• In the SAP Solution Manager system, you have the role SAP_CM_DEVELOPER_COMP.
• To release transport requests from the administration cockpit, you need the role
SAP_CHANGEMAN_OPERATOR in the managed system.

Change Control Management

Change Request Management PUBLIC 125
Context

There are two ways to release transport requests:

• From a change document in the WebClient UI

• From a task list in the administration cockpit

Releasing Transport Requests from a Change Document

The following actions release a transport request from within a change document:

• For urgent changes that are in status In Development: Go to the Transport Management assignment block,
select the transport request and choose Release Transport Request. In this case, you can also use the Code
Inspector.
Transport requests of urgent changes can also be released automatically when the change document is set
to To Be Tested.
• For normal changes: Transport requests are automatically released when the change document is set to
Successfully Tested.
• For Git-enabled changes: Transport requests are automatically released when the change document is set
to Successfully Tested.

Releasing Transport Requests from a Task List

To release a transport request from within a task list, proceed as follows:

Procedure

1. In the administration cockpit, go to Task Lists and choose the relevant change cycle.
2. Select the task list for which you want to release transport requests.

3. Under the task node of the development system, select Release Transport Request Execute .

You can decide whether you want to execute the task immediately or at a scheduled time.
4. In the dialog box, select the transport requests that you want to release.

 Note

Transport requests from urgent changes and standard changes are not listed in the dialog box. Release
them from the change document.

5. Check the status of your task.

For more details, check the application log in the Daily Overview of the task list.

Results

• In the selected development system, the transport requests that you specified are released.
• A transport request containing any open tasks is not released.

Change Control Management

126 PUBLIC Change Request Management
• Empty transport requests are deleted.

Related Information

Administration Cockpit for Change Request Management [page 291]

Change Control Management in the WebClient UI [page 15]
Processing Normal Changes [page 68]
Processing Standard Changes [page 89]
Processing Urgent Changes [page 81]
Using the Code Inspector in Urgent Changes [page 85]

4.3.4.5 Importing Transport Requests

Use

You want to import transport requests.

Prerequisites

• A task list exists with the status Active.

• In the SAP Solution Manager system, you have the role SAP_CM_OPERATOR_COMP.
• In the managed system, you have the role SAP_CHANGEMAN_OPERATOR.

 Note

If you want to import transport requests from within a change document, you must have the
SAP_CM_DEVELOPER_COMP role in the SAP Solution Manager system.

• If you want to use status-dependent or selective import, you have set up the respective import strategy.

Procedure

To import transport requests from within a task list, proceed as follows:

1. On the Task Lists tab page, under the relevant change cycle, choose the task list for which you want to
import transport requests.
2. Under the task node of the target system of your import, select Schedule Import Job for Transport
Requests and execute the task.

Change Control Management

Change Request Management PUBLIC 127
  Recommendation

If you have activated central CTS for your change cycle, choose the task under the cluster node to start
the import. Especially if you would like to start the import into several systems of the same cluster in
parallel, you must use this node.

3. In the dialog box that appears, enter or select the import options for this import.

 Note

The import parameter dialog box is only available for calls from the administration cockpit. This is the
case for urgent changes that are processed manually and for continual cycles. In the case of urgent
changes that are processed from within a change document, it is assumed that the import must be
started with the default import settings.

For continual cycles, the window displays the cycle that you specified and the import target. For urgent
changes, the box displays the corresponding requests and the import target.

4. If you select the Standard Change Only option, the import dialog box displays only standard changes.
Status-driven Customizing is considered. The Go-Live phase is not required to import the transport
request of a standard change into a production system.
5. On the Execution tab page, specify how you want the transport control program to start.
6. On the Options tab page, specify options for the import.
7. If you have activated central CTS for your project, the Systems tab page displays all the systems in the
target cluster. Select the target systems for your transport request.
8. After you have configured your settings, choose OK.
The transport requests are imported and the task list is displayed again.

 Note

If the system finds a downgrade conflict, the import is canceled. The conflicts are displayed in the
application log.

9. Check the status of your task. If you need more information about the task, check the application log in the
Daily overview of the task list.

Result

• In the selected system, the following types of transport requests are available for import (respecting your
import strategy):

Context Importable Transport Requests

Urgent change • All requests that belong to that urgent change and
that have been released
• Requests that have not already been imported
• Requests that have been recorded in the import
queue of the import target

Change Control Management

128 PUBLIC Change Request Management
 Context Importable Transport Requests

Continual cycle • All requests that belong to the CTS project connected
to that continual cycle.
• Requests that have been recorded in the import
queue of the import target.

 Note
The requests that are imported within an urgent
change cycle are flagged as preliminary imports.
This means that they will be imported again as
part of the regular project import of the corre-
sponding continual cycle.

Release cycle • All requests in the buffer that belong to change docu-
ments of the current release cycle.
• All requests in the buffer that belong to urgent
changes of an active predecessor release cycle with
the same cycle task list. (It is not important, if the ur-
gent changes from predecessor cycles were prelimi-
narily imported or not.).

Phase cycle • All requests that belong to the CTS project connected
to that phase cycle.
• Requests that have been recorded in the import
queue of the import target.

 Note
The requests that are imported within an urgent
change cycle are flagged as preliminary imports. This
means that they will be imported again as part of
the regular project import of the corresponding phase
cycle.

• If the active import feedback job SM: AI_CRM_CM_COM_IMPORT_FEEDBACK has been set up, the following
happens:
• Automated emails are sent, for example, to inform the IT operator about import errors and transport
return codes.
• All changed documents of the imported transport requests are processed as customized.
• Fully imported transport requests are removed from the STMS import queue after the import is
successfully done.
• In the WebClient UI, the Import Status column of the transport request is updated.
For more information about the active import feedback job, see the activity documentation in SAP
Solution Manager Configuration Change Request Management Prepare System Schedule Background
Jobs .

Change Control Management

Change Request Management PUBLIC 129
  Note

You need to install the latest SAP Solution Tools Plug-in (the ST-PI) onto the managed systems.

• If you want to define a specific user for this import action, use the Background User option on the Date tab
page of the import dialog box.

Related Information

Central Change and Transport System [page 400]

Change Control Management Using Central CTS [page 399]
Import Strategies: Standard, Status-Dependent, and Selective [page 396]
Processing Standard Changes [page 89]
Processing Urgent Changes [page 81]
Continual Cycle [page 29]
Release Cycle [page 44]
Preliminary Import of Normal Changes [page 71]
Updating Change Document Status After Import of Transport Requests [page 132]

4.3.4.5.1 Starting an Import: Scheduling

Scheduled transport is one of two options to import transport requests, including transports of copies.

When you execute an import task, you can choose between the following options:

• Immediate transport
All transport requests for this project that are in the import buffer are transported to the target system
immediately.
• Scheduled transport
The IT operator schedules a start time for the import - that is, either a specific date and time, or a period
such as every 15 minutes, hourly, or daily.

 Note

While it’s also possible to use transaction STMS to schedule periodic imports, we do not recommend this
option. If you still want to use it, perform the following steps:

1. In transaction STMS in the quality system, choose Import Overview and select the target system for the
import.
2. On the Import Queue screen, select a project and choose Filters. You see all transport requests for the
selected project.
3. Choose Queue Start Import and enter the intervals for importing transport requests, for
example, every 30 minutes.
4. After double-clicking an entry and choosing Maintain Project Status Switch, change the entry to
Requests can be imported. This schedules an import job. At the scheduled time, the system checks
whether the import is allowed and carries out the import.

Change Control Management

130 PUBLIC Change Request Management
Related Information

Scheduled Import Jobs [page 335]

Creating Transports of Copies (ToC) [page 123]

4.3.4.5.2 Transport Risks

Use

During the import of transport requests into a connected system, errors may occur and the import may fail.

From the Landscape assignment block, you can view these failed transport requests as transport errors in the
Transport Risk dialog box. You can find the transport log also in the Transport Risk dialog box, or directly access
the CTS+ Transport Organizer for the transport request to view the transport log. The log helps you analyze the
nature of the transport errors.

After you have fixed the inconsistencies in your transport requests, select Declare Error as Repaired to confirm
that the import status in SAP Solution Manager import tracking is repaired.

 Note

Selecting Declare Error as Repaired does not repair inconsistencies in your transports, it only cleans up the
the transport risk overview. Consequently, choose this pushbutton only if you have already repaired the
transport error.

Procedure

Proceed as follows:

1. In the Landscape assignment block, select the system that contains transport errors.
2. To navigate to the Transport Risk dialog box, click the link in the Transport Risks column.
3. The Transport Risk dialog box opens.
4. Fix the inconsistencies in your transport requests.
5. Select the import errors and choose the Declare Error as Repaired button.

 Note

You can declare multiple import errors at one time.

Change Control Management

Change Request Management PUBLIC 131
Result

Two outcomes are possible:

• If the error has occurred in the production system, error and risk do no longer exist.
• If the error has not occurred in the production system, the error is labelled as a missing transport risk.

Related Information

Importing Transport Requests [page 127]

4.3.4.5.3 Updating Change Document Status After Import

of Transport Requests

Context

When transport requests are imported into a target system, the status of their contained change documents is
not automatically updated by default.

For release cycles and phase cycles, this means that when a transport is imported into a production system,
the status of the relevant change document is not automatically updated.

Furthermore, at the cycle switch to the "Hypercare" phase (for release cycles) and to the "Completed" phase
(for phase cycles), open change documents are automatically reassigned to the successor cycle even though
they are no longer needed.

Use

To update the status of change documents after the import, create an automatic status shift job:

Through Customizing, in the maintenance view AIC_CRM_CM_ST_CH, you can define the target status and
perform an automatic status change of change documents when the relevant transport requests are imported
into a target system.

 Note

If you start the import from within the task list, the status shift job is performed for all import types
including selective import, status-dependent import, or import-all.

Change Control Management

132 PUBLIC Change Request Management
Prerequisites

In Customizing for SAP Solution Manager under Capabilities Change Control Management Transport
Management System Define Status of Change Documents for Import Job , you have defined the Post
Processing Framework (PPF) actions, which are executed for a change document after the transport request
for this change document is imported into the target system.

Results

• By defining the PPF actions per change control landscape, change document process type, and system
role of the system where the transport requests are imported, you are able to set a proper status value for
the relevant change document after the related transport requests are imported into a target system.
For example, this allows you to set the change document status after an import in a way that the attached
solution documentation elements are automatically activated in the production branch. It also enables you
to set a final status for change documents if the transport requests are successfully imported into the
production system. As a result, these change documents are not reassigned to the successor cycle when
the current cycle is switched to the “Hypercare” or “Completed” phase.
• By using a numeric value in the Action Order field, you can define the action sequence of multiple PPF
actions, which are executed when a transport request has been imported into a target system.
• The status shift job is displayed in Administration Cockpit among the tasks of a task list and among the
scheduled import jobs.

 Note

After maintaining the transaction type, you can view the values for the PPF actions by opening the
value help. To visualize the transactions process and to help identify the relevant actions, execute report
AI_CRM_CM_COM_ORDER_PROC_GUI.

Related Information

Importing Transport Requests [page 127]

Starting an Import: Scheduling [page 130]
Administration Cockpit for Change Request Management [page 291]

Change Control Management

Change Request Management PUBLIC 133
4.3.4.6 Decoupling Transport Requests in Change Request
Management
Change managers or developers can separate a transport request from its change document.

Prerequisites

• If you want to decouple released transport requests, you have activated the central Change and Transport
System (cCTS) for your scenario. Otherwise, you can decouple only modifiable transport requests.
• You have imported any transports of copies before you decouple the transport request. If you do not
import transports of copies before the decoupling, they’re still managed by the original task list and can
only be imported with the original task list via a mass import.
• The transport requests have not been imported into the production system. If a transport request has
already been imported into the production system, you can no longer decouple it from the change
document.
• For Git-enabled changes: All transport tasks are unreleased, and there has been no commit to Git. You
cannot decouple a transport request once a task is released and there is a commit to Git.

Context

 Example

A normal change has multiple transports requests assigned, one of them containing an unfinished
development. Because the change cycle is to be closed, or the remaining part of the project needs to
go live, you want to separate the unfinished developments from your change document. You can decouple
the transport request with the unwanted changes and finalize the other parts of your project.

Procedure

1. Check with the responsible developers that the decoupled transport request doesn’t have any
dependencies to other projects. If it has dependencies, there might be downgrade conflicts.
2. In the Transport Management assignment block, select the transport request.

3. Choose More Decouple Transport Request .

4. Confirm that you want to decouple the transport request

Results

The transport requests are decoupled from your change document, and are no longer displayed in the
Transport Management assignment block. When you transport the changes in this change document into your

Change Control Management

134 PUBLIC Change Request Management
production system, the decoupled request is not transported. You can assign it to another change document
with the function Assign Transport Request.

Related Information

Assigning Transport Requests [page 513]

4.3.4.7 Assigning Transport Requests

After Change Request Management is implemented, you can assign transport requests that were created
before you started using Change Request Management to change documents.

Context

In Change Request Management, you should always create transport requests from a change document or a
task list. Any transport requests that you’ve created manually in the transport management system are not
known to Change Request Management. However, if you start using Change Request Management, you can
assign your existing transport requests to change documents and then control them with Change Request
Management.

The following procedures explain you identify these transport requests and make them known to Change
Request Management.

 Note

As of SAP Solution Manager 7.2 support package 3, you can manage change documents without transport
requests. In doing so, transport-relevant actions and checks are ignored if no transport request has been
assigned to change documents.

If you want to make it mandatory for urgent changes, normal changes, and defect corrections that
transport requests are assigned to change documents, perform the Customizing activity Enable Mandatory
Transports in SAP Solution Manager Configuration (transaction SOLMAN_SETUP) under Change Request
Management Employ Additional Use Cases .

Supported Transport Request Types

Change managers or developers can assign the following transport requests to change documents:

• Decoupled transport requests

• Freely created transport requests
• External transport requests, that is, from another system landscape

Limitations
You can assign Workbench and Customizing transport requests but not transports of copies.

Change Control Management

Change Request Management PUBLIC 135
You can assign a transport request multiple times, as long as it’s assigned to different change cycles whose
landscape does not have the same production system.

For Git-enabled changes, you can only assign a transport request if the Git repository is assigned, and the
transport request is linked to the same repository.

Assigning Decoupled and Freely Created Transport Requests

Prerequisites

• To assign released transport requests, you have activated the central Change and Transport System
(central CTS) for your change cycle. Otherwise, you can only assign modifiable transport requests.
• To update the transport request description, BAdl /TMWFLOW/ASSIGN_TRANS_DESC_UPD has been
implemented in Configuration (transaction SOLMAN_SETUP) step Employ Additional Use Cases.

Procedure

1. To open the search for transport request, you have the following choices:

• In the WebClient UI, in the Transport Management assignment block, choose More Assign
Transport Request .
• In the task list, choose the Assign Transport Request task under the development system.

 Recommendation

While transport requests for release cycles and continual cycles can only be assigned in the WebClient
UI, transport requests for phase cycles can be assigned directly in the task list. However, we
recommend that you use the WebClient UI to assign transport requests.

For urgent changes without a change document, you can only use the task list.

You see the transport request search.

2. Search for the transport requests you want to assign.
3. Select the requests and choose Assign Transport Request.

If you have activated downgrade protection, you are informed about potential downgrade conflicts.

Results

The transport request is assigned to the change document.

The description of the transport request is updated to show the new change document.

Change Control Management

136 PUBLIC Change Request Management
  Note

When the transport request is assigned to the document, the description of the transport request can be
updated automatically by the system.

The description can be set up by BAdI BAdI: Change Description after Assign Transport Request to Change
Document TMWFLOW/ASSIGN_TRANS_DESC_UPD.

For updating the description of the transport request in the managed system, use SAP Note 2809667 .

Assigning External Transport Requests

Prerequisites

• You have activated the central Change and Transport System (central CTS) for your change cycle.
• In TMS, you have defined a delivery route to transport the external transport request from the
development system to the consolidation system, and from the development cluster to the consolidation
cluster.
• You have defined the source system of the external transport request in the transport target area of the
target clusters of your imports to transport the external transport request.
• Before you can assign an external transport request, it must be imported into the development system.
• You can only assign external transport requests from a change document created in your central CTS
change cycle.

Procedure

1. In the transport management system (transaction STMS), in the development system of the landscape
from which you want to import a transport request, choose Import Overview.
2. In the displayed list, select the development system by double-clicking.

3. Choose Extras Other Requests Add .

4. In the dialog box, enter the transport request ID and the target client of the system to which you want to
import.

5. Select the transport request, choose Request Import , and confirm the import to the development
system.

The transport request is now available in the import buffer of the quality system in the new target system
landscape.
6. To find the transport request you just imported into the development system, go to your change in the
WebClient UI and, in the Transport Management assignment block, choose More Assign Transport
Request .

Change Control Management

Change Request Management PUBLIC 137
  Recommendation

Do not assign the same external transport request into the same change document multiple times for
different development systems.

7. Select the transport request you just imported and choose Assign Transport Request.

If you have activated downgrade protection, you’re informed about potential downgrade conflicts.

Results

The transport request is assigned to the change document.

Related Information

Creating Transport Requests [page 119]

Central Change and Transport System [page 400]
Performing Transport-Related Checks [page 150]
Decoupling Transport Requests in Change Request Management [page 134]
Downgrade Protection [page 360]

4.3.4.8 Deleting Transport Requests That Do Not Exist in

Managed System

If the system tries to read information for a transport request that doesn’t exist in the managed system,
problems may occur during processing, for example, in CSOL/DGP. This report cleans up the Change Request
Management table that stores transport requests from such non-existing transport requests.

Prerequisites

• The RFC configurations are set up correctly for your development systems. Otherwise, the RFC doesn’t
find the transport requests, so they are considered as non-existing and deleted from the table
• The transport request does not exist in the managed system anymore.

Context

You can schedule the report as a background job to clean up the table periodically.

Change Control Management

138 PUBLIC Change Request Management
Procedure

1. Call report /TMWFLOW/TRANSPORT_DELETE.

2. Enter the transport request, or the solution or change control landscape.
3. If the transport request ID is not unique, enter the task list to clearly identify the transport request.
4. Select Execute.

Results

The Change Request Management table that stores transport requests is cleaned from transport requests that
don’t exist in the managed system.

For details, check the application log in SLG1 /TMWFLOW/CMSV TRANSPORT.

Related Information

Creating Transport Requests [page 119]

Releasing Transport Requests [page 125]
Importing Transport Requests [page 127]
Assigning Transport Requests [page 135]
Decoupling Transport Requests in Change Request Management [page 134]

4.3.4.9 Site-Specific Deployment of Changes

Use

You can assign an existing transport request to several change documents to support the site-specific
deployment of changes. The overall advantage of this concept is that you can minimize your risks by going
live in one region first before deploying the changes in another region. Also it improves traceability as the
original change document maps the go-live in the initial region while the second change document is created
for documenting the go-live in the subsequent region.

For example, a system landscape consists of one development system (A1D) and two transport tracks for
different geographical regions, ending in production systems with different go-live dates (A1P, AXP). The initial
change document manages the software distribution to the leading production system (for example, A1P). To
distribute the change to both production systems, that is, to both sites, the same transport request needs to be
assigned to different change documents.

Change Control Management

Change Request Management PUBLIC 139
 Site-Specific Deployment of Changes

Prerequisites

Your change cycles are enabled for the central change and transport system (central CTS).

Features

You can assign one transport request to several changes. Those changes need to be assigned to different
change cycles whose landscape does not share the same production system.

To do so, in the WebClient UI, manually assign the released transport request to an additional change of
the second change cycle. The same transport request is now managed by different changes within different
change cycles, and so the transport to different production systems at different points in time can be tracked
separately.

More Information

Assign Transport Requests [page 135]

Change Control Management

140 PUBLIC Change Request Management
4.3.4.10 Reassigning Change Transactions

You can reassign change transactions to other change cycles or subsequent releases.

Prerequisites

 Caution

Reassign a change to another change cycle with caution because not only the change documents are
affected, but also the source and target cycles.

For the change transaction, the following prerequisites must be fulfilled:

• The current status of the change transaction allows reassigning it.
• Change transactions that are assigned to an SAP PPM project must be allowed to be reassigned to another
cycle. If the project doesn’t allow the change transaction to be reassigned, you get an error message.
• If you have not activated the central Change and Transport System (central CTS) for your change cycle,
transport requests of the change transaction must be modifiable, with the release cycle being an exception
to this rule because in this case assignment is allowed on condition that the other cycle is also a release
cycle and is linked with the same task list.
If you have activated central CTS, you can assign change transactions with or without released transport
requests.

 Note

If you have activated central CTS, you can reassign change transactions with released transport
requests. The systems between the development and production systems (for example, the quality
assurance system) in a transport track can differ between the source and target cycles. If released
transport requests exist, and the source and target landscapes (including all transport tracks and all
cluster assignments in the transport tracks) are not identical, the system warns you that the import
buffer of the affected systems must be adjusted after the reassignment.

For the target change cycle, the following prerequisites must be fulfilled:
• The phase of the target cycle allows reassigning the change transaction.
• For the transport requests of the change transaction, the respective development systems must be
available as the target cycle's development systems.
• The production system that is identified by the IBase component of the change must be available in the
target cycle. Its system role type is production system.
• The target change cycle is not the source change cycle.

Change Control Management

Change Request Management PUBLIC 141
Depending on the change transaction type, the following conditions apply:

Source Cycle Without Task

Change Transaction Source Cycle With Task List List Comment

Request for Change (SMCR) Target cycle must have a task Can be reassigned to target
list. cycle with or without task list.

Normal Change (SMMJ) Target cycle must have a task Cannot be reassigned. All transports of copies of the
list. original transport requests
must have been imported be-
fore you can reassign a nor-
mal change.

You can only reassign a nor-

mal change as long as is it
not approved for preliminary
import. Once a preliminary
import has been started, for
example, by importing the
original transport into a qual-
ity assurance system, you
can no longer reassign the
normal change to another
change cycle.

Urgent Change (SMHF) Target cycle must have a task Cannot be reassigned.
 Caution
list.
We recommend that you
do not reassign urgent
changes.

Standard Change (SMSG) Target cycle must have a task Cannot be reassigned. All transports of copies of the
list. original transport requests
must have been imported
before you can reassign a
standard change.

Git-enabled Change (SMGH) Cannot be reassigned. Cannot be reassigned. Currently SMGH doesn’t sup-
port the Reassign function.

Defect Correction (SMTM) Target cycle must have a task Cannot be reassigned.
list.

Administrative Change Can be reassigned to target Can be reassigned to target

(SMAD) cycle with or without task list. cycle with or without task list.

General Change (SMCG) Can be reassigned to target Can be reassigned to target

cycle with or without task list. cycle with or without task list.

Change Control Management

142 PUBLIC Change Request Management
Reassigning Change Transactions Assigned to Continual
Cycles and Phase Cycles

Procedure

1. In the change transaction, choose More Change Cycle Assignment .

The system displays a dialog box.

2. Search for the change cycle to which you want to reassign the change transaction.
3. Select the change cycle and choose Reassign Change Transaction.

The cycle can be filtered by BAdI: Advanced Control of Cycle Field for RfC and Change Document
(AI_CM_CYCLE_CONTROL).

 Tip

This BAdI offers advanced control of the change cycle field when a request for change or change
document is created or reassigned.

Results

If a change document is linked to a request for change that only contains one change document, the request
for change is reassigned to the target cycle as well.

If a change document is linked to a request for change that contains more than one change document, the
change document is unlinked from the request for change.

 Note

Use the Related Document field in the Details assignment block to assign the unlinked change document to
another request for change. In the Scope assignment block of the request for change, reassigned change
documents show as Linked Manually.

Reassigning Change Documents Assigned to Release Cycles

Context

You can reassign a change document to a later minor or major release that has the same task list as the original
release cycle.

Change Control Management

Change Request Management PUBLIC 143
Procedure

1. In the change transaction, in assignment block Details, select Change Cycle / Phase.

A dropdown list displays the releases to which the change document can be assigned.
2. Choose the release to which you want to reassign the change transaction.

Related Information

Statuses and Phases That Allow Reassigning Change Transactions [page 144]
Preliminary Import of Normal Changes [page 71]
Using Change Cycles Without a Task List [page 35]
Project Management Integration [page 269]
Processing Release Cycles [page 110]
Using Change Cycles Without a Task List [page 35]

4.3.4.10.1 Statuses and Phases That Allow Reassigning

Change Transactions

In addition to the general prerequisites for reassigning change transactions to another change cycle, the status
of the change transaction and the phase of the target change cycle must allow reassigning.

Change Document Statuses

Basically, you can reassign most change transactions up until the moment they’re implemented in production.
Expand the following table for details.

Statuses That Allow Reassigning a Change Transaction to Another Change Cycle

Change Transaction Status Status Description

Request for Change (SMCR) E0004 Approved

E0011 Extend Scope

E0015 Being Implemented

Administrative Change (SMAD) E0001 Created

E0002 In Process

General Change (SMCG) E0001 Created

E0003 To Be Documented

E0004 Failed

Change Control Management

144 PUBLIC Change Request Management
Change Transaction Status Status Description

E0011 Change Analysis

E0012 To Be Tested

E0014 In Process

Urgent Change (SMHF) not relevant

Git-enabled Change (SMGH) not relevant

Normal Change (SMMJ) E0001 Created

E0002 In Development

E0004 To Be Tested

E0009 Successfully Tested (only for central

CTS-enabled change cycles)

Standard Change (SMSG) E0001 Created

E0002 In Development

E0004 To Be Tested

E0009 Successfully Tested (only for central

CTS-enabled change cycles)

Defect Correction (SMTM) E0002 In Correction

E0004 To Be Retested

E0011 In Delivery

Change Cycle Phases

The following reassignment actions are delivered in standard Customizing:

• AD_REASSIGN (Reassign Administrative Change)

• GC_REASSIGN (Reassign General Change)
• RC_REASSIGN (Reassign Normal Change)
• SG_REASSIGN (Reassign Standard Change)
• TM_REASSIGN (Reassign Defect Correction)

The phase of the target cycle defines which of these reassignment actions are allowed. Expand the following
table for details.

Change Control Management

Change Request Management PUBLIC 145
Change Cycle Phases That Allow Reassigning a Change Transaction

Reassign Administrative Change

Reassign Defect Correction

Reassign Standard Change
Reassign General Change

Reassign Normal Change

Target Change
Cycle Phase

Continual Cycle Created     

(E0001)
(SMAI)
Active (E0002)     

Phase Cycle Scope (E0002)     

(SMIM) Build (E0004)     

Test (E0005)     

Go Live (E0006)     

Being     
Completed
(E0007)

Release Cycle Created     

(SMRE) (E0001)

Scope (E0002)     

Build (E0004)     

Test (E0005)     

Deploy (E0006)     

Operate     
(E0007)

Hypercare     
(E0011)

Configuration

You can change the default settings in Customizing (transaction SPRO) under SAP Solution Manager
Capabilities (Optional) Change Control Management Change Request Management Framework Configure
status-dependent UI element control .

Change Control Management

146 PUBLIC Change Request Management
Related Information

Reassigning Change Transactions [page 141]

Defined Actions for Continual Cycles [page 30]
Defined Actions for Phase Cycles [page 36]
Defined Actions for Release Cycles [page 45]

4.3.4.11 Approving and Exporting Critical Objects

Prerequisites

To approve critical object conflicts in Change Request Management, you have one of these roles:

• SAP_CM_CHANGE_MANAGER_COMP (default role to approve critical object conflicts)

• SAP_CM_ADMINISTRATOR_COMP
• a custom partner role, configured to approve and reject critical object conflicts

Context

If the critical object check is active, transport requests that contain critical objects must be approved before
they can be exported.

When a user tries to export a transport request containing one or more critical objects, you receive a request
for approval. In the change transaction, in the Transport Management assignment block, in the Critical Objects
column, an icon is displayed.

Now you can either reject the request and remove the critical objects from the transport request, or explicitly
approve transport of the critical objects.

Procedure

1. Choose More Process Critical Object .

The system displays a list of the critical Workbench objects and critical Customizing objects.
2. For each object that you want to approve, select the entry and choose Approve Object.
3. The icon in the Status field changes color, indicating that the objects have now been approved for export.

Change Control Management

Change Request Management PUBLIC 147
  Note

You can revoke the approval for export by highlighting the entry and selecting Reject Object. You can
also process critical objects in the Transport-Related Checks assignment block or in the My Inbox SAP
Fiori app. After processing, the system enters your action as a text log in the change document itself.

Related Information

Defining Critical Objects [page 325]

Performing Transport-Related Checks [page 150]

4.3.4.12 Transports into the Sandbox System

To try out client-specific Customizing settings, you can import transport requests directly from a normal
change, an urgent change, or a defect correction into a sandbox system.

To change the default settings, in Customizing (transaction SPRO) perform the activities under SAP Solution
Manager Capabilities (Optional) Change Control Management Implementation of Dialog Boxes in the
WebClient UI .

Prerequisites

If you have already copied the relevant standard SAP transaction types to your namespace, you
are using the PPF action (for example, SMMJ_TRANSPORT_TO_SANDBOX_MJ) for SAP GUI to trigger
transports into the sandbox system. Adapt the PPF action and condition assigned to your transaction
types to the standard settings (new standard action definitions: SMMJ_TRANSPORT_TO_SANDBOX_W_MJ,
SMHF_TRANSPORT_TO_SANDBOX_W, SMTM_TRANSPORT_TO_SANDBOX_W). If you have customized the status
profile for your PPF condition, adapt it to the standard settings.

You make these settings in Customizing (transaction SPRO) under SAP Solution Manager Capabilities
(Optional) Change Control Management Transactions Actions Change Actions and Conditions Define
Action Profiles and Actions .

Activities

1. Choose Actions Transport into Sandbox System .

2. If the change document has several transport requests, or there are several sandbox systems, specify
which transport request to transport into which target client after saving the transaction.

Change Control Management

148 PUBLIC Change Request Management
3. Select the clients for the sandbox system.
4. The system informs you about a successful transport.

Related Information

Changing the Transaction Status with PPF Actions [page 169]

4.3.4.13 Reverting Changes

Use

Use this procedure to revert a code change that has already been transported to the test system, and to
prevent that it is imported into the production systems.

All transport requests that were released within a maintenance period are simultaneously imported into the
production systems at the end of the period. You cannot isolate the import and cancel the transport request of
a particular erroneous or undesired change (for a continual cycle or as part of an urgent change).

Instead, deimplement the development and ship it in an additional transport request.

The system automatically checks the import queue for changes to specific objects, and imports only the latest
version of a change or an object. If the import queue contains more than one version, the version on the latest
transport request overwrites the earlier versions during the import into the production system.

Activities

1. Create an additional transport request, linked to the same change document or cycle, for the change in its
desired version.
2. This new transport request is imported into your production systems together with the other transports in
the queue, and overwrites the undesired change that is on an earlier transport request.
3. The correct version, that is, the latest version of the object is active in the production system.

Related Information

Performing Transport-Related Checks [page 150]

Change Control Management

Change Request Management PUBLIC 149
4.3.5 Performing Transport-Related Checks

You can use several types of checks to detect issues related to a transport request. The checks are performed
in a unified way, and are centrally executed and displayed on a unified UI.

Use
These checks can be triggered automatically, for example, upon saving, or manually. You can use the standard
checks as delivered by SAP and implement custom-specific checks. The checks can be switched on and off
globally, or for specific managed systems.

Overview: Transport-Related Checks

Type of Check Use On/Off Switch

Cross-system object lock (CSOL) check Detects version conflicts when objects Administration Cockpit Cross-
are changed on more than one trans- System Object Lock and Downgrade
port request at the same time. Protection

Cross-System Object Lock [page 363]

Downgrade protection (DGP) check Detects when the same object has al- Administration Cockpit Cross-
ready been changed, released, or im- System Object Lock and Downgrade
ported earlier. Protection

Downgrade Protection [page 360]

Critical object check Detects a critical objects conflict. Administration Cockpit Critical
Objects
Defining Critical Objects [page 325]

Allowlist object check Checks transport requests of standard Administration Cockpit Allowlist
(Change Request Management only) changes for objects that aren’t on the Objects
allowlist.

Defining Allowlist Objects [page 329]

Cross-reference check Detects if a referenced object doesn’t Administration Cockpit Cross-

exist or has a different version in the Reference Check
target system.

Cross-Reference Check [page 332]

ABAP test cockpit (ATC) check Detects errors in ABAP code. managed system, transaction ATC

Quality Checking with the ABAP Test

Cockpit (ATC)

Code inspector check Checks the program code of objects on managed system, transaction ATC

the transport request.

Using the Code Inspector in Urgent

Changes [page 85]

Change Control Management

150 PUBLIC Change Request Management
Type of Check Use On/Off Switch

Customer-specific check (BAdI imple- Implement your own check logics. BAdI implementation definition /
mentation) TMWFLOW/TRANS_DEFINED_CHECK
Implementing Custom-Specific Checks
[page 163]

Prerequisites
You have installed the latest version of the Support Tools plug-in (ST-PI) in the managed development systems.

Available Transport-Related Check in Different Contexts

Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

Automatic  -   - - - 
check be-
fore saving
objects to a
transport
request
(CSOL
check also
when edit-
ing an ob-
ject) in a
managed
system.

Change Control Management

Change Request Management PUBLIC 151
 Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

Automatic -       
check be-
fore an op-
eration that
releases
transport
requests or
creates
transports
of copies
(ToC), such
as:

• You
trigger
a PPF
action
that re-
leases
a
trans-
port
re-
quest
or cre-
ates
ToC in
the
Web-
Client
UI.
• You re-
lease
trans-
port
re-
quests

Change Control Management

152 PUBLIC Change Request Management
 Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

or cre-
ate
ToC
from
assign-
ment
block
Transp
ort
Manag
ement
on the
Web-
Client
UI, or
from
the
task
list in
the Ad-
minis-
tration
Cock-
pit.

Change Control Management

Change Request Management PUBLIC 153
 Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

Automatic -  - -  - - 
check be-
fore an op-
eration that
decouples
or assigns
transport
requests, or
reassigns
change
documents,
such as

• You de-
couple
or as-
sign
trans-
port
re-
quests
from
assign-
ment
block
Transp
ort
Manag
ement
on the
Web-
Client
UI or
from
the
task
list in

Change Control Management

154 PUBLIC Change Request Management
 Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

the Ad-
minis-
tration
Cock-
pit.
• You re-
assign
change
docu-
ments
on the
Web-
Client
UI.

Change Control Management

Change Request Management PUBLIC 155
 Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

Automatic -  - - - - - 
check be-
fore an op-
eration that
imports
transport
requests,
such as

• You
trigger
a PPF
action
that
con-
tains
an im-
port
trans-
port
re-
quest
opera-
tion on
the
Web-
Client
UI.
• You im-
port
trans-
port
re-
quests
from
the
task

Change Control Management

156 PUBLIC Change Request Management
 Customer-Specific Check
Cross-Reference Check
Allowlist Object Check

Code Inspector Check

Critical Object Check
CSOL Check

DGP Check

ATC Check
Context

list in
the Ad-
minis-
tration
Cock-
pit.

Manually -       
performed
static
check;
started
from as-
signment
block
Transport-
Related
Checks on
the Web-
Client UI.

 Note

For custom-specific checks, the system performs both check before release and check before import.
If the check is performed manually from assignment block Transport-Related Checks, both methods
CHECK_BEFORE_RELEASE and CHECK_BEFORE_IMPORT are called. However, the following rules apply:

• The system only performs check before release on the open transport requests that are in the change
(manual check from the change) or in the cycle (manual check from the cycle).
• Regarding the check before import, the system detects issues based on the transport tracks and gets
all relevant target systems with possible importable transport requests (located in the buffer). Then,
they are passed to the method CHECK_BEFORE_IMPORT of the BAdI to perform the check.

Change Control Management

Change Request Management PUBLIC 157
When is a check active?
A check is regarded as active in the Transport-Related Checks assignment block, except if one of the following
rules applies:

Check Is inactive when...

Downgrade Protection (DGP) Check • The global switch is off.

• The global switch is on, but the switches of all the rele-
vant systems are off.
For a change document, these are all the development
systems of the transport requests that it contains and
all the target systems that these development systems
can reach via transport tracks. For a change cycle, these
are all the systems on the transport tracks of its task
list.
• If there is no relevant system (for example, for a change
document, it doesn’t contain any transport requests), it
also means off.

Critical Object Check • The global switch is off.

• The global switch is on, but the switches of all the rele-
vant systems are off.
For a change document, these are all the development
systems of the transport requests that it contains. For a
change cycle, these are all the development systems on
the transport tracks of its task lists.
• If there is no relevant system (for example, for a change
document, it doesn’t contain any transport requests), it
also means off.

Allowlist Object Check • The global switch is off.

(Change Request Management only)

• The global switch is on, but the switches of all the rele-
vant systems are off.
For a change document, these are all the development
systems of the transport requests that it contains.
• If there is no relevant system for a standard change
document, it also means off.

ABAP Test Cockpit (ATC) and Code Inspector Check • The switches of all the relevant systems are off.
For a change document, these are all the development
systems of the transport requests that it contains. For a
change cycle, these are all the development systems on
the transport tracks of its task list.
• If there is no relevant system (for example, for a change
document, it doesn’t contain any transport requests), it
also means off.

Custom-Specific Check • There is no active BAdI implementation.

Change Control Management

158 PUBLIC Change Request Management
Related Information

Automatic and Manual Check [page 159]

Upon-Saving Transport-Related Checks [page 161]
Implementing Custom-Specific Checks [page 163]
Changing the Transaction Status with PPF Actions [page 169]
Setting up E-Mail Notifications for Cycle-Level Scheduled Import Jobs [page 337]

4.3.5.1 Automatic and Manual Check

Use these checks to detect issues related to a transport request. These checks can be triggered automatically
(dynamic check) and manually (static check).

Automatic Check

Automatic checks are triggered by transport-related operations, such as saving a change to a transport
request or executing a PPF action that releases a transport request.

If the automatic check detects no conflicts, the action continues.

If the automatic check detects a conflict, on the WebClient UI, a dialog box displays the results: A result table
displays the overall status of each check type. Below this table, tab pages for the individual checks provide
a detailed list of conflicts. The overall status for each check type indicates the highest severity of the issues
detected.

There are two types of severity for each conflict:

• Warning (yellow status icon): If there are only warnings, you can choose to ignore the conflict and continue
the action. Alternatively, you can cancel your action.
• Error (red status icon): If one or more errors were detected, you must cancel your action and fix the errors.
You cannot ignore the conflict.

 Note

In the WebClient UI, you see the overall status and tab page only for checks that detected conflicts. For
example, if only the DGP check and ATC check detected conflicts, you see results only for these two
checks. For checks that detected no conflict or have not been activated, there is no tab page.

For checks performed before saving objects to a transport request in the managed system, the check
results are displayed on the SAP GUI, which is different from the WebClient UI. Here, the CSOL check result,
the critical object check result, and the custom-specific check result are shown side by side.

Manual Check

You can choose to perform a manual check for change documents and change cycles:

In the WebClient UI, in assignment block Transport-Related Checks, select Perform check to start an
asynchronous job that performs various checks for the current change document or change cycle. To update
the result list, select Refresh.

Change Control Management

Change Request Management PUBLIC 159
The assignment block Transport-Related Checks displays the tab pages for all check types, regardless of
whether or not conflicts exist. The following statuses exist:

• Error (red icon)

• Warning (yellow icon)
• Passed (green icon): no conflict has been detected so far
• Inactive (gray icon): the check is switched off or not active

When you load the assignment block for the first time or refresh manually, it displays the cached check results
of the checks performed in your last session (either by an automatic check from the WebClient UI or by manual
check).

 Note

You can display ATC check results for historical warnings that were ignored earlier.

Severity Determination

For CSOL and downgrade protection (DGP) checks Stop means error

(customized in SAP Solution Manager Configuration trans- Warning means warning

action SOLMAN_SETUP)
Silent / Off means passed.

For critical object check Conflicts detected before saving objects to transport re-
quests in managed systems are always categorized as a
Warning, or else as an Error.

For ABAP test cockpit check and code inspector check If Block on any errors is selected, priority 1 and 2 conflicts are
categorized as an Error, or else as a Warning.
(customized and controlled in the managed system: ATC
settings Behavior on Release configuration)

For custom-specific check Severity is determined and controlled by BAdI implementa-

tion.

Related Information

Performing Transport-Related Checks [page 150]

Implementing Custom-Specific Checks [page 163]
Changing the Transaction Status with PPF Actions [page 169]

Change Control Management

160 PUBLIC Change Request Management
4.3.5.2 Upon-Saving Transport-Related Checks

When you save your changes to a transport request, a detailed conflict analysis is performed.

Use

Saving changes to a transport request is one of the contexts that can trigger automatic transport-related
checks. A detailed conflict analysis is performed and a Transport-Related Errors and Warnings dialog box
appears, specifying the conflicting objects:

• If the highest overall severity is a warning, you can ignore the warning and continue by saving the objects to
the transport request; or you decide to cancel the saving process altogether.
• If there are one or more errors, you must cancel the saving process and fix the errors. The objects are not
saved to the current transport request.

To find out which specific checks are performed in which environment, see the installation matrix.

Upon-saving critical object check does not check whether the objects are modified objects.

In Change Request Management, the allowlist object check only allows saving objects that are defined on the
respective allowlist to a transport request belonging to a standard change.

 Note

We recommend that you save the objects immediately to a transport request to receive a detailed conflict
analysis.

Installation Matrix of Upon-Saving Checks

Managed System Managed System

Upon-Saving Checks /
SAP_BASIS Up-To-Date ST-PI Version Dropdown List Logic Applied

Yes New On New

Yes / No New / Old / No ST-PI On (Legacy CSOL) Old

Yes / No New / Old / No ST-PI Off Off

• Column “Managed System SAP_BASIS Up-to-Date” indicates whether in the managed development
system, either SAP Note 2402504 is implemented, or a support package stack containing this SAP
Note is installed.
• For ST-PI version, the value “New” means that the ST-PI version released is in alignment with SAP Solution
Manager 7.2 SPS 5, which is ST-PI 2008_1_700/710 SPS 16 and ST-PI 7.40 SPS 6.
• Each transport-related check has its own settings for being globally switched on or off. For more
information, see Overview: Transport-Related Checks [page 150].

Change Control Management

Change Request Management PUBLIC 161
 If you selected “Off”, no check is performed when you save an object to a transport request, or when you
switch to change mode after selecting an object. In this case, since no cross-system object lock check
is performed, no lock entry is created for the object. Yet, the lock entry is the basis for the downgrade
protection release check and reassign check. As a result, later no conflict can be detected for the object for
this type of check.
In the Administration Cockpit, the Landscape Overview displays the status of upon-saving checks for each
system in your landscape.
• Column “Logic Applied” indicates which checks are performed:
“New” refers to the new upon-saving checks in ST-PI, which contains CSOL, critical object, allowlist
objects, and custom checks.
“Old” refers to the old cross-system object lock (CSOL) check that is implemented in SAP_BASIS. With
SAP Solution Manager 7.2 SPS 3, it was extended to have a critical object (not supporting parent-child
relationship) and custom checks.

Integration

The upon-saving transport-related checks are available in the ABAP workbench. As of SAP Solution Manager
7.2 SPS 7, the upon-saving transport-related checks are also integrated in the ABAP Development Tools (ADT)
in Eclipse.

To use this function in the ABAP Development Tools (ADT) in Eclipse, you need the following versions:

• ABAP Development Tools 2.89 or higher

• Software component SAP_BASIS 740 or higher in managed development systems
• Solution Tools Plug-In (ST-PI) 740 SP08 or higher in managed development systems

In the ABAP workbench, when you switch to change mode, a dialog box notifies you about potential conflicts.

In the ABAP Development Tools (ADT), when you switch to change mode, you are notified about potential
conflicts.

Related Information

Performing Transport-Related Checks [page 150]

Automatic and Manual Check [page 159]
Implementing Custom-Specific Checks [page 163]
Defining Allowlist Objects [page 329]
Processing Standard Changes [page 89]

Change Control Management

162 PUBLIC Change Request Management
4.3.5.3 Implementing Custom-Specific Checks

Use

By implementing the BAdI definition /TMWFLOW/TRANS_DEFINED_CHECK, you can implement your own check
logics and integrate them into the transport-related checks framework. Before each transport operation, for
example, a release transport request is triggered (by the WebClient UI or the Administration Cockpit), the
respective BAdI implementation method is called to perform the check. Based on combined check results (also
from other checks), the system will decide whether the end user can continue the action.

• Check before save

By implementing the method CHECK_BEFORE_SAVE_TRANS_REQ, you can perform your own specific
check before you try to save objects to a transport request in the managed system. The check is also called
when you have selected an object in the workbench and switch to change mode. Note that allowlist object
checks and critical object checks are not performed in change mode.
Prerequisites:
You have enabled this check by setting the Cross-System Object Lock switch to active in the managed
development system.
Descriptions of the importing method parameters:
• IV_TRANSPORT_REQUEST: The ID of the transport request to which the objects are being saved. When
you switch to change mode for a selected object, the request ID is empty if the object has not been
locked in any request yet. You can decide for yourself whether to perform a check when the request ID
is not available.
• IV_SRC_SYS_TMS_SID: TMS short SID of the managed system
• IV_SRC_SYS_TMS_DOMAIN: TMS domain of the managed system
• IT_LOCKS_4_OBJECT: CTS locks for the objects to be saved
• IT_LOCKS_4_TABLE_KEY: CTS locks for the table keys to be saved
Descriptions of the exporting method parameters:
• ET_CHECK_RESULT: Check results
• ET_ERROR_MESSAGE: Error messages for runtime exceptions
• Check before release
By implementing the method CHECK_BEFORE_RELEASE, you can perform your own specific check just
before some transport requests are being released or some transports of copies are being created.
Description about the importing parameters of the method:
• IT_TRANSPORT_REQUEST: The IDs of the transport requests to be released or on which transport of
copies are to be created
• IV_TASKLIST_ID: The ID of the task list where the release is to be triggered
• IV_CYCLE_GUID: The GUID of the relevant cycle
• IV_CHANGE_GUID: The GUID of the relevant change document, if applicable
• IV_IMMEDIATE: Whether the operation is triggered immediately (abap_true) or scheduled at a later
time (abap_false)
• IV_CHECK_4_CREATING_TOC: Whether the method is invoked when creating transport of copies
Description about the exporting parameters of the method:
• ET_CHECK_RESULT: Check results
• ET_ERROR_MESSAGE: Error messages for runtime exceptions
• Check before import

Change Control Management

Change Request Management PUBLIC 163
 By implementing the method CHECK_BEFORE_IMPORT, you can perform your own specific check before
transport requests are imported into the target systems.
Descriptions of the importing method parameters:
• IT_TRANS_REQUESTS_TO_SYS: The internal table of mapping between target systems and transport
requests to be imported
• IV_TASKLIST_ID: The ID of the task list from which the import is to be triggered
• IV_CYCLE_GUID: The GUID of the relevant cycle
• IV_CHANGE_GUID: The GUID of the relevant change document
• IV_IMMEDIATE: Whether the operation is triggered immediately (ABAP_TRUE) or scheduled at a later
time (ABAP_FALSE)
Descriptions of the exporting method parameters:
• ET_CHECK_RESULT: Check results
• ET_ERROR_MESSAGE: Error messages for runtime exceptions
• Check before decouple
By implementing the method CHECK_BEFORE_DECOUPLE, you can perform your own specific check before
transport requests are decoupled.
Descriptions of the importing method parameters:
• IT_TRANSPORT_REQUEST: The IDs of the transport requests to be decoupled
• IV_TASKLIST_ID: The ID of the task list where the decouple is to be triggered
• IV_CYCLE_GUID: The GUID of the relevant cycle
• IV_CHANGE_GUID: The GUID of the relevant change document
Descriptions of the exporting method parameters:
• ET_CHECK_RESULT: Check results
• ET_ERROR_MESSAGE: Error messages for runtime exceptions
• Check before assign
By implementing the method CHECK_BEFORE_ASSIGN, you can perform your own specific check before
transport requests are assigned.
Descriptions of the importing method parameters:
• IT_TRANSPORT_REQUEST: The IDs of the transport requests to be assigned
• IV_TARGET_TASKLIST_ID: The ID of the task list where the assign is to be triggered
• IV_TARGET_CYCLE_GUID: The GUID of the relevant cycle
• IV_TARGET_CHANGE_GUID: The GUID of the relevant change document
Descriptions of the exporting method parameters:
• ET_CHECK_RESULT: Check results
• ET_ERROR_MESSAGE: Error messages for runtime exceptions
• Check before reassign change
By implementing the method CHECK_BEFORE_REASSIGN_CHNG, you can perform your own specific
check before a request for change or a change document is reassigned.
Descriptions of the importing method parameters:
• IV_CHANGE_GUID: The GUID of the request for change or the change document to be reassigned
• IV_SOURCE_CYCLE_GUID: The GUID of the source cycle
• IV_TARGET_CYCLE_GUID: The GUID of the target cycle
Descriptions of the exporting method parameters:
• ET_CHECK_RESULT: Check results
• ET_ERROR_MESSAGE: Error messages for runtime exceptions

Change Control Management

164 PUBLIC Change Request Management
 The exporting parameter ET_CHECK_RESULT contains the check results shown in the Transport-Related
Checks popup window and assignment block. For the result entry, the RESULT_STATUS field is important
as it determines whether the transport operation, for example release transport requests, can continue
or not. As long as there is one entry whose RESULT_STATUS is filled with the value STOP, the transport
operation will be stopped.

More Information

Automatic and Manual Check [page 159]

Transport-Related Checks [page 150]

4.3.5.4 Using the Transport-Related Checks Assignment

Block

Use

In the Transport-Related Checks assignment block, you can trigger the manual downgrade check and display
information related to potential downgrades and conflicts. The assignment block is available in the following
change transactions:

• Continual cycle
• Phase cycle
• Release cycle
• Urgent change
• Normal change
• Defect correction

Features

• Whenever the system finds conflicts related to transport-related checks, icons show how critical each
conflict is. The following conflict types are possible:
• Downgrade warning
When exporting transports (changes), you are notified of identical objects that have not been imported
into the productive system yet.
• Imminent downgrade
When importing transports (changes), you are notified of identical objects that have been released
later and have already been imported.
• Overtaker warning
When importing transports (changes), you are notified of identical objects that have been released
earlier, but have not been imported yet.

Change Control Management

Change Request Management PUBLIC 165
  Note

In Customizing, you can assign a conflict type to a check type. For each check type, you can configure
the conflict criticality and an icon.

Example: If you set the conflict type for the release check to “Warning” and assign the warning icon, the
system displays a conflict that is found when releasing a transport request as a warning and shows the
yellow warning icon.

• The status of the conflict is displayed. “Open” means that the conflict has not been handled yet. If you
explicitly ignore a conflict, the status changes to “Ignored”.
• You can display details for each conflict. The detail screen contains more information about the conflict, for
example, the source transport and the objects involved.
• You can ignore check results one by one by choosing Ignore. You can also ignore several check results at
the same time by selecting the relevant ones.
• You can trigger a downgrade check manually for the change transaction and recheck it. Choose Refresh to
display the check results.
• You can customize the Downgrade Protection Check (DGP) as Silent mode: During releasing and importing
of transport requests, the system does not perform the DGP check but skips it directly. In case of the
manual check in the assignment block, the system performs the DGP check. If any conflicts are detected,
the check result is reported as warning conflicts.

4.3.6 Monitoring the System Landscape, Transport Status

and Transport Risks

The Landscape assignment block provides various functions for the connected ABAP and Java systems and
external services. The assignment block is available in change documents and change cycles.

Prerequisites

• In Customizing (transaction SPRO) under SAP Solution Manager Capabilities (Optional) Change
Control Management Change Request Management Framework Make Settings for Change Transaction
Types , you can define a system as Relevant for Logon, depending on the user status of the change
document. For example, if a normal change has the status To Be Tested, the test system is the system
relevant for logon.
• In Customizing (transaction SPRO) under SAP Solution Manager Capabilities (Optional) Change
Control Management Change Request Management Framework Transport Risks , you can define the
display of transport risks.

Change Control Management

166 PUBLIC Change Request Management
Features

You see the relevant systems for the current status. By default, the system relevant for the current status is
displayed. For example, if the change document has the status In Development, only the development system
is displayed. You can also choose to see all systems in the system landscapes.

You can log on to a connected system. For connected cloud services based on CTS+, there are additional
options to log on to configured service URLs such as the HCP Dashboard (SAP BTP cockpit) or the SAP
SuccessFactors cockpit.

For Git-enabled changes, you see the current deployed commit of the Git repository linked to the system.

You see current information about the transport requests of the change document or change cycle:

• Transport status (only displayed in change documents): Summarizes the statuses of the transport
requests in the Transport Management assignment block.
The following statuses are possible:

Transport Status in Change Documents

Transport Status Meaning

Modifiable Transport request is open in development.

Partially released At least one transport request has been released.

Released All transport requests belonging to the change document

are released.

To be imported Transport requests or transport of copies must be im-

ported.

Partially imported At least one transport request has been successfully im-
ported into a follow-on system.

Imported All transport requests have been successfully imported

into a follow-on system.

Transport of copies partially imported Some of the transport of copies have been imported.

Transport of copies imported All of the transport of copies have been imported.

Partially imported with error Some of the transport requests or transport of copies
have been imported with error.

Imported with error All the transport requests or transport of copies have been
imported, but some of them with error.

• Risk status: A symbol indicates the transport status, depending on the status of the change document or
change cycle, and the system role.
• Transport risks: There is a link to an overview of the transport risks. You can show further risk details, for
example a description of the risk, and the transport request.

Change Control Management

Change Request Management PUBLIC 167
 Transport risks are classified in the following way:

Transport Risk Type Cause

Transport error If an error occurs when importing a transport request,

the transport error is reported as a transport risk for the
(return code ≥ 8)
target system.

Open transports If a transport request is not released, it is reported as an

open transport for the source system.

Missing transports If a released transport request is to be imported into this

system, but has not yet been imported, it is reported as
missing transport for the target system.

Missing transports are calculated for the respective trans-

port track, but are not reported for the source system.

Synchronization errors This refers to transports that did not run synchronously
(for example, synchronization errors in projects with more
than one export system).

Note that open transport requests are not reported as

synchronization errors, they are classified as open trans-
port.

Related Information

Change Cycles [page 28]

Change Documents [page 26]
Creating Transports of Copies (ToC) [page 123]
SAP Note 2833873

4.3.7 PPF Actions in Change Request Management

With these actions, you can change the statuses in change transactions and cycles, send automatic e-mails to
business partners, confirm changes, create new project management tasks or automatically calculate working
times, to name just a few.

The Post-Processing Framework (PPF) actions and their conditions listed in the following pages are delivered
with the SAP standard Change Request Management. They are defined in Customizing under SAP Solution
Manager Capabilities (Optional) Change Control Management Transactions Actions .

The following pages list the PPF actions for these change transactions with the following attributes:

• Scheduling conditions control whether an action is to be scheduled for processing. An action is only
generated if the scheduling condition is fulfilled.

Change Control Management

168 PUBLIC Change Request Management
• Start conditions are checked before the action is executed. Background actions are only executed if
the start condition is fulfilled. Dialog actions can be started manually from the action menu if the start
condition is fulfilled.
• Processing time defines when an action is executed. Processing can be started immediately when an action
is scheduled, or after the transaction has been saved. It is also possible to only schedule the actions to be
processed later by a user in the document.
• Processing mode defines whether actions are processed automatically (in the background) after
determination, that is, they are activated as soon as the schedule conditions are met. Actions can also
be processed manually, using dialog windows.

Related Information

PPF Actions for SMCR Request for Change [page 172]

PPF Actions for SMAD Administrative Change [page 181]
PPF Actions for SMCG General Change [page 187]
PPF Actions for SMGH Git-Enabled Change [page 194]
PPF Actions for SMHF Urgent Change [page 201]
PPF Actions for SMMJ Normal Change [page 212]
PPF Actions for SMSG Standard Change [page 222]
PPF Actions for SMTM Defect Correction [page 227]
PPF Actions for SMAI Continual Cycle [page 236]
PPF Actions for SMIM Phase Cycle [page 239]
PPF Actions for SMRE Release Cycle [page 243]

4.3.7.1 Changing the Transaction Status with PPF Actions

You control the status changes in change transactions as well as change cycles using Post-Processing
Framework (PPF) actions.

Prerequisites

You have configured the action profile. For more information, see Customizing for SAP Solution Manager
(transaction SPRO) under Capabilities (Optional) Change Control Management Transactions Change
Actions and Conditions Define Action Profiles and Actions .

Change Control Management

Change Request Management PUBLIC 169
Context

Whenever a transaction changes its status (for example, to Tested Successfully), certain Change Request
Management actions must be carried out, such as the release of a transport request. The system performs
these actions either automatically, or a user starts them manually.

 Note

Change Request Management uses generic PPF actions, which you can adjust to your requirements. In
contrast to PPF actions, Change Request Management actions run in the PPF action (HF_SET_STATUS),
dependent from the user status. For more information on Change Request Management actions, see
the Customizing (transaction code SPRO) under SAP Solution Manager Capabilities (Optional)
Change Control Management Change Request Management Framework Actions in Change Request
Management .

You can only execute actions under specific conditions. Which actions are executable depends on the status of
the change transaction and the status of the respective change cycle.

You can link actions with calls of dialog boxes in the WebClient UI, in which the user can, for example, enter or
confirm data. The dialog boxes can be displayed before or after processing the actions. For more information
about configuring the dialog box framework, see the Customizing (transaction code SPRO) under SAP
Solution Manager Capabilities Change Control Management Implementation of Dialog Boxes in WebClient
UI .

 Note

You need knowledge of the WebClient UI and ABAP development to adjust the dialog box framework.

Procedure

1. In the change transaction or in the change cycle, switch to change mode and select Actions and an
available action.
2. Save the change transaction or cycle.

The system changes the status and displays it in the header data.
3. Go ahead in the change process.

Next Steps

On assignment block Scheduled Actions, you can display, execute, and optionally schedule actions.

Change Control Management

170 PUBLIC Change Request Management
Related Information

Processing Change Transactions [page 56]

Automatic and Manual Check [page 159]

Change Control Management

Change Request Management PUBLIC 171
4.3.7.2 PPF Actions for SMCR Request for Change

These are the PPF actions for SMCR (Request for Change)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMCR_APPROVA This action au- Automatic When saving AIC_APPR_ME

L_PROCEDURE_ tomatically de- M_ID
STATUS termines the
approval status
based on the
decisions of all
approvers:

- If all of them
approve, it pro-
ceeds to status
Approved
(E0004).

- If one ap-
prover rejects
it, it proceeds to
status Rejected
(E0003). After
rejecting a
scope exten-
sion, the re-
quest for
change returns
to the status it
had before; for
example, Being
Implemented
(E0015).

- If all approvers
select "Not rele-
vant", it keeps
the status To Be
Approved
(E0012).

SMCR_APPROVE This action au- Automatic When saving System status: User status:
tomatically cre-
D_SYSTEMS NE I1005 Being
ates the change
Implemented
documents that
are related to Error-free
the request for
change.

Change Control Management

172 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_AWAITIN After validation, Manual When saving x One of the fol- Error-free
G_APPROVAL use this action lowing user sta-
to request ap- tuses:
proval from the Validation,
designated Extend Scope
business part-
ners.

The request for

change pro-
ceeds to status
To Be Approved
(E0012) when
you save it.

Note that the

request for
change must be
error-free.

SMCR_CANCEL_ Use this action Manual When saving x User status:

SCOPE_EXTENS to cancel a Extend Scope
ION scope exten-
sion for this re-
quest for
change.

The request for

change returns
to status Being
Implemented
(E0015) when
you save it.

SMCR_CHECK_S This action au- Automatic When saving Contains errors

tomatically
TATUS
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

Change Control Management

Change Request Management PUBLIC 173
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_CHECK_S When you se- Manual When saving Contains errors

lect this action,
TATUS_AGAIN
you start a re-
check of the
document con-
sistency ac-
cording user
status.

SMCR_CONFIRM When the re- Manual When saving x User status:

quest for Implemented
change is in sta-
tus
Implemented
(E0005):

Use this action

to confirm that
all required
changes have
been imple-
mented.

The request for

change pro-
ceeds to status
Confirmed
(E0006) when
you save it.

SMCR_CREATE_ For task-based Manual When saving PPM project as-

PPM_TASK Project Man- signed, but no
agement inte- PPM task yet.
gration:

Use this action

to create a new
project man-
agement task.

A project man-
agement task is
created from
this document
when you save
it.

Change Control Management

174 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_EXTEND_ Use this action Manual When saving x One of the fol-
SCOPE to extend the lowing user sta-
scope of re- tuses: Being
quest for Implemented,
change that is Implemented
already in sta-
tus Being
Implemented
(E0015).

The request for

change pro-
ceeds to status
Extend Scope
(E0011) when
you save the re-
quest for
change.

You must re-

quest approval
for the addi-
tional change
documents.

SMCR_IMPLEME Use this action Manual When saving

NTED_MANUALL
to close the re-
Y
quest for
change without
first closing the
related change
documents.

The request for

change pro-
ceeds to status
Implemented
(E0005) when
you save it.

SMCR_IT_RFC_ This system ac- Automatic When saving System status

tion starts the
APPROVAL_WOR LE I1387 (Await-
approval work-
KFLOW ing approval)
flow when the
request for
change is saved
with status To
Be Approved
(E0012).

Change Control Management

Change Request Management PUBLIC 175
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_IT_RFC_ This system ac- Automatic Via selection re-

CREATE_EMAIL tion sends e- port
_DOC mail notifica-
tions to all as-
signed business
partners when
a new request
for change has
been created.

This action is
executed with
selection report
RSPPFPRO-
CESS.

SMCR_IT_RFC_ This action au- Automatic Via selection re-

DISPATCH tomatically de- port
termines which
development
team is respon-
sible for proc-
essing this
document.

The respective
business part-
ner is assigned
with selection
report
RSPPFPRO-
CESS.

This action is
configured in
the rule editor.

SMCR_ON_CREA This action au- Automatic When saving x Change trans-

tomatically sets
TE action is open
the status
(system status
Created
(E0001) when I1002)
you save a new
request for
change.

Change Control Management

176 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_OPEN_UP Use this action Manual Immediately One of the fol-

_BPCA to start the lowing user sta-
Business Proc- tuses:
ess Change An- Validation, To
alyzer (BPCA). Be Approved,
Being
Solution,
Implemented,
branch, and
Implemented
transaction ID
are copied from Error-free
the document,
and displayed in
the BPCA.

SMCR_QUALIFY Use this action Manual When saving x System status

to validate a re-
_CHANGE E0001 (initial)
quest for
change:

Review the data

that has already
been entered,
and add infor-
mation as re-
quired.

The request for

change pro-
ceeds to status
Validation
(E0014) when
you save it.

Change Control Management

Change Request Management PUBLIC 177
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_REJECTE Use this action Manual When saving x User status:

D to reject a re- Validation
quest for
change:

Review the data

that has already
been entered,
and add infor-
mation as re-
quired.

The request for

change pro-
ceeds to status
Rejected
(E0003) when
you save it.

SMCR_RELEASE Use this action Manual When saving x User status:

_FOR_DEVELOP to release a re- Approved
MENT quest for
Error-free
change for de-
velopment after
it was ap-
proved.

The document
proceeds to
status Being
Implemented
(E0015) when
you save it.

The assigned
change docu-
ments proceed
to status
Created
(E0001).

Change Control Management

178 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_RESET_T During appro- Manual When saving x User status:

O_VALIDATION val, use this ac- Approved
tion to update
the information
in a request for
change.

The request for

change returns
to status
Validation
(E0014) when
you save it.

SMCR_SEND_MA Use this action Automatic When saving System status: One of the fol-
IL_CHANGE_MA to send a notifi- I1002 (open) lowing user sta-
NAGER cation to the tuses: Created,
One of the fol-
change man- Approved,
lowing user sta-
ager. Implemented
tuses: To Be
The e-mail is Approved,
sent when you Being
save the re- Implemented
quest for
change.

You can use

customized e-
mail templates
or the default
template.

SMCR_SEND_MA Use this action Automatic When saving One of the fol- One of the fol-
IL_REQUESTER to send a notifi- lowing user sta- lowing user sta-
cation to the re- tuses: tuses:
quester. Validation, To Approved,
Be Approved, Rejected,
The e-mail is
Being Confirmed
sent when you
Implemented,
save the re-
Implemented
quest for
change.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

Change Request Management PUBLIC 179
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

SMCR_START_I Use this action Manual When saving

MPLEMENTATIO
to start devel-
N
opment for a
standard
change (SMSG)
that is related
to this request
for change.

The status of
the request for
change pro-
ceeds to Being
Implemented
(E0015) when
you save it.

The change
document will
be created after
this action is
executed.

SMCR_UPDATE_ This action au- Automatic When saving

DURATIONS tomatically cal-
culates the total
working time.

The duration in
regard to serv-
ice level agree-
ment (SLA) is
calculated
when you save
the document.

Change Control Management

180 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCR_UPDATE_ After approval Manual

SCOPE
of a scope ex-
tension, use
this action to
create addi-
tional change
documents.

Note: This ac-

tion is delivered
as inactive; you
must activate it
before you can
use it.

Related Information

Processing Requests for Change [page 56]

4.3.7.3 PPF Actions for SMAD Administrative Change

These are the PPF actions for SMAD (Administrative Change)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMAD_CHECK_S This action au- Automatic When saving User status:

tomatically
TATUS_AD Created
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

Change Control Management

Change Request Management PUBLIC 181
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMAD_CHECK_S Use this action Manual When saving Contains errors

to start a re-
TATUS_AGAIN_
check of the
AD
document con-
sistency ac-
cording user
status.

SMAD_CREATE_ For task-based Manual When saving PPM project as-

PPM_TASK Project Man- signed, but no
agement inte- PPM task yet.
gration:

Use this action

create a new
project man-
agement task.

A project man-
agement task is
created from
this document
when you save
it.

SMAD_FIND_TE This action au- Automatic When saving

AM_FDT tomatically de-
termines which
development
team is respon-
sible for proc-
essing this
document.

The respective
business part-
ner is assigned
when you save
the document.

Note: This ac-

tion is delivered
as "inactive";
you must acti-
vate it before
you can use it.

Change Control Management

182 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMAD_FINISHE Use this action Manual When saving x User status: In

D_AD to confirm that Process
execution of
Error-free
this document
is finished.

The document
proceeds to
status
Completed
(E0004) when
you save it.

SMAD_IN_PROC Use this action Manual When saving x User status:

ESS_AD to start devel- Created
opment for this
Error-free
document.

The document
proceeds to
status In
Process
(E0002) when
you save it.

SMAD_OK_AD Use this action Manual When saving x User status:

to confirm that Completed
development
Error-free
for this docu-
ment is fin-
ished.

The document
proceeds to
status
Confirmed
(E0009) when
you save it.

Change Control Management

Change Request Management PUBLIC 183
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMAD_ON_CREA This action au- Automatic When saving x Change trans-

TE_AD tomatically initi- action is open
alizes the (system status
Change Re- I1002)
quest Manage-
ment frame-
work and sets
status Created
(E0001) when
you save a new
document.

Note: Do not
customize this
PPF action.

SMAD_SEND_MA This action au- Automatic When saving User-status: In User status:
IL_CHANGE_MA tomatically Process Completed
NAGER sends an e-mail
to the change
manager when
you save the
document.

You can use

customized e-
mail templates
or the default
template.

SMAD_SEND_MA This action au- Automatic When saving Change trans- User status:
IL_IT_OPERAT tomatically action is open Created
OR sends an e-mail (system status
to the IT opera- I1002)
tor when you
save the docu-
ment.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

184 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMAD_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

SMAD_TESTED_ Use this action Manual When saving x User status:

AND_NOT_OK_A if the document Completed
D was tested
Error-free
without suc-
cess.

The document
returns to sta-
tus In Process
(E0002) when
you save it.

SMAD_UPDATE_ This action au- Automatic When saving

DURATIONS tomatically cal-
culates the total
working time.

The duration in
regard to serv-
ice level agree-
ment (SLA) is
calculated
when you save
the document.

Change Control Management

Change Request Management PUBLIC 185
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMAD_WITHDRA Use this action Manual When saving x One of the fol-
W_AD to withdraw the lowing user sta-
change docu- tuses: Created,
ment. In Process,
Completed,
The document
Confirmed
proceeds to
status
Withdrawn
(E0010) when
you save it.

Note that
changes cannot
be withdrawn if
they contain
any changed
Solution Docu-
mentation ele-
ments.

Related Information

Processing Administrative Changes [page 95]

Change Control Management

186 PUBLIC Change Request Management
4.3.7.4 PPF Actions for SMCG General Change

These are the PPF actions for SMCG (General Change)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMCG_BACK_TO Use this action Manual When saving

_IN_PROCESS if the document

was tested
without suc-
cess.

The document
returns to sta-
tus In Process
(E0014) when
you save it.

SMCG_BUILDIN Use this action Manual When saving x User status:

G to start proc- Created
essing this
Error-free
document.

The document
proceeds to
status In
Process
(E0014) when
you save it.

SMCG_CANCELE Use this action Manual When saving x User status:

D to close a failed Restore Source
change.
Error-free
The document
proceeds to
status Canceled
(E0006) when
you save it.

SMCG_CHANGE_ Use this action Manual When saving x User status: To

DOCUMENTATIO to confirm suc- Be Tested
N cessful testing.
Error-free
The document
proceeds to
status To Be
Documented
(E0003) when
you save it.

Change Control Management

Change Request Management PUBLIC 187
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCG_CHANGE_ After documen- Manual When saving x User status: To

EVALUATION tation, use this Be Documented
action to start
Error-free
evaluation of
the change.

The document
proceeds to
status Change
Analysis
(E0011) when
you save it.

SMCG_CHECK_S This action au- Automatic When saving

tomatically
TATUS
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

SMCG_CHECK_S When you se- Manual When saving Contains errors

lect this action,
TATUS_AGAIN
you start a re-
check of the
document con-
sistency ac-
cording user
status.

SMCG_CONFIRM Use this action Manual When saving x User status:

ED to confirm that Change
the change Analysis
meets the re-
quirements.

The document
proceeds to
status
Confirmed
(E0005) when
you save it.

Change Control Management

188 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCG_CREATE_ For task-based Manual When saving PPM project as-

PPM_TASK
Project Man- signed, but no
agement inte- PPM task yet.
gration:

Use this action

to create a new
project man-
agement task.

A project man-
agement task is
created from
this document
when you save
it.

SMCG_FAILED Use this action Manual When saving x User status:

to confirm that Change
the change Analysis
does not meet
Error-free
the require-
ments.

The document
proceeds to
status Failed
(E0004) when
you save it.

SMCG_FALLBAC Use this action Manual When saving x User status:

K_EXECUTION to request an- Failed
other solution if
Error-free
a change does
not meet the re-
quirements.

The document
proceeds to
status Restore
Source (E0015)
when you save
it.

Change Control Management

Change Request Management PUBLIC 189
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCG_FIND_TE This action au- Automatic When saving

AM_FDT
tomatically de-
termines which
development
team is respon-
sible for proc-
essing this
document.

The respective
business part-
ner is assigned
when you save
the document.

Note: This ac-

tion is delivered
as "inactive";
you must acti-
vate it before
you can use it.

SMCG_ON_CREA This action au- Automatic When saving x Change trans-

TE tomatically initi- action is open
alizes the (system status
Change Re- I1002)
quest Manage-
ment frame-
work and sets
status Created
(E0001) when
you save a new
document.

Note: Do not
customize this
PPF action.

Change Control Management

190 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCG_SEND_MA This action au- Automatic When saving One of the fol- One of the fol-
IL_CHANGE_MA tomatically lowing user sta- lowing user sta-
NAGER sends an e-mail tuses: To Be tuses:
to the change Documented, Canceled,
manager when Restore Source Change
you save the Analysis
document.

You can use

customized e-
mail templates
or the default
template.

SMCG_SEND_MA This action au- Automatic When saving System status One of the fol-
IL_DEVELOPER tomatically I1002 (open) lowing user sta-
sends an e-mail tuses: Created,
One of the fol-
to the devel- To Be
lowing user sta-
oper when you Documented,
tuses: Change
save the docu- Failed
Analysis, To Be
ment.
Tested
You can use
customized e-
mail templates
or the default
template.

SMCG_SEND_MA This action au- Automatic When saving User status: In User status: To
IL_TESTER tomatically Process Be Tested
sends an e-mail
to the tester
when you save
the document.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

Change Request Management PUBLIC 191
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCG_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

SMCG_TO_BE_T Use this action Manual When saving x User status: In

ESTED to indicate that Process
processing this
Error-free
document is
finished.

The document
proceeds to
status To Be
Tested (E0012)
when you save
it.

SMCG_UPDATE_ This action au- Automatic When saving

DURATIONS tomatically cal-
culates the total
working time.

The duration in
regard to serv-
ice level agree-
ment (SLA) is
calculated
when you save
the document.

Change Control Management

192 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMCG_WITHDRA Use this action Manual When saving x One of the fol-
WN to withdraw the lowing user sta-
change docu- tuses: Created,
ment. In Process

The document Error-free

proceeds to
status
Withdrawn
(E0016) when
you save it.

Note that
changes cannot
be withdrawn if
they contain
any changed
Solution Docu-
mentation ele-
ments.

Related Information

Processing General Changes [page 97]

Change Control Management

Change Request Management PUBLIC 193
4.3.7.5 PPF Actions for SMGH Git-Enabled Change

These are the PPF actions for SMGH (Git-enabled Change)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMGH_AUTHORI Use this action Manual When saving x User status:

ZE_PRODUCTIO to authorize the Successfully
N_GH import into pro- Tested
duction.
Error-free
The document
proceeds to
status
Authorized for
Production
(E0014) when
you save it.

SMGH_CHECK_S When you se- Manual When saving Contains errors

lect this action,
TATUS_AGAIN_
you start a re-
GH
check of the
document con-
sistency ac-
cording user
status.

SMGH_CHECK_S This action au- Automatic When saving

tomatically
TATUS_GH
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

Change Control Management

194 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMGH_CREATE_ For task-based Manual When saving PPM project as-

PPM_TASK
Project Man- signed, but no
agement inte- PPM task yet.
gration:

Use this action

to create a new
project man-
agement task.

A project man-
agement task is
created from
this document
when you save
it.

SMGH_IN_PROC Use this action Manual When saving x User status:

ESS_GH to start devel- Created
opment for this
Error-free
document.

The document
proceeds to
status In
Development
(E0002) when
you save it.

SMGH_ON_CREA This system ac- Automatic When saving x Change trans-

TE_GH tion automati- action is open
cally initializes (system status
the Change Re- I1002)
quest Manage-
ment frame-
work and sets
status Created
(E0001) when
you save a new
document.

Note: Do not
customize this
PPF action.

Change Control Management

Change Request Management PUBLIC 195
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMGH_OPEN_UP When you se- Manual Immediately One of the fol-

_BPCA_GH lect this action, lowing user sta-
you start the tuses: In
Business Proc- Development,
ess Change An- To Be Tested
alyzer (BPCA).

Solution,
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

SMGH_PRODUCT Use this action Manual When saving x User status:

IVE_GH to import the Authorized for
document into Production
production.
Error-free
The document
proceeds to
status Deployed
into Production
(E0006) when
you save it.

SMGH_SEND_MA This action au- Automatic When saving User status: To User status:
IL_CHANGE_MA tomatically Be Tested Successfully
NAGER sends an e-mail Tested
to the change
manager when
you save the
document.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

196 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMGH_SEND_MA This action au- Automatic When saving Change trans- User status:
IL_DEVELOPER tomatically action is open Created
sends an e-mail (system status
to the devel- I1002)
oper when you
save the docu-
ment.

You can use

customized e-
mail templates
or the default
template.

SMGH_SEND_MA This action au- Automatic Immediately

IL_IMPORT_FE tomatically
EDBACK sends feedback
when an import
is finished.

The IT operator
gets an e-mail
for import er-
rors with trans-
port return co-
des.

You can use

customized e-
mail templates
or the default
template.

SMGH_SEND_MA This action au- Automatic When saving User status: User status:
IL_IT_OPERAT tomatically Successfully Authorized for
OR sends an e-mail Tested Production
to the IT opera-
tor when you
save the docu-
ment.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

Change Request Management PUBLIC 197
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMGH_SEND_MA This action au- Automatic When saving One of the fol- User status: To
IL_TESTER tomatically lowing user sta- Be Tested
sends an e-mail tuses: In
to the tester Development,
when you save Successfully
the document. Tested

You can use

customized e-
mail templates
or the default
template.

SMGH_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

SMGH_TESTED_ Use this action Manual When saving x One of the fol-
AND_NOT_OK_G if the document lowing user sta-
H was tested tuses: To Be
without suc- Tested,
cess. Successfully
Tested,
The document
Authorized for
returns to sta-
Production
tus In
Development
(E0002) when
you save it.

Change Control Management

198 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_TESTED_ Use this action Manual When saving x User status: To

AND_OK_MJ to confirm suc- Be Tested
cessful testing.
Error-free
The document
proceeds to
status
Successfully
Tested (E0009)
when you save
it.

SMGH_TO_BE_T Use this action Manual When saving x User status: In

ESTED_GH to indicate that Development
development
Error-free
for this docu-
ment is fin-
ished.

The document
proceeds to
status To Be
Tested (E0004)
when you save
it.

SMGH_UPDATE_ This action au- Automatic When saving

DURATIONS tomatically cal-
culates the total
working time
(SLA).

The duration in
regard to serv-
ice level agree-
ment (SLA) is
calculated
when you save
the document.

Change Control Management

Change Request Management PUBLIC 199
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMGH_WITHDRA Use this action Manual When saving x One of the fol-
W_GH to withdraw the lowing user sta-
change docu- tuses: Created,
ment. In Development

The document
proceeds to
status
Withdrawn
(E0010) when
you save it.

Note that
changes cannot
be withdrawn if
they contain
any non-empty
transport re-
quests or
changed Solu-
tion Documen-
tation ele-
ments.

Related Information

Processing Git-enabled Changes [page 99]

Change Control Management

200 PUBLIC Change Request Management
4.3.7.6 PPF Actions for SMHF Urgent Change

These are the PPF actions for SMHF (Urgent Change)

Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_CHECK_STATUS This action auto- Automatic When sav- User status: To

matically checks
ing Be Tested
the document
consistency ac- Error-free
cording to user
status when you
save the docu-
ment.

SMHF_CHECK_STATUS_AGAIN Use this action Manual When sav- Contains er-

to start a re-
ing rors
check of the
document con-
sistency accord-
ing user status.

SMHF_CLOSE Use this action Manual When sav- x User status:

to indicate that ing Confirmed
the execution of
Error-free
this document is
finished.

The document
proceeds to sta-
tus Completed
(E0008) when
you save it.

SMHF_CONFIRM Use this action Manual When sav- x User status:

to confirm that ing Imported into
the change Production
meets the re-
Error-free
quirements.

The document
proceeds to sta-
tus Confirmed
(E0007) when
you save it.

Change Control Management

Change Request Management PUBLIC 201
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_CREATE_PPM_TASK For task-based Manual When sav- PPM project

Project Manage- ing assigned, but
ment integra- no PPM task
tion: yet.

Use this action

to create a new
project manage-
ment task.

A project man-
agement task is
created from
this document
when you save
it.

SMHF_CREATE_TASKLIST Use this action if Manual Immedi-

automatic task ately
list creation
failed.

When you select

this action, you
create a task list
for this docu-
ment.

Change Control Management

202 PUBLIC Change Request Management
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_DISTRIBUTE For urgent Manual When sav-

changes that are ing
relevant for
more than one
productive sys-
tem or client:

Use this action

to copy an ur-
gent change and
distribute it to
other systems.

The original ur-

gent change
must have sta-
tus Successfully
Tested (E0005)
before you can
use this action.

A new urgent
change is cre-
ated for the se-
lected system
when you save
this document.

Note: This ac-

tion is delivered
as inactive; you
must activate it
before you can
use it.

Change Control Management

Change Request Management PUBLIC 203
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_FIND_TEAM_FDT This action auto- Automatic When sav-

matically deter- ing
mines which de-
velopment team
is responsible
for processing
this document.

The respective
business partner
is assigned
when you save
the document.

Note: This ac-

tion is delivered
as "inactive";
you must acti-
vate it before
you can use it.

SMHF_GO_LIVE Use this action Manual When sav- x User status:

to authorize the ing Successfully
document for Tested
import into pro-
Error-free
duction.

The document
proceeds to sta-
tus Authorized
for Production
(E0009) when
you save it.

SMHF_IN_PROCESS Use this action Manual When sav- x User status:

to start develop- ing Created
ment for this
Error-free
document.

The document
proceeds to sta-
tus In
Development
(E0002) when
you save it.

Change Control Management

204 PUBLIC Change Request Management
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_ON_SAVE This action initi- Automatic When sav- x Change trans-

alizes the ing action is open
Change Request (system status
Management I1002)
framework and
sets status
Created (E0001)
when you save a
new document.

Note: Do not
customize this
PPF action.

SMHF_OPEN_UP_BPCA Use this action Manual Immedi- User status: In

to start the Busi- ately Development,
ness Process To Be Tested
Change Ana-
Error-free
lyzer (BPCA).

Solution,
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

SMHF_PRODUCTIVE Use this action Manual When sav- x User status:

to import the ing Authorized for
document into Production
production.
Error-free
The document
proceeds to sta-
tus Imported
into Production
(E0006) when
you save it.

SMHF_RETROFIT_CRM When you select Manual Immedi- User status:

this action, you
ately Authorized for
start the retrofit
Production
process for
transport re- Retrofit-ena-
quests related to
bled
this document.

Change Control Management

Change Request Management PUBLIC 205
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_SEND_MAIL_APR_CRIT_OBJ This action Automatic Immedi-

sends an e-mail ately
to the requester
when a trans-
port request
that contains a
critical objects
conflict is ap-
proved.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

SMHF_SEND_MAIL_CHANGE_MANAGER This action auto- Automatic When sav- One of the fol- One of the
matically sends ing lowing user following
an e-mail to the statuses: To Be user sta-
change manager Tested, tuses:
when you save Imported into Successfull
the document. Production y Tested,
Confirmed
You can use cus-
tomized e-mail
templates or the
default tem-
plate.

SMHF_SEND_MAIL_DEVELOPER This action auto- Automatic When sav- System status User sta-
matically sends ing I1002 (open) tus:
an e-mail to the Created
developer when
you save the
document.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

Change Control Management

206 PUBLIC Change Request Management
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_SEND_MAIL_IMPORT_FEEDBACK This action auto- Automatic Immedi-

matically sends ately

feedback when
an import is fin-
ished.

The IT operator
gets an e-mail
for import errors
with transport
return codes.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

SMHF_SEND_MAIL_IT_OPERATOR This action auto- Automatic When sav- User status: User sta-
matically sends ing Successfully tus:
an e-mail to the Tested Authorized
IT operator for
when you save Production
the document.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

SMHF_SEND_MAIL_REJ_CRIT_OBJ This action auto- Automatic Immedi-

matically sends ately
an e-mail to the
requester when
a transport re-
quest that con-
tains a critical
objects conflict
is rejected.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

Change Control Management

Change Request Management PUBLIC 207
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_SEND_MAIL_REQ_CRIT_OBJ This action auto- Automatic Immedi-

matically sends ately
an e-mail to the
approver when
approval for a
critical objects
conflict is re-
quested.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

SMHF_SEND_MAIL_TESTER This action auto- Automatic When sav- User status: In User sta-
matically sends ing Development tus: To Be
an e-mail to the Tested
tester when you
save the docu-
ment.

You can use cus-

tomized e-mail
templates or the
default tem-
plate.

SMHF_SET_KB_DELTA For long text Automatic When sav-

search using ing
TREX:

This action auto-

matically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

Change Control Management

208 PUBLIC Change Request Management
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_TESTED_AND_NOT_OK Use this action if Manual When sav- x Not in the fol-
the document ing lowing user
was tested with- statuses:
out success. Created, In
Development,
The document
Confirmed,
returns to status
Completed,
In Development
Withdrawn
(E0002) when
you save it.

SMHF_TESTED_AND_OK Use this action Manual When sav- x User status: To

to confirm suc- ing Be Tested
cessful testing.
Error-free
The document
proceeds to sta-
tus Successfully
Tested (E0005)
when you save
it.

SMHF_TO_BE_TESTED Use this action Manual When sav- x User status: In

to indicate that ing Development
development for
Error-free
this document is
finished.

The document
proceeds to sta-
tus To Be Tested
(E0004) when
you save it.

Change Control Management

Change Request Management PUBLIC 209
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_TRANSPORT_TO_SANDBOX_W Use this action Manual When sav-

ing
to import the
transport re-
quest to the
sandbox system
when you save
the document.

Note: This ac-

tion is delivered
as inactive; you
must activate it
before you can
use it.

SMHF_UPDATE_DURATIONS This action auto- Automatic When sav-

matically calcu- ing
lates the total
working time.

The duration in
regard to service
level agreement
(SLA) is calcu-
lated when you
save the docu-
ment.

Change Control Management

210 PUBLIC Change Request Management
 Sets a
Process- Process- User Scheduling Start Con-
Action name Use ing Mode ing Time Status Condition dition

SMHF_WITHDRAW Use this action Manual When sav- x One of the fol-
to withdraw the ing lowing user
change docu- statuses:
ment. Created, In
Development
The document
proceeds to sta-
tus Withdrawn
(E0010) when
you save it.

Note that
changes cannot
be withdrawn if
they contain any
non-empty
transport re-
quests or
changed Solu-
tion Documen-
tation elements.

Related Information

Processing Urgent Changes [page 81]

Change Control Management

Change Request Management PUBLIC 211
4.3.7.7 PPF Actions for SMMJ Normal Change

These are the PPF actions for SMMJ (Normal Change)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMMJ_APPROVE Use this action Manual When saving x One of the fol-
_PRELIMINARY to approve the lowing user sta-
_MJ preliminary im- tuses:
port. Successfully
Tested,
The document
Preliminary
proceeds to
Import
status Testing
Requested
for Preliminary
Import (E0012) Error-free
when you save
Relevant au-
it.
thorization

SMMJ_AUTHORI Use this action Manual When saving x User status:

ZE_PRE_IMPOR to authorize a Tested for
T_MJ preliminary im- Production
port for import Import
into production.
Error-free
The document
proceeds to
status
Authorized for
Import (E0014)
when you save
it.

SMMJ_CANCEL_ Use this action Manual When saving x One of the fol-
PRELIMIN_IMP to cancel the lowing user sta-
ORT_MJ preliminary im- tuses: Testing
port. for Preliminary
Import, Tested
The document
for Production
returns to sta-
Import,
tus Successfully
Authorized for
Tested (E0009)
Import
when you save
it. Error-free

Change Control Management

212 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_CHECK_S When you se- Manual When saving Contains errors

lect this action,
TATUS_AGAIN_
you start a re-
MJ
check of the
document con-
sistency ac-
cording user
status.

SMMJ_CHECK_S This action au- Automatic When saving

tomatically
TATUS_MJ
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

SMMJ_CONFIRM Use this action Manual When saving x User status:

_SUCC_TEST_M to confirm suc- Testing for
J cessful testing Preliminary
for a prelimi- Import
nary import.
Error-free
The document
proceeds to
status Tested
for Production
Import (E0013)
when you save
it.

SMMJ_CREATE_ For task-based Manual When saving PPM project as-

PPM_TASK
Project Man- signed, but no
agement inte- PPM task yet.
gration:

Use this action

to create a new
project man-
agement task.

A project man-
agement task is
created from
this document
when you save
it.

Change Control Management

Change Request Management PUBLIC 213
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_DECLINE Use this action Manual When saving x User status:

_PRELIMINARY to reject a pre- Preliminary
_MJ liminary import. Import
Requested
The document
returns to sta- Error-free
tus Successfully
Tested (E0009)
when you save
it.

SMMJ_FIND_TE This action au- Automatic When saving

AM_FDT tomatically de-
termines which
development
team is respon-
sible for proc-
essing this
document.

The respective
business part-
ner is assigned
when you save
the document.

Note: This ac-

tion is delivered
as inactive; you
must activate it
before you can
use it.

SMMJ_IMPORT_ After authoriza- Manual When saving x User status:

NC_INTO_PROD tion of a pre- Authorized for
_MJ liminary import, Import
use this action
Error-free
to import the
document into
production.

The document
proceeds to
status Imported
into Production
(E0006) when
you save it.

Change Control Management

214 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_IN_PROC Use this action Manual When saving x User status:

ESS_MJ to start devel- Created
opment for this
Error-free
document.

The document
proceeds to
status In
Development
(E0002) when
you save it.

SMMJ_ON_CREA This system ac- Automatic When saving x Change trans-

TE_MJ tion automati- action is open
cally initializes (system status
the Change Re- I1002)
quest Manage-
ment frame-
work and sets
status Created
(E0001) when
you save a new
document.

Note: Do not
customize this
PPF action.

SMMJ_OPEN_UP When you se- Manual Immediately One of the fol-

_BPCA_MJ lect this action, lowing user sta-
you start the tuses: In
Business Proc- Development,
ess Change An- To Be Tested,
alyzer (BPCA). Testing for
Preliminary
Solution,
Import
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

Change Control Management

Change Request Management PUBLIC 215
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_PRODUCT Use this action Manual Background x User status:

IVE_MJ to import the Successfully
document into Tested
production.
Error-free
The document
proceeds to
status Imported
into Production
(E0006) when
you save it.

SMMJ_REQUEST Use this action Manual Background x User status:

_PRELIMINARY to request a Successfully
_MJ preliminary im- Tested
port.
Error-free
The document
proceeds to
status
Preliminary
Import
Requested
(E0011) when
you save it.

SMMJ_RETROFI When you se- Manual Immediately User status:

lect this action,
T_CRM_MJ Successfully
you start the
Tested
retrofit process
for transport re- Error-free
quests related
to this docu- Retrofit-ena-
ment. bled

Change Control Management

216 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_SEND_MA This action au- Automatic Immediately

IL_APR_CRIT_ tomatically
OBJ sends an e-mail
to the requester
when a trans-
port request
that contains a
critical objects
conflict is ap-
proved.

You can use

customized e-
mail templates
or the default
template.

SMMJ_SEND_MA This action au- Automatic When saving One of the fol- One of the fol-
IL_CHANGE_MA tomatically lowing user sta- lowing user sta-
NAGER sends an e-mail tuses: To Be tuses:
to the change Tested, Successfully
manager when Successfully Tested,
you save the Tested, Testing Preliminary
document. for Preliminary Import
Import Requested,
You can use
Tested for
customized e-
Production
mail templates
Import
or the default
template.

SMMJ_SEND_MA This action au- Automatic When saving Change trans- User status:
IL_DEVELOPER tomatically action is open Created
sends an e-mail (system status
to the devel- I1002)
oper when you
save the docu-
ment.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

Change Request Management PUBLIC 217
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_SEND_MA This action au- Automatic Immediately

IL_IMPORT_FE tomatically
EDBACK sends feedback
when an import
is finished.

The IT operator
gets an e-mail
for import er-
rors with trans-
port return co-
des.

You can use

customized e-
mail templates
or the default
template.

SMMJ_SEND_MA This action au- Automatic When saving User status: User status:
IL_IT_OPERAT tomatically Tested for Authorized for
OR sends an e-mail Production Import
to the IT opera- Import
tor when you
save the docu-
ment.

You can use

customized e-
mail templates
or the default
template.

SMMJ_SEND_MA This action Automatic Immediately

IL_REJ_CRIT_ sends an e-mail
OBJ to the requester
when a trans-
port request
that contains a
critical objects
conflict is re-
jected.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

218 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_SEND_MA This action au- Automatic Immediately

IL_REQ_CRIT_ tomatically
OBJ sends an e-mail
to the approver
when approval
for a critical ob-
jects conflict is
requested.

You can use

customized e-
mail templates
or the default
template.

SMMJ_SEND_MA This action au- Automatic When saving One of the fol- One of the fol-
IL_TESTER tomatically lowing user sta- lowing user sta-
sends an e-mail tuses: In tuses: To Be
to the tester Development, Tested, Testing
when you save Successfully for Preliminary
the document. Tested, Import
Preliminary
You can use
Import
customized e-
Requested
mail templates
or the default
template.

SMMJ_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

Change Control Management

Change Request Management PUBLIC 219
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_TESTED_ Use this action Manual When saving x One of the fol-
AND_NOT_OK_M if the document lowing user sta-
J was tested tuses: To Be
without suc- Tested, Testing
cess. for Preliminary
Import
The document
returns to sta-
tus In
Development
(E0002) when
you save it.

SMMJ_TESTED_ Use this action Manual When saving x User status: To

AND_OK_MJ to confirm suc- Be Tested
cessful testing
Error-free
for a transport
of copies (ToC).

The document
proceeds to
status
Successfully
Tested (E0009)
when you save
it.

SMMJ_TO_BE_T Use this action Manual When saving x User status: In

ESTED_MJ to indicate that Development
development
Error-free
for this docu-
ment is fin-
ished.

The document
proceeds to
status To Be
Tested (E0004)
when you save
it.

SMMJ_TRANSPO Use this action Manual When saving User status: In

to import the
RT_TO_SANDBO Development
transport re-
X_W_MJ
quest to the Error-free
sandbox sys-
tem when you
save the docu-
ment.

Change Control Management

220 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMMJ_UPDATE_ This action au- Automatic When saving

DURATIONS_MJ tomatically cal-
culates the total
working time
(SLA).

The duration in
regard to serv-
ice level agree-
ment (SLA) is
calculated
when you save
the document.

SMMJ_WITHDRA Use this action Manual When saving x One of the fol-
W_MJ to withdraw the lowing user sta-
change docu- tuses: Created,
ment. In Development

The document
proceeds to
status
Withdrawn
(E0010) when
you save it.

Note that
changes cannot
be withdrawn if
they contain
any non-empty
transport re-
quests or
changed Solu-
tion Documen-
tation ele-
ments.

Related Information

Processing Normal Changes [page 68]

Change Control Management

Change Request Management PUBLIC 221
4.3.7.8 PPF Actions for SMSG Standard Change

These are the PPF actions for SMSG (Standard Change)

Sets a
Processing Processing User Scheduling Start
Action name Use Mode Time Status Condition Condition

SMSG_CHECK_STATUS This action automati- Automatic When sav-

cally checks the docu- ing
ment consistency ac-
cording to user status
when you save the docu-
ment.

SMSG_CHECK_STATUS_AGAIN Use this action to start a Manual When sav-

recheck of the document ing
consistency according
user status.

SMSG_CREATE_PPM_TASK For task-based Project Manual When sav- PPM project

ing
Management integra- assigned,
tion: but no PPM
task yet.
Use this action to create
a new project manage-
ment task.

A project management
task is created from
this document when you
save it.

SMSG_FIND_TEAM_FDT This action automati- Automatic When sav-

ing
cally determines which
development team is re-
sponsible for processing
this document.

The respective business

partner is assigned when
you save the document.

Note: This action is de-

livered as "inactive"; you
must activate it before
you can use it.

Change Control Management

222 PUBLIC Change Request Management
 Sets a
Processing Processing User Scheduling Start
Action name Use Mode Time Status Condition Condition

SMSG_IN_PROCESS Use this action to start Manual When sav-

ing
development for this
document.

The document proceeds

to statusIn Development
(E0002) when you save
it.

SMSG_ON_CREATE This action initializes Automatic When sav-

ing
the Change Request
Management framework
and sets status Created
(E0001) when you save
a new document.

Note: Do not customize

this PPF action.

SMSG_OPEN_UP_BPCA Use this action to Manual Immedi-

ately
start the Business Proc-
ess Change Analyzer
(BPCA).

Solution, branch, and

transaction ID are copied
from the document, and
displayed in the BPCA

SMSG_PRODUCTIVE Use this action to import Manual When sav-

ing
the document into pro-
duction.

The document proceeds

to status Imported
into Production (E0006)
when you save it.

SMSG_RETROFIT_CRM Use this action to start Manual Immedi-

the retrofit process for ately
transport requests re-
lated to this document.

Change Control Management

Change Request Management PUBLIC 223
 Sets a
Processing Processing User Scheduling Start
Action name Use Mode Time Status Condition Condition

SMSG_SEND_MAIL_APR_WL_O This action automati- Automatic Immedi-

BJ ately
cally sends an e-mail to
the requester when a
new allowlist object is
approved.

You can use customized

e-mail templates or the
default template

SMSG_SEND_MAIL_CHANGE_M This action automati- Automatic When sav-

ANAGER ing
cally sends a notification
to the change manager.

The e-mail is sent when

you save the document.

You can use customized

e-mail templates or the
default template.

SMSG_SEND_MAIL_DEVELOPE This action automati- Automatic When sav-

R ing
cally sends a notification
to the developer.

The e-mail is sent when

you save the document.

You can use customized

e-mail templates or the
default template.

SMSG_SEND_MAIL_IMPORT_F This action sends auto- Automatic Immedi-

EEDBACK ately
matic feedback when an
import is finished.

The IT operator gets an

e-mail for import errors
with transport return co-
des.

You can use customized

e-mail templates or the
default template.

Change Control Management

224 PUBLIC Change Request Management
 Sets a
Processing Processing User Scheduling Start
Action name Use Mode Time Status Condition Condition

SMSG_SEND_MAIL_REJ_WL_O This action automati- Automatic Immedi-

BJ ately
cally sends an e-mail to
the requester when add-
ing an object to the al-
lowlist is rejected.

You can use customized

e-mail templates or the
default template.

SMSG_SEND_MAIL_REQ_WL_O This action automati- Automatic Immedi-

BJ ately
cally sends an e-mail
to the approver when a
new allowlist object is re-
quested.

You can use customized

e-mail templates or the
default template.

SMSG_SEND_MAIL_TESTER This action automati- Automatic When sav-

ing
cally sends a notification
to the tester when you
save the document.

You can use customized

e-mail templates or the
default template.

SMSG_SET_KB_DELTA For long text search us- Automatic When sav-

ing
ing TREX:

This action automati-

cally sets the Knowledge
Base delta update when
you save the document.

SMSG_TESTED_AND_NOT_OK Use this action if the Manual When sav-

ing
document was tested
without success.

The document returns

to status In Development
(E0002) when you save
it.

Change Control Management

Change Request Management PUBLIC 225
 Sets a
Processing Processing User Scheduling Start
Action name Use Mode Time Status Condition Condition

SMSG_TESTED_AND_OK Use this action to con- Manual When sav-

ing
firm successful testing
for a transport of copies
(ToC).

The document proceeds

to status Successfully
Tested (E0009) when
you save it.

SMSG_TO_BE_TESTED Use this action to indi- Manual When sav-

ing
cate that development
for this document is fin-
ished.

The document proceeds

to status To Be Tested
(E0004) when you save
it.

SMSG_TRANSPORT_TO_SANDB Use this action to import Manual When sav-

OX_W the transport request ing
to the sandbox system
when you save the docu-
ment.

SMSG_UPDATE DURATIONS This action automati- Automatic When sav-

ing
cally calculates the total
working time.

The duration in regard to

service level agreement
(SLA) is calculated when
you save the document.

Change Control Management

226 PUBLIC Change Request Management
 Sets a
Processing Processing User Scheduling Start
Action name Use Mode Time Status Condition Condition

SMSG_WITHDRAW Use this action to with- Manual When sav-

ing
draw the change docu-
ment.

The document proceeds

to status Withdrawn
(E0010) when you save
it.

Note that changes can-

not be withdrawn if they
contain any non-empty
transport requests or
changed Solution Docu-
mentation objects.

Related Information

Processing Standard Changes [page 89]

4.3.7.9 PPF Actions for SMTM Defect Correction

These are the PPF actions for SMTM (Defect Correction)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMTM_CHECK_S Use this action Manual When saving

TATUS_AGAIN_
to start a re-
TM
check of the
document con-
sistency ac-
cording to the
user status.

Change Control Management

Change Request Management PUBLIC 227
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_CHECK_S This action au- Automatic When Saving

TATUS_TM tomatically
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

SMTM_CLOSE_T Use this action Manual When Saving

M
to confirm that
execution of
this document
is finished.

The document
proceeds to
status Imported
into Production
(E0009) when
you save it.

SMTM_CREATE_ For task-based Manual When Saving PPM project as-

PPM_TASK
Project Man- signed, but no
agement inte- PPM task yet.
gration:

Use this action

to create a new
project man-
agement task.

A project man-
agement task is
created from
this document
when you save
it.

Change Control Management

228 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_FIND_TE This action au- Automatic When Saving

AM_FDT
tomatically de-
termines which
development
team is respon-
sible for proc-
essing this
document.

The respective
business part-
ner is assigned
when you save
the document.

Note: This ac-

tion is delivered
as inactive; you
must activate it
before you can
use it.

SMTM_IN_PROC Use this action Manual When Saving x User status:

ESS_TM
to start devel- Created
opment for this
Error-free
document.

The document
proceeds to
status In
Correction
(E0002) when
you save it.

Change Control Management

Change Request Management PUBLIC 229
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_ON_CREA This action au- Automatic When saving x Change trans-

TE_TM
tomatically initi- action is open
alizes the (system status
Change Re- I1002)
quest Manage-
ment frame-
work and sets
status Created
(E0001) when
you save a new
document.

Note: Do not
customize this
PPF action.

SMTM_OPEN_UP When you se- Manual Immediately One of the fol-

_BPCA_TM
lect this action, lowing user sta-
you start the tuses: In
Business Proc- Correction, To
ess Change An- Be Retested
alyzer (BPCA).
Error-free
Solution,
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

SMTM_SEND_MA This action au- Automatic Immediately

IL_APR_CRIT_
tomatically
OBJ
sends an e-mail
to the requester
when a trans-
port request
that contains a
critical objects
conflict is ap-
proved

You can use

customized e-
mail templates
or the default
template.

Change Control Management

230 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_SEND_MA This action au- Automatic When saving User status: To User status:
IL_CHANGE_MA
tomatically Be Retested Confirmed
NAGER
sends an e-mail
to the change
manager when
you save the
document.

You can use

customized e-
mail templates
or the default
template.

SMTM_SEND_MA This action au- Automatic When saving Change trans- User status:
IL_DEVELOPER
tomatically action is open Created
sends an e-mail (system status
to the devel- I1002)
oper when you
save the docu-
ment.

You can use

customized e-
mail templates
or the default
template.

SMTM_SEND_MA This action au- Automatic Immediately

IL_IMPORT_FE
tomatically
EDBACK
sends feedback
when an import
is finished.

The IT operator
gets an e-mail
for import er-
rors with trans-
port return co-
des.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

Change Request Management PUBLIC 231
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_SEND_MA This action au- Automatic Immediately

IL_REJ_CRIT_
tomatically
OBJ
sends an e-mail
to the requester
when a trans-
port request
that contains a
critical objects
conflict is re-
jected.

You can use

customized e-
mail templates
or the default
template.

SMTM_SEND_MA This action au- Automatic Immediately

IL_REQ_CRIT_
tomatically
OBJ
sends an e-mail
to the approver
when approval
for a critical ob-
jects conflict is
requested

You can use

customized e-
mail templates
or the default
template.

SMTM_SEND_MA This action au- Automatic When saving User status: In User status: To
IL_TESTER
tomatically Correction Be Retested
sends an e-mail
to the tester
when you save
the document.

You can use

customized e-
mail templates
or the default
template.

Change Control Management

232 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_SET_KB_ For long text Automatic When saving

DELTA
search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

SMTM_TESTED_ Use this action Manual When saving x User status: To

AND_NOT_OK_T
if the document Be Retested
M
was tested
Error-free
without suc-
cess.

The document
returns to sta-
tus In
Correction
(E0002) when
you save it.

SMTM_TESTED_ Use this action Manual When saving x User status: To

AND_OK_TM
to confirm suc- Be Retested
cessful testing
Error-free
for a defect cor-
rection.

The document
proceeds to
status
Successfully
Retested
(E0012) when
you save it.

Change Control Management

Change Request Management PUBLIC 233
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_TO_RETE Use this action Manual When saving x User status: In

ST_TM
to indicate that Correction
development
Error-free
for this docu-
ment is fin-
ished.

The document
proceeds to
status To Be
Retested
(E0004) when
you save it.

SMTM_TRANSPO Use this action Manual When saving

RT_TO_SANDBO to import the
X_W transport re-
quest to the
sandbox sys-
tem when you
save the docu-
ment.

SMTM_UPDATE_ This action au- Automatic When saving

DURATIONS
tomatically cal-
culates the total
working time.

The duration in
regard to serv-
ice level agree-
ment (SLA) is
calculated
when you save
the document.

Change Control Management

234 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMTM_WITHDRA Use this action Manual When saving x User status:

W_TM
to withdraw the Created
change docu-
ment.

The document
proceeds to
status
Withdrawn
(E0010) when
you save it.

Note that
changes cannot
be withdrawn if
they contain
any non-empty
transport re-
quests or
changed Solu-
tion Documen-
tation ele-
ments.

Related Information

Processing Defect Corrections [page 92]

Change Control Management

Change Request Management PUBLIC 235
4.3.7.10 PPF Actions for SMAI Continual Cycle

These are the PPF actions for SMAI (Continual Cycle)

Processing Processing Sets a User Scheduling Start Condi-

Action Name Use Mode Time Status Condition tion

SMAI_CHECK_S This action au- Automatic When saving x

TATUS tomatically
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

SMAI_CHECK_S Use this action Manual When saving x

TATUS_AGAIN to start a re-
check of the
document con-
sistency ac-
cording user
status.

SMAI_OPEN_UP Use this action Manual Immediately

_BPCA
to start the
Business Proc-
ess Change An-
alyzer (BPCA).

Solution,
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

Change Control Management

236 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action Name Use Mode Time Status Condition tion

SMAI_SEND_MA Use this action Manual Immediately

IL_IMPORT_JO
to set up an e-
B
mail notification
service that in-
forms you when
a cycle-level
scheduled im-
port job was
terminated be-
cause of block-
ing conflicts
that were de-
tected during
transport-re-
lated checks.

SMAI_SET_CAN Use this action Manual When saving x Of of the follow-

CELED
to withdraw the ing user sta-
cycle. tuses: Created,
Active
The cycle pro-
ceeds to phase
Withdrawn
(E0012) when
you save it.

If there are
open change
documents or
requests for
change, you
must create a
new cycle to
take over the
open items.

SMAI_SET_OPE Use this action Manual When saving x User status:

RATE
to start the ac- Created
tive phase of
the cycle.

The cycle pro-

ceeds to phase
Active (E0002)
when you save
it.

Change Control Management

Change Request Management PUBLIC 237
 Processing Processing Sets a User Scheduling Start Condi-
Action Name Use Mode Time Status Condition tion

SMAI_SET_RET Use this action Manual When saving x User status:

IRE
to close the cy- Active
cle.

If there are no
open change
documents or
open requests
for change and
you don’t cre-
ate a new cycle,
the closed cycle
proceeds to
phase
Completed
(E0008) when
you save it.

If there are
open change
documents or
requests for
change, you
must create a
new cycle to
take over the
open items.

SMAI_SET_KB_ For long text Automatic When saving

DELTA
search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

Related Information

Processing Continual Cycles [page 106]

Change Control Management

238 PUBLIC Change Request Management
4.3.7.11 PPF Actions for SMIM Phase Cycle

These are the PPF actions for SMIM (Phase Cycle)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMIM_CHECK_S This action au- Automatic When saving

TATUS_MN tomatically
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

SMIM_CHECK_S Use this action Manual When saving Contains errors

TATUS_AGAIN_ to start a re-
MN check of the
document con-
sistency ac-
cording user
status.

SMIM_CLOSE_M Use this action Manual When saving x User status:

N
to complete the Being
cycle. Completed

If there are no Error-free

open change
documents or
open requests
for change and
you don’t cre-
ate a new cycle,
the closed cycle
proceeds to
phase
Completed
(E0008) when
you save it.

If there are
open change
documents or
requests for
change, you
must create a
new cycle to
take over the
open items.

Change Control Management

Change Request Management PUBLIC 239
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMIM_IN_CANC Use this action Manual When saving

EL_MN
to withdraw the
cycle.

The cycle pro-

ceeds to status
Withdrawn
(E0011) when
you save it.

If there are
open change
documents or
requests for
change, you
must create a
new cycle to
take over the
open items.

SMIM_IN_GOLI After successful Manual When saving x User status:

FE_MN
integration test- Successfully
ing: Tested

Use this action Error-free

to switch the
cycle to phase
Go Live
(E0006) when
you save it.

SMIM_IN_PROC Use this action Manual When saving x User status:

ESS_MN to switch the
Created
cycle to phase
Scope (E0002) Error-free
when you save
it.

SMIM_IN_RELE Use this action Manual When saving x User status: In

ASE_MN to switch the
Development
cycle to phase
Build (E0004) Error-free
when you save
it.

Change Control Management

240 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMIM_SEND_MA Use this action Manual Immediately

IL_IMPORT_JO
to set up an e-
B
mail notification
service that in-
forms you when
a cycle-level
scheduled im-
port job was
terminated be-
cause of block-
ing conflicts
that were de-
tected during
transport-re-
lated checks.

SMIM_IN_TAKE Use this action Manual When saving x User status:

_MN
to close the cy- Imported into
cle. Production

The cycle pro- Error-free

ceeds to phase
Being
Completed
(E0007) when
you save it

SMIM_IN_TEST After successful Manual When saving x User status: To

_MN
development Be Tested
tests:
Error-free
Use this action
to switch the
cycle to phase
Test (E0005)
when you save
it.

SMIM_ONE_PHA Use this action Manual When saving x Not in the fol-
SE_BACK_MN
to move back lowing user sta-
one step. tuses: Created,
Being
The cycle re-
Completed,
turns to the
Completed,
previous phase
Withdrawn
when you save
it.

Change Control Management

Change Request Management PUBLIC 241
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMIM_OPEN_UP Use this action Manual

_BPCA
to start the
Business Proc-
ess Change An-
alyzer (BPCA).

Solution,
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

SMIM_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

Related Information

Processing Phase Cycles [page 108]

Change Control Management

242 PUBLIC Change Request Management
4.3.7.12 PPF Actions for SMRE Release Cycle

These are the PPF actions for SMRE (Release Cycle)

Processing Processing Sets a User Scheduling Start Condi-

Action name Use Mode Time Status Condition tion

SMRE_CHECK_S This action au- Automatic When saving

TATUS tomatically
checks the
document con-
sistency ac-
cording to user
status when
you save the
document.

SMRE_CHECK_S Use this action Manual When saving

TATUS_AGAIN to start a re-
check of the
document con-
sistency ac-
cording user
status.

SMRE_ONE_PHA Use this action Manual When saving x Not in the fol-
SE_BACK
to move back lowing user sta-
one step. tuses: Created,
Scope,
The cycle re-
Hypercare,
turns to the
Retired
previous phase
when you save
it.

SMRE_OPEN_UP Use this action Manual

_BPCA
to start the
Business Proc-
ess Change An-
alyzer (BPCA).

Solution,
branch, and
transaction ID
are copied from
the document,
and displayed in
the BPCA.

Change Control Management

Change Request Management PUBLIC 243
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMRE_SEND_MA Use this action Manual Immediately

IL_IMPORT_JO
to set up an e-
B
mail notification
service that in-
forms you when
a cycle-level
scheduled im-
port job was
terminated be-
cause of block-
ing conflicts
that were de-
tected during
transport-re-
lated checks.

SMRE_SET_KB_ For long text Automatic When saving

DELTA search using
TREX:

This action au-

tomatically sets
the Knowledge
Base delta up-
date when you
save the docu-
ment.

SMRE_SET_BUI Use this action Manual When saving x User Status:

to switch the
LD Scope
cycle to phase
Build (E0004)
when you save
it.

SMRE_SET_GOL After successful Manual When saving x User Status:

IFE integration test- Test
ing:

Use this action

to switch the
cycle to phase
Deploy (E0006)
when you save
it.

Change Control Management

244 PUBLIC Change Request Management
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMRE_SET_HYP Use this action Manual When saving x User Status:

ERCARE
to switch the Deploy
cycle to phase
Hypercare
(E0011) when
you save it.

You can trans-

fer any open
change docu-
ments or re-
quests for
change to a
successor cy-
cle.

SMRE_SET_OPE Use this action Manual When saving x User Status:

RATE to prepare the Created
completion of
the cycle.

The cycle pro-

ceeds to phase
Operate
(E0007) when
you save it.

SMRE_SET_RET Use this action Manual When saving x User Status:

IRE to complete the Operate
cycle.

The cycle pro-

ceeds to phase
Retired
(E0008) when
you save it.

You can trans-

fer any open
change docu-
ments or re-
quests for
change to a
successor cy-
cle.

Change Control Management

Change Request Management PUBLIC 245
 Processing Processing Sets a User Scheduling Start Condi-
Action name Use Mode Time Status Condition tion

SMRE_SET_SCO Use this action Manual When saving x User Status:

to switch the
PE Created
cycle to phase
Scope (E0002)
when you save
it.

SMRE_SET_TES After successful Manual When saving x User Status:

T development Build
tests:

Use this action

to switch the
cycle to phase
Test (E0005)
when you save
it.

Related Information

Processing Release Cycles [page 110]

4.3.7.13 Parameters for PPF Actions

Use

You can trigger Change Request Management actions directly via a PPF action in the WebClient UI. As a
prerequisite, enter the action ID of the PPF action as a container parameter in the PPF action, using the
implementation method HF_EXECUTE_TASK.

The parameters are assigned to action profiles in Customizing (transaction SPRO), under SAP Solution
Manager Capabilities (Optional) Change Control Management Transactions Actions Change Actions
and Conditions Define Action Profiles and Actions Processing Types .

Change Control Management

246 PUBLIC Change Request Management
Features

The following parameters are available:

Parameters Use

USER_STATUS Used in implementation HF_SET_STATUS: The user status to be set.

RESET_STATUS, value X If a consistency check fails, the system sets the status (phase) back. Parame-
ter is mainly used for continual cycles (transaction type SMAI).

Define this in Customizing (transaction SPRO), under SAP Solution

Manager Capabilities (Optional) Change Control Management Change

Request Management Framework Make Settings for Transaction Types

Specify Status Attributes .

ACTION ID Change Request Management action that is started manually with this PPF
action.

Only specified Change Request Management actions can be started using a

PPF action.

ACTION_ID, value NAV_SYS_WEB Navigate to the relevant system and log on in a separate window, depending
on the user status

ACTION_ID, value NAV_TASK_WEB Navigate to the task list, in a separate window

ACTION_ID, value NAV_BPCA Opens the Business Process Change Analyzer (BPCA) in a separate window,
to create a BPCA analysis

ACTION_ID, value APPRV_CO_WEB Opens the dialog window to approve critical objects

ACTION_ID, value ASSIGN_TRA ASSIGN_TRA: Opens the dialog window to assign transports

ASSIGNED_TRANSPORTS ASSIGNED_TRANSPORTS: PPF container element class for data transport

from the dialog window to assign transports to the Change Request Manage-
ment framework.

ACTION_ID, value DECOUPLE_TRA Decouples the transports marked in the Transport Management assignment
block

ACTION_ID, value DISTRIBUTE_W DISTRIBUTE_W: Opens the dialog window to distribute urgent changes

PROD_SYSTEMS PROD_SYSTEMS: PPF container element class. Contains the system data for
which a distributed urgent change is to be created.

ACTION_ID, value RETROFIT_WEB Starts the retrofit dialog window in SAP GUI

Change Control Management

Change Request Management PUBLIC 247
Parameters Use

MAIL_FORM_TEMPLATE Used in e-mail notification function.

DEFAULT_SENDER_EMAIL MAIL_FORM_TEMPLATE defines the e-mail template.

DEFAULT_SENDER_MAIL defines the e-mail sender

APPROVAL, value X Status change is triggered from the active Approvals assignment block. Only
relevant for action definition SMCR_APPROVAL_PROCEDURE_STATUS, and
used internally.

CREATE_TRANSPORT PPF container element class for dialog window to create transports. Contains
the data of created and existing transports.

PREDOC_STATUS Defines the status to which the transaction is to be set back, if a Change
Request Management consistency check fails in the new user status.

NOTIFICATION_SCENARIO, value 1 Request allowlist objects approval.

NOTIFICATION_SCENARIO, value 2 Approve allowlist object request.

NOTIFICATION_SCENARIO, value 3 Reject allowlist objects request.

NOTIFICATION_SCENARIO, value 4 Request critical objects approval.

NOTIFICATION_SCENARIO, value 5 Approve critical objects request.

NOTIFICATION_SCENARIO, value 6 Reject critical objects request.

NOTIFICATION_SCENARIO, value 7 Import error notification.

NOTIFICATION_SCENARIO, value 8 Change document status.

SET_IF_TEST_OK Not delivered by default.

If you use BAdI implementation AI_CRM_CM_TEST_EXECUTION, set this pa-

rameter to “X” for the PPF actions that change the status to Successfully
Tested.

Change Control Management

248 PUBLIC Change Request Management
4.3.8 Changing the Transaction Status with PPF Actions

You control the status changes in change transactions as well as change cycles using Post-Processing
Framework (PPF) actions.

Prerequisites

You have configured the action profile. For more information, see Customizing for SAP Solution Manager
(transaction SPRO) under Capabilities (Optional) Change Control Management Transactions Change
Actions and Conditions Define Action Profiles and Actions .

Context

Whenever a transaction changes its status (for example, to Tested Successfully), certain Change Request
Management actions must be carried out, such as the release of a transport request. The system performs
these actions either automatically, or a user starts them manually.

 Note

Change Request Management uses generic PPF actions, which you can adjust to your requirements. In
contrast to PPF actions, Change Request Management actions run in the PPF action (HF_SET_STATUS),
dependent from the user status. For more information on Change Request Management actions, see
the Customizing (transaction code SPRO) under SAP Solution Manager Capabilities (Optional)
Change Control Management Change Request Management Framework Actions in Change Request
Management .

You can only execute actions under specific conditions. Which actions are executable depends on the status of
the change transaction and the status of the respective change cycle.

You can link actions with calls of dialog boxes in the WebClient UI, in which the user can, for example, enter or
confirm data. The dialog boxes can be displayed before or after processing the actions. For more information
about configuring the dialog box framework, see the Customizing (transaction code SPRO) under SAP
Solution Manager Capabilities Change Control Management Implementation of Dialog Boxes in WebClient
UI .

 Note

You need knowledge of the WebClient UI and ABAP development to adjust the dialog box framework.

Change Control Management

Change Request Management PUBLIC 249
Procedure

1. In the change transaction or in the change cycle, switch to change mode and select Actions and an
available action.
2. Save the change transaction or cycle.

The system changes the status and displays it in the header data.
3. Go ahead in the change process.

Next Steps

On assignment block Scheduled Actions, you can display, execute, and optionally schedule actions.

Related Information

Processing Change Transactions [page 56]

Automatic and Manual Check [page 159]

4.3.9 Sending E-Mails

Use

You have various options of sending e-mails from change transactions.

Prerequisites

• The user master records of the sender and recipient contain e-mail addresses.
• The functions are set up in the SAP Solution Manager configuration.

Features

Creating Outbound E-Mails as Follow-Up Transactions

Via More Send E-Mail , you can create an e-mail and send it to a recipient. The e-mail is created as a
follow-on transaction to the change transaction. For more information, see Follow-Up Transactions [page 253].

Sending E-Mail Notifications

Change Control Management

250 PUBLIC Change Request Management
The system automatically sends an e-mail depending on the status of the change transaction, for example,
when a new request for change is created, the change manager is notified about it.

For more information, see E-Mail Notifications [page 286].

4.3.10 Processing Log

The processing log provides the transaction history of change transactions or IT requirements. You can see all
actions and status changes that you or another user carried out.

A log entry is created for each action and contains data such as the user name, action, time of execution, and
both the old and new status.

You can specify whether you want to display all processing steps, or only the executed actions, changed fields,
or other processing actions.

Configuration

1. In Customizing (transaction SPRO), go to:

• SAP Solution Manager Capabilities (Optional) Change Control Management Transactions
Processing Log (for change transactions)
• SAP Solution Manager Capabilities (Optional) Requirements Management Transactions
Processing Log (for requirements)
2. To define the kind of information (such as changed fields, actions, status change) that is recorded in the
processing log, assign the respective log types.
3. To specify the fields whose changes are recorded the processing log, define the change history based on
segment (assignment block).

4.3.11 Application Log

Use

The application log documents business and technical information that is relevant for processing a change
document or a change cycle.

Features

• Displays various activities, such as creation and release of transport requests, and supports navigation to
the related detail information

Change Control Management

Change Request Management PUBLIC 251
• Displays the status for activities, for example, that a transport request has been created
• Display activity type, such as program, job or transaction
• Displays who triggered the activity, for example, a user, transaction, or program
• Display start and end of an activity (date and time)
• Trigger of the activity, such as a task list or change document
• Integrates messages from the task list

4.3.12 Warnings and Errors in Change Transactions

The message bar displays status messages (green icon), warnings (yellow icon), and error messages (red
icon) for a change transaction. You must remove the cause of the error before you can process the change
transaction. Choose the message to see the long text of the error message.

Features

There are the following error types for change transactions:

• “Transaction is inconsistent”
There is at least one error message. The subsequent status cannot be set. You may have to perform an
action in the maintenance landscape (for example, release a task). The system checks the status again,
and the change document no longer contains any errors. If there’s no entry in the Action column, choose
Actions Recheck Correction .
• “Status reset by the system”
There are only warning messages. One message indicates that the current status was reset by the system
due to a possible error. The other warnings explain the error. Since no actual error exists, according to the
status set by the system, the subsequent activity can be performed.
• “Action cannot be performed in the current phase of the change cycle” (only relevant for change
documents)
There is at least one error message indicating that an action cannot be processed in the current phase of
the change cycle. The subsequent status cannot be set. Choose Actions Recheck Correction . The
system checks the current status of the change document and deletes the error message, if it determines
that the current status is consistent. The change document can then be processed, when the phase of the
change cycle has changed accordingly.
• “Unexpected technical exception triggered”
The message long text often provides additional information about the cause of the problem and how to
solve it. The application log in the task list provides additional information about errors caused by a task
that was executed incompletely or incorrectly.

The system sometimes displays an error because certain asynchronous processes have not yet been
completed, for example, starting an export. To check whether an action was completed successfully, check
the task list, by choosing it in the Related Transactions assignment block. If all processes in the task list have
been completed, go back to the change document and save it again. The system checks the status again and
the change document no longer contains errors.

Change Control Management

252 PUBLIC Change Request Management
Whenever the change transaction contains an error, the function Actions Recheck Correction is
available. The error message doesn’t always disappear, even if an error has been corrected (especially if you
used the task list to correct the error).

 Tip

If you cannot resolve an error, check the configuration prerequisites by running report
SOCM_CRM_SERVICE_CHECK.

Related Information

Changing the Transaction Status with PPF Actions [page 169]

Defined Actions for Continual Cycles [page 30]
Defined Actions for Phase Cycles [page 36]
Defined Actions for Release Cycles [page 45]

4.3.13 Creating Follow-Up Transactions

Follow-up transactions are new transactions, created from a message or a change transaction. Data is copied
from the original transaction to the new transaction, and the two transactions are linked.

Context

You can create various follow-up transactions, depending on the source transaction. You specify which follow-
up transactions are possible for each transaction type in Customizing.

You see previous transactions in the Related Transactions assignment block in each transaction.

Prerequisites

• You have configured the Customizing settings for copy control.

• The source transaction is error-free.

Procedure

You can create follow-up transactions from the search, or directly from an open transaction.

Change Control Management

Change Request Management PUBLIC 253
1. Choose Create Follow-Up Document.
The system displays the available follow-up transaction types.
2. Choose a transaction type.
3. Add information in the transaction, and save your data.

The Related Transactions assignment block shows the link between the source and target transactions.

Related Information

Copying Transactions [page 254]

4.3.14 Copying Transactions

To save time when you create a new transaction, you can copy an existing transaction (or template) that
contains the data you need.

Integration

In contrast to follow-up transactions, which are linked to the existing transaction, copies are not linked.

Prerequisites

You have specified valid combinations of source and target transactions, and the data to be copied, in the
following Customizing (transaction SPRO) activities:

Change Request Management:

• SAP Solution Manager Capabilities (Optional) Change Control Management Transactions Copy
Control Define Copy Control for Transaction Types
• SAP Solution Manager Capabilities (Optional) Change Control Management Change Request
Management Framework Make Settings for Change Transaction Types Copy Control Rules

IT Service Management:

SAP Solution Manager Capabilities (Optional) IT Service Management Create Follow-Up Document
Specify Transaction Type Copy Control and Specify Copy Control Mapping Rules.

Change Control Management

254 PUBLIC Change Request Management
Features

In Customizing, you can specify per transaction type which data you want to be copied from the source to the
target transaction. You enter the additional data directly in the transaction.

 Note

• The category is always copied from the source to the target transaction. If the source and target
transaction type categorization schema do not match, the system issues a warning.
• IT Service Management: By default, the system copies the existing SAP data (for example, System ID)
and SAP Notes, into the target transaction.

Activities

1. In an existing transaction, choose Copy.

You see the new transaction. It has the same transaction type as the source transaction, and contains the
data that was configured to be copied.
2. Add additional data, change and complete the transaction.
3. Save the transaction.

 Note

You can also decide to create a separate customer UI configuration for your customer transaction type by
selecting ChaRM: Copy CRM UI configuration.

Related Information

Creating Follow-Up Transactions [page 253]

4.3.15 Time Recording

Use

You can record the effort (the time spent on each message, IT requirement, or change document) that you
process as an employee or have already processed and confirmed.

You can specify your own activity types for effort recording.

You can analyze the effort in reporting.

Change Control Management

Change Request Management PUBLIC 255
Prerequisites

For the following functions, you must configure scenario-specific settings in SAP Solution Manager
configuration:

• You want to use your own activity types for effort recording.
• You want to be reminded about effort recording automatically when you save a message.

For more information, see Customizing for SAP Solution Manager, under SAP Solution Manager
Capabilities (Optional) IT Service Management Time Recording .

Features

You can record any number of times in a message and change them at any time.

 Note

If you have an employee role in SAP Solution Manager, you can only display and change times that you
recorded yourself.

If you have an administration role, you can also display all the times recorded by other processors and
record times for another person.

For more information, see the security guide for IT Service Management on SAP Help
Portal at https://help.sap.com/viewer/p/SAP_Solution_Manager <current release> Security
Application-Specific Security Guide Change Control and IT Service Management Scenarios .

You can record the time you spent on a change transaction or IT requirement. If your project is integrated with
SAP Portfolio and Project Management, the data is also transferred to the corresponding SAP Portfolio and
Project Management project task.

More Information

Recording Working Time

Time Recording from a Request for Change to a Project Management Task

4.3.16 Solution Documentation Assignment Block

The Solution Documentation assignment block contains references to Solution Documentation elements that
are assigned to the message, change transaction, business requirement, or IT requirement. Additionally, for
change documents, the changed Solution Documentation elements in the context of the present change
document are displayed.

Change Control Management

256 PUBLIC Change Request Management
Features

• You can refresh the view to update the assigned elements. You can update data in Solution Documentation
and directly show these updates in the Solution Documentation assignment block.
• You can manually assign Solution Documentation elements to a transaction. You can choose to add either
one single item, or multiple items at once.

 Note

In Change Request Management and Requirements Management, to assign Solution Documentation

elements, the change transaction or IT requirement must be in edit mode, and its current status
must allow assigning Solution Documentation elements. You can customize for each transaction type
whether assigning is possible.

A newly created IT requirement, request for change, or change document must have been saved for the
first time before you can assign Solution Documentation elements.

• You can view information about the status of assigned Solution Documentation elements.
• You can add and remove references to Solution Documentation elements.

 Note

If a change document has been created from the scope of a request for change or an IT requirement,
the Solution Documentation elements assigned to the request for change or IT requirement are
automatically also assigned to the change document. In the Assignment Type column of the change
document, such Solution Documentation elements have the status Automatic. Note that also these
“inherited” Solution Documentation elements can be removed.

• In Change Request Management, if a change document is assigned to a branch in which Change Control
is activated, you can use change documents to record changes in the assigned Solution Documentation
elements.
• If the connection of the Embedded Search with TREX or SAP HANA has been established, you can search
for Solution Documentation elements that are added to the Solution Documentation assignment block.
To establish the connection, open SAP Solution Manager Configuration (transaction SOLMAN_SETUP)
scenario Process Management and perform step Configure Embedded Search.

 Note

SAP Solution Manager 7.1 had the assignment blocks Documents and Projects and Solutions to display
documents, projects, and solutions that are assigned to change transactions.

When you upgrade from SAP Solution Manager 7.1 to 7.2, the contents of the assignment blocks are
migrated to the Solution Documentation assignment block of the change transaction wherever possible.
The assignment blocks can contain content that is referenced from different projects. Unless these projects
have been migrated, the referenced content cannot be migrated.

For more information about which functions used to be available in the assignment blocks, see
the application help for SAP Solution Manager 7.1 at http://help.sap.com/solutionmanager SAP
Solution Manager 7.1 Application Help <language> Change Control Management Change Request
Management Functions in Change Transactions Projects and Solutions and Documents.

Change Control Management

Change Request Management PUBLIC 257
Related Information

Solution Documentation
Using Scopes for Assigning Solution Documentation Elements [page 258]
Release Check for Solution Documentation Elements Assigned to a Change Document [page 260]
Status Information About Assigned Solution Documentation Elements [page 260]
Change Recording [page 259]

4.3.16.1 Using Scopes for Assigning Solution Documentation

Elements

The Solution Documentation scope specifies a relevant part of the complete Solution Documentation content.
You can use this scope to find and assign the correct Solution Documentation elements to ITSM transactions,
IT requirements, or change transactions.

When you assign a single element or multiple elements to a transaction, you can select a Solution
Documentation scope in the Search Criteria dialog. In the result list, select Solution Documentation elements
from this scope to assign them to the ITSM transaction, IT requirement, or change transaction.

In IT requirements or change transactions, you can use the following types of scope created in the Solution
Documentation:

• If the IT requirement or change transaction is assigned to a project, you can select a scope assigned to the
project.
• If the IT requirement or change transaction is not assigned to a project, or if the project does not have a
scope assigned, you can select any scope created in the Solution Documentation. You should use a scope
that is public.
• To view the complete Solution Documentation content, select Show All.

Related Information

Scope Binding for IT Requirements and Change Transactions [page 271]

Change Control Management

258 PUBLIC Change Request Management
4.3.16.2 Change Recording

You can use change documents to record changes in the assigned Solution Documentation elements. If change
control is active for a branch, Solution Documentation elements in this branch can only be changed using
change documents.

Use

On the Solution Documentation UI, you can select only those change documents for which you are entered as
a business partner and that don’t have a “final” status. When Solution Documentation elements are changed
using a change document, the change is recorded.

You activate (release) the change by setting a certain status for the change document.

Prerequisites

• The change document is assigned to a branch in which Change Control is activated.

• In the change document, your business partner is assigned to at least one business partner function.
• The change document has a status that allows adding references to Solution Documentation elements (for
details, expand the following table). The changed Solution Documentation elements can be activated into
the production branch with a defined change document status change.

Status Values That Activate Solution Documentation Elements

Transaction Type Status Value

Administrative Change (SMAD) Completed, Confirmed

General Change (SMCG) Confirmed

Standard Change (SMSG) Imported into Production

Urgent Change (SMHF) Imported into Production

Normal Change (SMMJ) Imported into Production

Git-enabled Change (SMGH) Deployed into Production

Defect Correction (SMTM) Imported into Production

 Caution

If changes in Solution Documentation elements are recorded in several change documents, and the
first of the change documents is set to a status that activates the changed Solution Documentation
elements, the system does not issue a warning that the elements are also assigned to other change
documents.

Change Control Management

Change Request Management PUBLIC 259
Related Information

Solution Documentation Assignment Block [page 256]

Status Information About Assigned Solution Documentation Elements [page 260]
Change Documents [page 26]
Withdrawing Change Documents with Solution Documentation Elements [page 112]
Release Check for Solution Documentation Elements Assigned to a Change Document [page 260]

4.3.16.3 Status Information About Assigned Solution

Documentation Elements

The following columns in the Solution Documentation assignment block indicate status information about the
assigned Solution Documentation elements:

• Assignment Type
The Assignment Type column indicates how the Solution Documentation elements have been assigned:
• Manual
Solution Documentation elements can be assigned manually to requests for change, IT requirements,
business requirements and change documents.
• Automatic
For change documents only, the Solution Documentation elements can also be recorded
automatically. They are assigned automatically to the change document because they have been
changed as a result of the change document.
• Change Status (for change documents only)
The Change Status column indicates the lifecycle status that the assigned Solution Documentation
elements have in the change document. An element can have one of the following status values:
• Changed - if the element has been changed by processing the change document
• Released - if the element has been released to the production branch by processing the change
document
• Deleted - if the element will be deleted from the production branch as a result of the change document
• Document Status
The Document Status column shows the status that assigned documents have in the Solution
Documentation.

4.3.16.4 Release Check for Solution Documentation

Elements Assigned to a Change Document

Use the Release Check to find out whether possible conflicts arise for the assigned Solution Documentation
elements when the change is activated (released).

The Release Check function in the Solution Documentation assignment block of a change transaction opens
the Release Changes view in Solution Documentation. This view lists the Solution Documentation elements
affected by the change, and, in the Release Check column, displays conflicts for the elements.

Change Control Management

260 PUBLIC Change Request Management
  Note

For custom transaction types, you must configure the Release Check function manually.

Related Information

Solution Documentation
Change Documents [page 26]
Configuring the Release Check for Custom Transaction Types [page 261]

4.3.16.4.1 Configuring the Release Check for Custom

Transaction Types

In the WebClient UI, in the Solution Documentation assignment block, you can use the Release Check function
to check whether possible conflicts arise for the assigned Solution Documentation elements when the change
is activated. For custom transaction types, the configuration of the Release Check function must be done
manually.

Context

For the default change transaction types SMMJ, SMHF, SMGH, SMAD, SMSG, SMCG, and SMTM, the
Release Check function is configured as UI element SMUD_RELEASE_CHK_BUTTON in the Customizing.
In the Customizing activity Configure Status-Dependent UI Element Control in the Implementation Guide
(IMG, transaction SPRO), under SAP Solution Manager Implementation Guide SAP Solution Manager
Capabilities (Optional) Change Request Management Framework , you can copy the entries for UI element
SMUD_RELEASE_CHK_BUTTON from the default transactions to your custom transactions.

Alternatively, you can create new entries for customized transactions with the following steps:

Procedure

1. Open the Customizing activity Configure Status-Dependent UI Element Control in the Implementation
Guide (IMG, transaction SPRO), under SAP Solution Manager Implementation Guide SAP Solution
Manager Capabilities (Optional) Change Request Management Framework .
2. To configure the Release Check UI element, select either the Solution Documentation assignment block or
a specific transaction type:

Change Control Management

Change Request Management PUBLIC 261
 • To configure by assignment block, under Assignment Blocks, select Solution Documentation, and
under UI Elements, select SMUD_RELEASE_CHK_BUTTON. Under Status-Dependent Control of UI
Elements, go to the entries for the transaction types for which you want to configure the UI element.
• To configure by transaction type, under Transaction Type, select the transaction. Under Status-
Dependent Control of UI Elements, go to the entries for the UI element SMUD_RELEASE_CHK_BUTTON.
3. Under Status-Dependent Control of UI Elements, create new entries for each user status for which you want
the settings to apply.
4. To activate the UI element for a user status, select Editable/Executable and Visible.
5. Save your settings.

Related Information

Change Documents [page 26]

Solution Documentation

4.3.17 Test Management Integration

You can create test cases based on the change transaction, and assign existing test plans and test packages.

Use

You can automatically create test plans based on the information related to a change transaction. Such a test
plan is automatically linked to the change transaction; it does not have to be assigned manually.

You can also assign existing test plans and test packages to change transactions to document and track tests
and to execute them directly. You assign test plans and test packages in the Test Management assignment
block.

Features

• Creation of test plans based on the associated Solution Documentation entries and based on a BPCA
analysis.
• Assignment of test plans and test packages from Test Workbench
If you have already assigned a change cycle, the system displays only the test plans and test packages that
belong to it. If you have not yet assigned a change cycle, you can only assign test packages.
You can add new assignments and change existing ones as long as the test for the change document has
not yet begun, that is, as long as the status allows it.
• Navigation to test execution
• Automatic status update after successful testing

Change Control Management

262 PUBLIC Change Request Management
• Display of test status in the status information system for test plans and test packages
To display the status information system and the test report, select a row containing a test plan or test
package and choose the desired function.
• Consistency check TWB_TEST_OK checks if a test plan is attached to the change document and
if the test status is OK. By default, this consistency check is customized for the normal change
(standard transaction type SMMJ). SAP delivers the standard Business Add-In (BAdI) implementation
AGS_CHARM_TWB_STATUS_CHECK, which performs the check. You can implement your own check
using BAdI BADI_TWB_CHECK (see Customizing under SAP Solution Manager Capabilities (Optional)
Change Control Management Business Add-Ins BAdI: Enhance Consistency Check for Test Plan
Status .

Activities

 Note

Due to the enhanced concept of the test workbench in SAP Solution Manager 7.2, the method for opening
the test packages has changed as follows:

• In SAP Solution Manager 7.1, the tester worklist was the same for any users assigned to the test
package. Here, you can navigate with the test package only. There is only one status for a test case in
a test package. Anybody can access it.
• In SAP Solution Manager 7.2, the tester worklist depends on the user who executes it. Each tester has
their own execution status (one status by the tester on the same test case / test package). When the
user navigates from the old test package display link to the worklist, the worklist is empty because the
user is not assigned to the mentioned test package.

Therefore, you use the test package analysis link with which any user can display the whole test package.
You can always access the details by choosing the corresponding test cases.

We recommend that you work with the new analytic report as follows:

1. Navigate to the analytic report: Test plan / test package test case analysis.
This is a more complete overview and anyone with display authorization can see it. Additionally, it is
possible to navigate to the details of the status if required.
2. From this list, if a status has been set and you have the necessary authorization, you can access its
details and the status maintenance UI to change it.

Automatic Test Plan and Test Package Creation

As prerequisite for automatic test plan and test package creation, a default test profile must have been defined.

Go to the Test Management assignment block and choose one of the following:

• To create a test plan and a test package based on the associated Solution Documentation elements, select
Add New Test Plan/Package from Solution Documentation .
• To create a test plan and a test package based on a BPCA analysis result, make sure that there is a recent
BPCA analysis and select Add New Test Plan/Package from BPCA result .

For more information, see SAP Note 3237802 .

Change Control Management

Change Request Management PUBLIC 263
Manual Test Item Assignment

1. To assign a test item to your change, go to the Test Management assignment block and choose Add
Existing Test Plans or Test Packages .
The system displays a search screen.
2. Use the available search criteria to find the test item to add to the change transaction.
3. Confirm your selection.
The system adds the test item to the assignment block.

Related Information

Test Plan Management

4.3.18 Assigning SAP Notes

You can link your change transaction, message, or IT requirement to SAP Notes in the SAP Notes assignment
block.

Features

• Add and remove SAP Notes

• Search for SAP Notes in various ways:
• SAP xSearch
• SAP Note Search
• SAP Note Search with Context
• Navigate to system recommendations and Note Assistant
• If you create a change transaction in the system recommendations, you can process it further in
the WebClient UI. The SAP Notes assignment block contains the SAP Notes selected in the system
recommendations.
• If you create a request for change from a message to which SAP Notes are already assigned, they are
automatically assigned to the change request. You can display the details, and delete notes.

Related Information

System Recommendations [page 658]

Creating Follow-Up Transactions [page 253]
Request for Change [page 24]

Change Control Management

264 PUBLIC Change Request Management
4.3.19 Using Checklists

You manage tasks for service requests, change transactions, and IT requirements from the Checklist
assignment block.

Use

You can create tasks for each category of service request or change transaction.

You can create workflow tasks so that the system can notify the processor.

The processors see any tasks that are assigned to them on their start page. If a support team is assigned, all
members of the support team see the task.

If configured, use decision-based checklists to adapt the workflow.

Prerequisites

• You have configured for checklists, including decision-based checklists, in Customizing (transaction SPRO)
under Customer Relationship Management Transactions Basic Settings Checklist Settings .
You can also enter the mandatory Customizing for using checklists in the following scenarios as follows:
• For IT Service Management, under SAP Solution Manager Capabilities (Optional) IT Service
Management Checklists .
• For Change Request Management, under SAP Solution Manager Capabilities (Optional) Change
Control Management Transactions Checklists
• For Requirements Management, under SAP Solution Manager Capabilities (Optional)
Requirements Management Transactions Checklists

• You have created rules for transactions, categories, and partner determination under Service Operations
Rules .
• You have personalized your display to show the Checklist assignment block.

Features

• The system shows all tasks required to process a service request, change transaction, or IT requirement.
• You can specify which tasks can be performed at the same time and which must be performed
consecutively. You can display the sequence graphically by choosing Display Process Flow.
• A support team member or support team can be assigned as partner.
• When a task is confirmed, the system releases the subsequent tasks.

Change Control Management

Change Request Management PUBLIC 265
• You can create further tasks to process a service request, change transaction, or IT requirement. You
can add these tasks to a service request, change transaction, or IT requirement and assign them to a
processor.

Activities

1. Set the tasks to in process and confirm them.

2. Open Check list step: Details to display any processing information specified in the configuration of the
SAP Solution Manager.
3. Specify deadlines and other processing information, and forward the task.
4. Confirm that a task is completed by setting its status to Completed.
5. If configured: Process the steps based on decisions you take that trigger different actions.

More Information

• Processing Service Requests

• Using Workflow Tasks
• For more information about configuring checklists, in the How to Guide Service Request Management, see
section Setup of Service Request Fulfillment, as referenced from the SAP Solution Manager Configuration,
IT Service Management scenario under Perform Optional Configuration Configure Service Catalog and
Request Configure Service Request Management .
• For more information about checklists in SAP Customer Relationship Management, see the SAP Library
for SAP Customer Relationship Management at http://help.sap.com/crm <current release>
Application Help Service Service Request Management Processing Service Requests Checklist

4.3.20 Opening the IT Calendar

To optimize your IT planning activities, you can display several Change Request Management and Quality Gate
Management objects in the IT calendar.

Use

You can see the following objects:

• Change cycle phases

• Change transactions
• QGM phases
• QGM Q-Gates and milestones

Change Control Management

266 PUBLIC Change Request Management
During planned downtimes, transports to the affected systems are not possible. This is because the system
availability check during the transport process also considers the system status as defined in WMM (Work
Mode Management).

Prerequisites

You have made the following settings in SAP Solution Manager Configuration (transaction SOLMAN_SETUP):

• You defined the display colors for your objects in the IT calendar.
• For change cycle phases and QGM phases, you specified for which system roles the entries are created in
the IT calendar.
• You specified a threshold for the grouping of similar objects. For example, you can specify that all requests
for change on a particular date are displayed as a group in the IT calendar, if their number exceeds 5.

 Note

Existing objects cannot be migrated to the IT calendar. Only after you have performed the Customizing for
the required objects, entries are created in the IT calendar every time you save an object.

You can initially load calendar entries into the IT calendar, and delete entries, if necessary. To do so, in
Customizing, choose SAP Solution Manager Capabilities (Optional) Change Control Management
Change Request Management Framework IT Calendar Integration .

Change Control Management

Change Request Management PUBLIC 267
Features

• The IT calendar is a tool in SAP Solution Manager that is used in various scenarios. You can display specific
events, according to event categories. For Change Request Management and Quality Gate Management,
the following event categories are displayed:

Object Event categories Navigation to IT Calendar Displayed contents

Change transaction Request for change, urgent • Via More Open IT Transactions are displayed
change, normal change, ad- Calendar . with their due dates. The
ministrative change, general system displays bars for the
• Change documents:
change, defect correction specific date (one day), and
From the Landscape
only for the productive sys-
assignment block. Only
tem.
the selected system is
displayed.

 Note
From urgent changes,
you can display the IT
calendar only from the
Landscape assignment
block.

Change cycle phases Phases assigned to the • Via More Open Phases are displayed with
change cycle, for example, IT Calendar . All sys- their start and end time
Created, Scope, Build, Test, tems are displayed, re- stamp, for the system roles
Go Live, Being Completed, gardless of the client. maintained in Customizing.
Completed
• From the Landscape
assignment block. Only
the selected system is
displayed.

QGM phases Scope, Build, Test, Deploy From the Calendar View tab Phases are displayed with
page their start and end dates,
for the system roles main-
tained in Customizing.

QGM Q-Gates and mile- For example, Start of From the Calendar View tab Displayed for a specific
stones project, Scope to Build, page (due) date.
Build to Test, Test to Deploy,
or Milestones

 Note

Events are the actual displayed events in the IT calendar, for example, a QGM milestone on a specific
date.

Change Control Management

268 PUBLIC Change Request Management
• You can display the IT calendar on the Technical Administration launchpad group. There, you have the
following options:
• From the displayed contents, you can navigate directly to the change transactions in the WebClient UI
or to the QGM objects.
• Under Categories, you can select which event categories are displayed. For example, you can only
display certain phases or change documents.
• The system displays details for each object and date. You can switch between a monthly, weekly, and
daily display mode.

More Information

IT Calendar

4.3.21 Project Management Integration

In the WebClient UI, you can assign IT requirements, requests for change, and change documents to projects
and you can use the scopes assigned to the project to assign Solution Documentation elements to the IT
requirements or change transactions.

Requirements management and Change Request Management are both integrated with Project Management:
If you are using Project Management to plan and manage projects in an IT environment, you use Change
Request Management to implement your plans. You can use a task-based integration or a header-based
integration:

• With the task-based integration you can do the following:

• Create IT requirements, requests for change or change documents from project tasks.
• Assign existing IT requirements or change transactions to tasks.
• Create tasks from requests for change or change documents to include smaller changes in your
project planning and monitoring in a maintenance scenario.
The task-based integration includes a data synchronization of the project tasks and the IT requirements or
change transactions.
For more information about the task-based integration, see Task-Based Integration with Business
Transactions (Implementation Scenario) and Task-Based Integration with Business Transactions
(Maintenance Scenario).
• Header-based integration means IT requirements or change transaction are assigned to the project
header, but not to specific project tasks.
The header-based integration has no data synchronization. For more information about the header-based
integration see Header-Based Integration with Business Transactions.

In the WebClient UI, in the Details assignment block, you can assign IT requirements or change transactions
to a project and, in the Solution Documentation assignment block, you can the use the scopes assigned to the
project to assign Solution Documentation elements to the IT requirements or change transactions.

Change Control Management

Change Request Management PUBLIC 269
Related Information

Project Management
Assigning IT Requirements or Change Transactions to Projects [page 270]
Task-Based Integration with Business Transactions (Implementation Scenario)
Task-Based Integration with Business Transactions (Maintenance Scenario)
Header-Based Integration with Business Transactions
Scope Binding for IT Requirements and Change Transactions [page 271]

4.3.21.1 Assigning IT Requirements or Change Transactions

to Projects

You can assign IT requirements, requests for change, or change documents to projects.

Prerequisites

• The project is a header-based IT project.

• The requirement, request for change, or change document is assigned to the same change cycle as the
project

Context

If you are using project management together with requirements management and Change Request
Management to plan software innovations or changes in projects, you can assign IT requirements, requests
for change, or change documents to projects.

Procedure

In the Details assignment block, under Project Planning, in the Project Name field, open the value help and
select a project.

Results

When you assign a requirement or change transaction to a project, information from the project, such as the
solution branch or the change cycle, is automatically assigned to the requirement or change transaction and
filled into the fields of the Details assignment block.

Change Control Management

270 PUBLIC Change Request Management
  Note

Once you have assigned a requirement or change transaction to a project, all follow-up documents are
automatically assigned to the same project.

Related Information

Scope Binding for IT Requirements and Change Transactions [page 271]

Header-Based Integration with Business Transactions

4.3.21.2 Scope Binding for IT Requirements and Change

Transactions

In the WebClient UI in the Solution Documentation assignment block, you can use scopes as selection criteria
when assigning Solution Documentation elements to an IT requirement or change transaction. Since a scope
specifies a relevant part of the complete Solution Documentation content, this preselection makes it easier to
find and assign the correct Solution Documentation elements. If you use a scope assigned to a project as a
selection criterion to assign a Solution Documentation element to an IT requirement or change transaction,
the IT requirement or change transaction will be restricted to this scope. You can then only assign Solution
Documentation elements from this scope to the IT requirement or change transaction.

Prerequisites:

• The scope is assigned to the project.

• Change control is enabled for the branch.
• The IT requirement or change transaction is assigned to the project.

After having assigned a Solution Documentation element from a scope, you can assign only elements from
this scope to the IT requirement or change transaction, and, in a change document, only elements from this
scope can be changed. The binding to the scope cannot be changed or removed and the scope can no longer
be deleted in the Solution Documentation as long as any Solution Documentation elements from the scope are
assigned to the transaction.

Related Information

Assigning IT Requirements or Change Transactions to Projects [page 270]

Scope
Using Scopes for Assigning Solution Documentation Elements [page 258]

Change Control Management

Change Request Management PUBLIC 271
4.3.22 Configuration Check for Change Cycles

You can check whether a change cycle is correctly configured with respect to Change Request Management.

Prerequisites

• You have configured your system for Change Request Management.

• You have created a change cycle.

Features

You can check the following:

• General configuration
• Scheduled background jobs
• Number ranges
• Piece list activation in Customizing
• TMS
• CRM service
The system checks whether the settings required for using business transactions have been configured
in Change Request Management. This includes the registration of proxy classes for the transaction types
used, the assignment of business partners to users, and so on.
• System overview
• Change cycle consistency

Activities

1. You can access the configuration check in the following ways:

• In the WebClient UI, choose the change cycle for which you want to run a configuration check. Then
choose More Check Cycle Document
• In the administration cockpit, on the Task Lists tab, choose the cycle type or Urgent Changes.
2. Select the cycle for which you want to run a configuration check.
3. Choose Check Configuration.
The check results are presented as a list of nodes, which you can expand for more details. Items with
configuration error are marked in red. To correct an error, open the corresponding long text and follow the
instructions.

Change Control Management

272 PUBLIC Change Request Management
Related Information

Configuring Change Request Management [page 473]

4.3.23 Creating Task Lists

Use

You can create task lists in the WebClient UI using a guided procedure. Task lists are linked to change cycles.
Depending on the cycle type, the following applies:

• Continual cycle: Each continual cycle has its own task list. You create each task list in the WebClient UI.
• Phase cycle: If you have created the cycle in the WebClient UI, it has its own task list. If the cycle is created
as a successor cycle, the task list is continued and you do not have to create a new one.
• Release cycle: For all release cycles that have the same change control landscape and branch, the same
task list is used. When you put a release cycle in the Hypercare phase, the following release cycle takes over
all unfinished change documents and continue the task list.
Only if there is no existing task list for any predecessor or successor release cycle with the same
combination of change control landscape and branch, you must create a task list in the WebClient UI.

Prerequisites

You have created a change cycle. Depending on the cycle type, the system starts the guided procedure
automatically when the following status is set:

• Continual cycle: Set the phase to Active

• Phase cycle: Set the phase to Scope
• Release cycle: Set the phase to Scope

 Note

If there already is a task list for any successor or predecessor release cycle with the same combination
of branch and change control landscape as the current one, the system links it automatically to the
current release cycle and the guided procedure is not displayed.

Process

1. The system checks whether the prerequisites for creating a task list are fulfilled. It checks for errors, for
the RFC connection, for number ranges, and for transport management settings. The system behavior is
as follows:
• If the status is green for all lines, the system has not found any errors. You can continue to the next
step.

Change Control Management

Change Request Management PUBLIC 273
 • If the status is yellow, the system has found errors but they do not interfere with the task list
generation. For example, an RFC error has occurred or the system is not relevant for the transport
track. You can continue to the next step.
• If the status is red, the system has found errors that interfere with the task list generation. You have to
resolve the errors before you can continue to the next step.
2. The Define Scope step contains general information about the cycle. If required, you can activate the
central Change and Transport System (central CTS). You can add a retrofit system and additional
production systems that are not on the transport tracks below.
When switching to this step, you can display detailed information on the transport tracks overview. In the
transport track overview you can select the desired managed landscape for your cycle. Choose the long
text of the displayed message.

 Note

If your system landscape has changed and you recreate your task list, the system does not allow you to
remove the central CTS enablement flag if transport requests have been created already. This means
that tasks lists that were enabled for central CTS before must remain enabled. If it was not enabled, you
cannot enable it.

Any clusters that were already assigned to the existing systems cannot be changed. However, you can
assign additional systems or remove existing system to existing clusters.

In this step, you choose a task list variant that determines the import strategy of the task list.
3. The Check Cluster Assignment step is relevant only for central CTS-related cycles. It is skipped
automatically for other cycles.
The system first tries to automatically assign a suitable cluster, based on the transport track. If there is no
cluster that covers all systems in the transport track, you must assign the cluster manually to the systems
in the transport track, starting from the source system. The clusters are grouped by transport track
header, represented by the full name of the source system, and systems in the transport track. You can
reset the cluster pre-assignment and select another cluster. You can also restore the default assignment.
4. Choose the Complete step.

Result

The task list is created and all information is displayed, including the cluster assignment overview.

From the Related Transactions assignment block, you can navigate to the task list tab in the administration
cockpit. Here, you can perform any required administrative tasks for the task list.

 Note

The change cycle type determines what happens to the task list when the assigned change cycle is closed:

• Continual cycle: When the related change cycle is closed, the system closes the task list.
• Phase cycle: When the predecessor cycle is closed and there are open change documents or open
transport requests, the task list is reused by the successor cycle. If you do not create a successor cycle,
the task list is closed. However, if there are open change documents or open transport requests, there
is no option to close the task list.
• Release cycle: The task list remains active so that you can plan new releases and reuse the task list for
the release cycle.

Change Control Management

274 PUBLIC Change Request Management
Related Information

Change Cycles [page 28]

Task List [page 53]
Central Change and Transport System [page 400]
Redefining a Landscape [page 275]
Task List Variants [page 55]
Managing the Task List [page 294]
Closing Task Lists [page 278]

4.3.24 Redefining a Landscape

Use

If your system landscape is modified, you can recreate the task list structure based on these changes. There
are two use cases:

• A change control landscape is changed in the solution landscape (transaction SLAN) and the landscape
management database (transaction LMDB). For example, a logical component group was added or a
system was removed from a logical component group.
• You want to add or remove systems to / from transport tracks.

 Note

Retrofit systems cannot be added or removed in the overview. Edit them in the Retrofit Systems table.

Prerequisites

• The change cycle is not in final status.

• An active task list is assigned to the change cycle.
• You have sufficient authorization to create a task list.

Features

• When calling up a change cycle, the system automatically checks whether the assigned change control
landscape has changed and whether the change affects the landscape assigned to the cycle. If this is the
case, the system displays a warning message.
By default, the following Business Add-Ins (BAdIs) are used to provide a notification to Change Request
Management when the solution landscape or the landscape management database are changed. The
system determines which cycles are affected by the change. If you want to enhance this system behavior,
you can use these BAdIs.

Change Control Management

Change Request Management PUBLIC 275
 • BADI_SLANE_ADMIN_NOTIFICATION: Get notification when a logical component group is added/
removed to/from a change control landscape
• BADI_SMUDE_LC_NOTIFICATION: Get notification when a logical component is added/removed to/
from a logical component group
• LMDB_NOTIF_BADI_LC: Get notification when a system is added/removed to/from a logical
component
• You can change the transport tracks in the transport tracks overview and then recreate the task list based
on your changed landscape.

Activities

Recreating a Task List Based on a Landscape Change

1. You call up a change cycle in edit mode in the WebClient UI.

2. The system automatically checks whether the assigned change control landscape has changed and
whether the change affects the change cycle.
3. If it has changed and affects the cycle, the system displays a warning message, asking you to redefine the
landscape.
4. You choose More Redefine Landscape .
5. The system automatically regenerates the task list structure, based on the new landscape. After
redefinition, all the transport tracks in the task list are unlocked by default. Any related urgent change
task lists are also updated during this process in the background.

Redefining a Landscape in the WebClient UI

1. In the change cycle, you choose More Redefine Landscape .

2. When you switch to the Define Scope phase, the system displays a message and a long text explaining the
functions in the transport tracks overview.
3. You make the required changes, for example, you can add or remove a system in the transport track
overview, or change the task list variant.
If you want to remove single productive systems from a track (scenario 1) or a whole track (scenario 2),
certain conditions must be met.

Change Control Management

276 PUBLIC Change Request Management
 Scenario 1: Scenario 2:

You keep the track but want to remove one of several You want to remove whole track(s), that is: the develop-
production systems. ment system or the exclusive production system.

These checks are performed: To remove the exclusive production system, all the checks
• There is no open change document to which the of scenario 1 are performed.
configuration item of the production system to be To remove the development system, the following checks
deleted is assigned. (Only for Change Request Man- are performed:
agement)
• There is no open transport request from that track.
• There is no scope item of open RfC to which the
• There is no open change document which contains
configuration item of the production system to be
the transport request from that track.
deleted is assigned. (Only for Change Request Man-
• If the development system to be deleted is assigned
agement) to the “Development <-> Retrofit” relationship, there
• There is no active H task list which contains the pro- is no unfinished retrofit transport request.
duction system to be deleted. (Only for Change Re-
quest Management)
• If the import buffer of the production systems to be
deleted is still reachable, there is no “waiting for im-
port” transport requests from the relevant track in
the buffer.

If the checks are not passed, the redefinition of the system landscape is stopped. Detailed information is
logged in SLG1 log /TMWFLOW/CMSV TRACK_LANDSCAPE.
Exceptions
• If you remove inactive or disused systems, you get a warning but you can continue the redefinition.
• If you remove systems that have been deleted from the LMDB, the checks are skipped and you can
continue the redefinition.

 Note

Consider the following before changing the task list variant:

If the task list variant to which you want to change has a different setting for "Deletion of Import Buffer"
option compared to the previously used task list variant, make sure that all the normal changes and
urgent changes in the change cycle are completed before you change to the new task list variant.
Otherwise the import behavior for these change documents can be unpredictable after the task list
variant has been changed.

4. Choose Confirm to save your redefined landscape.

If you removed a development or productive system, the following actions are performed:
• In SLG1 log /TMWFLOW/CMSV TRACK_LANDSCAPE, information is logged about the systems that
have been removed.
• For a removed development system, the CTS project is changed to locked.
• For a removed development system, the “Development <-> Retrofit” relationship is deleted.
• For a removed production system, the relevant CSOL lock entries are deleted.
5. The system automatically updates the task list structure and the contents of the Landscape assignment
block. After redefinition, all the transport tracks in the task list are unlocked by default. Any related urgent
change task lists are also updated during this process in the background.

Change Control Management

Change Request Management PUBLIC 277
4.3.25 Closing Task Lists

Use

Depending on the assigned change cycle, task lists are closed or continued.

Features

• Continual cycle: Each continual cycle has a dedicated task list. Once the cycle is closed, the task list is
closed as well. If there are open change documents or transport requests for the cycle, the system displays
an error message and the cycle cannot be completed. The change documents and transport requests
must be finished before the cycle is completed.
• Phase cycle: Each phase cycle has a dedicated task list. The task list is closed once the cycle has been
closed, all change documents have been completed, and the transport requests have been imported into
the production system. If there are any open change documents or transport requests, they are assigned
to the next phase cycle and the task list is continued.
When a phase cycle is completed, you can create a new successor cycle if all change documents have been
completed and all transport requests have been imported into the production system. In this case, the task
list is also continued, that is, the old cycle is completed and the new cycle continues with the old task list.
• Release cycle: For all release cycles that have the same change control landscape and branch, the same
task list is used. When you put a release cycle in the “Hypercare” phase, the following release cycle takes
over all unfinished change documents and continues the task list.

More Information

Continual Cycle [page 29]

Phase Cycle [page 35]

Release Cycle [page 44]

4.3.26 Editing Job Scheduling Change Documents

You want to edit a request to change or create job documentation using Change Request Management.

Prerequisites

• The change manager has approved a request for change based on a job request, and created a change
document.

Change Control Management

278 PUBLIC Change Request Management
• The Job Management assignment block is configured in the WebClient UI.
• You have opened the job request in change mode.

Features

You can edit change documents for job scheduling in the Job Management assignment block of the WebClient
UI.

You can use this assignment block for all change document types.

By default, the system uses the change document type Administrative Change for job scheduling.

Activities

You find the relevant administrative change in one of the following ways:

In the WebClient UI

1. Choose Change Request Management Change Document .

2. Select the transaction type, for example, SMAD for administrative changes.

In the Job Management launchpad group

1. Choose the Job Requests.

Your personal object worklist (POWL) is displayed. For more information, see Requesting Jobs.
2. Click an entry in the CRM Document column. The system starts the WebClient UI.

Related Information

Change Documents [page 26]

Change Control Management in the WebClient UI [page 15]

4.4 Advanced Features of Change Request Management

With the advanced options, administrators and configuration users can adjust Change Request Management to
your company's needs.

Change Control Management

Change Request Management PUBLIC 279
4.4.1 Adapting the WebClient UI: Personalization and
Configuration

Administrators can set up the WebClient UI according to the company's needs (configuration). In addition to
this, end users can then adapt the WebClient UI according to their needs (personalization).

 Note

System administrators can restrict the options for end users to make specific settings.

The WebClient UI basically consists of three main areas: header, navigation bar and work area.

Personalization

You can use the following Personalization settings:

• General Personalization Settings - for example, to maintain personal data or change the password.
• Overview Page personalization - to arrange the assignment blocks.
• Table View personalization - for example, to define the number and size of table columns.

With Saved Searches, you can save search patterns that you want to use frequently as template with a unique
name.

Configuration

Administrators have the following Configuration options to adjust the WebClient UI according to their
company's needs:

• Business Role (customizing activity Define Business Role)

• Navigation Bar Profile Customizing (customizing activity Define Navigation Bar Profile)
• UI Configuration Tool and Application Enhancement Tool (AET) (WebClient UI configuration mode )
• Skin Workbench (customizing activity Access Skin Workbench)
• Component Workbench (customizing activity Access UI Component Workbench)
• Component Enhancements
• Redefine Methods

For more information, see SAP Solution Manager Configuration (SOLMAN_SETUP) under Change Control
Management Change Request Management Configure User Interface .

Related Information

Change Control Management in the WebClient UI [page 15]

Change Control Management

280 PUBLIC Change Request Management
WebClient UI Framework
User Interface Personalization

4.4.2 Rule Policies

Use

Rule policies invoke specified actions automatically, when their conditions are satisfied. Rule policies are a set
of rules, which are a combination of conditions and actions. Depending on the conditions, the system performs
specified actions.

Prerequisites

• You have defined contexts in Customizing, under SAP Customer Relationship Management E-Mail
Response Management Define Repository .
• Approval procedures:
• In Customizing, under SAP Solution Manager Capabilities Change Request Management
Transactions Approvals Define Approval Settings , you have specified whether the system is to
determine the approval procedure by the rule modeler or by default.
• You have created two rules for approval management. For more information, see the Customizing
documentation, under SAP Solution Manager Capabilities Change Request Management
Transactions Approvals Create Approval Procedure Rules .
• If you want to use the rule policy to dispatch requests for change or service requests, to the appropriate
persons, you have assigned the dispatching service manager profile to the transaction types, under
SAP Customer Relationship Management Transactions Additional Settings Assign Dispatching Rule
Profiles to Transaction Types .

Features

• You can define rules for processing service requests or requests for change, which specify who performs
which processing step, in which order.
• In Change Request Management, you can specify rules for approval procedures.
• You can display and edit rule policies in the WebClient UI, under Service Operations Rule Policies . In
the search screen, if you choose a context, the related rule polices are displayed:
• “Approval Management” displays the rule policies for approval procedures in change request
management.
• “Service Request Management” displays the IT Service Management rule policies.
• “Checklist Determination” displays the rule policies for checklists.

Change Control Management

Change Request Management PUBLIC 281
• You can use rule policies to specify which checklists are used, and which processors the system assigns to
the checklist steps. For more information, see Checklists [page 265].
• If you choose More Dispatch in a request for change or a service request, the system finds the next
available service team, according to the rule policies.

More Information

For information on the prerequisites for using rule policies, and how to create, edit and enhance rule policies,
see SAP Help Portal for SAP CRM (http://help.sap.com/crm) and search for “Rule Modeler”.

4.4.3 Approval Procedures

Use

Approval procedures control the approval process for requests for change. In an organization, certain
processes must be approved by the persons responsible, before they can be performed. For example, a request
for change must be approved before an urgent or normal change can be made.

Approval procedures can be edited manually and integrated into the workflow. For all information relevant to
the approval of a request for change, see the Approvals assignment block of the request for change.

 Note

You can also create approval procedures for change documents. This is an optional scenario. For
more information, see the Customizing (transaction SPRO) under SAP Solution Manager Capabilities
(Optional) Change Control Management Transactions Approvals Approval Settings Overview for
Change Documents .

Integration

You can control approval procedures using rule policies.

Prerequisites

The standard authorization object CRM_APPRVL has been assigned to your user.

In Customizing (transaction SPRO), you have maintained the Approval Settings in SAP Solution Manager
Capabilities (Optional) Change Control Management Transactions Approvals .

Change Control Management

282 PUBLIC Change Request Management
Features

• In the header data of the request for change, you assign the approval procedure. By default, the approval
procedure CR Approval Procedure is proposed.
• The following functions are available in the Approvals assignment block:
• You can monitor the approval steps and their details. For example, you can see which business partner
approved the step, and when.
• The change manager is entered as the approver, by default. You can add other approvers.
• The participants in the request for change enter their approval activities, with the options Approved,
Not Relevant, and Rejected. The approvers can add comments to the activity, for example to explain a
rejection.
• You can add or remove approval steps and approvers until the status of the request for change is set to
Approved.
• In the WebClient UI, you see the requests for change awaiting approval that are assigned to you.
• You can use workflow functions for the request for change approval process, so that approvers are
informed when requests for change are to be approved. You can choose between two workflow templates:
• CRM_RFC_APRV provides plain text e-mail notifications
• CRM_RFC_APPR allows the use of personalized HTML e-mail (mail form) notifications. Create your mail
form with dynamic attributes using the Approval Proc Attributes option from the Attribute Context in a
mail form and choose Attribute to add specific standard text attributes. For parallel approval steps, this
template notifies each approver only once.

Enhanced Approval Procedure Functions

The following features are available if you have activated the enhanced approval procedure functions in
Customizing (transaction SPRO), under SAP Solution Manager Capabilities (Optional) Change Control
Management Transactions Approvals Activate Enhanced Approval Procedure Functions and Activate
Workflow Feature for Enhance Approval Procedure:

• Restrict the approval procedure functions using the authorization object SM_APP_AP. For more
information, refer to Customizing documentation.
By default, the Change Request Management roles contain the following authorizations:

Role Transaction Type Authorized Activities

SAP_CM_SMAN_ADMINISTRATOR SMCR, SMCT Change, Enter, Include, Assign, Accept, Adminis-

ter, Remove

SAP_CM_SMAN_CHANGE_MAN- SMCR Change, Enter, Include, Assign, Accept, Remove

AGER
SMCT Change, Enter, Include, Assign, Remove

SAP_CM_SMAN_OPERATOR SMCR Accept (inactive)

SAP_CM_SMAN_DEVELOPER SMCR Accept (inactive)

SAP_CM_SMAN_TESTER SMCR Accept (inactive)

• You can designate a substitute, who can also approve or reject your requests for change, for example,
while you are out of the office. In the WebClient UI, select Maintain Substitute and choose the business

Change Control Management

Change Request Management PUBLIC 283
 partner who is your substitute. Your substitute’s user needs authorization object SM_APP_AP with activity
Accept for the specific transaction types.
The system sends a workflow item to the original approver and to the assigned substitute.
• You can assign an approval group to approval steps. Only one group member needs to approve the
request.
To do this, you must have created a business partner group of type “Organization” in the organizational
model (transaction PPOMA_CRM), and assigned the business partners which belong to the business partner
organization.
The system sends a workflow item to the members of the organization and to any assigned substitutes.
• If a business partner is not authorized to approve a request for change, the relevant fields and buttons (for
example, Delete and Add) in the Approvals assignment block are inactive.

Activities

1. A service employee creates a request for change and the change manager classifies it, for example, as a
normal change.
2. The change manager checks the request and releases it for approval. The request for change has the
status Awaiting Approval, so the system starts the approval procedure.
3. The system sends a notification to the assigned approver and to any assigned substitutes.
4. When all approval steps have been completed, the request for change proceeds to status Approved, and
the associated change documents are created.

 Note

For more information, see Customizing (transaction SPRO) documentation under SAP Solution Manager
Capabilities (Optional) Change Control Management Transactions Approvals Approval Settings for
Requests For Change and Approval Settings Overview for Change Documents.

Related Information

Rule Policies [page 281]

Substitution [page 285]
Processing Requests for Change [page 56]
Change Documents [page 26]

Change Control Management

284 PUBLIC Change Request Management
4.4.3.1 Substitution

Use

As an end user or processor, you can assign substitutes as follows:

• Assign a colleague as your substitute, for example, when you are on vacation or on a business trip.
• Assign yourself as a substitute for one or more colleagues, for example, when they are on sick leave.

On the Home screen, in the My Messages screen area, the substitute can see all the messages (incidents,
service requests, requests for change, and change documents) for the colleagues that they substitute. For
example, messages assigned to, or reported by, the colleagues are displayed.

Prerequisites

• You are authorized to assign substitutes.

• You and your substitutes belong to the same organizational unit.
• For Change Request Management, the following additional prerequisites apply:
• You have activated the enhanced approval procedure functions in Customizing under
SAP Solution Manager Capabilities Change Request Management Transactions Approvals
Activate Enhanced Approval Procedure Functions .
• You are authorized to approve and reject approval steps.
• You have taken SAP Note 1256661 into account.

Features

• Manage substitutes from the My Messages screen area.

• In requests for change, you can assign substitutes by choosing More Manage Substitutes .
• Display and edit messages for the substitutes.
• The substitution relationships are also displayed in the Employee screen, Relationships assignment block.
The Replaces relationship shows the business partners that the substitute replaces. Is Replaced By shows
the business partners of the substitutes.
• In Change Request Management, you can approve requests for change in which you substitute business
partners who have been assigned to approval steps.

Activities

• Assign a business partner.

• Specify the substitution period.

Change Control Management

Change Request Management PUBLIC 285
• Deassign a substitute.

More Information

Approval Procedures [page 282]

4.4.3.2 Change Request Management Tasks in the My Inbox

SAP Fiori App

Change Request Management supports the My Inbox SAP Fiori app to handle multiple on-premise backend
systems

You can use the following Change Request Management tasks in the My Inbox SAP Fiori app:

• Change Request Mgmt Urgent Change Approval

Approve the import of urgent changes into the production system or reset the change document to the
status In Development.
• Change Request Mgmt Preliminary Import Approval
Approve the preliminary import of normal changes or change the status of the change document
• Change Request Mgmt Critical Object Approval
Approve or reject the critical objects in the transport requests of change documents
• Change Request Mgmt Allowlist Object Approval
Approve the allowlist objects in the transport requests of a change document
• Change Request Mgmt RfC Approval
Approve or reject requests for change
• Change Request Mgmt Git-enabled Change Approval
Approve the deployment of Git-enabled changes into the production systems

To use this function, make sure that the My Inbox SAP Fiori app has been installed and set up.

Then set up and activate the Change Request Management tasks in the SAP Solution Manager Configuration
(transaction SOLMAN_SETUP) under Change Request Management Integrate Additional Functions Set Up
My Inbox SAP Fiori App . For more information, see 2590554

4.4.4 E-Mail Notifications

You can set up your system to send e-mails to users involved in the change request management process
whenever they must perform a task with regard to a change transaction.

The system uses PPF actions to send the e-mail depending on the status of the change transaction. For
example, when a new request for change is created, the change manager gets a notification.

Change Control Management

286 PUBLIC Change Request Management
Prerequisites

You have set up the e-mail notifications in the SAP Solution Manager Configuration (transaction
SOLMAN_SETUP), under Change Request Management Define Change Process Set up E-Mail
Notifications .

If you want to use a customized e-mail content for the e-mail notifications, you can configure and use mail
forms. You can use the attribute context CHARM_ATTRIBUTES, which contains attributes specific to Change
Request Management, such as “Change Manager”, “Change Cycle ID”, “Change Cycle Phase”, or “Branch
Description” with the mail forms. You can also implement the BAdI AI_CM_MAIL_ATTRBUTRE_BADI to create
your own attribute context for the mail forms.

Alternatively, you can implement the BAdI AI_CM_MAIL_TEMPL_ENHANCE_BADI to customize your own
e-mail template. By implementing this BAdI, you can define the following:

• E-mail text
• E-mail subject line
• E-mail recipient address
• E-mail sender address
• E-mail attachment

Features

• You can use customized e-mail content or the default e-mail templates included in the standard delivery for
your e-mail notifications.
• The e-mail recipient is defined by the business partner function in the change transaction. If no business
partner has been entered for the particular business partner function, no e-mail is sent.
• For a particular event in a change transaction, several e-mails can be sent to business partners of different
business partner functions, but each business partner receives only one e-mail.
• By default, e-mail notifications are triggered by a new status in the change transaction.

Statuses That Trigger E-mail Notifications

Change Transaction Status changes to Recipient

Request for Change Created Change manager (if already entered in the change
(SMCR) transaction)

Approved Change manager

Confirmed Requester

Rejected Requester

Normal Change Created Developer (if already entered in the change transac-
(SMMJ) tion)

Change Control Management

Change Request Management PUBLIC 287
 Change Transaction Status changes to Recipient

To Be Tested Tester

Successfully Tested Change manager

Preliminary Import Requested Change manager

Testing for Preliminary Import Tester

Tested for Production Import Change manager

Authorized for Import IT operator

Urgent change Created Developer (if already entered in the change transac-
(SMHF) tion)

To Be Tested Tester

Successfully Tested Change manager

Authorized for Production IT operator

Confirmed Change manager

Git-enabled change Created Developer (if already entered in the change transac-
(SMGH) tion)

To Be Tested Tester

Successfully Tested Change manager

Authorized for Production IT operator

Administrative Created IT operator (if already entered in the change transac-

change (SMAD) tion)

Completed Change manager

Defect correction Created Developer (if already entered in the change transac-
(SMTM) tion)

To Be Retested Tester

Imported into Production Change manager

General change Created Developer (if already entered in the change transac-
(SMCG) tion)

To Be Tested Tester

To Be Documented Developer

Change Control Management

288 PUBLIC Change Request Management
 Change Transaction Status changes to Recipient

Change Analysis Change manager

Failed Developer

Canceled Change manager

 Note

• The system does not send e-mail notifications to business partners used in several partner functions in
a change transaction. If you want the system to send e-mails anyway, refer to SAP Note 621183 .
• In a normal change, when the tester changes the status Successfully Tested to Preliminary Import
Requested, and the system changes the status to Testing for Preliminary Import, no e-mail is sent to the
tester, unless the Business Add-In Partner-Dependent Actions has been deactivated.
For more information, see SAP Note 621183 and the Business Add-In documentation in
Customizing (SPRO) under Customer Relationship Management Basic Functions Actions
Actions in Transaction Business Add-Ins BAdI: Partner-Dependent Actions .

 Note

If the system does not send any e-mail notifications although you have made the required settings, contact
your system administrator.

More Information

SAP Help Portal at http://help.sap.com/crm <SAP CRM 7.0 and above> Application Help Marketing
Campaign Management Personalized Mail .

Related Information

PPF Actions in Change Request Management [page 168]

4.4.5 Multilevel Categorization

You can use categories to classify requests for change and change documents on up to 10 levels with one or
more categorization blocks.

In the WebClient UI, you see the categories of a change transaction in assignment block Details, under
Category.

Change Control Management

Change Request Management PUBLIC 289
  Note

In the standard delivery, only one category block is available.

Prerequisites

You have defined your categorization schema and other settings in SAP Solution Manager Configuration
(SOLMAN_SETUP) under Change Control Management Change Request Management Define Change
Process Maintain Multilevel Categorization .

Features

Multilevel categorization integrates functions such as the following:

• Auto Complete fills out predefined template data, for example, business partners, status, priority, or text
information.
• Category-based item determination
• Search for related problems, knowledge articles, and requests for change
• If you use the Business Rule Framework (BRF+), multilevel categorization can determine business partners
in partner functions.

The displayed categories depend on the targets in the statistical evaluation of the change transactions, and on
your system configuration.

 Note

For more information, see the Application Help for SAP Customer Relationship Management, under
Multilevel Categorization.

Related Information

Functions in Change Transactions [page 113]

Change Control Management

290 PUBLIC Change Request Management
4.4.6 Administration Cockpit for Change Request
Management

The administration cockpit provides a central entry point to all administrative activities for Change Control
Management.

Use

Depending on business role, the following tab pages can be displayed or edited:

• Task Lists: You see the details of task lists and execute operational and background activities for
distributing software in your system landscape - for example, handling change cycles, task lists, and import
scheduling.
• Landscape Overview: You see information about the managed systems contained in the logical component
groups that are connected to Change Request Management, via the solution landscape (transaction SLAN)
or the change control landscape assignment. Each managed system in the logical component groups is
listed along with the communication systems.
• Critical Objects: You can define and edit critical transport objects. You can activate and deactivate the
modification check.
• Allowlist Objects: You can add the objects that are allowed to be saved to a transport request of a standard
change to an allowlist.
• Cross-System Object Lock and Downgrade Protection: You can manage cross-system object lock entries.
You can display lock entries according to defined criteria, remove them or register lock entries for
transport requests that are managed by Change Request Management.
• Cross-Reference Check: You can activate, deactivate and configure the cross-reference check, which
detects inconsistencies for objects that are referenced in transport requests.
• Transport Analysis: You can analyze the transport requests in your landscape in different views.
• Search: You can search for various objects based on your search criteria. You can also do a full-text search.
You can activate and deactivate object reporting.
Depending on the type you selected in the Search In field, the system displays change transactions,
transport objects, or transport requests as the search results.

 Note

If you have selected the criterion Transport Objects – Change Request Mgmt, the search can detect
only ABAP-based objects. If you use a SAP HANA database system, and the communication system is
the same as the SAP Solution Manager system, you can also search for SAP HANA database objects.

Apart from that, non-ABAP objects and transports containing those objects are not supported.

The link in the ID column leads directly to the transactions in the WebClient UI. If you have searched for
transport objects or transport requests, you can navigate from the result list to the change transaction to
which the particular transport request belongs.
For more information, see Change Request Management Reporting [page 476].
• Scheduled Import Jobs: You get an overview of the scheduled import jobs. You can filter the background
jobs scheduled for importing transport requests.

Change Control Management

Change Request Management PUBLIC 291
Prerequisites

Your business role must be authorized to display or edit the tab pages.

The following table specifies the functions for which each Change Request Management role is authorized in
the administration cockpit tab pages.

Note: An administrator has access to all functions. A requester does not have access to the administration
cockpit.

Authorizations for Roles in Change Request Management

Release Manager
Change Manager
Administrator

IT Operator

Requester
Developer

Tester
TSKLT_DISP       

Display task
lists

SYSTM_DISP       

Display land-
scape over-
view

SYSTM_EDIT       

Make
changes in
landscape
overview

CRIT_DISP       

Display criti-
cal object
configura-
tion

CRIT_EDIT       

Change criti-
cal object

Change Control Management

292 PUBLIC Change Request Management
 Release Manager
Change Manager
Administrator

IT Operator

Requester
Developer

Tester
configura-
tion

WHIT_DISP       

Display Al-
lowlist Ob-
ject configu-
ration

WHIT_EDIT       

Change Al-
lowlist Ob-
ject configu-
ration

CSOL_DISP       

Display
cross-sys-
tem object
lock entries

CSOL_EDIT       

Change
cross-sys-
tem object
lock entries

CRF_DIS-       
PLAY

Display
cross-refer-
ence check
tab

CRF_EDIT       

Change Control Management

Change Request Management PUBLIC 293
 Release Manager
Change Manager
Administrator

IT Operator

Requester
Developer

Tester
Change
cross-refer-
ence check
entries

TRACK_DISP       

Display
transport
analysis

SEARCH_DI       
SP

Perform
search

SCIMP_DISP       

Display
Scheduled
Import Jobs

4.4.6.1 Managing the Task List

On the Task Lists tab, you can display information and execute operational activities for distributing software in
your system landscape. The functions are based on the Schedule Manager.

Prerequisites

You have created change cycles.

Change Control Management

294 PUBLIC Change Request Management
Features

You can display the following information about your task lists:

• The assignment of task lists to change cycles

• The task list structure including the task status such as Locked, Unlocked, Active
• The overall view of the task execution on the Monitor tab
• The Daily Overview of task execution in a task list
• The Transport Requests belonging to a task list including the following information:
• Name and status of the transport request in the source system
• Transport request type
• System in which the request was created
From the Transport Requests tab, you can directly navigate to the change cycle in Change Request
Management.
• Landscape View of a task list with all assigned transport tracks. To see additional systems that are not on a
transport track, open the node Systems Without Transport Connection in the task list structure.
• Configuration gives you an overview of your system settings and links to the transactions where you can
change them.
• CSOL and downgrade protection
• Critical and allowlist objects
• ATC and code inspector
• Custom check
• Cross reference check
• Retrofit system
• Import strategy
In the Phase Controller view, you see which actions are available for each phase of the selected change
cycle.

You can perform the following activities:

• Create new change cycles.

When you choose Create Cycle, the system starts the WebClient UI.
• Distribute software changes of ABAP and non-ABAP objects (for example, Java archives)
• Create new task lists for urgent changes
You can create a task list for an urgent change directly from the Task Lists tab. Note that this task list is not
connected to a change document on the WebClient UI.
• Perform a configuration check for change cycles
• Change the CTS status switch
Usually, the CTS status switches are switched on. You should switch them off only in the following cases:
• You want to schedule an import in the transport management system.
• The SAP Solution Manager system is not available and you would like to perform a local import.
• Lock systems for the creation, export, or import of transport requests

Change Control Management

Change Request Management PUBLIC 295
Related Information

Change Cycles [page 28]

Configuration Check for Change Cycles [page 272]
Changing CTS Status Switches [page 300]
Locking Systems for the Creation, Export, or Import of Transport Requests [page 322]

4.4.6.1.1 Task List

A task list is a structured group of tasks, which are executed periodically by one or more users, to complete a
certain process, such as the handling of changes.

Structure

The task list is displayed as a structure tree. It contains tasks relevant for the process and defines which
processes can be performed for a change, depending on the change cycle to which it is assigned.

For more information, you can select the following tabs:

• Monitor: List of application logs for a task. This corresponds to the Application Log assignment block of the
associated change cycle in the WebClient UI.
• Daily overview for the tasks that are executed or planned on a daily basis.
• Transport request overview for a task list
• Transport landscape graphic

Integration

You create task lists in the WebClient UI, depending on the assigned change cycle.

From a change document and from a change cycle, you can call up the relevant task list by choosing More
Open Task List .

In the administration cockpit, you can manage your task lists on the Task Lists tab.

At your request, the system generates the task lists based on the settings for the change cycle (such as change
control landscape and branch).

Customizing provides the tasks that are generated for each system, depending on the system role type. You
can change the Customizing settings under the following paths:

• SAP Solution Manager Capabilities (Optional) Change Control Management Schedule Manager
Define Additional Tasks for Task Lists
• SAP Solution Manager Capabilities (Optional) Change Control Management Schedule Manager
Create Customer-Specific Header and Footer Tasks

Change Control Management

296 PUBLIC Change Request Management
If you make changes to the change cycle or in Customizing, these changes apply to all new task lists that are
generated from then on.

 Note

For Change Request Management, the task list also contains the status switch job that automatically
updates the status of change documents after they are imported into a target system.

Related Information

Change Control Management in the WebClient UI [page 15]

Creating Task Lists [page 273]
Managing the Task List [page 294]
Updating Change Document Status After Import of Transport Requests [page 132]

4.4.6.1.1.1 Task List Variants

Use

A change cycle defines the system landscape (change control landscape and branch) and the transport tracks
you use in Change Request Management. Each change cycle has a defined set of phases depending on its type.
The phases define which activities are permitted as part of change control. The transport tracks are defined in
the Transport Management System (TMS).

If you use Change Request Management, your systems are set up in such a way that you can only perform
the transport tasks (create, release, and import transport requests) in Change Request Management. This is
determined by the Central Transport System (CTS) project assigned to the transport requests, and the CTS
status switch which defines that you cannot create, release, or import transport requests using transactions
SE09 and STMS. Only the Change Request Management programs can perform these functions based on the
task list assigned to every change cycle.

Features

There are two SAP standard task list variants that determine the import strategy of changes:

• SAP0: Standard import strategy (recommended)

Distinguishes between two types of import:
• Normal changes are always imported into the system together (that is, all transport requests for a CTS
project in the import buffer) in the order of their release. The transport requests are then removed
from the import buffer.
You can perform a preliminary import of normal changes to accelerate the transport process. In this
case, the transport requests of the normal change stay in the import buffer.

Change Control Management

Change Request Management PUBLIC 297
 • Urgent changes are transported separately and as quickly as possible. After import, the transport
requests of the urgent change stay in the import buffer. They are imported with other related CTS
project transport requests in the order of their release, and only deleted from the buffer during the
mass import.

 Note

You must ensure consistency between urgent changes manually, that is, you must ensure that
the import sequence of urgent changes matches the release sequence, especially, if they are
interdependent.

Because normal and urgent changes are imported together as part of the CTS project import based on
their release sequence, any inconsistencies caused by urgent changes may be repaired.

• SAP1: Deletion of import buffer strategy

All imports are handled like urgent changes, but the transport requests are removed from the import buffer
after import. If you do not import in the release sequence, inconsistencies can occur. You cannot repair
these by performing the CTS project import because the buffer entries no longer exist.

 Caution

Use this import strategy with caution. Use it only if you are making small changes that are not
interdependent. Note that only the developer can determine which transports are to be determined
if there are interdependencies. In such a case, import the transport requests separately using this
import strategy, and not as part of a CTS project import.

By default, you have the following selection options for the task list variant:

• For phase cycles or release cycles:

Select SAP0 or a customized task list variant
• For continual cycles:
Select SAP1 or a customized task list variant

If you want to have different selection options for the task list variant for a change cycle, you can overwrite this
default selection option for the change cycle in the customizing table /TMWFLOW/TLVARCY.

More Information

Preliminary Import of Normal Changes [page 71]

4.4.6.1.1.2 Status Administration in Task Lists

Use

The task list consists of a structured group of tasks related to the distribution of software in the context of
change request management. The task list is displayed as a structure tree, into which you can insert different
task types.

Change Control Management

298 PUBLIC Change Request Management
Features

Task lists in change request management provide the following specific status administration functions:

• The status of the tasks in the daily overview or in the monitor is transferred automatically to the task list.
In the task list, the status of the tasks is initially Locked or Unlocked, depending on the status of the task
group. As soon as a task has been executed, its status is changed to the status of the (last) execution.

 Example

You start a task that returns the status Contains Errors. You then see this status in the daily overview, in
the monitor, and in the task list. If you start the task again but the task returns the status Warning, you
see this status for the newly scheduled items in the daily overview, in the monitor, and in the task list.
The former Contains Errors status in the task list has now changed to Warning, while the status of the
previous execution remains unchanged in the daily overview and in the monitor.

• The status in the task list refers to the last execution of the corresponding task. You can manually set the
status by selecting the task and choosing Change Task Status. If you want to see additional information
apart from the status history of all previous executions, you can check the daily overview or the monitor.
• Task groups and the task list also have a status. Task groups are either locked or unlocked. The tasks
initially have the same status as the task group to which they belong. Tasks can only be executed if the
status of all task groups higher in the hierarchy is Unlocked. The status of the entire task list, which is the
highest node in the task list display, can be Initial, Locked, Active, or Completed.
• Tasks that belong to a task list can only be executed if the task list is active. If the status of the task list is
Completed, it can no longer be changed or activated, and tasks in this task list can no longer be executed.
Any tasks that have never been executed then receive the status Skipped.

4.4.6.1.1.2.1 Changing the Status of Task Lists

Context

For example, if you decide that no tasks are to be executed for a certain period of time, you can lock the task
list. You can only continue to execute tasks for this cycle after activating the task list again.

If the end of a change cycle has been reached, you set the status of the cycle to Completed in the WebClient UI.
This ensures that no more tasks can be executed and no more changes can be made to this task list. Once a
task list has been completed, it can no longer be locked or activated.

Procedure

1. In the administration cockpit, go to the Task Lists tab.

2. Select the relevant change cycle.

Change Control Management

Change Request Management PUBLIC 299
 The system displays a list of all task lists.
3. Select the task list for which you want to change the status.
4. Change the status:

• If the task list is active, you can lock it.

• If the task list is locked, you can activate it.

Next Steps

You can display additional information about a task list by selecting it and choosing the Landscape View tab
page.

4.4.6.1.2 Changing CTS Status Switches

Prerequisites

• You have been assigned the SAP_CM_ADMINISTRATOR_COMP role.

• You have generated a change cycle.
• A task list exists for the change cycle.

Context

Once you have created a change cycle for a managed landscape, a CTS project is created automatically for
each of the development systems and clients that act as source systems in the landscape. By default, the CTS
status switches are closed. This means that the tools of the Change and Transport System cannot be used to
create, release, or import transport requests. For troubleshooting purposes, however, system administrators
are allowed to open the switches. You should only open the switches in the following cases:

• You want to perform a transport action directly in the transport management system, for example,
schedule an import in the transport management system.
• The SAP Solution Manager system is not available and you would like to perform a transport action.

 Note

If the SAP Solution Manager system is not available, go to transaction SE01 and enter any transport
request. Choose Go to Edit Project Project Status Switch and open the switch.

For change cycles that have been enabled for central CTS, the import status switches no longer control
imports. The imports are locked on central CTS level. In case of an emergency (for example, if the SAP

Change Control Management

300 PUBLIC Change Request Management
 Solution Manager system is not available), perform the steps as described under Performing Imports in
System Clusters [page 442].

Procedure

1. On the Task Lists tab page, select a task list and choose Change CTS Status Switch.
2. You have the following options for changing the CTS status switch:

• To change the CTS status switch for all systems and clients of the landscape, choose Select All and
then change the CTS status switch.
• To change the CTS status switch for selected systems, expand the structure tree and select the
systems. Then change the CTS status switch.
3. Choose Display Application Log in the dialog to check the recent logs of the CTS status switch changes that
were made here.

 Note

If you want to use SAP Solution Manager to control the transport activities of your landscape, we
recommend that you close the CTS status switch for all the systems and the clients of the landscape. In
addition, before transport activities are triggered from SAP Solution Manager, the corresponding CTS
project status switches will open beforehand and close afterwards automatically.

To track all the operations of the CTS status switches, in the application log transaction code SLG1,
search using the following criteria:

• For the Object enter /TMWFLOW/CMSCV.

• For the Subobject enter DRPS.
• For the External ID enter your task list ID.
• For Job Creation:
• If the action is triggered in the dialog, choose Dialog.
• If the action is triggered in the background via transport activities, choose In batch mode.

4.4.6.1.3 Configuration Check for Change Cycles

You can check whether a change cycle is correctly configured with respect to Change Request Management.

Prerequisites

• You have configured your system for Change Request Management.

• You have created a change cycle.

Change Control Management

Change Request Management PUBLIC 301
Features

You can check the following:

• General configuration
• Scheduled background jobs
• Number ranges
• Piece list activation in Customizing
• TMS
• CRM service
The system checks whether the settings required for using business transactions have been configured
in Change Request Management. This includes the registration of proxy classes for the transaction types
used, the assignment of business partners to users, and so on.
• System overview
• Change cycle consistency

Activities

1. You can access the configuration check in the following ways:

• In the WebClient UI, choose the change cycle for which you want to run a configuration check. Then
choose More Check Cycle Document
• In the administration cockpit, on the Task Lists tab, choose the cycle type or Urgent Changes.
2. Select the cycle for which you want to run a configuration check.
3. Choose Check Configuration.
The check results are presented as a list of nodes, which you can expand for more details. Items with
configuration error are marked in red. To correct an error, open the corresponding long text and follow the
instructions.

Related Information

Configuring Change Request Management [page 473]

4.4.6.1.4 Transport Management Functions in the

Administration Cockpit

Use

You can use various functions from the Transport Management System. These functions allow you to carry out
and monitor transports between SAP systems.

Change Control Management

302 PUBLIC Change Request Management
  Note

While most transport management functions are available on the WebClient UI and in the administration
cockpit, we recommend that you use the functions in the WebClient UI. Specific authorizations might be
required to execute them from the task list in the administration cockpit. For more information, see the
documentation for each function.

Features

You can execute the following transport management functions from the Task Lists tab page in the
administration cockpit:

• Create and release transport requests

• Create transport tasks
• Create transports of copies
• Import transport requests
• Assign transport requests
• Schedule imports of transport requests

4.4.6.1.4.1 Creating Transport Requests

In SAP Solution Manager, you can create transport requests from a change document, or from a task list.

Prerequisites

• A task list exists with the status Active.

• In the Solution Manager system, you have the role SAP_CM_DEVELOPER_COMP or
SAP_CM_OPERATOR_COMP.
• If you want to create a transport request from within the task list: In the managed system, you have the role
SAP_CHANGEMAN_OPERATOR.
• For Git-enabled changes: You have assigned the Git repository.

 Note

For urgent changes, only one open workbench and one open Customizing request are permitted at any
time.

Change Control Management

Change Request Management PUBLIC 303
Context

The transport requests are created for the development system where your software changes are recorded.
The transport requests are connected to the CTS project created from the change cycle used in the change
document and the task list. The transport requests get the transport request attributes SAP_CTS_PROJECT
(which contains the CTS project ID) and SAP_TMWFLOW (which contains the task list ID of your task list).

 Caution

For non-ABAP developments, see the Strategy for User Collaboration in Non-ABAP Development.

Creating Transport Requests from a Change Document

Procedure

1. In the WebClient UI, select the change document.

2. On the Transport Management assignment block, choose New Transport Request.
3. By default, your user is the owner and there is a single task for your user, and a generated short
description.
a. You can change the owner and short description.
b. You can also add developers to whom you want to assign transport tasks within this request.
4. Select the type of transport request you want to create (workbench or Customizing request for an ABAP
system, workbench for non-ABAP systems).

Results

In the selected development system, a transport request is created for the specified owner and developers.

Creating Transport Requests from a Task List

Procedure

1. In the administration cockpit, choose Task Lists.

2. Choose the change cycle or urgent change.

By default, you get a list of the task lists with the status Active. To select or activate task lists with other
statuses, change the status of the task list.
3. Select the track for which you want to create a new transport request.

Change Control Management

304 PUBLIC Change Request Management
4. Under the task node of the development system, select Create Transport Request Execute .
5. By default, your user is the owner and there is a single task for your user, and a generated short
description.
a. You can change the owner and short description.
b. You can also add developers to whom you want to assign transport tasks within this request.
6. Select the type of transport request you want to create (workbench or Customizing request for an ABAP
system, workbench for non-ABAP systems).

Results

In the selected development system, a transport request is created for the specified owner and developers.

After the transport request has been created, the task list is displayed again.

You can check the status of your task. If you need more information about the task, check the application log in
the Daily overview of the task list.

In the selected development system, a transport request is created for the specified owner and developers.

Related Information

Changing the Status of Task Lists [page 299]

Strategy for Collaboration in Non-ABAP Development

Context

In non-ABAP developments, you can have only one modifiable transport request per change document. This
ensures consistency in software distribution. Also, in non-ABAP developments, you cannot create tasks under
a transport request.

If you want to collaborate with other non-ABAP developers in the same transport request, you can preselect all
developers involved to enable them to use this particular transport request. This is the only way to guarantee
that non-ABAP content is transported in the correct order and to avoid downgrade.

Procedure

1. Call transaction STMS (Transport Management System).

2. On the menu bar, choose Transport Organizer Web UI and select the system.

Change Control Management

Change Request Management PUBLIC 305
3. Select the transport request for which you want to preselect users.
4. Under Details of Transport Request, find the Preselection tab.
5. You can search and add preselected users. To add more names, add another row.
6. Save your entries.

4.4.6.1.4.2 Creating Transport Tasks

Use

You want to create new transport tasks for an existing transport request. This may be necessary, for example, if
additional developers need to take part in the development, or if old tasks have already been released.

Prerequisites

• A task list exists with the status Active.

• You have been assigned the SAP_CM_DEVELOPER_COMP role in the SAP Solution Manager system.
• A transport request has been created for your user.

 Note

If you want to create transport tasks in the administration cockpit, you must have the
SAP_CHANGEMAN_OPERATOR role in the managed system.

Procedure

Creating Transport Tasks from a Change Document

To create transport tasks from within a change document, proceed as follows:

1. In the Transport Management assignment block, select a transport request and choose New Task.
2. In the dialog window, specify the users who need a transport task in this transport request.

Creating Transport Tasks from a Task List

To create transport tasks from within a task list, proceed as follows:

1. In the administration cockpit, choose Task Lists.

2. Select the relevant change cycle.
3. Click the task list for which you need to create new transport tasks.
4. Under the task node of the development system, select Create Transport Task and start the action by
clicking Execute task.
5. On the screen that appears, enter or select the request number and the names of the developers for whom
you want to create new tasks.

Change Control Management

306 PUBLIC Change Request Management
 After the transport tasks have been created, the task list is displayed again.
6. Check the status of your task. If you need more information about the task, check the application log in the
Daily overview of the task list.

Result

In the selected development system, new tasks have been created in the specified transport request for the
specified developers.

4.4.6.1.4.3 Creating Transports of Copies (ToC)

With transports of copies, you can transport your software changes to the consolidation system without having
to transport them automatically to other systems in your transport track. The objects are transported with the
version they have in the current SAP system. The original location of the objects remains unchanged.

Prerequisites

• A task list exists with the status Active.

• The tasks associated with the transport request have been released.
• In the SAP Solution Manager system, you have the role SAP_CM_DEVELOPER_COMP.
• To release transport requests from the task list, you have the role SAP_CHANGEMAN_OPERATOR in the
managed system.

Context

You can create transports of copies (ToC) in the WebClient UI (normal change or standard change), or from a
task list.

Can I create a ToC?

Change Transaction In Webclient UI From Task List

Request for Change (SMCR)  

Normal Change (SMMJ)  

Administrative Change (SMAD) n/a n/a

General Change (SMCG) n/a n/a

Standard Change (SMSG)  

Urgent Change (SMHF)  

Change Control Management

Change Request Management PUBLIC 307
Change Transaction In Webclient UI From Task List

Git-enabled Change (SMGH)  

Defect Correction (SMTM)  

Creating Transports of Copies (ToC) in the WebClient UI

To create a transport of copies from within a normal change or standard change, you have the following
options:

• On the Transport Management assignment block, select a transport request and choose New Transport of
Copies.
Transports of copies are released and imported automatically into the consolidation system.
• Set the change document status To Be Tested.
Transports of copies for the existing transport requests are created and exported automatically.

Creating Transports of Copies (ToC) from a Task List

To create a transport of copies from within a task list, proceed as follows:

Procedure

1. In the administration cockpit, go to Task Lists and select the change cycle and task list for which you want
to create a transport of copies.
2. In structure tree of the selected task list, find the track of the development system for which you want to
create a transport of copies.

3. Expand the task nodes of the development system and select Create Transport of Copies Execute
Task .

A dialog box lists the available original transport requests.

 Note

The available transport requests are from the change transactions (except for urgent changes,
standard changes and Git-enabled changes) assigned to the CTS project that is connected to the
cycle.

4. Select one or more original transport requests for which you want to create transports of copies.

After the transports of copies have been created, you return to the change cycle's task list.
5. Check the status of your task.

For more details, check the application log in the Daily Overview of the task list.

Change Control Management

308 PUBLIC Change Request Management
Results

For each selected transport request, the object list is used to create a new transport of copies. Transports of
copies are released and added to the import queue of your consolidation system. Now, you can import these
transport requests for testing.

 Note

Transports of copies are not included in the CTS delivery mechanism, so they aren’t transported across
your system and are, therefore, not imported into your production system.

If the tests of your transports of copies are successful, you release the original transports, which can then be
transported across your landscape.

The transports of copies are provided with transport request attributes SAP_CTS_PROJECT (which contains
the CTS project ID) and SAP_TMWFLOW (which contains the task list ID of your task list).

Related Information

Processing Normal Changes [page 68]

Processing Standard Changes [page 89]
Managing the Task List [page 294]

4.4.6.1.4.4 Releasing Transport Requests

You can release the transport requests that are part of your changes from the Solution Manager system in the
WebClient UI and in the Administration Cockpit.

Prerequisites

• A task list exists with the status Active.

• In the SAP Solution Manager system, you have the role SAP_CM_DEVELOPER_COMP.
• To release transport requests from the administration cockpit, you need the role
SAP_CHANGEMAN_OPERATOR in the managed system.

Context

There are two ways to release transport requests:

• From a change document in the WebClient UI

Change Control Management

Change Request Management PUBLIC 309
• From a task list in the administration cockpit

Releasing Transport Requests from a Change Document

The following actions release a transport request from within a change document:

• For urgent changes that are in status In Development: Go to the Transport Management assignment block,
select the transport request and choose Release Transport Request. In this case, you can also use the Code
Inspector.
Transport requests of urgent changes can also be released automatically when the change document is set
to To Be Tested.
• For normal changes: Transport requests are automatically released when the change document is set to
Successfully Tested.
• For Git-enabled changes: Transport requests are automatically released when the change document is set
to Successfully Tested.

Releasing Transport Requests from a Task List

To release a transport request from within a task list, proceed as follows:

Procedure

1. In the administration cockpit, go to Task Lists and choose the relevant change cycle.
2. Select the task list for which you want to release transport requests.

3. Under the task node of the development system, select Release Transport Request Execute .

You can decide whether you want to execute the task immediately or at a scheduled time.
4. In the dialog box, select the transport requests that you want to release.

 Note

Transport requests from urgent changes and standard changes are not listed in the dialog box. Release
them from the change document.

5. Check the status of your task.

For more details, check the application log in the Daily Overview of the task list.

Results

• In the selected development system, the transport requests that you specified are released.
• A transport request containing any open tasks is not released.
• Empty transport requests are deleted.

Change Control Management

310 PUBLIC Change Request Management
Related Information

Administration Cockpit for Change Request Management [page 291]

Change Control Management in the WebClient UI [page 15]
Processing Normal Changes [page 68]
Processing Standard Changes [page 89]
Processing Urgent Changes [page 81]
Using the Code Inspector in Urgent Changes [page 85]

4.4.6.1.4.5 Importing Transport Requests

Use

You want to import transport requests.

Prerequisites

• A task list exists with the status Active.

• In the SAP Solution Manager system, you have the role SAP_CM_OPERATOR_COMP.
• In the managed system, you have the role SAP_CHANGEMAN_OPERATOR.

 Note

If you want to import transport requests from within a change document, you must have the
SAP_CM_DEVELOPER_COMP role in the SAP Solution Manager system.

• If you want to use status-dependent or selective import, you have set up the respective import strategy.

Procedure

To import transport requests from within a task list, proceed as follows:

1. On the Task Lists tab page, under the relevant change cycle, choose the task list for which you want to
import transport requests.
2. Under the task node of the target system of your import, select Schedule Import Job for Transport
Requests and execute the task.

 Recommendation

If you have activated central CTS for your change cycle, choose the task under the cluster node to start
the import. Especially if you would like to start the import into several systems of the same cluster in
parallel, you must use this node.

Change Control Management

Change Request Management PUBLIC 311
3. In the dialog box that appears, enter or select the import options for this import.

 Note

The import parameter dialog box is only available for calls from the administration cockpit. This is the
case for urgent changes that are processed manually and for continual cycles. In the case of urgent
changes that are processed from within a change document, it is assumed that the import must be
started with the default import settings.

For continual cycles, the window displays the cycle that you specified and the import target. For urgent
changes, the box displays the corresponding requests and the import target.

4. If you select the Standard Change Only option, the import dialog box displays only standard changes.
Status-driven Customizing is considered. The Go-Live phase is not required to import the transport
request of a standard change into a production system.
5. On the Execution tab page, specify how you want the transport control program to start.
6. On the Options tab page, specify options for the import.
7. If you have activated central CTS for your project, the Systems tab page displays all the systems in the
target cluster. Select the target systems for your transport request.
8. After you have configured your settings, choose OK.
The transport requests are imported and the task list is displayed again.

 Note

If the system finds a downgrade conflict, the import is canceled. The conflicts are displayed in the
application log.

9. Check the status of your task. If you need more information about the task, check the application log in the
Daily overview of the task list.

Result

• In the selected system, the following types of transport requests are available for import (respecting your
import strategy):

Context Importable Transport Requests

Urgent change • All requests that belong to that urgent change and
that have been released
• Requests that have not already been imported
• Requests that have been recorded in the import
queue of the import target

Change Control Management

312 PUBLIC Change Request Management
 Context Importable Transport Requests

Continual cycle • All requests that belong to the CTS project connected
to that continual cycle.
• Requests that have been recorded in the import
queue of the import target.

 Note
The requests that are imported within an urgent
change cycle are flagged as preliminary imports.
This means that they will be imported again as
part of the regular project import of the corre-
sponding continual cycle.

Release cycle • All requests in the buffer that belong to change docu-
ments of the current release cycle.
• All requests in the buffer that belong to urgent
changes of an active predecessor release cycle with
the same cycle task list. (It is not important, if the ur-
gent changes from predecessor cycles were prelimi-
narily imported or not.).

Phase cycle • All requests that belong to the CTS project connected
to that phase cycle.
• Requests that have been recorded in the import
queue of the import target.

 Note
The requests that are imported within an urgent
change cycle are flagged as preliminary imports. This
means that they will be imported again as part of
the regular project import of the corresponding phase
cycle.

• If the active import feedback job SM: AI_CRM_CM_COM_IMPORT_FEEDBACK has been set up, the following
happens:
• Automated emails are sent, for example, to inform the IT operator about import errors and transport
return codes.
• All changed documents of the imported transport requests are processed as customized.
• Fully imported transport requests are removed from the STMS import queue after the import is
successfully done.
• In the WebClient UI, the Import Status column of the transport request is updated.
For more information about the active import feedback job, see the activity documentation in SAP
Solution Manager Configuration Change Request Management Prepare System Schedule Background
Jobs .

Change Control Management

Change Request Management PUBLIC 313
  Note

You need to install the latest SAP Solution Tools Plug-in (the ST-PI) onto the managed systems.

• If you want to define a specific user for this import action, use the Background User option on the Date tab
page of the import dialog box.

Related Information

Central Change and Transport System [page 400]

Change Control Management Using Central CTS [page 399]
Import Strategies: Standard, Status-Dependent, and Selective [page 396]
Processing Standard Changes [page 89]
Processing Urgent Changes [page 81]
Continual Cycle [page 29]
Release Cycle [page 44]
Preliminary Import of Normal Changes [page 71]
Updating Change Document Status After Import of Transport Requests [page 132]

4.4.6.1.4.5.1 Starting an Import: Scheduling

Scheduled transport is one of two options to import transport requests, including transports of copies.

When you execute an import task, you can choose between the following options:

• Immediate transport
All transport requests for this project that are in the import buffer are transported to the target system
immediately.
• Scheduled transport
The IT operator schedules a start time for the import - that is, either a specific date and time, or a period
such as every 15 minutes, hourly, or daily.

 Note

While it’s also possible to use transaction STMS to schedule periodic imports, we do not recommend this
option. If you still want to use it, perform the following steps:

1. In transaction STMS in the quality system, choose Import Overview and select the target system for the
import.
2. On the Import Queue screen, select a project and choose Filters. You see all transport requests for the
selected project.
3. Choose Queue Start Import and enter the intervals for importing transport requests, for
example, every 30 minutes.
4. After double-clicking an entry and choosing Maintain Project Status Switch, change the entry to
Requests can be imported. This schedules an import job. At the scheduled time, the system checks
whether the import is allowed and carries out the import.

Change Control Management

314 PUBLIC Change Request Management
Related Information

Scheduled Import Jobs [page 335]

Creating Transports of Copies (ToC) [page 123]

4.4.6.1.4.6 Declaring Import Errors as Repaired

If you repair import errors manually, you must update the status in the task list.

Context

Change cycles run through fixed phases that start when the cycle is created and end when it is closed. During
the change process, there are checks if corresponding transport requests have been imported successfully into
the target system.

If errors occur during the import, you can correct them manually.

Procedure

1. To display import errors, in the cycle task list, under General Tasks, select Declare Import Errors as
Repaired.

The system displays an overview of the imports with errors in each of the target systems for the task list.
2. To see the log overview, select the target system and choose Log.
3. To display more detailed information about import errors, select the import with errors with the status
Ended with Errors.

The system displays the log file with the import error.
4. Correct the error in the target system.

If, for example, a missing domain caused the import error, import the domain transport request and
regenerate the corresponding data element.
5. Return to the administration cockpit and select the Declare Import Errors as Repaired task again.

The system displays an overview of the imports with errors with their target system.
6. To change the import status of the corrected error, select the transport request and choose Declare Error
as Repaired.

 Note

You can declare multiple import errors at once.

Change Control Management

Change Request Management PUBLIC 315
Results

The system corrects the internal status in SAP Solution Manager.

The changes on the transport request can move forward.

 Note

The system does not correct the status of the underlying import in the log because log files cannot be
changed. The import log still has the status “With Errors”.

Related Information

Change Cycles [page 28]

Task List [page 53]

4.4.6.1.4.7 Displaying Import Information from the TMS

Prerequisites

A task list exists with the status Active.

Context

Having started an import, you discover that errors occurred. You now want to see more detailed information
about the import. The following information is available from the task lists:

• Alert monitor: provides an overview of all the actions that are performed in the Transport Management
System
• Import monitor: provides an overview of the current status of imports into a system
• Import history: provides an overview of all the requests imported into a particular system for a specific
time interval, including their maximum return codes

Procedure

1. On the Task Lists tab page, choose the change cycle.

Change Control Management

316 PUBLIC Change Request Management
2. Select the task list for which you want to display the details.
3. Under the task node of the system for which you want to see import information, select one of the following
options:

• Display TMS Alert Monitor

• Display TMS Import Monitor
• Display TMS Import History
4. Choose the system and OK.

The system automatically opens the SAP GUI transaction.

Related Information

4.4.6.1.4.8 Synchronizing Urgent Changes in Parallel

Systems

To ensure consistency in parallel test and production systems, you can use periodic background processes to
schedule the import of transport requests created from urgent changes.

 Note

Urgent changes that are imported into the production system where the request for change originated
aren't imported into other parallel production systems.

Prerequisites

• A change cycle with task list status Active exists. The automatic import includes only urgent changes that
are assigned to this change cycle.
• For one development system, you have defined and activated multiple, parallel follow-on systems (test
systems).
• For one development system, you have defined and activated multiple, parallel production systems.
• The urgent change has been imported into the production system where the request for change originated,
the tracking process of the central system knows about it, and the corresponding change document has
status Completed.

Procedure

1. In the Administration Cockpit, on the Task Lists tab, select the change cycle.

Change Control Management

Change Request Management PUBLIC 317
2. Expand the task list and, depending on the system type, execute the following tasks:
• For the test system, select Synchronize Urgent Changes from Other Test Systems.
• For the production system, select Synchronize Urgent Change.
3. Choose between immediate execution and a scheduled start time - that is, either a specific date and time,
or a period such as every 15 minutes, hourly, or daily.

Result

The task is executed and recorded in the application log.

To view the application log, execute transaction SLG1 for object /TMWFLOW/CMSCV and subobject SCHEDMAN.

Related Information

Processing Urgent Changes [page 81]

4.4.6.1.4.9 Assigning Transport Requests

After Change Request Management is implemented, you can assign transport requests that were created
before you started using Change Request Management to change documents.

Context

In Change Request Management, you should always create transport requests from a change document or a
task list. Any transport requests that you’ve created manually in the transport management system are not
known to Change Request Management. However, if you start using Change Request Management, you can
assign your existing transport requests to change documents and then control them with Change Request
Management.

The following procedures explain you identify these transport requests and make them known to Change
Request Management.

 Note

As of SAP Solution Manager 7.2 support package 3, you can manage change documents without transport
requests. In doing so, transport-relevant actions and checks are ignored if no transport request has been
assigned to change documents.

If you want to make it mandatory for urgent changes, normal changes, and defect corrections that
transport requests are assigned to change documents, perform the Customizing activity Enable Mandatory
Transports in SAP Solution Manager Configuration (transaction SOLMAN_SETUP) under Change Request
Management Employ Additional Use Cases .

Change Control Management

318 PUBLIC Change Request Management
Supported Transport Request Types
Change managers or developers can assign the following transport requests to change documents:

• Decoupled transport requests

• Freely created transport requests
• External transport requests, that is, from another system landscape

Limitations
You can assign Workbench and Customizing transport requests but not transports of copies.

You can assign a transport request multiple times, as long as it’s assigned to different change cycles whose
landscape does not have the same production system.

For Git-enabled changes, you can only assign a transport request if the Git repository is assigned, and the
transport request is linked to the same repository.

Assigning Decoupled and Freely Created Transport Requests

Prerequisites

• To assign released transport requests, you have activated the central Change and Transport System
(central CTS) for your change cycle. Otherwise, you can only assign modifiable transport requests.
• To update the transport request description, BAdl /TMWFLOW/ASSIGN_TRANS_DESC_UPD has been
implemented in Configuration (transaction SOLMAN_SETUP) step Employ Additional Use Cases.

Procedure

1. To open the search for transport request, you have the following choices:

• In the WebClient UI, in the Transport Management assignment block, choose More Assign
Transport Request .
• In the task list, choose the Assign Transport Request task under the development system.

 Recommendation

While transport requests for release cycles and continual cycles can only be assigned in the WebClient
UI, transport requests for phase cycles can be assigned directly in the task list. However, we
recommend that you use the WebClient UI to assign transport requests.

For urgent changes without a change document, you can only use the task list.

You see the transport request search.

2. Search for the transport requests you want to assign.
3. Select the requests and choose Assign Transport Request.

If you have activated downgrade protection, you are informed about potential downgrade conflicts.

Change Control Management

Change Request Management PUBLIC 319
Results

The transport request is assigned to the change document.

The description of the transport request is updated to show the new change document.

 Note

When the transport request is assigned to the document, the description of the transport request can be
updated automatically by the system.

The description can be set up by BAdI BAdI: Change Description after Assign Transport Request to Change
Document TMWFLOW/ASSIGN_TRANS_DESC_UPD.

For updating the description of the transport request in the managed system, use SAP Note 2809667 .

Assigning External Transport Requests

Prerequisites

• You have activated the central Change and Transport System (central CTS) for your change cycle.
• In TMS, you have defined a delivery route to transport the external transport request from the
development system to the consolidation system, and from the development cluster to the consolidation
cluster.
• You have defined the source system of the external transport request in the transport target area of the
target clusters of your imports to transport the external transport request.
• Before you can assign an external transport request, it must be imported into the development system.
• You can only assign external transport requests from a change document created in your central CTS
change cycle.

Procedure

1. In the transport management system (transaction STMS), in the development system of the landscape
from which you want to import a transport request, choose Import Overview.
2. In the displayed list, select the development system by double-clicking.

3. Choose Extras Other Requests Add .

4. In the dialog box, enter the transport request ID and the target client of the system to which you want to
import.

5. Select the transport request, choose Request Import , and confirm the import to the development
system.

The transport request is now available in the import buffer of the quality system in the new target system
landscape.

Change Control Management

320 PUBLIC Change Request Management
6. To find the transport request you just imported into the development system, go to your change in the
WebClient UI and, in the Transport Management assignment block, choose More Assign Transport
Request .

 Recommendation

Do not assign the same external transport request into the same change document multiple times for
different development systems.

7. Select the transport request you just imported and choose Assign Transport Request.

If you have activated downgrade protection, you’re informed about potential downgrade conflicts.

Results

The transport request is assigned to the change document.

Related Information

Creating Transport Requests [page 119]

Central Change and Transport System [page 400]
Performing Transport-Related Checks [page 150]
Decoupling Transport Requests in Change Request Management [page 134]
Downgrade Protection [page 360]

4.4.6.1.5 Displaying Transport Analyses

Before you start an import into a production system, you want to compare the software level of your production
system with that of your development system.

Prerequisites

A task list exists with the status Active.

Procedure

1. In the administration cockpit, under Task Lists, select the task list of the change cycle for which you want to
check transports.

Change Control Management

Change Request Management PUBLIC 321
2. Under the task node of the production system, select Display Transport Analysis and execute the task.
You see the project analysis of the change tracking function. The system displays the transport status of all
the transport requests for the production system.
3. Close the analysis and check whether your task was processed without errors or warnings.
4. For more information about the task, check the application log in the Daily Overview of the task list.

Result

You see an overview of the software state in your production system compared with the development system.

 Recommendation

To decide whether you can start the import into the production system, we recommend that you check
the kernel, SAP Note, and Support Package Stack level, as well as the sequence and completeness of the
transports.

4.4.6.1.6 Locking Systems for the Creation, Export, or

Import of Transport Requests

You can block the creation, export, or import of transport requests for individual systems in the system
landscape of a change cycle.

You can use this function, for example, during a cutover when you are switching to a new development system
during an active change cycle. In this case, you can lock the old development system for the creation and
export of transport requests when you start using the new development system. You can also lock the import
into specific follow-on systems.

 Note

This feature can be used only by IT operators and administrators.

There are three separate locks for blocking the creation, export, or import of transport requests:

• If the transport creation lock is enabled for a development system, transport requests cannot be created
in the system.
• If the export lock is enabled for a development system, transport requests cannot be exported from the
system.
• If the import lock is enabled for a follow-on system, transport requests cannot be imported into the
system.

You enable and disable the creation, export, and import locks in the Administration Cockpit on the Task List tab
in the Landscape View: In the Landscape View, choose the legend area for the system for which you want to
enable or disable a lock and then choose the required option in the menu.

Without using the Administration Cockpit, you can also enable and disable the creation, export, and import
locks directly in a task list: In a change cycle or change document, you can also open the task list by choosing
More Open Task List , then navigate to the Landscape View of the task list.

Change Control Management

322 PUBLIC Change Request Management
In the Landscape View, a system for which a lock is enabled is marked with a lock icon.

 Note

In case of multiple tracks or cycles using cCTS, only the locks for the relevant transport request track are
considered.

 Note

The Transport into Sandbox System action can only be controlled by an import lock of the target system. It's
not affected by an export lock of the development system.

 Note

If you schedule a release job or an import job, and the relevant locks are enabled, you will get a warning
message. When the release or import is then executed at real time, and a relevant lock is still enabled, an
error message will be written in the execution log.

4.4.6.2 Landscape Overview

The Landscape Overview tab displays information on the managed systems contained in the logical component
groups that are connected to Change Request Management or QGM via the solution landscape (transaction
SLAN) or the change control landscape assignment. Each managed system in the logical component groups is
listed together with its communication systems.

Features

The following functions are available:

• From the System Status column, you see details of the configuration check result.
• From the Technical System column, you see and edit the system in LMDB.
• From the Work Mode column, you see the work mode status in the IT calendar. You can navigate directly to
the IT calendar.
• The Lifecycle Status displays the status set in the landscape management database (transaction LMDB).
You can navigate directly to LMDB.
• In the Upon-Saving Checks column, you can activate the upon-saving transport-related checks framework
for each managed ABAP development system. In the dropdown list, select Off, On, or On (Legacy CSOL).
To enable single checks in this framework, you must switch on each check individually. For example, to
activate the cross-system object lock check, call transaction SOLMAN_SETUP and in your scenario Change
Request Management or QGM, select Set up Downgrade Protection and Retrofit Configure CSOL and
DGP Globally Activate CSOL and DGP (Master Data) .
• In the CTS Project Assignment column, you can check and edit the entries. You can directly navigate to the
managed system.

Change Control Management

Change Request Management PUBLIC 323
 For each system in which you want to create transport requests, select the project assignment attribute
(SAP_CTS_PROJECT):
We recommend that you set the CTS project assignment as mandatory to prevent the creation of transport
requests outside Change Control Management. Note that if it is mandatory, you cannot release transport
requests without CTS projects. If you set up CTS projects during a transition period, you may have
to create dummy CTS projects so that developments made before the availability of Change Request
Management can still be transported.

 Note

Note: If your Solution Manager system is not available, you can make these settings in transaction
SE03 of the managed development system.

• Change Document Assignment: You can allow your developers the manual creation of transport requests
directly in the managed ABAP development system and the assignment of these transport requests to
a change document that is managed in the SAP Solution Manager. Depending on the option you select,
developers see different fields in WBO, in the transport request creation dialog. You can select one of the
following options:

Not Required Developers can assign the transport request to a local CTS Project or leave the CTS
Project unassigned.
(This is the default option and
deactivates the change docu- They cannot select a change document ID.
ment assignment functionality.)

Required Developers must select a change document ID. They can only select change docu-
ments that have a status that allows transport request creation and for which they
are assigned as developer (business partner role).

They cannot assign the transport request to a CTS Project.

These transport requests are managed inside SAP Solution Manager, in the change
document.

Optional Developers can either select a change document ID or assign the transport to a CTS
Project or leave the project unassigned.

 Note

To assign a transport request to a CTS project that was created from a Change Request Management
cycle, the CTS Project switches must allow transport request creation.

To allow creating a transport request without a mandatory project assignment, set attribute
SAP_CTS_PROJECT to Not mandatory.

• If a trusted RFC destination has been configured, you can log on to an ABAP system. If host and port data
is provided for the Java system in transaction LMDB, you can log on to the SAP NetWeaver Java starting
page.
• Display the defined RFC connections. You can directly navigate to LMDB to configure the connections.
• To perform a check for selected systems, choose Perform Check. The Last Check column indicates the
date or time of the system check.

Change Control Management

324 PUBLIC Change Request Management
• To delete the transport tracking data of one or more selected systems, select Delete Transport Tracking
Data. If you want to copy a managed system but the transport history of the central SAP Solution Manager
system already contains transport data (for example, transport statuses and objects), use this function to
delete the buffered transport data information contained in the SAP Solution Manager system.
• You can re-read the transport tracking data of a single system, a change cycle, or a QGM scenario.

Related Information

Managing Logical Component Groups

Upon-Saving Transport-Related Checks [page 161]
Assigning a Change Document to Transport Requests Created Outside SAP Solution Manager [page 394]

4.4.6.3 Defining Critical Objects

To prevent improper modification of objects that are especially important for your core business processes,
you can define such objects as critical and monitor any changes.

Use

The change and transport process across your solution landscape may include objects that are especially
important for your core business processes. Improper modification of those objects may result in serious
business impact on the whole solution’s stability. Therefore, a strict monitoring mechanism is needed to
control those objects’ change and transport.

You can activate a check to determine if transport requests contain critical transport objects, which require
approval before they can be exported from the development system. This check can be activated both on
system and client level.

Critical object checks are available for Quality Gate Management and Change Request Management.

 Note

Critical object checks are available only for ABAP systems. Critical object definitions are applicable only to
development systems.

In Change Request Management, approval for critical objects conflicts is requested in the following ways -
depending on the status of the upon-saving transport-related check:

• If the check is active: When developers save a transport request even though there is a critical object
conflict, the change manager (or other designated partner function) receives an e-mail notification.
• If the check is inactive: When developers set a change document to status To Be Tested, or release the
transport requests in normal changes and defect corrections, they can manually request approval.

Change Control Management

Change Request Management PUBLIC 325
Prerequisites

To define critical objects, you have one of the following roles:

• SAP_CM_ADMINISTRATOR_COMP or SAP_CM_CHANGE_MANAGER_COMP (for Change Request Management)

• SAP_QGM_ADMIN_COMP or SAP_QGM_CHANGE_MANAGER_COMP (for Quality Gate Management)

Activities

 Note

You can define generic critical objects by entering wildcards in the fields.

1. You have the following options:

• To create a critical object manually for selected systems and clients, choose Add and in the menu,
choose New.
• To create a new critical object based on an existing one, select a critical object, choose Add
From Selected Object . Adapt the data as needed. You must assign another system or object name
because duplicate objects are not allowed.
• You can also select objects in a transport request and flag them as critical objects: Choose Add
From Transport Request . Select the system and the transport request and then select the objects
that you want to flag as critical objects.
• To copy multiple critical objects across your systems, select all required critical objects, choose Copy
and select one or more target systems.

 Note

To ensure consistency, we recommend that you choose one logical system (system/client) as the
“original” system. Only in this system, you should create, change, or delete objects, and then copy
them to other systems.

2. Activate the check for specific critical objects.

To specify the start and end date of the "active" status for one or more critical objects, you have the
following options:
• When creating or editing a critical object, change the values in the respective fields. Per default, start
date is the current day, with unlimited validity.
• In the critical objects list, select one or more critical objects and activate or deactivate them.
Define whether the check is to be active at global level or at system level. The global switch controls
whether the check is off for all managed systems. The system switch controls whether the check is off for
specific systems. The check is only performed if both the global and the system switch are on.
3. In the change log, you see all critical object-related changes.
4. While a transport request is being exported, the source and target system and the source and target client
are determined. If the transport object checks are active for the relevant client and system, the export
program checks whether the transport request contains critical transport objects, or subobjects of critical
transport objects. The export does not take place if the transport request contains critical objects but has
to be approved by the change manager.

Change Control Management

326 PUBLIC Change Request Management
Related Information

Performing Transport-Related Checks [page 150]

Generic Critical Objects [page 327]
Approving and Exporting Critical Objects [page 147]

4.4.6.3.1 Generic Critical Objects

You can use asterisks as “wildcards” to specify generic critical Customizing and Workbench objects.

 Tip

If you are not sure which object type and object name to enter, check the object list of your transport
request, and check the Object Type and Object Name columns.

Generic Critical Customizing Objects

For Customizing objects, you can flag generic critical objects based on:

• Generic Table Key

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TABU

Object Name: UST04

Table Key: 100*

In this case, the entries in table UST04 that have a table key beginning with “100” must be approved
before they can be transported.

• Generic Table Name

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Change Control Management

Change Request Management PUBLIC 327
 Object Type: TDAT

Object Name: UST*

Table Key: 100ENK1

In this case, Customizing content of tables with a name beginning with “UST” must be approved before
they can be transported.

• Generic View Name

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: CDAT

Object Name: SCMGV_ATTR*

Table Key: *

In this case, Customizing objects of the views in the view cluster with names beginning with
“SCMGV_ATTR” must be approved before they can be transported.

• Generic Object Type

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: CD*

Object Name: SCMGV_ATTR*

Table Key: *

In this case, Customizing objects with types beginning with “CD” and names beginning with
“SCMGV_ATTR” must be approved before they can be transported.

Generic Critical Workbench Objects

For Workbench objects, you can flag generic critical objects based on:

• Generic Object Name

Change Control Management

328 PUBLIC Change Request Management
  Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TABL

Object Name: ZCUST*

In this case, all tables with a name beginning with “ZCUST” must be approved before they can be
transported.

• Generic Object Type

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TA*

Object Name: ZCUST*

In this case, all Workbench objects with types beginning with “TA” and names beginning with “ZCUST”
must be approved before they can be transported.

4.4.6.4 Defining Allowlist Objects

On the Allowlist Objects tab, you specify which objects are allowed to be saved to a transport request of a
standard change.

Use

Allowlist object checks are only available for Change Request Management and they are only relevant for
standard changes.

Standard changes are no-risk or low-risk changes and can therefore be processed without approval. On the
Allowlist Objects tab, you define the objects that are allowed to be saved to a transport request of a standard
change.

If you try to save objects that are not part of the allowlist to a transport request of a standard change, you
receive an error message. In this case, you must either add the relevant objects to the allowlist, or reassign the
transport request to a normal change or to an urgent change.

Change Control Management

Change Request Management PUBLIC 329
Developers can request that objects are added to the allowlist when they try to save it in the managed system,
or from the WebClient UI, in the transport-related checks dialog. Alternatively, developers can create the
request in Eclipse ADT.

On the Allowlist Objects tab, you specify the objects for the allowlist and you specify for which systems and
clients the allowlist applies.

 Note

Allowlist objects are available only for ABAP systems. The allowlist object definitions are applicable only to
development systems.

Prerequisites

• To create allowlist objects, you have the role SAP_CM_ADMINISTRATOR_COMP or

SAP_CM_CHANGE_MANAGER_COMP.
• To support requests created in Eclipse ADT, you have installed ADT 3.14.

Activities

1. To add objects to the allowlist, you have the following options:

• To create an allowlist object manually for selected systems and clients, choose Add and in the menu,
choose New.
• To create a new allowlist object based on an existing one, select an allowlist object, choose Add and in
the menu, choose From Selected Object. Adapt the data as needed. You must assign another system or
object name because duplicate objects are not allowed.
• You can also select objects in a transport request and add them to the allowlist: Go to Add From
Transport Request , select the system and the transport request and select the objects that you want
to add to the allowlist.
• To copy multiple allowlist objects across your systems, select all required allowlist objects, choose
Copy, and select one or more target systems.

 Note

To ensure consistency, we recommend that you choose one logical system (system/client) as the
“original” system. Only in this system, you should create, change, or delete objects, and then copy
them to other systems.

• To approve requests for objects to be added to the allowlist, choose Display Requested Objects, select
the objects you want to add, and choose Approve.
2. Set the specific allowlist objects to Active.
• To activate or deactivate single allowlist objects, check the box in the Active column to change the
status.
• To activate or deactivate multiple allowlist objects, select them in the first column and choose the
Activate or Deactivate button to change their status.

Change Control Management

330 PUBLIC Change Request Management
3. Define whether the allowlist is applied at global level or at system level:
• With the global switch, you can switch off the allowlist for all managed systems.
• With the system switch, you can switch off the allowlist for specific systems and clients.
The allowlist applies to a system if both the global and the system switch are on.

While a transport request of a standard change is being exported, the source and target system and the source
and target client are determined. If the allowlist is active for the relevant client and system, the export program
checks whether the objects on the transport request are on the allowlist. Objects that are on the allowlist are
saved to the transport request.

In the change log, you see all changes related to allowlist objects.

Related Information

Processing Standard Changes [page 89]

Performing Transport-Related Checks [page 150]

4.4.6.5 Creating Cross-System Object Lock Entries

You can manage cross-system object lock entries in the administration cockpit.

Procedure

1. In the administration cockpit, go to Cross-System Object Locks Register .

2. Select a development system or choose all systems. You can also use the following options:

• You can restrict the range of transport requests by request number. For external requests, the
transport request number prefix (containing the external system name) can be different from the
real (internal) source system name.
• You can choose to send e-mail notifications if conflicts are detected: Default recipients are the change
managers (and for Change Control Management, also IT operators) of the change documents or QGM
changes that contain the transport requests with conflicts. You can also enter an additional e-mail
address.

 Note

To send a notification to the change manager and IT operator, the e-mail addresses must be
maintained for their business partners.

The system does not send any e-mail notifications to the transport request owners.

• You can specify the execution time (immediate or scheduled).

3. After you have registered the lock entries, to see the progress, monitor the job log.

Change Control Management

Change Request Management PUBLIC 331
 a. Call transaction SM36 (Define Background Job) and select Own jobs.
b. Find job CM_CROSS_SYS_OBJ_LOCK_REGISTER, scheduled to run at the time you specified, and open
Job Log.

When the job is finished, the job log refers to the application log. The application log contains detailed
messages, whereas the job log shows only the job progress.

Results

For each system, the application log displays the final processing result. You see warning messages for
transport requests that cannot be processed, and, for example, if the system does not find an e-mail address.

Next Steps

To check the application log, call transaction SLG1 with object /TMWFLOW/CMSCV and subobject
CROSS_SYS_OBJ_LOCK.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Downgrade Protection [page 360]

4.4.6.6 Cross-Reference Check

You can use the cross-reference check to detect inconsistencies for objects that are referenced in transport
requests.

Objects in transport requests sometimes refer to other objects that are not included in the transport. The
cross-reference check applies a where-used-analysis to check the referenced objects in transport requests. If
a referenced object doesn’t exist in the target system or if the referenced object in the source system has a
different version than in the target system, the check indicates a potential error. In addition, the check shows
the last transport requests for the missing object versions.

The cross-reference check can handle the following type of data:

• ABAP repository data.

• Dictionary objects
• Customizing objects

Logical transport objects and SAP HANA objects are not supported.

Git-enabled changes (SMGH) don’t use the cross-reference check.

Change Control Management

332 PUBLIC Change Request Management
The cross-reference check is triggered automatically when a transport request is exported from the
development system to follow-up systems or when a transport request is imported into a system. You can
also perform the check manually in the Transport-Related Checks assignment block on the WebClient UI.

It depends on the authorizations of the users whether they can ignore the error messages or warnings and
continue the action:

• Change Request Management: Administrators, change managers, and IT operators can ignore both errors
and warnings. Developers can ignore warnings.
• Quality Gate Management: QGM administrators, QGM change managers, and QGM IT operators can ignore
both errors and warnings. Developers can ignore warnings.

Prerequisites

• You have the installed the ST-PI plug in ST-PI 740 or ST-PI 2008.1 SP16 in the managed systems.
• You have implemented the SAP Notes listed in the collective note 2475591
• To display the Cross-Reference Check tab and change the settings for the cross-reference check, you have
the role administrator, change manager, or IT operator.

Configuring the Cross-Reference Check

In the Administration Cockpit, on the Cross-Reference Check tab, you can do the following:

• Deactivate or activate the check

• Configure general settings for the check
• Configure track-specific settings

You can specify the check mode that determines what happens when the check detects a potential error in a
transport request:

• In the default mode, only a warning is issued when you release the transport request and an error message
is issued and the import is blocked when you import a transport request.
• If you select the Stop at Error mode, the system always issues an error message and blocks the release or
import of the transport request.
• If you select the Warning Only mode, the system always only issues a warning.
• If you select Silent, you must check the transport request manually to get a conflict warning. There’s no
automatic check during release or import

 Note

Any settings that you make on the Cross-Reference Check tab in the Administration Cockpit are active
immediately.

Change Control Management

Change Request Management PUBLIC 333
Related Information

Performing Transport-Related Checks [page 150]

Administration Cockpit for Change Request Management [page 291]
Administration Cockpit for Quality Gate Management [page 535]

4.4.6.7 Transport Analysis Tab for Change Request

Management

Use

You can use the Transport Analysis tab to analyze the transport requests in your system landscape using
different views.

Prerequisites

You have created a change cycle.

Features

In the administration cockpit, on the Transport Analysis tab, you can use the following views:

• Cycle analysis
Display an analysis of all transport requests in a change cycle
• System analysis
Analyze all transport requests between two systems. You can compare two systems (for example, a
development system with a consolidation system, or two target systems) to check which transport
requests have been imported or exported.
• Request analysis
Display the transport logs for a transport request

When you click the links in the overview results, the system displays details about the transport requests at the
bottom of the screen.

The views display the number of transport requests and their statuses:

• Transport requests in the development system:

• Open: Modifiable transport requests
• Released: Released transport requests
• Transport requests in the target system:
• Waiting for Import: Released transport requests that have already reached the queue of the current
system. It includes the ones that have been preliminary imported but left in the queue.

Change Control Management

334 PUBLIC Change Request Management
 • Imported: Released transport requests that have been imported into the current system
• Import Error: Released transport requests that have been imported into the current system, but the
import resulted in an error.
• Missing Imports: Released transport requests that haven’t yet been finally imported into the current
system. These requests may or may not be in the queue of the current system.
• Sequence Violation: Transport requests that have been imported into the current system, but not in
the sequence in which they were released.

4.4.6.8 Scheduled Import Jobs

Use

You can display background jobs scheduled for importing transport requests independent of task lists, change
cycles, and target systems.

You can also display jobs from batch imports in Change Request Management. Jobs from batch imports do not
display a target system in the result list.

Procedure

To filter the background jobs scheduled for importing transport requests, use the following criteria:

• Target System
Select a system into which the transport request is to be imported.
• Cycle
Select the change cycle to which the transport request belongs (Change Request Management only).
• QGM Scenario
Select the scenario in which the transport request is imported (Quality Gate Management only).
• Task List
Select a task list that triggers the transport request import.
• Job Type
Select whether you want to see only import jobs or, for Change Request Management, status shift jobs for
batch reports.
• Job Status
Select one or more status the import jobs can have.
• Job Scheduled Date and Time
Filter for the time period in which the import job is scheduled to be executed.
• To see all jobs of every scheduled date and time, leave the date and time blank.
• To see all jobs scheduled for a specific time of day, define only the time and leave the date blank.
• To see all jobs scheduled after a specific point in time, define date and time only for the From criterion.
• To see all jobs scheduled prior to a specific point in time, define date and time only for the To criterion.
• Job Executed Date and Time

Change Control Management

Change Request Management PUBLIC 335
 Filter for the time period in which the import job is actually executed. Import jobs may be delayed due to
system resources or system environment, so they will not be executed exactly as scheduled.

 Note

If you tick the checkboxes Finished and Canceled in the Job Status section, you can select all change
cycles, QGM scenarios, or task lists in the respective dropdown menus. Otherwise, the system only
displays the active ones.

In the search result list, you can perform the following activities for the background jobs:

• Display variant of a job (for single selection only)

• Show log of an import job (with status Finished)
• Delete an import job (excluding status Finished and Canceled)
• Cancel an import job (with status Active).
• Redefine an import job based on an existing one (excluding status Finished and Canceled; for non-multi
selection). A dialog box appears in which you can reschedule the job.

4.4.6.8.1 Handling Import Jobs During Cycle Switch

When you switch a current cycle to a new cycle or close a current cycle, the active import jobs assigned to the
current cycle are handled automatically.

For continual cycles and phase cycles:

• When you swich cycles, all ongoing scheduled import jobs of the current active cycle are removed. New
import jobs with the same job variants are rescheduled in the new cycle.
• When you close a cycle, all ongoing scheduled import jobs of the cycle are removed.

For release cycles:

• When you set the release cycle to the Hypercare phase, all ongoing scheduled import jobs are kept in the
current release cycle.
If a successor release cycle follows a cycle switch, new import jobs with the same job variant are scheduled
for the successor release cycle.
• When you set the release cycle to the Retired phase, all ongoing scheduled import jobs in the current
release cycle are removed.

Related Information

Scheduled Import Jobs [page 335]

Overview of Scheduled Import Jobs [page 530]

Change Control Management

336 PUBLIC Change Request Management
4.4.6.8.2 Setting up E-Mail Notifications for Cycle-Level
Scheduled Import Jobs

Set up an e-mail notification service that informs you when a cycle-level scheduled import job was terminated
because of blocking conflicts that were detected during transport-related checks.

Prerequisites

• You need an e-mail address for the e-mail sender (parameter DEFAULT_SENDER_EMAIL) and a business
partner (BP) number for the receiver (parameter RECEIVER_BP).
• If you want to send notification e-mails to several users, you need to assign the business partners of these
users to an organizational unit with an employee relationship. The organizational unit BP is needed for
parameter RECEIVER_BP.

Context

You’ve scheduled an import job for a change cycle. Now, you want to make sure that a notification e-mail is sent
out when the import job is terminated because of a blocking conflict that was detected by transport-related
checks.

Procedure

1. Under SAP Solution Manager Implementation Guide SAP Solution Manager Capabilities (Optional)
IT Service Management Define Action Profile Change Actions and Conditions , open the Define Action
Profiles and Actions Customizing activity.
2. Change to edit mode (  ).
3. Under Action Profile, select the <type of cycle>_ACTIONS action profile.
4. Under Dialog Structure, choose Action Definition.
5. Under Action Definition, select <type of cycle>_SEND_MAIL_IMPORT_JOB.
6. Under Dialog Structure, choose Processing Types.
7. Under Settings Method Call, choose Change Definition (  ) to open the Container Editor.
8. Choose DEFAULT_SENDER_EMAIL.
9. Under Initial Value, add the sender's e-mail address.
10. Choose Confirm (  ).
11. Choose RECEIVER_BP.
12. Under Initial Value, add the business partner number or the organizational unit BP that contains the
business partners that should receive the notification e-mail.

Change Control Management

Change Request Management PUBLIC 337
  Note

The sender (DEFAULT_SENDER_EMAIL) and the business partner (RECEIVER_BP) must be two
different people with different e-mail addresses.

If the sender and the business partner have the same e-mail address, the notification e-mail is not sent
out.

If the business partner of an employee under the organizational unit has the same e-mail address as
the sender defined in parameter DEFAULT_SENDER_EMAIL, no e-mail is sent to any user.

13. Choose Confirm (  ).

14. Choose Apply Entries (  ).

Related Information

Performing Transport-Related Checks [page 150]

4.4.7 Dual Landscape Synchronization (Retrofit)

Retrofit helps to synchronize changed objects (both customizing and workbench) from maintenance
development system to project or upgrade development system in dual track landscapes (also known as N
1 landscapes). In contrast to manual synchronization of transport requests with changed objects between
development systems, retrofit allows to detect and manage conflicts when the same object changed in both
systems. You can use the retrofit functions with a Change Control Management scenario (Change Request
Management or Quality Gate Management), or standalone.

Use

In system landscapes in which several releases are processed at the same time, similar changes can be made
in different development systems. For example, new developments can be made in the new implementation
development system, while at the same time, errors are corrected or improvements are made in a maintenance
system for the production system landscape. The system release levels must be adjusted regularly to ensure
that changes are synchronized in parallel across different system landscapes. This synchronization is called
retrofitting.

Change Control Management

338 PUBLIC Change Request Management
 A Phased System Landscape as an Example of System Relationships

Related Information

Setting Up Retrofit [page 354]

Performing the Retrofit [page 345]
Standalone Retrofit [page 356]
Tool-Assisted Retrofit [page 348]
Displaying Import Information from the TMS [page 316]

4.4.7.1 Retrofit Categories

Retrofit categorizes transport objects for automatic (green), tool-assisted (yellow), and manual (red)
processing.

You can see the processing mode and categorization reason for each object on the transport request in the
object list.

For more information about the objects in the transport request, select the traffic light icon. The system
displays the log for this transport request, as well as SAP Notes in the transport requests, because they are
transport-critical, and can cause problems in the retrofit system.

Change Control Management

Change Request Management PUBLIC 339
  Tip

In Customizing, you can define object types for specific scenarios (retrofit scenario for Business
Warehouse objects, retrofit scenario for manual processing). Objects of these object types are always
retrofitted manually. Use the retrofit scenario for manual processing (parameter SCEN_MAN) to define the
objects that you want to exclude from automatic retrofit.

Retrofit Processes According to Categorization

Category Process Object Types Supported Can Be Used For

Green Automatic All object types (Business • Objects without cross-

Warehouse objects are parti- system object lock in the
The object can be imported
ally supported) retrofit system
automatically using ToC
(transports of copies).
• Objects that weren’t
changed in the retrofit
system

Yellow Tool-Assisted Correction Workbench: • Objects with cross-sys-

Workbench objects tem object lock in the
The object can be retrofitted
retrofit system
with post-processing tools, Business Configuration Sets:
either SCWB (workbench) or Customizing objects
• Objects that were
changed in the retrofit
the BC set (Customizing).
system

Change Control Management

340 PUBLIC Change Request Management
Category Process Object Types Supported Can Be Used For

Red Manual Objects that cannot be im- All other objects:

ported automatically and
The object must be proc- • Objects locked in the
that aren’t supported by the
essed manually. target system
postprocessing tools
• Objects not suitable for
a tool-assisted synchro-
nization
• Objects containing an
SAP Note
• Objects containing spe-
cial content (for exam-
ple, PFCG)
• it does not exist but is
critical for activating a
BC set
• the scenario check re-
calculation was not suc-
cessful
• the scenario check re-
calculation FM was not
specified
• the cross scenario check
detected an SAP object
• the cross-scenario
check detected changes
in a view
• the cross-scenario
check detected changes
in a table
• the ATC (ABAP Test
Cockpit) Central Check
System detected a
change affecting SAP S/
4HANA
• an error had occurred
generating the BC set
• no RFC destination was
found
• a general internal error
had occurred during the
object check

Change Control Management

Change Request Management PUBLIC 341
  Note

If an object has been changed in the maintenance development landscape, but the same object has not
been changed in the implementation development landscape, in the retrofit system, a cross-system object
lock is not created, and you can use the auto import option for retrofitting.

The system collects all objects that do not have any conflicts in a transport of copies. The system imports
the transport of copies directly into the retrofit development system and copies the objects to the target
transport request, in order to distribute them to the development-implementation system landscape.

Related Information

Dual Landscape Synchronization (Retrofit) [page 338]

Performing the Retrofit [page 345]

4.4.7.2 Retrofit Checks

You can perform retrofits for systems that are on different support package, enhancement package, or release
levels (cross-release retrofit). The system performs several checks to ensure that no downgrade occurs.

Check for Customizing objects

If table structures, views, or view structures have changed, the object is set to “manual retrofit”.

 Note

If you retrofit ERP to SAP S/4HANA and you have set up an ATC (ABAP Test Cockpit) Central Check
System, SAP S/4HANA objects are set to“manual retrofit”.

As a development user, you can manually select “automatic import” for each object.

Check for Workbench objects

SAP objects are set to “manual retrofit”.

Check for SAP Notes

SAP Notes cannot be retrofitted.

Check for conflicts in PFCG roles

If there are conflicts for some of the dependent objects of a role, the role and all of the dependent objects of the
role are set to “manual retrofit”.

 Note

The table AGR_DEFINE (logical object ACGR, role definition) has been chosen to represent all dependent
objects. Instead of checking all dependent objects of a role separately, the cross-system object lock checks
if the table AGR_DEFINE and the personalization data (table /TMWFLOW/CSOLPER) exist for the role, and if

Change Control Management

342 PUBLIC Change Request Management
 they can be released for an automatic retrofit. If not, the role and all dependent objects must be imported
with a manual retrofit.

For the transport of a derived role, not only the derived role but also the root role is checked. If the root role has
a conflict, you must perform a manual retrofit to transport the derived role.

4.4.7.3 Additional Functions in Retrofit

You can use additional functions to prepare and process the retrofit.

Retrofit Status
See the status of the transport request and its objects. You can filter the objects according to their status.

• Process Retrofit: Transports that haven’t been processed yet

• Manual Retrofit: Transports that were manually retrofitted
• Retrofitted: Transports that have been processed
• Retrofit Rejected: Transports that have been rejected for retrofit

Object List of the Transport Request

See the objects included in the transport request that you want to retrofit, including the object types and the
specific target transport request of each object.

Sequence Dependency
Indicates whether a transport request is dependent on other transport requests. If you choose the icon in the
field, the system lists the transport requests that belong to the sequence-dependent requests. If there’s no
sequence dependency, for example, several users can process a retrofit.

 Example

Transport request A contains object X, which is already in transport request B. Thus, there’s a sequence
dependency between transport requests A and B.

The sequence dependency implies the following:

• A transport request can have a sequence dependency to more than one other transport request, that is,
different objects are in different transport requests.
• There’s just one sequence dependency for an object X between transport request A and transport request
B if transport request B is the only request with object X or is the request that was last released. There can
also be a sequence dependency between transport request B and a third transport request.
• The sequence dependency is based on the objects in the object list for the entire retrofit queue. It’s
updated or deleted as soon as the retrofit for a transport request is completed.
• If there’s no sequence dependency, and some requests haven’t yet been processed, the system displays a
message. You can specify in the Customizing settings whether the message is to be displayed as a warning
or as an error.
• For customizing objects, sequence dependency will be calculated only on object level but not on table key
level.

Change Control Management

Change Request Management PUBLIC 343
Consistency Check
The system checks whether the retrofit was prepared correctly:

• Have transport requests been created in the retrofit system into which you want to import the changes
from the maintenance system?
• Has the execution sequence of the transport requests to be imported been observed?
• Does the transport request contain objects from SAP Notes that could cause conflicts during the import?

Display Logs and Display Old Logs

Read messages for the transport requests.

If a log exists, it is displayed automatically in the following situations:

• When you select a retrofit entry in the retrofit overview (same functionality as “Display Log”).
• When you process an action

Select Display old Logs to see old logs sorted by timestamp, and select one for details.

Display and Edit BC Sets

See and process transport requests that contain Customizing objects. For more information, see Copying
Changes Using the Correction Workbench and BC Sets [page 348].

TMS Alert Viewer

See import information from the Transport Management System. For more information, see Displaying the
TMS Alert Viewer [page 316].

Show Requests
• To see the source transport request in the development system of the maintenance landscape, select
Request / Task.
• To see the target transport request in the development system of the project landscape, select Retrofit
Request.

Add Note
You can add a note with information to a transport request, for example, the reasons for manually processing
objects.

Implement SAP Notes

Find SAP Notes relevant to the selected retrofit entry and open the Note Assistant (transaction SNOTE) to
implement them.

Create Retrofit Data Again

If an error occurred during the creation of the retrofit data (for example, because no categorization is done,
or the RFC connection wasn’t available), you can use this option to create new retrofit data for the selected
transport request. Note that the latest versions of the relevant objects are used.

Set/Reset Manual Status

Flag transport requests that haven’t been processed by the retrofit process tools, as completed. The status of
the selected transport request in the overview changes to Manual Retrofit. When you re-execute this step, the
previous action is undone.

Change Control Management

344 PUBLIC Change Request Management
Set/Reset Rejected Status
Prevent transport requests from being processed, for example, because the change is no longer required. The
status of the selected transport request in the overview changes to Retrofit Rejected. When you re-execute this
step, the previous action is undone.

Structure Comparison
This additional function is only visible in the SAP S/4HANA upgrade scenario.

The system analyzes the selected transport request. The system compares the structure for all included tables
and views and identifies the differences. The following status values are possible for the field differences:

• Added: The field has been added in the retrofit target system
• Removed: The field has been removed in the retrofit target system
• Shorter: The field is shorter in the retrofit target system
• Longer: The field is longer in the retrofit target system
• Typediff: The field has a different type in the retrofit source and target system
• Keydiff: The table key is different in the retrofit source and target system

Check Customizing Objects

This additional function is only visible in the SAP S/4HANA upgrade scenario.

The system shows the possible impact on the customizing objects in a transport request. This helps to
understand whether a customizing object can be retrofitted automatically (green rating) or not (red rating).
The displayed table includes the following columns:

• STRU: Uncritical structure difference in table or view (without impact on transportability)

• STRUCRIT: Critical structure difference in table or view
• SDB: Object is in the simplification database
• BL: Object is on the exclude list
• WL: Object is on the include list
• RES: Overall result ("X" means not transportable and manual retrofit)

4.4.7.4 Performing the Retrofit

Use this process to find transport requests available for retrofit, check the status of each transport request and
the objects in the requests, and perform the retrofit.

Prerequisites

• Your systems are set up to support the retrofit function, see Setting Up Retrofit [page 354].
• In both development systems and in the 000 clients of these systems, you have the required
authorizations.
• You have created transport requests for the retrofit in the retrofit system into which you want to import the
changes from the maintenance system.

Change Control Management

Change Request Management PUBLIC 345
• For Change Request Management: Your change document has the status Successfully Tested, Authorized
for Production, Imported into Production or Confirmed (urgent change) or Successfully Tested (normal
change, standard change).
• For standalone retrofit: You have performed the preparation as explained in Standalone Retrofit [page
356].

Context

You can use retrofit with a Change Control Management scenario (Change Request Management or Quality
Gate Management) or standalone.

 Note

To see explanations for all symbols used on the screen, select Legend. For more information, see Additional
Functions in Retrofit [page 343].

Procedure

1. To see the transport requests available for the selected retrofit system, start the retrofit process.

• For Change Request Management: In your change document, select Actions Start Retrofit .
• For Quality Gate Management: Select Scenario Transport Start Retrofit .
• For Standalone Retrofit (without Change Control Management scenario), you start the retrofit in the
administration cockpit, directly from the task list.

By default, the system only displays transport requests that are released and those for which the retrofit
isn’t finished yet.

Transport requests are categorized (green, yellow, red) according to the objects on the transport.

 Note

You must process the transport requests in the specified sequence, matching the release date of the
source transport request.

2. For each transport request, specify the retrofit request in the retrofit system into which the changes are to
be imported.

You see the transport requests owned by you and the transports requests in which you have a task. The
transport request in the system determines the adjustment.
3. Open the respective object list of a transport request and check the retrofit status for each of the objects.

The color (green, yellow, and red) indicates the status of the object. If the retrofit has been implemented,
the implementation status is “I”. You can set a status for multiple objects.

You can filter the objects according to their status. You can also compare the objects in the source and
retrofit systems. The object list shows the specific target transport request into which an object was

Change Control Management

346 PUBLIC Change Request Management
 transported. Correction workbench objects (SCWB scenario) can have a different target transport request
depending on the transport requests in which the objects were locked in the retrofit system.
4. Select the transport request you want to process, and choose a retrofit method.

• Retrofit for All Categories: The retrofit is performed for all objects in this transport request. The relevant
method is applied based on the object type and status.
• Auto-Import: The retrofit is performed for the objects that can be imported automatically. The system
collects all objects that don’t have any conflicts in a transport of copies. The system imports the
transport of copies directly into the retrofit development system and copies them to the target
transport request, in order to distribute them to the development implementation system landscape.
• Transfer with SCWB: The retrofit is performed for the objects supported by the Correction Workbench.
• Transfer with BC Set: The retrofit is performed for the objects supported by BC Sets.

For transport requests containing green, yellow, and red objects, use the functionalities and procedures in
the following order:
a. Green objects can be imported automatically.
b. Yellow objects can be retrofitted with BC-Sets or the SCWB.
c. Red object must be retrofitted manually.
5. Before an automatic import, the system always rechecks the retrofit classification to ensure consistency
and security. If there are any cross-system object locks that were not detected before (that is, a former
conflict-free object now causes a conflict with the retrofit system), a popup informs you that a repeated
check of retrofit data has returned differences in categorization. In this popup, you have the following
options to proceed:
• Close/Display object list – Toggle list with changed classification objects
• Help  – Shows a help text explaining the issue shown here in more detail
• Recalculate category and proceed – Recreate the retrofit data to resolve the conflicts shown and
continue with the retrofit process.
• Ignore warnings and proceed – Ignore the conflicts shown and continue with retrofit process. You may
risk unwanted overwriting of objects in target system.
• Cancel  – Cancel retrofit process and return to retrofit overview screen with the processing log. All
activities you made on this popup are logged here.
6. Use the retrofit status inquiry to state whether the retrofit was completed successfully.

You must specify this because the absence of object transfer warnings only means that there were no
technical system errors. Cancelled procedures don’t cause errors, so you must confirm that you have
completed the procedure successfully, manually.
• When you set the retrofit to completed successfully, the transport requests no longer appear in the
transport request overview for the retrofit.
• If you specify the retrofit as not completed successfully, the transport requests remain in the transport
request overview for the retrofit, and continue to show the retrofit status Process Retrofit.

Results

• The monitored transport from the maintenance system into the development system is completed.
• In the task list daily overview, the system shows the entry Start Retrofit at the time that you executed the
retrofit.

Change Control Management

Change Request Management PUBLIC 347
Next Steps

To leave the retrofit transport request window, choose End.

To display the retrofit application log, double-click on Start Retrofit in the daily overview. The log displays all
messages for the retrofit steps. You can also display the retrofit status in the WebClient UI, in the Transport
Management assignment block.

If an error occurred during the creation of the retrofit data (for example, because no categorization is done, or
the RFC connection wasn’t available), you can choose Additional Functions Create Retrofit Data Again to
create new retrofit data for the selected transport request. Note that the latest versions of the relevant objects
are used.

 Note

You can change the recheck settings in Customizing under SAP Solution Manager Capabilities
Change Request Management Retrofit Maintenance of Retrofit Parameters .

Related Information

Change Documents [page 26]

Managing Transport Requests [page 118]

4.4.7.5 Tool-Assisted Retrofit

Objects with cross-system object locks in the retrofit system, or that were changed in the retrofit system, can
be retrofitted with postprocessing tools.

For such semi-automatic retrofit, you can use the following tools:

• Correction Workbench (transaction SCWB): For changes to program, dictionary, and documentation
objects (in transport requests of type “Workbench”)
• Business Configuration Sets (BC Sets): For changes to Customizing content (in transport requests of type
“Customizing”)

Features

• Detailed change display in the merge editor, comprising the split-screen editor and the table changes
display
• Traffic light icons that indicate which objects are changed when the changes are copied, and whether the
changes can be copied completely, partially, or not at all

Change Control Management

348 PUBLIC Change Request Management
More Information

• Merge Editor [page 352]

• Split-Screen Editor [page 353]
• Business Configuration Sets

4.4.7.5.1 Retrofit Using the Correction Workbench (SCWB)

Use the Correction Workbench for changes to program, dictionary, and documentation objects.

Prerequisites

• A trusted RFC connection has been established from the retrofit system to the development system.

 Note

The user performing the retrofit needs sufficient authorization to create RFC connections on the
managed systems, because the RFC connection is generated automatically when the first retrofit
activity is performed with the Correction Workbench.

• You have prepared the retrofit. For more information, see Retrofitting Transport Requests [page 345].
• The selection screen for transport requests is currently displayed.

Context

You can use the Correction Workbench to copy changes that you made in the development or maintenance
systems and that are not imported automatically. The Correction Workbench performs a remote delta
comparison between the retrofit system and the development system.

Procedure

1. Select your change request or task and choose Transfer with SCWB.

The Confirm Changes dialog box appears, containing a list of all changed repository objects.

 Note

A traffic light symbol indicates whether or not the system can copy the change automatically. You can
find more information about the traffic light icons under Confirm Changes [page 351].

Change Control Management

Change Request Management PUBLIC 349
  Caution

A green traffic light does not mean that the system can copy the changes completely. If the starting
status is different in the source system and the retrofit system, the green traffic light does not
guarantee that copying the changes result in a program that is syntactically and semantically correct.

You must check the accuracy of the program yourself after copying the changes. This is your
responsibility.

2. Note the detailed change display (Merge Editor [page 352]) and the messages displayed for the object.

To access the detailed change display for an object, click the object name in question.

 Note

If necessary, you can make manual adjustments to source code changes here (see Splitscreen Editor
[page 353]). This type of adjustment isn’t possible for non-source code type repository objects (such
as function modules).

3. If you want to copy the changes, select all objects to be changed that have either a green traffic light
(complete copy possible) or a yellow one (limited copy possible). Confirm the dialog with the list of objects
to be changed.

 Caution

The system only changes objects that you have selected.

At first, the system saves the changed objects as inactive versions in the database.

The Inactive Objects Belonging to <USERNAME> dialog box appears.

4. Activate the changed objects and confirm by choosing Continue.

The system checks the syntax in the changed objects. If it finds any syntax errors, the system cancels
activation.
5. Confirm the syntax check.

The Retrofit Status Query dialog box appears.

6. Choose Yes, No or Cancel.

Using a traffic light display, the system creates a log of the status of the change copy and the retrofit in the
task list.

Results

You can now test the semantic and syntactical accuracy of the change that you’ve copied in the retrofit system.
If you don’t find any errors, you can release the change request previously created in the retrofit system.

Change Control Management

350 PUBLIC Change Request Management
Next Steps

If not all objects were processed successfully with Transfer with SCWB, repeat the procedure with the different
target requests in which the target objects were locked in the retrofit system until all objects are successfully
transferred into the retrofit system.

4.4.7.5.2 Retrofit Using Business Configuration Sets

The system creates the Business Configuration set (BC-Set) locally on the development system. During the
retrofit process, the system transfers it to the retrofit system and it gets activated there.

Prerequisites

• You have established a trusted RFC connection from the development system to the retrofit system.

 Note

The user performing the retrofit needs sufficient authorization to create RFC connections on the
managed systems, because the RFC connection is generated automatically when the first retrofit
activity is performed with BC sets.

• You have switched on the deletion functionality for BC sets. Call transaction SCPR20 and go to Utilities
User Settings Maint. Transaction .

4.4.7.5.3 Confirm Changes

This dialog box indicates which objects will be changed by copying the changes, and whether the changes can
be copied completely, in part or not at all. If you confirm this dialog, the system copies the changes to the
specified objects. If you cancel, the system will not make any changes.

Features

Traffic light icons show you whether the system can copy the changes:

• Green traffic light: The system can copy the changes completely as they are.
• Yellow traffic light: The system can only copy the changes in part.
To ensure that the object changes are implemented correctly, you can use the split-screen editor to adjust
corrections to the source text in a repository object. Corrections to other types of data, such as the
properties and parameters of a repository object, can be displayed but not changed.
To open the the object change display screen and check object changes or edit the source code, click the
object name or the traffic light icon.

Change Control Management

Change Request Management PUBLIC 351
• Red traffic light: The system cannot copy the object changes.
This can have various causes, such as the object not being supported by this function, being locked in
another change request, or not existing.

There’s a message text for each object (for example, “changes have not been copied completely”). Select this
message to read a long text with detailed information.

4.4.7.5.4 Merge Editor

The merge editor shows the changes made to a repository object when you copy an object change. If the
changes are already in your system, completely or partially, the system tells you so. The system also tells you if
it can’t copy the change because of differences between the source and retrofit systems.

Features

The Merge Editor has two subfunctions:

• Split-screen editor:
This function provides a detailed display of all changes to the source text in a repository object. You can
also adjust the changes manually here.
• Display table changes:
This function provides a detailed display of all changes to the table entries for a repository object. Unlike in
the split-screen editor, you can’t make manual changes here.

 Caution

This is an expert function that requires detailed knowledge of ABAP Workbench. The main purpose of
this function is for troubleshooting by SAP support.

Activities

Source text changes

Source text changes are shown in the split-screen editor [page 353].

Table content changes

The non-source text parts of a repository object are put in database tables. The change display shows the table
contents for a repository object, with the changes to be made to it. This display helps experts to troubleshoot
when problems arise while copying changes. You can’t change table contents manually. The change display for
a table contains the entire table contents plus additional information about changes made or not made. The
first column in the display contains a symbol specifying which operation is to be performed on a table entry.

Change Control Management

352 PUBLIC Change Request Management
You can do the following:

• Insert a row
• Delete a row
• Change non-key fields
• Move a row and change non-key fields. (In this case, the first two columns are used for the operation.)
• Make no changes to the row

A traffic light symbol in the second column indicates whether the operation is possible. The remaining columns
contain the table content. The display contains rows with additional information about the changes to be
made, as well as the table contents rows. If you copy changes, this additional information is not written to the
database.

• For non-key field changes, the old field value is displayed in an additional row directly below the changed
table row. If you can’t change the field value, the unchanged row is displayed in the table row, and the old
row to be deleted and the new value in two rows below it.
• If a row can’t be inserted because the insertion position - the row that should be directly before the
insertion position - can’t be found, the system displays the row to be inserted and the key values of the row
that couldn’t be found, in two additional rows at the end of the table.
• Rows to be deleted are displayed in additional rows.

Changes to files
Files in repository objects are not changed when changes are copied, they’re just created or switched.
Examples of this are Mime objects or files used by Internet Transaction Server as Mime objects. Whenever
you copy changes, the system displays the files to be deleted or created. To display the files, double-click on
the entry in the navigation area, or select the entry and choose F2.

4.4.7.5.5 Split-Screen Editor

In the split-screen editor, you see the details of all changes to the source text of a repository object. You can
adjust the changes to your own modifications here.

Features

The split-screen editor has two areas:

On the left-hand side, you see the source text as it appears after copying changes. Next to the source text rows,
symbols indicate the changes:

• Context rows, that is, unchanged rows that system used to find the position at which to make changes.

• Inserted rows

• Deleted rows

• Unchanged rows

On the right-hand side, you see deleted program components and corrections that the system cannot
automatically take over. These are flagged by symbols as context, delete, and inset blocks.

Change Control Management

Change Request Management PUBLIC 353
Activities

On the left-hand side, you can:

• Edit manually
• Select, delete, copy, and insert blocks
To select a block and highlight it, position the cursor on the header row and choose Select.
You can also select rows. Position the cursor on the first row of the block you want to select, and choose
Select. Then position the cursor on the last row and choose Select again.
• Reset all changes that you have made in the split-screen editor, one-by-one, with Reset Changes (Undo)
• Restore changes that have been reset, with Restore Previous Status (Redo)
• Navigate forward to the next change, or back to the last one, with the arrow keys
• Merge two rows with Concatenate
The Undo/Redo function appears between the left and right-hand side of the editor, whenever a block is
inserted or deleted. You can use these functions to reset or restore individual changes. When you do this,
individual delete and insert blocks are swapped over.

4.4.7.6 Setting Up Retrofit

Your system must be configured to use retrofit.

Procedure

1. In the managed systems, implement SAP Note 1703391 .

2. Open SAP Solution Manager Configuration (transaction SOLMAN_SETUP) scenario Change Control
Management and perform the required settings in the following guided procedures:

a. Change Request Management Configure Retrofit

b. Managed System Setup Configure Retrofit

 Note

If you want to use cross-release retrofit, ensure that you have activated the Cross-Release Retrofit
parameter and that you have defined for which systems the cross-release retrofit is to be allowed,
under Define System-Specific Retrofit Settings.

Do not activate the Cross-Release Retrofit parameter and the Cross Release Checks for S/4HANA
parameter in parallel for the same retrofit target system.

 Note

If you want to use the SAP S/4 HANA conversion check enhancement, ensure that you have
activated the Cross Release Checks for S/4 HANA parameter, under Define Retrofit Parameters. For
more information, see SAP S/4HANA Upgrade Scenario [page 358].

Change Control Management

354 PUBLIC Change Request Management
 To know more about the checks that are performed if this option is chosen, uncollapse the Checks
Performed table:

Checks Performed
Conflict check Check if the table key was already changed in S/
4HANA (customizing conflict).

Simplification DB check Check if the customizing object is listed in the SAP S/

4HANA simplification DB as part of a relevant release
(between the retrofit source and target release).

Exclusion check Check if the object is added in the customer-individ-

ual exclude list.

Inclusion check Check if the object is included in the customer-indi-

vidual allow list. The allow list can overrule the previ-
ous checks (except for the conflict check) if a test
shows that the object can be retrofitted automati-
cally. This can be evaluated for frequently changed
customizing tables.

Structure check Check if the technical structure of the table or view is

different in source and target (for object types: TABU,
VDAT, CDAT, TDAT, TLOGO).

3. Make sure both systems that are to be part of the retrofit scenario are in the same transport management
system (TMS) domain or in linked TMS domains.
4. Activate the retrofit function in SAP Solution Manager. For more information about using an RFC trusted/
trusting relationship between two SAP systems, see System Users and RFC Destinations with Trusted
Systems.
5. Activate the cross-system object lock globally. In the administration cockpit navigate to Cross-System
Object Lock and Downgrade Protection Cross-System Object Lock and Downgrade Protection Settings
Activate Cross-System Object Lock .
6. Activate cross-system object lock for the retrofit target system. In the administration cockpit, navigate to
Landscape Overview and activate the Upon-Saving Check for the retrofit target system. Add BACK RFC
user authorizations as described in SAP Note 2745405 .
7. Set up the following RFC connections in SAP Solution Manager, for each working client specified in the
logical components used to represent each system landscape, the maintenance landscape, and the new
development landscape. This includes the TMS landscape domain controller systems.
• SM_<SID>CLNT<...>_TMW
• SM_<SID>CLNT<...>_TRUSTED

These RFC connections must be established from SAP Solution Manager to the development landscape
and from SAP Solution Manager to the maintenance landscape.

 Note

Additional RFC connections are created automatically when the retrofit scenario is activated in SAP
Solution Manager.

For more information, see SAP Note 1175098 .

Change Control Management

Change Request Management PUBLIC 355
8. In both development systems, assign the following authorization objects to the users who are going to
perform retrofit:
• S_RFC_ADM
• S_TRANSPORT
• S_SYS_RWBO
9. Define a change control landscape that contains development systems and retrofit systems.
10. For managed systems used as retrofit systems, be aware of the following conditions:

If a client is assigned to a productive client role, the BC Set function is disabled for all system clients. You
can avoid this by selecting a nonproductive client role in the system.

In addition, if a client is not assigned to any client role, set the role to “Customizing” to activate the BC Set
for retrofit. To activate the BC Set function for the logical system, proceed as follows:
a. Call transaction SCC4.
b. In edit mode, double-click on the respective client to open the Details screen.
c. Set the client role to Customizing.
d. Save your changes.

Next Steps

If you want to use the standalone retrofit function without Change Request Management or Quality Gate
Management, proceed as explained in Standalone Retrofit [page 356].

If you want to use retrofit for SAP S/4HANA in your SAP S/4HANA landscape with additional functionality,
proceed as explained in SAP S/4HANA Upgrade Scenario [page 358].

To check your retrofit configuration for your entire landscape, you can use the
RETRO_SERVICE_CONFIG_CHECK report. For more information, see the report documentation.

4.4.7.7 Standalone Retrofit

You can use the retrofit functions without the Change Control Management scenarios (Change Request
Management or Quality Gate Management). This approach includes all standard retrofit functions, however,
you handle the retrofit functions via the task list.

Prerequisites

You made the settings as explained in Setting Up Retrofit [page 354].

For standalone retrofit, perform the following additional preparatory steps:

1. In SAP Solution Manager Configuration (transaction SOLMAN_SETUP), configure the required settings
under Change Control Management Managed System Setup Configure Extended Functions
Configure Retrofit .

Change Control Management

356 PUBLIC Change Request Management
2. In SAP Solution Manager Configuration, under Change Control Management Change Request
Management Setup Downgrade Protection and Retrofit Configure Retrofit Define Retrofit
Parameters , activate the STANDALONE parameter.
3. Create a change cycle for the implementation landscape for assigning transport requests that are not
yet assigned to a cycle. You do this so that you can use them within the Change Request Management
framework.
4. Create a change cycle for the maintenance landscape for assigning transport requests that are not yet
assigned to a change cycle.
5. Implement the Business Add-In CTS_EXPORT_FEEDBACK in accordance with SAP Note 2179147 .
6. In SAP Solution Manager Configuration, under Change Control Management Managed System Setup
Configure Extended Functions Configure Retrofit Prepare Implementation Landscape for Retrofit ,
select the already existing transport requests created in the development system of the implementation
landscape that you want to be included in the standalone retrofit scenario and register them to the cycle
created for the implementation landscape.
This creates the entries in table /TMWFLOW/CTS_MAP for the mapped CTS projects to the CTS project
created for the implementation cycle and also the CSOL entries for the corresponding objects in these
transport requests. These CSOL entries are needed for retrofit.
7. In SAP Solution Manager Configuration, under Change Control Management Managed System Setup
Configure Extended Functions Configure Retrofit Prepare Maintenance Landscape for Retrofit , select
the already existing transport requests created in the development system of the maintenance landscape
that you want to be included in the standalone retrofit scenario and register them to the cycle created for
the Maintenance landscape.
This creates the entries in table /TMWFLOW/CTS_MAP for the mapped CTS projects to the CTS project
created for the maintenance cycle and also the retrofit data for the corresponding objects in these released
transport requests.
Note that for the creation of retrofit entries, the active version of the object is used.

Context

You can use this approach and start using Change Control Management later on.

Procedure

1. In the Administration Cockpit, in the task list, create and release transport requests.
2. In the relevant system, for example, in the implementation system, create the target transport request.

The system creates the data for the retrofit process.

3. Start the retrofit by executing the relevant task in the cycle that was created for the maintenance
landscape.

Change Control Management

Change Request Management PUBLIC 357
Next Steps

Performing the Retrofit [page 345]

If you want to use retrofit for SAP S/4HANA in your SAP S/4HANA landscape with additional functionality,
proceed as explained in SAP S/4HANA Upgrade Scenario [page 358].

4.4.7.8 SAP S/4HANA Upgrade Scenario

Use retrofit for SAP S/4HANA in your SAP S/4HANA landscape with additional functionality. This includes
advanced checks (ATC checks and customizing checks) for compatibility when synchronizing workbench and
customizing objects from a lower to a higher SAP S/4HANA release or support package level.

Prerequisites

• You have set up retrofit either as part of a Change Control Management scenario as explained in Setting Up
Retrofit [page 354] or as a standalone function as explained in Standalone Retrofit [page 356].
• All the included systems are SAP S/4HANA systems (source and target).
• The landscape management database (LMDB) contains the correct information of the retrofit system.
Therefore, the product version (SAP S/4HANA <target release>) and product instance (SAP S/
4HANA server) must be maintained.
• You have configured an ATC Hub (central scenario) and connected the development system (retrofit
source system) as an Object Provider (as described in the document Custom Code Migration Guide for SAP
S/4HANA available in the SAP Help Portal in the section Conversion & Upgrade Assets).

Procedure

Configuring ATC Hub Checks for Custom Code

1. Connect SAP Solution Manager to the ATC Hub.

1. In SAP Solution Manager, use transaction DNO_CUST04.
2. Specify the field name and field value. Entries for name, description and seq. No. are optional.
3. As the field name, enter ATC_HUB_RFC.
4. For the field value, enter a connection that has enough authorizations to start remote ATC checks in
the ATC Hub system (for example the SAP TMW connection SM_<SID>CLNT<CLNT>_TMW).
5. Use transaction SM30 to maintain the table /TMWFLOW/RSCENS4 with the following values:
1. ExtSID: Enter the SID of your retrofit target system.
2. ATC Check: X
3. Check Variant: If left empty, the standard variant S4HANA_READINESS_<target_release> is
used for the ATC check in the retrofit system. Only enter a variant name if you want to use a
modified version of this variant.

Change Control Management

358 PUBLIC Change Request Management
Configuring SAP S/4HANA Checks for Customizing

1. Implement the SAP Notes 2825417 and 2841592 in the managed development systems. If you have
maintained the parameter ATC_HUB_RFC in transaction DNO_CUST04 of SAP Solution Manager, these
notes must also be implemented in the ATC Hub system.
2. Set up custom SAP S/4HANA retrofit checks.
1. In SAP Solution Manager, use transaction SM30 to edit the table /TMWFLOW/RCONFIG and set the
parameter SCEN_S4CHK to Active.
2. Use transaction SM30 to maintain the table /TMWFLOW/RSCENS4 with the following values:
1. ExtSID: Add the SID of your retrofit target system.
2. Cus. Check: X
3. Update the simplification database. If you have specified an ATC_HUB_RFC in transaction DNO_CUST04,
you must update the simplification database in the ATC Hub system. If you haven’t specified an
ATC_HUB_RFC, you must update the simplification database in the retrofit target system:
1. Follow the steps described in SAP Note 2241080 .
4. (Optional) Maintain the exclude list that can be used to categorize incompatible customizing tables or
views for manual retrofit (red category). This can be necessary for customizing certain third-party add-ons.
For SAP standard objects, this is not necessary in the SAP S/4HANA upgrade scenario.
1. Check which of your third-party add-ons are compatible.
2. Add any incompatible components to the list by using transaction SM30 for SAP Solution Manager and
maintaining the table /TMWFLOW/S4BLACK as follows:
1. PgID: Enter a program ID, for example R3TR.
2. Obj.: Enter a DDIC object type, for example TABL.
3. Object Name: Enter an object name.
4. Software Component: Enter a software component, for example S4CORE.
5. SAP Release: Specify the release with which the incompatible change was introduced, for example
102.
6. SP Level: Specify the SP level with which the incompatible change was introduced.
7. Short Description: Add a description.
5. (Optional) Maintain the include list to allow certain customizing tables and views to be retrofitted by
auto-import (green category) even though they are listed in the simplification database. For SAP standard
objects, this is not necessary in the SAP S/4HANA upgrade scenario.
1. Check which objects are compatible but are listed in the simplification database.
2. Maintain the table /TMWFLOW/S4WHITE in SAP Solution Manager by using transaction SM30.

 Note

The columns are the same as the ones in the exclude list.

Related Information

• Additional Functions in Retrofit [page 343]

• Information for the Integration of the ABAP Test Cockpit (ATC) with Change Request Management in SAP
Note 2590595
• Retrofit to SAP S/4HANA in SAP Note 2652106

Change Control Management

Change Request Management PUBLIC 359
4.4.8 Downgrade Protection

The downgrade protection (DGP) function tracks objects in transport requests, and reports conflicts in five
scenarios when an object that is saved in two or more transport requests is released, reassigned, or imported.

Use

Downgrade protection is available in Change Request Management and in Quality Gate Management. The
function is identical, however, the user interfaces and the related terminology may differ.

Downgrade protection is available for ABAP systems as well as for non-ABAP systems. For non-ABAP systems,
only imminent downgrade and predecessor checks are supported.

For Git-enabled changes (Change Request Management only), cross-system object lock (CSOL), release check,
and reassign check are available.

 Tip

If you use these functions on a regular basis and with a large amount of data, consider using the
housekeeping reports as described in SAP Note 2138047 .

Prerequisites

• You have configured downgrade protection and the cross-system object lock in the SAP Solution Manager
Configuration (transaction SOLMAN_SETUP), in the Change Request Management or the Quality Gate
Management scenario, under Set up Downgrade Protection and Retrofit Configure CSOL and DGP ,
globally, and locally in the development system.

 Note

You can configure the conflict criticality for each check type as well as the systems that have custom
DGP responses.

For more information, see the detailed documentation for the activities in the Configure CSOL and DGP
substep of your scenario in SAP Solution Manager Configuration (transaction SOLMAN_SETUP).

• The SAP Solution Manager system has an up-to-date CTS plug-in version installed.
For more information, see SAP Note 1665940 .
The import check logic depends on the central CTS import check logic for downgrade protection, which is
a part of the CTS plug-in.
• If you want to use the predecessor and the imminent downgrade checks, you have installed and
distributed the CTS service plug-in to the managed systems (including development, quality assurance,
and production systems). For more information, see SAP Note 1665940 .
• Authorization object SM_CM_DGPN has been assigned to your role so that you can explicitly ignore conflicts.
If you don’t have one of the following roles (which are in the standard SAP delivery), the authorization
object must be assigned to your user.

Change Control Management

360 PUBLIC Change Request Management
 • SAP_CM_SMAN_CHANGE_MANAGER (Change Manager)
• SAP_CM_SMAN_OPERATOR (IT Operator)
• SAP_CM_SMAN_ADMINISTRATOR (Administrator)
• SAP_CM_SMAN_DEVELOPER (Developer)
• SAP_CM_SMAN_TESTER (Tester)
• SAP_SM_QGM_CM_CHANGE (Change Manager)
• SAP_SM_QGM_CM_TRANSPORT (IT Operator)
• SAP_SM_QGM_CM_ALL (Administrator)

Features

• Integration in the WebClient UI

In Change Request Management, the Transport-Related Checks assignment block is available for change
cycles and change documents. Detected conflicts are displayed in the assignment block.
In Quality Gate Management, information related to downgrade protection is displayed in the Downgrade
Protection dialog box.
• Manual and automatic checks:
• In Change Request Management, you can start downgrade checks from the Transport-Related Checks
assignment block. In Change Request Management, you can also start a downgrade check from a task
list. If a conflict is detected, a popup notifies you, and you can choose to ignore the conflict or to cancel
the operation.
In Quality Gate Management, you can start the check manually with Actions Transport-Related
Checks (in the scenario overview) or Actions Downgrade Protection (in the change overview).
The system analyzes potential release check conflicts for all open transport requests in the
development system, and import check conflicts for all released transport requests in all systems
into which they can be imported. This helps you to handle the conflicts before triggering the transport.
When you do a manual check in the assignment block, the system performs the DGP check. Detected
conflicts are reported as warnings.
• Downgrade checks run automatically when transport requests are released, imported, decoupled, or
assigned. They are also triggered when a change document is reassigned.
If a conflict is detected, you can choose to ignore it and continue the operation. Ignored conflicts are
shown in the assignment block or dialog box.
You can configure the system so that developers and testers can ignore any automatic check. For
more information, see the documentation in the Customizing activities for downgrade protection. You
can customize the DGP check as “Silent” mode: During release and import of transport requests, the
system doesn’t perform the DGP check but skips it directly.

 Note

The automatic check analyzes a smaller number of transport requests: The manual check analyzes
all open transport requests (release check) and all importable transport requests (import check),
including all corresponding target systems. The automatic check analyzes only the transport requests
to be released or imported, and only the relevant target systems.

Change Control Management

Change Request Management PUBLIC 361
Downgrade Check Scenarios

The following downgrade checks can be performed:

Cross-System Object Lock

The cross-system object lock (CSOL) ensures that when an object is changed in a managed system, it is locked
in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being
made to this object in any other transport request.

Release Check
When you release a transport request, downgrade protection can detect conflicts for objects in transport
requests. The conflicts are the same as those displayed by the cross-system object lock when saving the
objects to the transport requests.

Reassign Check
The system performs this check when you reassign a change document or assign or decouple transport
requests in a change document.

Predecessor Check
The system can detect conflicting predecessors, that is, preceding transport requests containing conflicts, at
the time of importing transport requests or transports of copies to the production or quality assurance system.

Imminent Check
The system can detect impending (imminent) downgrade conflicts when transport requests are imported. This
kind of conflict would become an actual downgrade if you ignored the conflict.

 Note

Import checks depend on the transport requests being imported. Any conflicts found while importing a
change cycle or urgent change task list are displayed in the Transport-Related Checks assignment block of
the change cycle document. Any conflicts found while importing a change document are displayed in the
Transport-Related Checks assignment block of the change document.

The check for potential downgrades is carried out both when you perform a preliminary import of a change
(normal change or urgent change) and when you import via the task list for the change cycle. The duplicate
check ensures that potential downgrades are identified even if changes belong to the same change cycle.
If you plan to ignore the conflicts, pay attention to the type of import operation you’re performing. If you
perform a preliminary import, the system prompts you to ignore the conflicts at change level. When you
later import the changes at cycle level, the system prompts you to ignore the changes again, but this time
at cycle level. If you import changes only at cycle level, you have to ignore only the cycle-level conflicts.

 Caution

Release check conflicts are sometimes not seen during an import check. This is because the release
check reports conflicts between the same objects in different transport requests to be imported into the
production system. In one particular case, they are not reported as import check conflicts: when the import
order of the transport requests is the same as the release order. For example, if TR1 and TR2 have modified
the same object, they result in release check conflicts. However, if TR1 is released first, TR2 is released

Change Control Management

362 PUBLIC Change Request Management
 second, and TR1 is imported first, TR2 is imported second, the system reports no conflicts during the
predecessor check and the imminent check.

Related Information

Cross-System Object Lock [page 363]

Technical Details of the CTS Plug-In [page 383]
Performing Transport-Related Checks [page 150]
Using the Transport-Related Checks Assignment Block [page 165]
Release Check [page 373]
Reassign Check [page 374]
Predecessor Check [page 376]
Imminent Check [page 377]
Using the CTS Plug-In Management Web UI [page 382]

4.4.8.1 Cross-System Object Lock

Use

The cross-system object lock (CSOL) ensures that when an object is changed in a managed system, it is locked
in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being
made to this object in any other transport request. This applies to all managed systems and clients for which
the cross-system lock is active and prevents version conflicts at an early stage.

Regardless of whether you use a separate development system or share the same system for your projects,
you must avoid different teams working on the same object concurrently if the changes are to be imported
in the same production system. It can lead to inconsistencies. The object must stay locked until it has been
imported in the production system.

Prerequisites

The cross-system object lock has been configured and activated in SAP Solution Manager Configuration
(transaction SOLMAN_SETUP) by completing the activities in the Change Request Management scenario or the
Quality Gate Management scenario in the Configure CSOL and DGP sub-step.

Change Control Management

Change Request Management PUBLIC 363
Features

• You can activate or deactivate the cross-system object lock.

When the cross-system object lock is active, the system can detect conflicts between objects in different
transport requests that are part of the same production logical system (system and client) as their
transport target, depending on the type of object that was changed.
• When the cross-system object lock is active, you can activate downgrade protection. Downgrade
protection cannot be activated if the cross-system object lock is inactive.
• You can define your cross-system object lock conflict scenario by choosing between the default mode
and the expert mode. The default conflict analysis scenario is cross-cycle (cycle relation Cross) with
change type relation Urgent Only. In the expert mode, you define customized conflict scenarios for the
cross-system object lock. For more information, see the system documentation of the activity.
• If you want to get notified about the cross-system object lock conflicts, you can select a Warning Only
option. Only a warning message is displayed for all conflicts. You can still save your data. Be aware that
when choosing this option, you might run the risk of possible software downgrades when older transport
requests overwrite more recent transports containing the same objects.

 Caution

Transport requests that are assigned neither to a Change Request Management cycle nor to a quality
gate management cycle are not taken into account during conflict analysis.

• If you are using the Stop at Error check mode for the CSOL check, you can configure that the check reports
only a warning, and not an error, if it detects conflicts for specific Customizing objects and Workbench
objects. for this, you specify these objects in the Administration Cockpit on the Cross-System Object
Lock and Downgrade Protection tab. On the Cross-System Object Lock and Downgrade Protection Settings
subtab, you can configure these settings in the Object-Specific Warning Mode Configuration section .
• Defect corrections: You will not be notified about cross-system object lock conflicts that are detected
during upon-saving checks and release checks, and when the conflicts originate from a defect correction
itself, from a normal change, or a standard change in same cycle.
• You can define your own conflict scenario for the cross-system object lock. You can label the conflict with
message types such as Error or Warning, depending on your scenario. The final conflict message to be
displayed contains the following information:
• Conflict type (error or warning)
• Affected transport requests
• Owners of the transport requests
It depends on the conflict type whether you can continue to change an object.

Extended Features

• The conflict analysis tracks the objects stored in transport requests using lock entries. Within one
transport request and one production logical system, there are records for each object in the transport
request.

 Note

In the central SAP Solution Manager system, the cross-system object lock manager (in the
Administration Cockpit) provides an overview of all current lock entries. The entries are displayed
in table form, and can be selected if you need to delete them, for example.

Change Control Management

364 PUBLIC Change Request Management
• You can activate and deactivate the cross-system object lock in each managed system with the
TMW_CONTROL_PROJECT_LOCK report in the managed system. You can also do this on the Landscape
Overview tab in the administration cockpit by setting the CSOL Check checkbox for managed development
systems.

 Caution

To execute the TMW_CONTROL_PROJECT_LOCK report, you require change authorization for the
Transport Management System.

• You might need to update the central object lock information about a transport request. You can do so by
using the TMW_TRKORR_LOCK_UPDATE report. If you are the owner of the transport request, you have the
required authorization. Enter the name of the transport request for which you want to update the object
lock information.

 Note

If SAP Solution Manager is temporarily unavailable but you still want to change objects in the
development system, use the TMW_CONTROL_PROJECT_LOCK report to deactivate the cross-system
object lock temporarily and change the objects. When SAP Solution Manager is available again, you can
activate the cross-system object lock and run the TMW_TRKORR_LOCK_UPDATE report for the transport
request in which you saved objects during the inactive period.

You can also update the lock entries for a batch of transport requests in the cross-system object lock
manager of the SAP Solution Manager system.

• With regard to the cross-system object lock, the Workbench Organizer provides the following features:
• When changing to edit mode for an object, the system displays a warning message and prompts you to
save any changes as soon as possible.
• When you change transport objects manually, that is, you delete, edit, or merge objects, the lock
entries in SAP Solution Manager are updated automatically.

 Note

To use these features, you have to implement the SAP Notes listed in SAP Note 1900560 in the
development systems in your landscape.

More Information

Conflict Analysis Scenarios [page 369]

Change Control Management

Change Request Management PUBLIC 365
4.4.8.1.1 Track-Specific CSOL Configuration

Use the track-specific configuration to specify cross-system object lock (CSOL) configuration for each
managed development system. These settings override the general settings made when you activate CSOL
globally.

Procedure

1. Go to Administration Cockpit Cross-System Object Lock and Downgrade Protection Cross-System

Object Lock and Downgrade Protection Settings . Under Cross-System Object Lock Configuration, open
Track-Specific Conflict Configuration.

 Note

Any settings that you make or change on this tab are active immediately.

2. Add a new entry and specify the scope by the following categories. You can use an asterisk (“*”) as a
wildcard to allow all possible values of the category.
• Landscape
• Branch
• Cycle type
• Managed development system name
• Managed development system type
• Managed development system client

 Example

If you specify landscape “*”, branch “*”, cycle type “*”, managed development system name “DV1”,
type “ABAP”, client “100”, the CSOL configuration applies to all transport requests created from the
specified development system.

If you specify landscape “LANDSCAPE1”, branch “MAINTENANCE”, cycle type “*”, managed
development system name/type/client “*”, the CSOL configuration row applies to all transport
requests that belong to cycles using the specified change control landscape and branch.

3. Select a CSOL check mode:

• Stop at Error: You can define the conditions that categorize conflicts as error, which the end user
cannot ignore. If the conditions are not met, the conflicts are classified as warning, which the end user
can choose to ignore.
• Warning Only: Any conflicts detected between transport requests are classified as warning, which the
end user can ignore.
• Silent: Any conflicts detected between transport requests are categorized as “information”, and are
only logged in database table /TMWFLOW/CSOLILG.
• Off: CSOL check is switched off for transport requests from the specified development system (or
cycles with the specified landscape, branch, and type).

Change Control Management

366 PUBLIC Change Request Management
  Caution

For check modes Warning Only, Silent, and Off, be aware of the risk of possible software downgrades
when newer transport requests overwrite older transports requests containing the same objects.

4. For check mode Stop at Error, specify the conditions that categorize a conflict as error with the following
options:
• Same Development System
• Cycle Relationship
• Change Type Relationship
5. Any settings are active immediately. You don't have to save your changes manually.

CSOL Check Options

For check mode Stop at Error, the following options define the conditions for the conflicts that are classified as
Error, which the end user cannot ignore.

Same Development System

• Inactive (default setting): Conflicts between transport requests are categorized as error unless cycle
relation and change type relation specify otherwise.
• Active: Conflicts between transport requests from different managed development systems are
categorized as a warning. Transport requests from the same managed development system are
categorized as error, unless cycle relation and change type relation specify otherwise.

 Note

Activate this option if you work with retrofit in combination with a maintenance landscape and an
implementation landscape and you want to treat conflicts between the two landscapes as warning, not
as an error.

Cycle Relationship

• All Cycles: Conflicts between transport requests are categorized as error, unless the Same Development
System option or the change type relationship specify otherwise.
• Same Cycle: Conflicts between transport requests from the same cycle are categorized as error, unless
the Same Development System option or the change type relationship specify otherwise. Conflicts between
transport requests from different cycles are categorized as a warning.
• Different Cycles: Conflicts between transport requests from different change cycles are categorized as
error, unless the Same Development System option or the change type relationship specify otherwise.
Conflicts between transport requests from the same cycle are categorized as a warning.

Change Type Relationship

• Both Urgent Changes: Conflicts between transport requests that both belong to urgent changes (or QGM
changes) are categorized as error, unless they are categorized as warning by the Same Development
System option or the cycle Relationship. Other conflicts are handled as warning.

Change Control Management

Change Request Management PUBLIC 367
• Either of two is Urgent Change: Conflicts between transport requests of which one belongs to an urgent
change are categorized as error, unless they are categorized as warning by the Same Development System
or the cycle relationship. Other conflicts are classified as warning.
• Any Change Type: Conflicts between transport requests of any change type are categorized as error, unless
they are categorized as warning by the Same Development System option or the cycle relationship.

 Note

Select Both Urgent Changes if you want to prevent conflicts between urgent changes while, at the same
time, importing other types of changes on the cycle level to keep them free from downgrades.

Related Information

Cross-System Object Lock [page 363]

Creating Cross-System Object Lock Entries [page 331]
Conflict Analysis Scenarios [page 369]

4.4.8.1.2 Creating Cross-System Object Lock Entries

You can manage cross-system object lock entries in the administration cockpit.

Procedure

1. In the administration cockpit, go to Cross-System Object Locks Register .

2. Select a development system or choose all systems. You can also use the following options:

• You can restrict the range of transport requests by request number. For external requests, the
transport request number prefix (containing the external system name) can be different from the
real (internal) source system name.
• You can choose to send e-mail notifications if conflicts are detected: Default recipients are the change
managers (and for Change Control Management, also IT operators) of the change documents or QGM
changes that contain the transport requests with conflicts. You can also enter an additional e-mail
address.

 Note

To send a notification to the change manager and IT operator, the e-mail addresses must be
maintained for their business partners.

The system does not send any e-mail notifications to the transport request owners.

• You can specify the execution time (immediate or scheduled).

3. After you have registered the lock entries, to see the progress, monitor the job log.

Change Control Management

368 PUBLIC Change Request Management
 a. Call transaction SM36 (Define Background Job) and select Own jobs.
b. Find job CM_CROSS_SYS_OBJ_LOCK_REGISTER, scheduled to run at the time you specified, and open
Job Log.

When the job is finished, the job log refers to the application log. The application log contains detailed
messages, whereas the job log shows only the job progress.

Results

For each system, the application log displays the final processing result. You see warning messages for
transport requests that cannot be processed, and, for example, if the system does not find an e-mail address.

Next Steps

To check the application log, call transaction SLG1 with object /TMWFLOW/CMSCV and subobject
CROSS_SYS_OBJ_LOCK.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Downgrade Protection [page 360]

4.4.8.1.3 Conflict Analysis Scenarios

The selected scenario specifies which kind of transport conflict is classified as an error, which in turn means
that the object can’t be changed. All other conflicts cause a warning only; you can decide whether to change
the object.

Features

The conflict analysis function is defined by the relationship between the change cycles, and between the
change transaction types:

• Conflicts between transport requests that belong to the same change cycle and conflicts between
transport requests that belong to different change cycles
• Conflicts for urgent changes and conflicts between transactions of another type (for example, between an
urgent change and a normal change, or between normal changes)

You can use this function in Change Request Management and Quality Gate Management.

Change Control Management

Change Request Management PUBLIC 369
Scenarios

By default, it's an error when the conflicting transport requests both are in urgent changes, regardless if they
are in the same or different change cycle. You can select other scenarios.

To select a scenario, go to Administration Cockpit Cross-System Object Lock and Downgrade Protection
Cross-System Object Lock and Downgrade Protection Settings .

Cross-System Object Lock Scenarios

Cycle Relation Change Type Relation Conflict Causing an Error

All Cycles Both Urgent Changes This is the default mode:

An object conflict between transport

requests of two urgent changes, both
belonging to the same or two different
change cycles.

Either of two is Urgent Change An object conflict between two trans-

port requests and at least one of them
is contained in an urgent change, both
belonging to the same or two different
change cycles.

Any Change Type An object conflict between two trans-

port requests for any change type, both
belonging to the same or two different
change cycles.

Same Cycle Both Urgent Changes An object conflict between transport re-
quests of two urgent changes, both be-
longing to the same cycle.

Either of two is Urgent Change An object conflict between two trans-

port requests and at least one of them
is contained in an urgent change, both
belonging to the same cycle.

Any Change Type An object conflict between two trans-

port requests for any change type, both
belonging to the same cycle.

Different Cycles Both Urgent Changes An object conflict between transport re-
quests of two urgent changes, both be-
longing to two different cycles.

Either of two is Urgent Change An object conflict between two trans-

port requests and at least one of them
is contained in an urgent change, both
belonging to two different cycles.

Change Control Management

370 PUBLIC Change Request Management
Cycle Relation Change Type Relation Conflict Causing an Error

Any Change Type An object conflict between two trans-

port requests for any change type, both
belonging to different cycles.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Change Cycles [page 28]
Processing Urgent Changes [page 81]
Creating Cross-System Object Lock Entries [page 331]

4.4.8.1.4 Skipping CSOL and DGP Check for PFCG Roles

and Customizing Objects

Context

In Administration Cockpit, you can configure the cross-system object lock and downgrade protection check to
skip the check for PFCG role objects or for all customizing objects. This can improve the performance of the
check if the transports contain large amounts of PFCG role objects or other customizing objects.

Procedure

1. In the Administration Cockpit, navigate to Cross-System Object Lock and Downgrade Protection Cross-
System Object Lock and Downgrade Protection Settings .
2. In the Cross-System Object Lock and Downgrade Protection Settings, under Advanced Configuration, select
the option for the Role and Customizing Object Check:

• On: Check all PFCG role objects and other customizing objects (This is the default setting.)
• Skip Role Objects Check: Skip the check for PFCG role objects
• Skip All Customizing Objects Checks: Skip the check for all customizing objects.

If you choose Skip Role Objects Check or Skip All Customizing Objects Checks, either only PFCG role
objects or all customizing objects will be filtered out of the conflict calculation.

Change Control Management

Change Request Management PUBLIC 371
  Note

CSOL lock entries are still generated for all objects to support the retrofit functionality.

DGP tracking data is still generated for all objects in case the customizing is reset.

4.4.8.2 Downgrade Protection System Configuration

Use the downgrade protection system configuration to configure the downgrade protection (DGP) for each
managed system. These settings override the general settings made when you activate DGP globally.

Procedure

1. Go to Administration Cockpit Cross-System Object Lock and Downgrade Protection Cross-System

Object Lock and Downgrade Protection Settings Downgrade Protection Configuration Downgrade
Protection System Configuration .

 Note

Settings on this tab are active immediately.

2. Add a new entry and specify the scope with the following categories. You can use an asterisk (*) as a
wildcard to allow all possible values of the category:
• Landscape
• Branch
• Cycle type
• Managed system name
• Managed system type
• Managed system client
• Managed system role
3. Select a DGP check mode:
• Stop: You can define the conditions that categorize conflicts as errors, which the end user cannot
ignore. If the conditions are not met, the conflicts are classified as warnings, which the end user can
choose to ignore.
• Warning: Any conflicts detected between transport requests are classified as warnings, which the end
user can choose to ignore.
• Silent: Any conflicts detected between transport requests are categorized as “information” and are
only logged in the backend database table.
• Off: The DGP check is switched off for transport requests from the specified system (or cycles with the
specified landscape, branch, and type).

 Caution

For check modes Warning, Silent, and Off, be aware of the risk of possible software downgrades when
newer transport requests overwrite older transports requests containing the same objects.

Change Control Management

372 PUBLIC Change Request Management
4. Select a DGP check type:
• Release Check: Performs a DGP check before releasing a transport request or transport of copy.
• Reassign Check: Performs a DGP check before assigning a transport request to a change document.
• Predecessor Check: Performs a DGP check before importing a transport request or transport of copy
into the target system.
• Imminent Check: Performs a DGP check before importing a transport request or transport of copy into
the target system.
5. All settings are active immediately. You don't have to save your changes manually.

Check Options

For check type Predecessor Check and Imminent Check, the following option defines whether conflicts that
occur between transport requests from different development systems should be reported or not.

Same Development System

• Inactive (default setting): If conflicts are detected between transport requests, the conflicts are always
reported.
• Active: If conflicts are detected between transport requests, and only if these transport requests are from
the same managed development system, the conflicts are reported. If the transport requests are from
different managed development systems, the conflicts are not reported.

 Note

Activate the Same Development System option if you work with the retrofit function in combination with a
maintenance landscape and an implementation landscape, and you don't intend to treat conflicts between
two transport requests across the two landscapes as a real downgrade. In this case, you can select the
Same Development System option to prevent the conflicts from being reported.

4.4.8.3 Release Check

Use

The system performs this downgrade check when you release a transport request. The system can detect
conflicts for objects in different transport requests. If a transport request that was released first were to
be imported second, the conflict object would be downgraded. The release check prevents this issue from
occurring.

Prerequisites

For a list of prerequisites, see Downgrade Protection [page 360].

Change Control Management

Change Request Management PUBLIC 373
Activities

1. You release a transport request.

2. The system performs the downgrade check.
3. If the system detects a conflict, you are prompted to either cancel the release or (depending on your
authorizations) to ignore the conflict and continue with the release.
• If you cancel the release, the conflicts that were detected are logged. The conflict check results are
displayed in the Downgrade Protection assignment block in Change Request Management or in the
Downgrade Protection dialog box in quality gate management.
• If you ignore the conflicts and continue with the release, the conflicts are archived in the system.

Example

1. You modify function module Z_TEST_FUNC1 and save it in transport request DEVK000001 in change NC1.
2. You release DEVK000001 without noticing any conflicts.
3. You modify the function module again and save it to another transport request, DEVK000002, in change
NC2, bypassing the cross-system object lock warning in the managed system.
4. When you try to release DEVK000002, a conflict is shown.
5. To continue with the release, you can ignore these conflicts. Alternatively, you can import DEVK000001
into the production system by importing it into the quality assurance system, and then import it into the
production system. DEVK000002 can then be released without conflicts.

4.4.8.4 Reassign Check

This check detects conflicts when you reassign a change, or when you assign or decouple transport requests in
a change document.

If the transport requests belong to different change cycles after one of these actions, the transport requests
might be released and imported in a different order. This type of conflict can cause a downgrade.

Before you carry out any of these actions, consider whether assignment, reassignment, or decoupling can be
avoided.

Prerequisites

For a list of prerequisites, see Downgrade Protection [page 360].

Change Control Management

374 PUBLIC Change Request Management
Activities

1. You reassign a change, or you assign or decouple a transport request.

2. You get information about potential conflicts of the involved transport requests.
3. You can either cancel the operation, or ignore the warning and continue.

Example

Example 1

1. You modify function module Z_TEST_FUNC1 and save it to transport request DEVK000001. You release
the transport request.
2. You modify the function module again and save it to transport request DEVK000002, ignoring the warning
about the cross-system object lock. DEVK000001 belongs to change NC1, while DEVK000002 belongs to
change NC2.
3. When you try to reassign change NC2 to another change cycle, potential conflicts with NC1 are detected. A
simulation shows the effects of reassignment.
4. If you ignore the conflicts, NC2 is reassigned.

Example 2

You already have two conflicting transport requests, DEVK000001 and DEVK000002, in changes NC1 and
NC2. When you decouple DEVK000002 from NC2, you get information about the existing conflicts on
DEVK000002. You can continue only if you ignore the conflicts.

Example 3

Transport request DEVK000002 was previously decoupled and has conflicts with DEVK000001 in change NC1.
When you try to assign DEVK000002 to normal change NC2, conflicts are detected. A simulation shows what
would happen if you reassigned DEVK000002 to the normal change.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Reassigning Change Transactions [page 141]
Decoupling Transport Requests in Change Request Management [page 134]
Assigning Transport Requests [page 135]

Change Control Management

Change Request Management PUBLIC 375
4.4.8.5 Predecessor Check

When a transport is imported into the production or quality assurance system, this import check detects
whether there are any conflicting older transport requests. Importing a newer transport request before its
predecessor would cause a downgrade.

 Example

A transport request containing object “A” in a new version is to be imported into a system, while an
older transport request containing the same object “A” is also yet to be released into the same system.
If the more recent transport request is imported before the older transport request, the result is an
imminent downgrade. For business reasons, system administrators generally are instructed to import the
older request, but they must be careful to avoid a downgrade. To prevent such downgrade situations, the
predecessor check reports the initial conflict and stops the import.

Import checks depend on the transport requests being imported. Any conflicts found while importing in a
change cycle task list are displayed in the Transport Related-Checks assignment block of the change cycle
document or in the Transport Related-Checks dialog box in Quality Gate Management. Any conflicts found while
importing a change document are displayed in the same assignment block of the change document.

Prerequisites

For a list of prerequisites, see Downgrade Protection [page 360].

Activities

1. You start to import a transport request.

2. The system performs the downgrade check.
3. If there is a conflict, the import is stopped and you get a message.
You can view the logged conflicts in the Transport Related-Checks assignment block in Change Request
Management and in the Transport Related-Checks dialog box in Quality Gate Management.
4. To continue, you can ignore the conflicts and repeat the import.
Ignored conflicts are archived as conflict history.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Change Control Management

376 PUBLIC Change Request Management
4.4.8.6 Imminent Check

Use

The system can detect impending (imminent) downgrade conflicts when transport requests are imported. This
kind of conflict would become an actual downgrade if you ignored the conflict.

 Example

Any kind of transport request (workbench request, a customizing request or a transport of copies)
containing, object “A” is imported on top of another transport request containing the same object “A”
but with a more recent export time stamp. It is also referred to as an “overtaker”. This situation is reported
within Downgrade Protection and the import is canceled.

Prerequisites

See Downgrade Protection [page 360].

Activities

1. When a transport request is imported into the production or quality assurance system, a downgrade check
is performed.
2. If the system detects a conflict, it displays an error message and cancels the import.
The conflicts are logged and displayed in the Downgrade Protection assignment block in Change Request
Management and in the Downgrade Protection dialog box in quality gate management.
3. To import the transport requests, you can ignore the conflicts in the assignment block or dialog box and
repeat the import.
If you ignore the conflicts and continue with the import, the conflicts are archived in the system.

 Recommendation

Do not ignore the imminent downgrade conflicts and continue with the import. Import the transport
requests in the correct order, including the newer request and its predecessor (if the newer request is in the
project import).

4.4.8.7 Delta Downgrade Protection Check

The delta downgrade protection check (delta DGP check) is an incremental check based on a previous
complete downgrade check.

The delta DGP check is an import check (predecessor or imminent check) check, which is triggered
automatically when you import the transport requests of a change cycle or scenario into the follow-on system

Change Control Management

Change Request Management PUBLIC 377
(for example the quality assurance system or production system). You can also trigger it with a manual
downgrade check of the change cycle or QGM scenario. The delta DGP check is intended for the following use
case:

Before a go-live phase, you made a complete manual downgrade check of all transport requests in the change
cycle (or QGM scenario) to identify conflicts before transporting the changes to the follow-on system (for
example, the quality assurance or production system). After this complete downgrade check, new transport
requests have been added to the import buffer of the follow-on system. If you then trigger the import of the
transport requests of the cycle (or scenario) to the follow-on system, instead of a new complete downgrade
check, which would check again all transport requests, a delta DGP check is performed to check only the
transport requests that have been added since the last complete check. Since the delta DGP check checks only
the transport requests that have been added since the last complete downgrade check, the delta DGP check is
much faster than a complete check.

Prerequisites

Downgrade protection performs delta DGP checks only if the following prerequisites are met:

• No imports into the production system happened during or since the last complete downgrade check. If
imports, for example, urgent changes, have been made during or since the last check, a new complete DGP
check is required.
• New transport requests have been added to the import buffer of the follow-on system since the last
complete downgrade check..
• If the change cycle is not cCTS-enabled, it depends on whether the new transport requests have been
added at the end of the import buffer or not:
• A delta DGP check is performed only if the transport request are found at the end of the buffer.
• If they are not at the end of the buffer, it is assumed that the buffer has been manipulated and a new
complete downgrade check is required.

Enabling the Delta Downgrade Protection Check

To enable the delta DGP check, do the following:

1. In transaction SM30 (Maintain Table Views) , open table AGS_WORK_CUSTOM (Workcenter Customizing).
2. In the table, for the parameter key AIC_DGP_DELTA_SWITCH, enter the value X.

Change Control Management

378 PUBLIC Change Request Management
4.4.8.8 Import Groups in Downgrade Protection

An import group comprises transport requests that are imported into the same production system in the
sequence in which they were released. If the same object is changed in different transport requests, but the
transport requests belong to the same import group, there is no risk of a downgrade and thus no conflict.

Use

Import groups are used by the following downgrade protection checks when dealing with conflicts:

• Cross-system object lock

• Release check
• Reassign check

Features

Transport requests belong to the same import group under the following conditions:

• Two transport requests in the same normal change, git-enabled change, standard change, or defect
correction that are on the same transport track
• Two transport requests in the same QGM change or QGM urgent change that are on the same transport
track
• Two transport requests in the same urgent change

 Note

Transport requests in the same urgent change are always imported into the same production system
from one development system. There cannot be two transport tracks in an urgent change.

In all other cases, two transport requests belong to different import groups, for example:

• Two transport requests created from the same task list

• Two transport requests in the same normal change that are on different transport tracks. They can be
imported separately into the production system by transport track, using the CTS project ID.
• One transport request in a normal change and another transport request in an urgent change. They can be
imported into the production system independently.
• Two transport requests in different urgent changes because they can be imported into the production
system independently
• Two transport requests in the same QGM change that are on different transport tracks. They can be
imported separately into the production system, by transport track, using the CTS project ID.
• Two transport requests in different QGM changes. They can be imported into the production system
independently.
• One transport request in Change Request Management and another in QGM. They can be imported
independently.

Change Control Management

Change Request Management PUBLIC 379
  Note

Two transport requests created from the same task list can be on the same transport track. In this case,
they don't cause a potential downgrade but they are still in different import groups. This allows for conflict
reporting for task list-only use cases.

The import group function does not prevent downgrades caused by selective imports. Use the downgrade
protection import check for this purpose. During the selective import, downgrade protection may report
new conflicts that were not reported when saving or releasing transport objects.

Related Information

Downgrade Protection [page 360]

Import Strategies: Standard, Status-Dependent, and Selective [page 396]

4.4.8.9 Conditions for Ignoring Transport Conflicts

For Change Request Management and Quality Gate Management, matrixes display the conditions when
transport conflicts can be ignored by specific business roles.

Default Configuration for Conflict Type

To view and change the default and system-specific settings, go to Administration Cockpit Cross-System
Object Lock and Downgrade Protection Cross-System Object Lock and Downgrade Protection Settings
Downgrade Protection Configuration .

You can choose the check mode based on the type of check, and you can choose to use only warning mode or
stop mode for specific systems

Default Matrix for Conflict Type as in Table Downgrade Conflict Type

Check Type Check Mode

Release check, reassign check Warning mode

Import check (predecessor check, imminent check) Stop mode

In general, errors must be solved, while warnings can be ignored. There are exceptions for particular business
roles, which are highlighted in the following matrixes.

Change Control Management

380 PUBLIC Change Request Management
Conflict Matrix for Change Request Management

Trans-
Check port Op- Ignoring Conflict in DGP (or Transport-Related Ignoring Conflict in DGP (or Transport-Re-
Mode eration Checks) Popup lated Checks) Assignment Block

DEV TST ITO CM ADM DEV TST ITO CM ADM

Warning Release          
mode
Reassign      N/A
(assign,
decou-
ple)

Stop Selective      N/A

mode import

Nonse-          
lective
import

Conflict Matrix for Quality Gate Management

Trans-
port
Check Opera- Ignoring Conflict in DGP (or Transport-Related Ignoring Conflict in DGP (or Transport-Related
Mode tion Checks) Dynamic Check Popup Checks) Static Check Popup

DEV TST ITO CM ADM DEV TST ITO CM ADM

Warning Release          
mode
Reas-      N/A
sign (as-
sign, de-
couple)

Stop Import          
mode (either
selec-
tive or
nonse-
lective)

Related Information

Downgrade Protection [page 360]

Performing Transport-Related Checks [page 150]
Transport-Related Checks in QGM [page 530]

Change Control Management

Change Request Management PUBLIC 381
Release Check [page 373]
Reassign Check [page 374]
Predecessor Check [page 376]
Imminent Check [page 377]
Import Strategies: Standard, Status-Dependent, and Selective [page 396]

4.4.8.10 Using the CTS Plug-In Management Web UI

If you use Change Request Management without central CTS, you can distribute CTS plug-ins with the CTS
Plug-In Management Web UI.

Prerequisites

 Note

If you use Change Request Management with the central CTS infrastructure, you don’t need the CTS
Plug-In Management Web UI to distribute CTS plug-ins.

Instead, you can use the Central CTS Configuration Web UI, which is also used to configure central CTS.

• The CTS plug-in (software component CTS_PLUG) is installed on your SAP Solution Manager. This is
done automatically as part of the SAP Solution Manager installation. For more information, see SAP Note
1665940 .
• A specific RFC destination is required between the CTS server (SAP Solution Manager) and the managed
systems to which you want to distribute the plug-ins, the import destination. For this, a SAP Solution
Manager destination is reused, which was created during Managed Systems Configuration in SAP Solution
Manager Configuration (transaction SOLMAN_SETUP). If the Change and Transport System - Plug-in
Management Web UI tells you that the import destination is missing, check that the RFC destinations
in your SAP Solution Manager configuration are correctly configured.
• If the managed systems are not part of the SAP Solution Manager transport domain, or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute the
CTS plug-ins.
For more information, see SAP Note 1688276 .
• You have the correct authorizations.

Context

With the Change and Transport System - Plug-in Management Web UI, you can distribute the CTS Service and
CTS Bootstrapper plug-ins from the CTS server to the managed systems in your transport landscape. For
non-ABAP systems, the plug-ins are distributed to the ABAP communication system of the non-ABAP system.

Change Control Management

382 PUBLIC Change Request Management
The CTS Service plug-ins contain analysis functions for downgrading and overtaker requests based on object
overlaps. The CTS Bootstrapper plug-in is required for activation.

If a message informs you that the functions of the CTS Service plug-in are needed for downgrade protection
functions in Change Control Management, use the Plug-in Management Web UI to distribute the plug-ins.

Procedure

1. Start the Plug-in Management Web UI in your CTS server (SAP Solution Manager).
2. Select the systems to which you want to distribute the plug-in and validate their status to find out whether
all prerequisites are met.

Under Status, a traffic light icon indicates the overall result. To see a list of status messages, select the link
in the Status column. If you select a status message, you see the associated long text.
3. Distribute the CTS Service and CTS Bootstrapper plug-ins.

If the plug-ins are not up to date, you must distribute them. For ABAP systems, this means importing
transport requests into the managed systems. For non-ABAP systems, this means importing the transport
requests in the ABAP communication system of the non-ABAP system.

Related Information

Plug-In Management Web UI - Layout [page 389]

Central Change and Transport System [page 400]
Technical Details of the CTS Plug-In [page 383]
Plug-In Management Web UI - Authorizations [page 385]
Downgrade Protection [page 360]
Starting the Plug-in Management Web UI [page 387]
Plug-In Management Web UI - Distributing CTS Plug-Ins [page 392]

4.4.8.10.1 Technical Details of the CTS Plug-In

Use

The CTS plug-in is an add-on that installs the software component CTS_PLUG on SAP systems. This classifies
the SAP system as a CTS server. You can find details on the installation and supported SAP releases in SAP
Note 1665940 .

The CTS plug-in (software component CTS_PLUG) contains the following further plug-ins:

• CTS Service plug-in

Change Control Management

Change Request Management PUBLIC 383
 This plug-in contains CTS functions that are required in the managed systems. This includes central CTS
functions as well as functions required for downgrade protection checks in Change Control Management of
SAP Solution Manager.
The CTS Service plug-in is release-dependent. There is one CTS Service plug-in for each SAP NetWeaver
release. For an overview of supported releases, refer to SAP Note 1665940 .
• CTS Bootstrapper plug-in
This plug-in contains functions that are required to activate the CTS Service plug-ins on the managed
systems.
There is one Bootstrapper plug-in for each SAP NetWeaver release, available for the same releases as the
CTS Service plug-ins.

From a technical point of view, the CTS plug-ins are transport requests. When the CTS plug-in (software
component CTS_PLUG) is installed in an SAP system, the CTS Service plug-ins and the CTS Bootstrapper
plug-in are extracted to the transport directory. They can be distributed from the CTS server to the managed
systems. Distributing the plug-in means importing the transport requests in the managed systems.

CTS Service plug-ins are independent of the SAP NetWeaver Support Package level. Therefore, they can always
be installed in a system with a minimum Support Package level of the software component SAP_BASIS. When
the transport request of the CTS Service plug-in is imported in the managed system, the transport request of
the CTS Bootstrapper plug-in is also imported.

These characteristics enable the CTS Service and Bootstrapper plug-ins to be installed at any time, even during
production operation. In particular, no system restart is necessary and there are no constraints concerning
production usage. In this way, you can use the current SAP technology in SAP systems without the need to
update all managed systems to the current Support Package level. You can update the managed systems in the
maintenance cycles that you are used to.

Figure: Distribution of CTS plug-ins to managed systems

Change Control Management

384 PUBLIC Change Request Management
The graphic illustrates the plug-in distribution process.

1. The CTS server asks the managed system if the CTS Service and the Bootstrapper plug-ins are available
and in which version.
2. The managed system returns the required information.
3. If the CTS Service or Bootstrapper plug-ins need to be updated, you can trigger the distribution from the
CTS server to the managed system.

 Note

The system compares the versions of the CTS Service and Bootstrapper plug-ins on the managed
systems with the versions available in the transport directory of the CTS server. It does not check for
versions of the CTS plug-in that are available on SAP Support Portal.

If the CTS plug-ins on managed systems are out of date, that means if they have lower version than the
plug-in on the CTS server, you get a warning but you can still perform operations that use central CTS
or downgrade protection.

 Note

If the managed systems are not part of the SAP Solution Manager transport domain or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute
the CTS plug-ins.

For more information, see SAP Note 1688276 .

Updates to the CTS Plug-In

To import updates or corrections to the CTS server (SAP Solution Manager), you must import the relevant SAP
NetWeaver Support Packages, or implement the relevant SAP Note corrections into SAP Solution Manager.

To import corrections that are required on the managed systems, you must import the relevant Support
Packages for the CTS plug-in into SAP Solution Manager and distribute the CTS plug-ins to the managed
systems. For an overview of the Support Packages available for the CTS plug-in, refer to SAP Note 1665940 .

More Information

• Central CTS: Distributing CTS Plug-Ins to the Managed Systems [page 432]
• Plug-In Management Web UI - Distributing CTS Plug-Ins [page 392]

4.4.8.10.2 Plug-In Management Web UI - Authorizations

Use

To be able to distribute CTS plug-ins using the Plug-In Management Web UI, the logon user must be assigned
specific authorizations.

Change Control Management

Change Request Management PUBLIC 385
Authorizations Required on the CTS Server (SAP Solution Manager)

In general, the user must have a copy of the following role assigned:

• SAP_BC_TRANSPORT_ADMINISTRATOR

If you do not want to use the predefined authorization or if the role contains too many authorizations, you
can run an authorization trace to find out which authorizations are required. For more information, refer to the
information provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

Task Authorization

Starting the Plug-In Management Web UI using the transac- The user who starts the UI using the transaction code SZEN-
tion code SZENPLUGIN. PLUGIN needs to be assigned authorization object S_TCODE
with field TCD and value SZENPLUGIN.

This authorization object is part of the roles

SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANS-
PORT_ADMINISTRATOR as of SAP NetWeaver 7.0 Enhance-
ment Package 2, SP13.

Displaying objects on the UI including the following tasks: Display authorization: The user needs to be assigned au-
thorization object S_TRANSPRT with field ACTVT and value
• Searching for systems
03.
• Displaying search help and value help

Distributing CTS plug-ins to the managed systems. On the CTS server, the user needs to be assigned the author-
ization object S_CTS_ADMI with field CTS_ADMFC and value
TABL.

 Note

If the user needs both display and change authorization, assign both authorizations.

Authorizations Required on the Managed System

• User TMSADM must exist on the managed system. It must not be locked and must have the standard
profile assigned (S_A.TMSADM).

• Make sure that the user who performs a validation in the Plug-In Management Web UI also exists in the
managed systems for which he wants to perform the validation. Otherwise, validation will fail.
• To distribute CTS plug-ins, the user who is used for plug-in distribution to the managed system (usually
the user that is logged on to the current system) must have the authorization object S_RFCACL in the
managed system if the import destination uses Trust Relationship. For more information on S_RFCACL and
Trust Relationship, refer to the information provided in the “More Information” section.

In general, the user who is used for plug-in distribution to the managed system must have copies of the
following roles assigned:

• SAP_BC_TRANSPORT_OPERATOR: Required for distributing CTS plug-ins

• SAP_BC_TRANSPORT_ADMINISTRATOR: Required if the managed system is not in the same transport
domain as the CTS server.

Change Control Management

386 PUBLIC Change Request Management
If you do not want to use the predefined authorization or if it contains too many authorizations, you can run an
authorization trace to find out which authorizations are required. For more information, refer to the information
provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

• S_TRANSPRT with field ACTVT and value 03

• S_CTS_ADMI with field CTS_ADMFC and value IMPA
• S_DATASET with the values required to access the transport directory. This authorization is required
to read files. If the user does not have this authorization object assigned the error message
OPEN_DATASET_NO_AUTHORITY is displayed.
• S_RFC with the following values:
• field ACTVT and value 16
• field RFC_NAME and values STPA and TMSC
• field RFC_TYPE and value FUGR

More Information

• Maintaining Trust Relationships between SAP Systems

• Authorization Object S_RFCACL
• Using the System Trace to Record Authorization Checks (Transaction STAUTHRACE)
• Authorizations in the CTS
• Transport Operator
• Transport Administrator
• For more information on authorization object S_TCODE, see Authorization Checks.
• For more information on the releases and Support Packages which delivered changes to the
roles SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANSPORT_ADMINISTRATOR, see SAP Note
1748949 .

4.4.8.10.3 Starting the Plug-in Management Web UI

The Plug-in Management Web UI distributes CTS Service plug-ins to managed systems. You usually use it when
the system asks you to. You can start it with a transaction code, or using your favorites in the SAP Easy Access
user menu.

Prerequisites

• You have activated the services for the Plug-ln Management Web UI. The service is called
CTS_CONFIGURATION_PLUGIN_MGNT.
For more information on ICF services required to run an ABAP Web Dynpro application, see SAP Note
517484 .

Change Control Management

Change Request Management PUBLIC 387
 For more information on activating ICF services, see Activating and Deactivating ICF Services.
• To start the UI using a transaction code, you have the required authorization.

Context

 Note

To start the Plug-in Management Web UI with a Transaction Code, log on to your CTS server with the user
and password that you use to perform imports and call transaction SZENPLUGIN.

To start the Plug-in Management Web UI using the SAP Easy Access user menu, you must first create it as a
favorite:

Procedure

1. Log on to your CTS server with the user and password that you use to perform imports.

2. In SAP Easy Access user menu, choose Favorites Add Other Objects Web Dynpro Application .

The Web Dynpro Application dialog box is displayed.

3. In the Web Dynpro Application field, enter CTS_CONFIGURATION_PLUGIN_MGNT.
4. Specify a description of the favorite, for example CTS Plug-in Management Web UI.
5. Choose Enter.

The Plug-in Management Web UI has been added to your SAP Easy Access user menu.
6. To start the UI, double-click the entry.

Results

CTS Plug-in Management Web UI starts in a web browser.

Related Information

Plug-In Management Web UI - Authorizations [page 385]

Change Control Management

388 PUBLIC Change Request Management
4.4.8.10.3.1 Plug-In Management Web UI - Layout

Context

The Change and Transport System - Plug-In Management Web UI provides an overview of all systems that
belong to your transport landscape. You can use this UI to validate the status of the systems with respect to the
distribution of the CTS service plug-in.

For some screen elements, quick help is available. Quick help provides additional explanation of the screen
elements, mainly for inexperienced users. A green line below the text indicates that quick help is available. To
enable quick help, right-click anywhere on the screen and choose Display Quick Help.

Layout

The Plug-In Management Web UI is divided into a Search Area in the top half of the screen and a Search Result
and Work Area in the lower half.

The Search Area allows you to search for systems according to specific criteria. This enables you to reduce the
number of systems that is displayed in the Work Area. The Search Area is hidden by default.

For more information, see Plug-In Management Web UI - Searching and Refreshing Data [page 390].

At the left side of the Work Area, a small black triangle is displayed. Clicking on the triangle opens a small box
that contains Related Links to related functions. Clicking on a link in the box opens the corresponding function
using SAP NetWeaver Business Client (NWBC) for HTML.

Details on Work Area

The Work Area displays all systems of your transport landscape that have been found according to the search
criteria you specified in the Search Area.

The Work Area allows you to perform the actual tasks that are required for the distribution of CTS plug-ins.
Validating the systems in your transport landscape is the starting-point in the CTS Plug-In Management Web
UI. The validation evaluates whether the CTS Service and CTS Bootstrapper plug-ins need to be updated on the
managed systems. The results of the validation are displayed using traffic light icons in the Status column and
using a link in the Plug-In Distribution column. If the plug-in needs to be updated, the link takes you to a dialog
box that lets you distribute the plug-ins.

The following functions are available:

Function Description More information

Validate Starts a validation for the selected sys-

tems.

Distribute Plug-in Imports the current version of the CTS Plug-In Management Web UI - Distribut-
Service and CTS Bootstrapper plug-ins ing CTS Plug-Ins [page 392]
into the managed system.

Change Control Management

Change Request Management PUBLIC 389
Function Description More information

Filter Allows you to filter the elements dis- Plug-in Management Web UI - Filtering
played in the work area according to [page 391]
different criteria.

Refresh Refreshes the data of all elements dis- Plug-in Management Web UI - Search-
played in the work area. ing and Refreshing Data [page 390]

Personalize Allows you to personalize the layout of

the work area according to your needs.
This includes setting the number of visi-
ble rows and changing the sequence of
the columns in the table as well as hid-
ing columns that you do not need.

The following traffic light icons are available:

Status Quick Info Description

Green light Plug-in distribution is up-to-date The CTS Service and the CTS Boot-
strapper plug-ins are up-to-date in the
managed system.

Red light See details - Validation completed with The CTS Bootstrapper plug-in or the
errors CTS Service plug-in or both are not up-
to-date. Moreover, it is possible that the
import destination required to update
the plug-ins has not been configured.

Grey light Not Yet Validated The system has not yet been validated
since you have started the Plug-In Man-
agement Web UI.

4.4.8.10.3.2 Plug-In Management Web UI - Searching and

Refreshing Data

Use

When the Plug-in Management Web UI is called, the system initially searches for all systems in the transport
landscape.

You can use the search function to perform a search according to specific criteria. By default, the search
criteria are hidden. You can display them using Display Search Criteria. The results of the search are displayed
in the work area.

Change Control Management

390 PUBLIC Change Request Management
The Refresh function is available in the work area. It refreshes the data for the systems that are displayed in
the work area. Note that the refresh function does not perform a new search. It just refreshes the data for all
systems that have been found during the current session.

Procedure

Performing a Search

1. To enable the search, choose Display Search Criteria.

2. Enter your search criteria or select them from the value help. You can specify a range or use the asterisk
(*).
3. To start the search, choose Search or Search and Hide Search Criteria as required.
The systems that are found are displayed in the work area. The search criteria are either displayed or
hidden depending on the option that you selected.
If you select Search and Hide Search Criteria and no systems are found, the search criteria are still
displayed.
4. Reset Search Criteria resets the search criteria to the values with which the Plug-in Management Web UI
was started.

Performing a Refresh

To refresh the data in the work area, choose Refresh.

4.4.8.10.3.3 Plug-in Management Web UI - Filtering

Use

You can use the filter function in the Plug-in Management Web UI to reduce the number of elements in your
work area or to display only specific systems that match your filter criteria.

Procedure

1. To enable the filter function, choose Filter.

A filter row appears.
2. Depending on the elements that are displayed in the column, either enter text or select filter criteria from
the dropdown list.
You can enter any character or character strings including asterisks. You can combine different filter
criteria in multiple text fields. Icons are filtered using their tooltip text. For icons, you select the filter criteria
from a dropdown list.
3. If you have selected a filter criterion from a dropdown list, the filtering result is immediately displayed.
4. If you have entered text, choose Enter to display the filter result.

Additional Notes on the Filter Function

Change Control Management

Change Request Management PUBLIC 391
• To disable the filter function, choose Filter again. This discards the filter and displays all systems and
clusters according to the search criteria.
• The value help of the filter criteria is generated dynamically from the visible elements in the work area.

4.4.8.10.4 Plug-In Management Web UI - Distributing CTS

Plug-Ins

Prerequisites

• You have performed a validation in the CTS Plug-In Management Web UI and the system tells you that there
are CTS plug-ins (CTS Bootstrapper or CTS Service plug-in) that need to be updated.
• All prerequisites are fulfilled that are described in Using the CTS Plug-In Management Web UI [page 382].
• The managed systems to which you want to distribute the CTS plug-ins have the required version of the
transport tools tp and R3trans. For more information, see SAP Note 1665940 .
• The user who is used for plug-in distribution exists in the managed system, and, if the import destination
uses Trust Relationship, the user has the authorization object S_RFCACL in the managed system.

Procedure

1. In the CTS Plug-In Management Web UI, choose the link in the Plug-In Distribution column.

Dialog boxes inform you about the distribution of CTS plug-ins and the detailed results of the validation.
2. Confirm that you want to distribute the plug-in to the managed system.
3. If the plug-ins can be distributed, choose Distribute Plug-Ins.

If the plug-ins cannot be distributed, a message informs you about the reasons.

The CTS plug-ins that must be updated are distributed to the managed system. If the managed system
is a non-ABAP system, the plug-ins are distributed to the ABAP communication system of the non-ABAP
system.

Results

The transport requests for the updated CTS plug-ins are imported in the managed system. The CTS server can
use the functions of the CTS Service plug-in in the managed system.

Change Control Management

392 PUBLIC Change Request Management
4.4.9 Cross-Reference Check

You can use the cross-reference check to detect inconsistencies for objects that are referenced in transport
requests.

Objects in transport requests sometimes refer to other objects that are not included in the transport. The
cross-reference check applies a where-used-analysis to check the referenced objects in transport requests. If
a referenced object doesn’t exist in the target system or if the referenced object in the source system has a
different version than in the target system, the check indicates a potential error. In addition, the check shows
the last transport requests for the missing object versions.

The cross-reference check can handle the following type of data:

• ABAP repository data.

• Dictionary objects
• Customizing objects

Logical transport objects and SAP HANA objects are not supported.

Git-enabled changes (SMGH) don’t use the cross-reference check.

The cross-reference check is triggered automatically when a transport request is exported from the
development system to follow-up systems or when a transport request is imported into a system. You can
also perform the check manually in the Transport-Related Checks assignment block on the WebClient UI.

It depends on the authorizations of the users whether they can ignore the error messages or warnings and
continue the action:

• Change Request Management: Administrators, change managers, and IT operators can ignore both errors
and warnings. Developers can ignore warnings.
• Quality Gate Management: QGM administrators, QGM change managers, and QGM IT operators can ignore
both errors and warnings. Developers can ignore warnings.

Prerequisites

• You have the installed the ST-PI plug in ST-PI 740 or ST-PI 2008.1 SP16 in the managed systems.
• You have implemented the SAP Notes listed in the collective note 2475591
• To display the Cross-Reference Check tab and change the settings for the cross-reference check, you have
the role administrator, change manager, or IT operator.

Configuring the Cross-Reference Check

In the Administration Cockpit, on the Cross-Reference Check tab, you can do the following:

• Deactivate or activate the check

• Configure general settings for the check
• Configure track-specific settings

Change Control Management

Change Request Management PUBLIC 393
You can specify the check mode that determines what happens when the check detects a potential error in a
transport request:

• In the default mode, only a warning is issued when you release the transport request and an error message
is issued and the import is blocked when you import a transport request.
• If you select the Stop at Error mode, the system always issues an error message and blocks the release or
import of the transport request.
• If you select the Warning Only mode, the system always only issues a warning.
• If you select Silent, you must check the transport request manually to get a conflict warning. There’s no
automatic check during release or import

 Note

Any settings that you make on the Cross-Reference Check tab in the Administration Cockpit are active
immediately.

Related Information

Performing Transport-Related Checks [page 150]

Administration Cockpit for Change Request Management [page 291]
Administration Cockpit for Quality Gate Management [page 535]

4.4.10 Assigning a Change Document to Transport Requests

Created Outside SAP Solution Manager

In Change Request Management and Quality Gate Management (QGM), you can assign a change document to
transport requests created in a managed ABAP development system or in Eclipse ADT.

Prerequisites

• In the managed development system, you have implemented SAP Note 2471766 , or you have installed a
support package stack containing this SAP Note.
• In the managed development system, you have installed the latest SAP Solution Tools Plug-in (ST-PI) in
alignment with SAP Solution Manager 7.2 SPS 6.
• If you are using central CTS, you have customized the role SAP_CM_SMAN_BACK and applied it to the back
RFC user for the correct authorization.
• To support transport requests created in Eclipse ADT, you have installed SAP BASIS release is NW 750 and
ADT 3.14.
• To configure whether a change document must be assigned, in the SAP Solution Manager system, go
to the Administration Cockpit Landscape Overview . For each managed development system, under
Change Document Assignment you choose whether an additional change document attribute is needed

Change Control Management

394 PUBLIC Change Request Management
 when creating a transport request in the transport organizer of the managed development system. You can
select the option “required”, “optional”, or “not required”.
• To assign a change document to transport requests created in Eclipse, you have installed the latest ST-PI
in alignment with SAP Solution Manager 7.2 SP12, and you have implemented SAP Note 2958393 in the
SAP Solution Manager system.

Activities

Creating Transport Requests in the Managed System

1. In your managed development system, call transaction SE09.

2. To create a transport request, choose Create and enter the required information.
Depending on the selected option for change document assignment, the transport request creation dialog
offers different fields:
• If change document assignment is required, you must enter a change document ID.
• If change document assignment is optional, you can choose to leave the change document ID field
empty and instead fill out the fields Project and Target. If you assign a change document ID, the Project
field and Target field are ignored.
• If change document assignment is not required, you cannot assign a change document.

 Note

To search for the change document, use the F4 value help. You can use the search criteria of change
description, change ID, user name (only for Change Request Management), transaction type, and
cycle / QGM scenario.

The fields “Change Description”, “Change ID”, “Transaction Type”，“Cycle / QGM Scenario” support
wildcards (‘*’) in the search value. For example, you can enter ZM* as transaction type.

The search results offer only change documents with a status that allows transport request creation:
For Change Request Management, this means UI object CREATE_REQ in the Customizing table
AIC_PROC_EDIT. QGM change documents must have an “open” status.

3. Save the transport request. The transport request is created and, if applicable, assigned to the change
document.
4. If the transport request is created but fails to be registered to the SAP Solution Manager system, the
local transport request stays as it is. For trouble shooting, go to the SAP Solution Manager system to
see the application log. Call transaction SLG1 and search for the object /TMWFLOW/CMSCV and sub-object
CHNG_ASSI_TR_CREATE for your application log. After solving the issue, manually reassign the transport
request to the change document in the SAP Solution Manager system.

Creating Transport Requests in Eclipse ADT

In Eclipse, when you save an object you created or edited, you can choose an existing transport request or
create a new transport request.

When you create a new transport request to save the object, select a change document ID by browsing the list.

Change Control Management

Change Request Management PUBLIC 395
Related Information

SAP Note 2745405

Landscape Overview [page 323]

4.4.11 Import Strategies: Standard, Status-Dependent, and

Selective

Use

When you import transport requests into the quality, preproduction, and production systems, the system
imports all transport requests in the import queue of the system, regardless of the status of the change
document. Using the status-dependent import, you can import transport requests into systems with specific
roles, depending on the status of the change documents. Using the selective import, you can remove changes
and transport requests from the import.

Prerequisites

• You have made the settings in Customizing (transaction SPRO) under SAP Solution Manager
Capabilities (Optional) Change Control Management Transport Management System Define Import
Strategy for Transport Requests .
• To enhance your preferred import strategy with custom checks, you have implemented BAdl /
TMWFLOW/SCMA_IMPORT_BADI in Customizing (transaction SPRO) under SAP Solution Manager
Capabilities (Optional) Change Control Management Business Add-Ins BAdI: Custom Import Strategy
Enhancement .

If you make no settings, all released transport requests for a change document are imported, independently of
the change document status.

Features

If you do not want to import all transport requests of the import queue, choose your preferred import strategy:

• You can import a transport request only if the change document has a specified status.

 Example

You can specify, for example, the following:

• Transport requests for normal changes are imported only if the change document has the status
Successfully Tested.

Change Control Management

396 PUBLIC Change Request Management
 • Transport requests for urgent changes are imported only if the change document has the status
Authorized for Production.
• Transport requests for defect corrections are imported only if the change document has the status
Successfully Retested.

• You can specify in Customizing (transaction SPRO), per cycle type, system, system role and transaction
type, whether and how imports depend on the status.
• You can specify that you want to select the transport requests that are to be imported. The system
displays a dialog box showing all transport requests for an import, either all or those in a change document
with a specific status. To avoid an unintentional import, by default, no transport request is selected. Select
the transport requests you want to import. You can also select all or deselect all transport requests.

 Note

Selecting change documents individually can affect the transport request import sequence, because
the import buffers of the follow-on systems are modified. If the transported change documentss are
related to each other, or have interdependencies, we do not recomment that you import selectively.

The following table provides an overview of which transport requests are imported with each of the import
strategies:

Import Strategy Change Documents Change Documents with Non-Applicable Sta- Transport Requests
with Specified Status tus without Assignment
to Change Document
Original Transport Re- Transport of Copies
quest

Standard strategy (Im-    

port all transport re-
quests)

Status-Dependent Im-    
port

Selective Import    

(depending on selec- (depending on selec- (depending on selec- (depending on selec-

tion) tion) tion) tion)

Status-Dependent Se-    
lective Import (depending on status (depending on selec- (depending on selec-
and selection) tion) tion)

The import strategy should be defined at the beginning of your change cycle processes and you should keep
it as stable as possible. If you want to change the import strategy, for example, from status-dependent import
to selective import, you must cancel all old import jobs scheduled in the affected cycles and reschedule them
afterward.

Change Control Management

Change Request Management PUBLIC 397
  Note

With BAdl /TMWFLOW/SCMA_IMPORT_BADI, you can define custom checks to enhance your existing import
strategy during cycle level import. The BAdI applies to the following actions:

• Imports triggered from task list

• Imports triggered by scheduled import jobs for change cycle
• Transport-related checks on change cycle level

Integration

Integration with downgrade protection: After selecting the changes and transport requests for import, the
transport requests are checked for potential downgrade conflicts. If the system finds conflicts, they are
displayed in a dialog window. You can either ignore all conflicts or cancel the operation.

• If you ignore all conflicts, the import continues. The conflicts are recorded in the conflict history and in the
application log.
• If you cancel the operation, the selective import dialog window is displayed again.

Related Information

Importing Transport Requests [page 127]

Downgrade Protection [page 360]

4.4.12 Managing Changes for Non-ABAP Systems

The Enhanced Change and Transport System (CTS+) enables you to transport Java objects and SAP-related
non-ABAP applications in your system landscape, alongside ABAP objects. You can also administer non-ABAP
systems in a CTS transport domain in SAP NetWeaver Application Server ABAP.

Use

Moving developments and changes across a system landscape requires the management of transport. In
response to this need, SAP offers the Change and Transport System (CTS) for ABAP transports and the
Enhanced CTS (CTS+) for non-ABAP as well as non-SAP applications.

CTS helps you to transport software changes between the systems in your transport landscape. It assures that
every change that has been performed in the development system is first imported into the test system before
it can be imported into the production system.

The Enhanced CTS synchronizes changes for ABAP- and non-ABAP-based SAP system landscapes. It
consolidates the changes independent of whether they’re based on ABAP or non-ABAP or even non-SAP.

Change Control Management

398 PUBLIC Change Request Management
CTS+ provides a unified transport tool and makes the work of administrators easier when executing imports.
You only need access to one tool to execute imports for different backend systems. The deployment tools are
called automatically.

CTS together with CTS+ enables the management of ABAP and non-ABAP objects, including combined
transports for mixed objects like ABAP and JAVA.

Integration

CTS and CTS+ are fully compatible with SAP Solution Manager, and can be used in Quality Gate Management
and Change Request Management.

The enhanced CTS is an additional option to manage changes for non-ABAP content. Its integration into SAP
Solution Manager makes it easier to control of different types of changes within SAP system landscapes that
are based, for example, on AS Java.

For information how to set up CTS+, see Configuring CTS+ in SAP Solution Manager 7.1 and 7.2 .

Related Information

Change Control Management Using Central CTS [page 399]

Enhanced Change and Transport System

4.4.13 Change Control Management Using Central CTS

The central Change and Transport System (central CTS) provides a technical infrastructure for the enhanced
flexibility functions in Change Control Management.

Use

You can use central CTS with Change Request Management and Quality Gate Management. Central CTS is the
transport foundation; Change Request Management and Quality Gate Management (QGM) manage the change
control process and provide the user interfaces.

For each new change cycle, you can decide whether you want to use CTS or central CTS.

If you activate central CTS for your change cycle, several functions in Change Request Management and Quality
Gate Management have enhanced features. These are described in the documentation of each function.

Change Control Management

Change Request Management PUBLIC 399
Prerequisites

• You are using a SAP Solution Manager version that supports central CTS. Central CTS is delivered as the
CTS Plug-In add-on, which is part of the SAP Solution Manager 7.1 stack, as of Support Package 05.
• Your system landscape is set up accordingly. For central CTS, you need the SAP Solution Manager system,
and managed systems that are connected to the central CTS server and that can be controlled by it.

Features

After activating central CTS for your change cycle, you can use the following functions:

• Flexible assignment of transport requests, even after their release

• Synchronous control and monitoring of parallel transport routes
• Prevention of conflicts between central transport control and local transport administration (local
Transport Management System — STMS)
• Combine individual systems (different applications) to reflect semantic dependencies
• Synchronize transports requests if the resolution of an issue involves different applications
• Bundle transports if more than one transport request is to be imported to complete the issue (for example,
initial change and corrections)
• Ensure that only the most recent version of an object is imported and that no objects are overwritten
(downgrade protection)
• Enhanced unification of ABAP and non-ABAP transports

Related Information

Central Change and Transport System [page 400]

Configuring Central Change and Transport System - Overview [page 407]
Change Request Management [page 21]
Quality Gate Management [page 478]
Setting Up Quality Gates and Assigning Phases [page 487]
Enhanced Transport Functions with Central CTS [page 448]
SAP Note 1665940
https://archive.sap.com/documents/docs/DOC-49155

4.4.13.1 Central Change and Transport System

Use

Central Change and Transport System (central CTS) enhances the classic CTS with functions for complex
heterogeneous system landscapes, which allow you to control transports within a transport landscape

Change Control Management

400 PUBLIC Change Request Management
centrally. This means you can combine multiple systems of your transport landscape into system clusters.
You can bundle transports between these clusters using transport collections. A transport collection is a
combination of the transports from the different systems of a cluster.

SAP Solution Manager represents the central CTS server that is responsible for the central management of the
transport landscape. You can control transports into the managed systems from the central CTS server.

 Note

Before using central CTS on SAP Solution Manager, read SAP Note 2231041 Collective Note: central CTS
with SAP Solution Manager 7.2.

Implementation Considerations

The functions of central CTS on SAP Solution Manager are provided as part of SAP NetWeaver. In addition,
the CTS plug-in (software component CTS_PLUG) is installed in SAP Solution Manager. This classifies SAP
Solution Manager as a central CTS server and makes the functions of central CTS available for distribution to
the managed systems.

Managed systems can have the following releases:

• ABAP systems: For more information on the releases of the managed systems that are supported by
central CTS as well as on the required tp and R3trans versions, refer to SAP Note 1665940 .
• Non-ABAP systems: The enhanced CTS must be configured for the non-ABAP system and SAP Solution
Manager must be used as the domain controller and communication system.

Usage of central CTS is optional. You can use it to exploit the enhanced flexibility functions in Change Request
Management and Quality Gate Management (QGM). Before you implement central CTS for your transports,
check whether it is suitable for your situation. You can also continue to use classic CTS, TMS, or classic Change
Request Management and QGM.

If you want to test whether the functions of central CTS are suitable for your requirements, you can initially use
central CTS for just part of your landscape or projects, or just for a test project.

Integration

Central CTS enhances the existing Change and Transport System. You can only use central CTS in connection
with the existing CTS. Depending on the configuration of central CTS, some functions of the existing CTS might
be disabled. For example, if the central control of transports is activated, then the local execution of transports
in the systems might be deactivated. Central CTS is integrated into Change Request Management and QGM of
SAP Solution Manager. It is required if you want to use the enhanced flexibility functions.

Features

Combine individual systems with content dependencies into system clusters

Change Control Management

Change Request Management PUBLIC 401
• All systems in your transport landscape that you want to supply with transports at the same time can
be grouped into clusters. You can combine Business Suite development systems and Portal development
systems to form a single cluster. You can also combine the relevant consolidation, test, and production
systems into clusters of their own. This means, you create system clusters for systems that have the same
role (for example, DEV, QAS, and PRD).
• You can combine ABAP and non-ABAP systems into a system cluster.
• System clusters are defined centrally for your transport landscapes in the central CTS server.

Combine transports into transport collections

• You create transport collections to combine transports from different systems. In this way you can, for
example, transport ABAP developments together with non-ABAP developments.
• After exporting a transport collection you can add further transport requests to the transport collection.
You can then import the transport collection again but only the changed transport requests will be
reimported. This means, for example, that you can collect all related transport requests in a collection
which contains both a new version of an application as well as the necessary corrections for that
application.

 Note

You create transport collections in Change Request Management or QGM.

More Information

• Concepts for Central CTS [page 402]

• Configuring Central Change and Transport System - Overview [page 407]
• Using Central Change and Transport System [page 436]
• Change Control Management Using Central CTS [page 399]
• Central CTS on SAP Community Network: https://scn.sap.com/docs/DOC-7643#centralCTS

4.4.13.1.1 Concepts for Central CTS

Use

For central CTS, new entities are required to combine systems and the transports within the systems. The
entity which combines systems is called system cluster. The entity which combines transport requests is called
transport collection.

More Information

• System Cluster [page 403]

Change Control Management

402 PUBLIC Change Request Management
• Transport Collection [page 404]
• Technical Details of the CTS Plug-In [page 383]

4.4.13.1.1.1 System Cluster

Use

Those systems in your transport landscape that you want to supply with transports at the same time can be
grouped into system clusters. You create a system cluster for systems that have the same role (for example,
DEV, TST, and PRD). In this way you can, for example, combine a Process Integration (PI) development system
together with a Business Suite development system and a Portal development system into a single cluster. You
can also combine the relevant test, and production systems into one cluster.

You can combine ABAP and non-ABAP systems into a system cluster.

You configure system clusters centrally in the central CTS server using the Central CTS Configuration Web
UI. System clusters are represented in Transport Management System (TMS) by a three-character system
identifier (SID), like any other system. However, they are not real systems that you have to install. The cluster
SID has to be unique in your transport landscape.

You can configure your system clusters in such a way that the central CTS server takes over the control of your
transports. This means the local CTS can be deactivated.

Figure: Example of a system cluster track for PI, Portal, and Business Suite developments consisting of development, test,
and production clusters.

The graphic shows a sample three-cluster track. There is one development cluster, one test cluster, and one
production cluster. Each cluster contains a PI, a Portal, and a Business Suite system with the respective role
(development, test, and production).

Change Control Management

Change Request Management PUBLIC 403
  Note

When creating a cluster track, for example, consisting of a development, a test, a pre-production, and a
production cluster, it is possible to set up a so-called “uneven” cluster track. “Uneven” means that not all
system clusters in the cluster track contain the same number of systems with the same roles. For example,
if the PI track does not have a pre-production system, but all other tracks have one, you can create a
pre-production cluster for the other applications and omit PI from the pre-production cluster.

More Information

• Transport Collection [page 404]

4.4.13.1.1.2 Transport Collection

Use

After combining systems as system clusters, you can combine transport requests within the system clusters.
The entity which combines transport requests is called a transport collection.

Transport requests that are part of a transport collection are released separately. The released transport
requests are transported when the transport collection is released. They are then imported into the
corresponding test or production systems contained in the follow-on system cluster.

Change Control Management

404 PUBLIC Change Request Management
 Figure: Example of a transport collection that contains transport requests from Process Integration (PI), Enterprise Portal,
and Business Suite systems.

The graphic shows a transport collection that contains multiple transport requests from the development
systems that are part of the system cluster. The transport collection contains transport requests from the
development systems: one transport request from the Business Suite system (BSD), two transport requests
from the Portal system (EPD), and one transport request from the Process Integration system (PID).

More Information

System Cluster [page 403]

4.4.13.1.1.3 Technical Details of the CTS Plug-In

Use

The CTS plug-in is an add-on that installs the software component CTS_PLUG on SAP systems. This classifies
the SAP system as a CTS server. You can find details on the installation and supported SAP releases in SAP
Note 1665940 .

The CTS plug-in (software component CTS_PLUG) contains the following further plug-ins:

• CTS Service plug-in

This plug-in contains CTS functions that are required in the managed systems. This includes central CTS
functions as well as functions required for downgrade protection checks in Change Control Management of
SAP Solution Manager.

Change Control Management

Change Request Management PUBLIC 405
 The CTS Service plug-in is release-dependent. There is one CTS Service plug-in for each SAP NetWeaver
release. For an overview of supported releases, refer to SAP Note 1665940 .
• CTS Bootstrapper plug-in
This plug-in contains functions that are required to activate the CTS Service plug-ins on the managed
systems.
There is one Bootstrapper plug-in for each SAP NetWeaver release, available for the same releases as the
CTS Service plug-ins.

From a technical point of view, the CTS plug-ins are transport requests. When the CTS plug-in (software
component CTS_PLUG) is installed in an SAP system, the CTS Service plug-ins and the CTS Bootstrapper
plug-in are extracted to the transport directory. They can be distributed from the CTS server to the managed
systems. Distributing the plug-in means importing the transport requests in the managed systems.

CTS Service plug-ins are independent of the SAP NetWeaver Support Package level. Therefore, they can always
be installed in a system with a minimum Support Package level of the software component SAP_BASIS. When
the transport request of the CTS Service plug-in is imported in the managed system, the transport request of
the CTS Bootstrapper plug-in is also imported.

These characteristics enable the CTS Service and Bootstrapper plug-ins to be installed at any time, even during
production operation. In particular, no system restart is necessary and there are no constraints concerning
production usage. In this way, you can use the current SAP technology in SAP systems without the need to
update all managed systems to the current Support Package level. You can update the managed systems in the
maintenance cycles that you are used to.

Figure: Distribution of CTS plug-ins to managed systems

The graphic illustrates the plug-in distribution process.

Change Control Management

406 PUBLIC Change Request Management
1. The CTS server asks the managed system if the CTS Service and the Bootstrapper plug-ins are available
and in which version.
2. The managed system returns the required information.
3. If the CTS Service or Bootstrapper plug-ins need to be updated, you can trigger the distribution from the
CTS server to the managed system.

 Note

The system compares the versions of the CTS Service and Bootstrapper plug-ins on the managed
systems with the versions available in the transport directory of the CTS server. It does not check for
versions of the CTS plug-in that are available on SAP Support Portal.

If the CTS plug-ins on managed systems are out of date, that means if they have lower version than the
plug-in on the CTS server, you get a warning but you can still perform operations that use central CTS
or downgrade protection.

 Note

If the managed systems are not part of the SAP Solution Manager transport domain or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute
the CTS plug-ins.

For more information, see SAP Note 1688276 .

Updates to the CTS Plug-In

To import updates or corrections to the CTS server (SAP Solution Manager), you must import the relevant SAP
NetWeaver Support Packages, or implement the relevant SAP Note corrections into SAP Solution Manager.

To import corrections that are required on the managed systems, you must import the relevant Support
Packages for the CTS plug-in into SAP Solution Manager and distribute the CTS plug-ins to the managed
systems. For an overview of the Support Packages available for the CTS plug-in, refer to SAP Note 1665940 .

More Information

• Central CTS: Distributing CTS Plug-Ins to the Managed Systems [page 432]
• Plug-In Management Web UI - Distributing CTS Plug-Ins [page 392]

4.4.13.1.2 Configuring Central Change and Transport System

- Overview

Use

Before you can use the central Change and Transport System (central CTS), you must prepare the systems
involved.

Change Control Management

Change Request Management PUBLIC 407
The starting point for the configuration is the Central CTS Configuration Web UI. This UI shows an overview of
all systems of your transport landscape. You can check whether the systems can be used for central CTS and
perform all configuration tasks required for setting up your systems for central CTS.

 Note

You can also find all configuration steps including screenshots and examples in the How-
To-Guide How To... Set Up cCTS for ChaRM and QGM at https://www.sap.com/documents/
2016/08/2cd565a1-847c-0010-82c7-eda71af511fa.html .

Procedure

The following table lists the tasks that are required to configure central CTS. To navigate directly to a specific
topic use the links in the More Information section.

Make sure that the systems that you want to use with There are specific prerequisites concerning the availability of
central CTS meet the requirements. central CTS software, and required authorizations, for exam-
ple.

Start the Central CTS Configuration Web UI in your cen- Your central CTS server is your SAP Solution Manager sys-
tral CTS server. tem. Start the Central CTS Configuration Web UI there to
perform all configuration tasks.

Select the systems that you want to configure for central Before you can begin to configure your systems for central
CTS and validate their statuses. CTS, you need to find out if the systems meet the require-
ments. To do this, select the systems that you want to use
with central CTS and choose Validate.

The system checks which configuration tasks have already

been performed. Depending on the result, the system shows
you the tasks you still need to perform.

Change Control Management

408 PUBLIC Change Request Management
Perform the missing configuration tasks. An overall status is displayed for each system that has been
validated. If all configuration tasks have been performed, a
green traffic light icon appears. If there are configuration
tasks missing or if the system could not calculate a result, a
red traffic light icon is displayed. To view the results, choose
See Details in the Status column. The dialog box displays a
list of status messages. If you select a status message in the
upper area of the dialog box, the long text of the message is
displayed in the lower area of the dialog box. If a column con-
tains a link with an error message, selecting the link either
lets you perform the configuration task or provides more
information about the required task.

This can include the following tasks:

• Creating system clusters

• Creating RFC connections to the managed systems
• Setting TMS parameters that are required for using cen-
tral CTS
• Distributing plug-ins to the managed systems

Depending on the task you performed and on your personal

settings, the system may automatically trigger validation
(when assigning systems to clusters, for example). If this
is not the case, choose Validate after performing the task to
retrieve the current configuration status.

Repeat the configuration steps for all systems that you If all traffic lights are green for all systems that you want to
want to configure for central CTS. use with central CTS, you must still perform the following
steps.

Connect the system clusters. To enable transports between clusters, you need to define
transport routes between the clusters. You do this in the
same way as for systems in Transport Management System
in your central CTS server.

Connect the individual systems that are contained in the After you have configured the transport routes at cluster
clusters. level, define the transport process of the individual systems.
You do this by determing the import targets for all target
systems that belong to a cluster.

Change Control Management

Change Request Management PUBLIC 409
Distribute the TMS configuration to all systems in the Perform this task once you have completed the configura-
transport domain. tion steps for all the systems that you want to use with
central CTS. To distribute the configuration to all systems
in the transport domain, choose Distribute Configuration in
the central CTS Configuration Web UI.

 Note
It is sufficient to perform this configuration step once af-
ter you have performed all steps for all systems that you
want to use with central CTS. The configuration will then
be distributed to all systems of the transport domain.

If systems from foreign domains (with or without do-

main links) are part of your system clusters, you must
perform the configuration distribution on the domain
controller(s) of these systems.

Result

You can use the systems for central CTS.

More Information

• Prerequisites for Configuring Central CTS [page 411]

• Central CTS Configuration Web UI - Layout [page 414]
• Starting the Central CTS Configuration Web UI [page 416]
• Creating or Changing System Clusters [page 421]
• Configuring RFC Destinations for Cenral CTS [page 428]
• Setting TMS Parameters for Central CTS [page 424]
• Distributing CTS Plug-ins to the Managed Systems [page 432]
• Configuring Transport Routes (link to classic Transport Management System documentation)
• Defining Import Targets [page 434]

Change Control Management

410 PUBLIC Change Request Management
4.4.13.1.2.1 Prerequisites for Configuring Central CTS

Use

To configure central Change and Transport System (CTS) make sure that the following prerequisites are met:

• The SAP Solution Manager system and the systems that you want to manage centrally have a release that
is supported by central CTS. The CTS plug-in is installed in SAP Solution Manager. For further information
on the CTS plug-in and an overview of the supported releases for managed systems, see SAP Note
1665940 .
• You have activated the ICF service for the central Change and Transport System Configuration UI. The
service is called CTS_CONFIGURATION.
• You have a basic understanding of working with the existing Change and Transport System and with the
Transport Management System, particularly its configuration.
• Transport Management System is configured for the managed systems.
• The managed ABAP systems and the communication systems of the non-ABAP systems have a trust
relationship with the central CTS Server (SAP Solution Manager). For this, you have performed the
Managed Systems Configuration in SAP Solution Manager.
• If the managed systems are not part of the SAP Solution Manager transport domain or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute the
CTS plug-ins.
For more information, see SAP Note 1688276 .
• You have the relevant authorizations for configuring central CTS.

More Information

• Links to CTS and TMS documentation:

• Change and Transport System - Overview (BC-CTS)
• Transport Management System (BC-CTS-TMS)
• Links to ICF documentation:
• Activating and Deactivating ICF Services
• For more information on ICF services required to run an ABAP Web Dynpro application, see SAP Note
517484 .
• SICF authorizations: Authorizations
• Maintaining Trust Relationships between SAP Systems
• Authorizations for Configuring Central CTS [page 412]

Change Control Management

Change Request Management PUBLIC 411
4.4.13.1.2.2 Authorizations for Configuring Central CTS

Use

Authorizations Required on the CTS Server (SAP Solution Manager)

In general, the user must have a copy of the following role assigned:

• SAP_BC_TRANSPORT_ADMINISTRATOR

If you do not want to use the predefined authorization or if the role contains too many authorizations, you
can run an authorization trace to find out which authorizations are required. For more information, refer to the
information provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

Task Authorization

Starting the Central CTS Configuration Web UI using the The user who wants to start the UI using the transaction
transaction code SZENCONFIG. code SZENCONFIG needs to be assigned authorization ob-
ject S_TCODE with field TCD and value SZENCONFIG.

This authorization object is part of the roles

SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANS-
PORT_ADMINISTRATOR as of SAP NetWeaver 7.0 Enhance-
ment Package 2, SP13.

Displaying objects on the UI including the following tasks: Display authorization: The user needs to be assigned au-
thorization object S_TRANSPRT with field ACTVT and value
• Searching for systems or system clusters
03.
• Displaying clusters
• Displaying search help and value help

Changing objects including the following tasks: Change authorization: The user needs to be assigned the au-
thorization object S_CTS_ADMI with field CTS_ADMFC and
• Creating, changing, or deleting system clusters
value TABL.
• Changing TMS parameters
• Distributing the TMS configuration

Distributing CTS plug-ins to the managed systems On the CTS server, the user needs to be assigned
change authorization (see above) and authorization object
S_TRANSPRT with field ACTVT and value 03.

 Note

If the user needs both display and change authorization, assign both authorizations.

Authorizations Required on the Managed System

• User TMSADM must exist on the managed system. It must not be locked and must have the standard
profile assigned (S_A.TMSADM).

Change Control Management

412 PUBLIC Change Request Management
• Make sure that the user who performs a validation in the Central CTS Configuration Web UI (logon user)
also exists in the managed systems for which he wants to perform the validation. Otherwise, validatation
will fail.
• To distribute CTS plug-ins, the user who is used for plug-in distribution to the managed system (usually
the user that is logged on to the current system) must have the authorization object S_RFCACL in the
managed system if the import destination uses Trust Relationship. For more information on S_RFCACL and
Trust Relationship, refer to the information provided in the “More Information” section.

In general, the user who is used for plug-in distribution to the managed system must have copies of the
following roles assigned:

• SAP_BC_TRANSPORT_OPERATOR: Required for distributing CTS plug-ins

• SAP_BC_TRANSPORT_ADMINISTRATOR: Required if the managed system is not in the same transport
domain as the CTS server.

If you do not want to use the predefined authorization or if it contains too many authorizations, you can run an
authorization trace to find out which authorizations are required. For more information, refer to the information
provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

• S_TRANSPRT with field ACTVT and value 03

• S_CTS_ADMI with field CTS_ADMFC and value IMPA
• S_DATASET with the values required to access the transport directory. This authorization is required
to read files. If the user does not have this authorization object assigned the error message
OPEN_DATASET_NO_AUTHORITY is displayed.
• S_RFC with the following values:
• field ACTVT and value 16
• field RFC_NAME and values STPA and TMSC
• field RFC_TYPE and value FUGR

More Information

• Maintaining Trust Relationships between SAP Systems

• Authorization Object S_RFCACL
• Using the System Trace to Record Authorization Checks (Transaction STAUTHRACE)
• Authorizations in the CTS
• Transport Operator
• Transport Administrator
• For more information on authorization object S_TCODE, see Authorization Checks.
• For more information on the releases and Support Packages which delivered changes to the
roles SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANSPORT_ADMINISTRATOR, see SAP Note
1748949 .

Change Control Management

Change Request Management PUBLIC 413
4.4.13.1.2.3 Central CTS Configuration Web UI - Layout

Concept

The Central Change and Transport System (central CTS) Configuration Web UI provides an overview of all
systems and system clusters that belong to your transport landscape. It displays the configuration status of
systems and clusters with respect to central CTS.

You can use the Central CTS Configuration Web UI to perform all tasks that are necessary for configuring the
systems for central CTS.

For some screen elements, quick help is available. Quick help provides additional explanation of the screen
elements, mainly for inexperienced users. A green line below the text indicates that quick help is available. To
enable quick help, right-click anywhere on the screen and choose Display Quick Help.

Features

Layout

The Central CTS Configuration Web UI is divided into a Search Criteria area in the top half of the screen and a
Search Result and Work Area (Work Area) in the lower half.

The search area allows you to search for system clusters or systems according to specific criteria. This enables
you to reduce the number of systems displayed in the work area. The search area is hidden by default.

At the left side of the Work Area, a small black triangle is displayed. Clicking on the triangle opens a small box
that contains Related Links to important functions that you may need to configure central CTS, such as RFC
Destination Maintenance. Clicking on a link in the box opens the corresponding function using SAP NetWeaver
Business Client (NWBC) for HTML.

Work Area

The work area displays all systems and system clusters of your transport landscape that have been found
according to the search criteria you specified in the search area. The work area allows you to perform the actual
tasks that are required for configuring the systems for central CTS.

Validating the systems is the starting point in the Central CTS Configuration Web UI. The validation evaluates
whether the systems can be configured for use with central CTS. The results of the validation are displayed
using traffic light icons in the Status column and by using text messages. If actions need to be performed,
the text is displayed as a link that either leads to additional explanation or allows you to perform the required
action.

The Status column gives an overall status of the results of the validation for the system or cluster.

Change Control Management

414 PUBLIC Change Request Management
The following functions are available in the toolbar:

Function Description More information

Validate Starts a validation for the selected sys- Configuring Systems for Central
tems and system clusters Change and Transport System [page
407]

Cluster Create Cluster /Display/ Allows you to create system clusters Creating or Changing System Clusters

Change Cluster/Delete Cluster and/or assign systems to existing clus- [page 421]
ters, as well as delete existing clusters

Distribute Configuration Allows you to distribute the TMS config- Configuring Systems for Central
uration to all systems in the transport Change and Transport System [page
domain 407]

Display as: Allows you to switch the layout of the Central CTS Configuration Web UI - Per-
work area between Hierarchical List and sonalization [page 419]
Flat List.

Filter Allows you to filter the elements dis- Central CTS Configuration Web UI - Fil-
played in the work area according to tering [page 417]
different criteria.

Refresh Refreshes the data of all elements dis- Central CTS Configuration Web UI -
played in the work area. Searching and Refreshing Data [page
418]

Personalize Allows you to personalize the layout of Central CTS Configuration Web UI - Per-
the work area according to your needs. sonalization [page 419]
This includes setting the number of visi-
ble rows and changing the order of the
columns in the table as well as hiding
columns that you do not need.

The following traffic light icons exist:

Status Tooltip Text Description

Green light Configuration is up-to-date The system has been configured for central CTS. It
can be used with central CTS.

Red light See details - Validation com- Some configuration steps are missing for the system
pleted with errors to be used with central CTS or the system cannot
be used at all with central CTS. For example, if the
release or Support Package level of the system is not
supported, it cannot be used with central CTS.

Yellow light Cannot be validated This status is for clusters that do not contain any sys-
tems.

Change Control Management

Change Request Management PUBLIC 415
Status Tooltip Text Description

Grey light Not yet validated The system has not yet been validated since you have
started the Central CTS Configuration Web UI.

The following tasks have to be performed on request if the system displays a related error message:

Task Description More information

Setting TMS To be able to use central CTS, the system requires Setting TMS Parameters [page 424]
parameters specific TMS parameters. If these are not set cor-
rectly, you must set them. A detailed description is
provided on how to set them.

Creating RFC To be able to communicate with the managed sys- Configuring RFC Destinations [page 428]
connections tems, specific RFC connections between the central
CTS server and the managed systems are required.
If the RFC connections have not been created, you
must do this. A detailed description is provided on
how to create them.

Updating plug- To be able to use the up-to-date functions of central Distributing CTS Service Plug-Ins to the Managed
ins CTS in the managed systems, the current version Systems [page 432]
of the CTS Service and CTS Bootstrapper plug-ins
must exist there. You can update them by clicking
on the corresponding link.

4.4.13.1.2.3.1 Starting the Central CTS Configuration Web UI

Use

You can start the UI using a transaction code if you have sufficient authorization to do so, or using your
favorites in the SAP Easy Access user menu.

Prerequisites

• You have activated the ICF service for the Central CTS Configuration Web UI.
• To start the UI using a transaction code, you have the required authorization.

Change Control Management

416 PUBLIC Change Request Management
Procedure

Starting Central Change and Transport System Configuration Web UI

To start the UI using a transaction code, log on to your SAP Solution Manager system and call transaction
SZENCONFIG.

Optional: Adding the Central CTS Configuration Web UI to your favorites in the SAP Easy Access user
menu

This allows you to call the Central CTS Configuration Web UI from the SAP Easy Access user menu.

1. In SAP Easy Access user menu, choose Favorites Add Other Objects Web Dynpro Application .
The Web Dynpro Application dialog box is displayed.
2. Enter CTS_CONFIGURATION in the Web Dynpro Application field.
3. Specify a description of the favorite, for example cCTS Config UI.

You can now start the Central CTS Configuration Web UI from your Easy Access user menu.

More Information

• Prerequisites for Configuring Central CTS [page 411]

• Authorizations for Configuring Central CTS [page 412]

4.4.13.1.2.3.2 Central CTS Configuration Web UI - Filtering

Context

You can use the filter function in the central Change and Transport System Configuration Web UI to reduce
the number of elements in your work area or to display only specific systems or clusters that match your filter
criteria.

Procedure

1. To enable the filter function, choose Filter.

A filter row appears.

2. Depending on the elements that are displayed in the column, either enter text or select filter criteria from
the dropdown list.

Change Control Management

Change Request Management PUBLIC 417
 You can enter any character or character strings. The system will search for any text that contains the
character or character string. You can combine different filter criteria in multiple text fields. Icons are
filtered using their tooltip text. For icons, you select the filter criterion from a dropdown list.

If you have selected a filter criterion from a dropdown list, the filtering result is immediately displayed.
3. If you have entered text, choose Enter to display the filter result.

4.4.13.1.2.3.3 Central CTS Configuration Web UI - Searching

and Refreshing Data

Use

When the Central CTS Configuration Web UI is called, the system performs an initial search. The search criteria
for the initial search may vary depending on the application that starts the Central CTS Configuration Web UI.
If you start the UI directly, the system initially searches for all systems and system clusters in the transport
landscape.

You can use the search function to perform a search according to specific criteria. By default, the search
criteria are hidden. You can display them using Display Search Criteria. The results of the search are displayed
in the work area.

The Refresh function is available in the work area. It refreshes the data for the systems and clusters that are
displayed in the work area. Note that the refresh function does not perform a new search. It just refreshes the
data for all systems that have been found using the search and for all clusters that have been created during
the current session.

Procedure

Performing a Search

1. To enable the search, choose Display Search Criteria.

2. Enter your search criteria or select them from the value help. You can specify a range or use the asterisk
(*).
3. Optional: Select or deselect the options under Further Settings.
4. To start the search, choose Search or Search and Hide Search Criteria as required.
The systems and clusters that are found are displayed in the work area. The search criteria are either
displayed or hidden depending on the option that you selected. If you select Search and Hide Search
Criteria and no systems and clusters are found, the search criteria are still displayed.
5. Reset Search Criteria resets the search criteria to the values with which the Central CTS Configuration Web
UI was started.

Performing a Refresh

1. To refresh the data in the work area, choose Refresh.

Change Control Management

418 PUBLIC Change Request Management
Example

You want to display all clusters that start with an A. You enter A* in the Cluster ID field. Cluster AB1 is displayed.

Afterwards, you create cluster CD2. Cluster CD2 is also displayed in the work area. Then, another user adds
systems to cluster CD2.

If you use the Refresh function, the data for both clusters AB1 and CD2 is refreshed in the work area. The
systems that the other user has added are now displayed.

The other user then creates cluster AB3 in another session. If you use the Refresh function now, cluster AB3
will not be displayed because the refresh function only refreshes data in the work area. It does not perform a
new search. To display cluster AB3, you need to perform a new search.

4.4.13.1.2.3.4 Central CTS Configuration Web UI -

Personalization

Use

Web Dynpro provides a framework for personalizing applications. Since the Central CTS Configuration Web UI
is a Web Dynpro application, it offers the default options for personalizing general settings. In addition, it offers
other options for adjusting the layout in the work area to your requirements.

Procedure

1. Choose Personalize....
2. A dialog box opens with the following tabs:
• General Settings
• Other Settings
3. Make your changes on the tab pages as desired. For more information on the options you have on the tab
pages, refer to the sections below.
4. To confirm your settings, choose Save.

Personalizing General Settings

On this tab you can add columns to and remove columns from the list as well as change the sequence of the
columns. You can also reset to the default settings.

 Note

The first column is a key column. You cannot move it.

 Note

If you move columns in Central CTS Web UI using drag & drop this will be reflected in the list here.

Change Control Management

Change Request Management PUBLIC 419
Personalizing Other Settings

• Number of Visible Rows

You can change the number of visible rows in the Work Area. Up to 99 rows are allowed. Reset resets the
number of visible rows to the default value of 20.
• Display as ...
You can set the display of the work area as a flat list or a hierarchical list.
The hierarchical list displays clusters and their systems in one column, and is therefore able to group
certain information. This reduces the number of columns displayed and provides a better overview. The flat
list displays clusters and systems and their descriptions in individual columns. This option provides more
filter options.

 Note

You can also set the type of list display by selecting it from the dropdown list in the work area.

• Display Systems not yet assigned to a Cluster in ...

You can specify where systems are displayed which are not yet assigned to a cluster. They are either
displayed in the main view in the work area or in a separate tab (separate view). If main view is selected,
systems without cluster assignment are grouped in a “dummy”cluster called N.A. (not applicable) only for
display reasons. You cannot display or edit the N.A. cluster.
• Automatic Validation
You can specify whether the system automatically starts a validation after you have made an important
change to the configuration. Important changes are creating or deleting a cluster, or making changes to a
cluster, for example.
• Distribution of Configuration
You can specify if the TMS configuration is to be distributed by default after you have made an important
change to the configuration. You can override the default setting on the individual dialog boxes.

More Information

For more information on how to personalize Web Dynpro ABAP applications, see .

4.4.13.1.2.4 Tasks for Configuring Central CTS

Use

To be able to use central CTS you need to create system clusters and assign the systems in your transport
landscape to these clusters. To be able to work with the clusters, you have to make additional settings. This
includes setting TMS parameters to classify systems as managed systems, configuring RFC destinations for
communication between the CTS server and the managed system, and distributing CTS plug-ins which contain
the CTS functions required on the managed systems. The system tells you which tasks you must perform when
you validate a system in the Central CTS Configuration Web UI.

Change Control Management

420 PUBLIC Change Request Management
  Note

You do not have to perform the tasks in a specific sequence. However, some tasks depend on each other.
For example, the import destination is required to distribute CTS plug-ins.

In addition, you must ensure that the transports created in the systems that belong to system clusters reach
the correct systems. Therefore, you need to connect the system clusters as well as define import targets for
the systems that belong to the clusters. You do this in the classic Transport Management System. The Central
CTS Configuration Web UI cannot validate whether you have performed these tasks.

Procedure

Tasks in the Central CTS Configuration UI

• Creating or Changing System Clusters [page 421]

• Setting TMS Parameters for Central CTS [page 424]
• Configuring RFC Destinations for Central CTS [page 428]
• Distributing CTS Plug-Ins to the Managed Systems [page 432]

Additional Tasks

• Connecting System Clusters [page 433]

• Defining Import Targets [page 434]

4.4.13.1.2.4.1 Creating or Changing System Clusters

Use

You create system clusters to group different systems with the same role. You do this in the Central CTS
Configuration Web UI.

From a technical point of view, this means creating a virtual system with a system ID as a system cluster, and
assigning systems that are to be contained in the cluster.

Prerequisites

• The systems fulfill the basic requirements to be included in system clusters (Release and Support Package
level).
• You are in the Central CTS Configuration Web UI.

Change Control Management

Change Request Management PUBLIC 421
Procedure

Creating a New Cluster

1. To create a new cluster and add systems to it, choose Cluster Create Cluster .
2. In the dialog box, enter the required information, such as Cluster ID and Description. The Cluster ID must
consist of three characters and must be unique within the transport domain.
3. If you are configuring a source cluster, that is if you want to group development (source) systems in one
cluster, select the Source cluster check box.
For source clusters, you must select a client. The client is required to create transport collections.
Therefore, you must select the client in which you want to use Transport Organizer and in which you want
to create transport collections. Since the cluster is a virtual system, you must use the client of the ABAP
communication system of the cluster. The correct client is usually the production client of the system to
which you are currently logged on.
4. Optional: If you want to add systems to the system cluster, select the systems from the list.

 Note

If you want to add a system to the cluster that is not contained in the list, check that the configuration
of the Landscape Management Database (LMDB) is consistent. You can do this in LMDB on the tab
page Transport Domains.

For source systems, also select the client where you want to use Transport Organizer and in which you want
to create transport requests.
• For ABAP and dual-stack systems: All clients that exist in the ABAP system are displayed. Select the
client in which development takes place. If you want to develop in multiple clients of an ABAP system
you can add the system more than once using different clients.
• For non-ABAP systems: The client that has been defined as TMS parameter NON_ABAP_WBO_CLIENT
for this system is pre-selected. You cannot edit the client here.
• For virtual or external systems: You must enter a client only if extended transport control is active in
the system. You can either select one of the clients that exist in the system (or in the communication
system) or enter any other client. This option is useful if you want to prepare the cluster assignment
for systems or clients which do not yet exist.
For target systems, it depends on your transport strategy whether you must select a client or not.
• For target ABAP and dual-stack systems: You must select a client only if extended transport control is
active in the system. All clients that exist in the system can be selected. If extended transport control is
not active, no client can be selected.
• For target non-ABAP systems: No client can be selected.
• For virtual or external systems: You must enter a client only if extended transport control is active in
the system. You can either select one of the clients that exist in the system (or in the communication
system) or enter any other client. This option is useful if you want to prepare the cluster assignment
for systems or clients which do not yet exist.
5. If you want to distribute the TMS configuration to all systems in the transport landscape after the cluster
has been created, select the corresponding checkbox.
6. Choose Check to check your entries for completeness and consistency without closing the dialog box.
7. If the check does not display any errors create the cluster.

Change Control Management

422 PUBLIC Change Request Management
  Note

The cluster can only be created if the client is valid.

Changing an Existing Cluster

1. To change an existing cluster, select the link with the cluster ID.
2. Choose Display <-> Change.
Except for the cluster ID, you can change any data of the cluster.
3. Optional: To add systems to the cluster, choose Add Row and select the system that you want to add to the
cluster. If a client is required, proceed as described under Creating a New Cluster.
4. Optional: To remove systems from the cluster, choose Delete Row for the corresponding system.

 Note

Before you remove a system from a cluster make sure that there are no modifiable transport requests
of this system that are part of modifiable transport collections of the cluster. Otherwise, you will get an
inconsistent system state.

If you have defined an import target for the removed system you must delete the entry for this system
after removing the system from the cluster.

5. Repeat the previous steps for all systems that you want to add to the cluster or delete from it.
6. If you want to distribute the TMS configuration to all systems in the transport landscape after the cluster
has been changed, select the corresponding checkbox.
7. Choose Check to check your entries for completeness and consistency without closing the dialog box.
8. If the check does not display any errors save your changes.

Result

The cluster has been created in the transport domain of the system to which you are logged on or changes
have been made to an existing cluster of this transport domain.

More Information

• System Cluster [page 403]

• For more information on clients, see Clients and Their Roles.
• TMS Parameters for Central CTS [page 426]
• Deleting a System Cluster [page 435]
• Defining Import Targets [page 434]

Change Control Management

Change Request Management PUBLIC 423
4.4.13.1.2.4.2 Setting TMS Parameters for Central CTS

Use

To be able to use central CTS, you must set specific parameters in the Transport Management System
(TMS) configuration. Depending on whether the managed system belongs to the same transport domain
as the central CTS server or not, you can use the Central CTS Configuration Web UI to set the missing TMS
parameters or you must set them in TMS.

The following TMS parameters are relevant for central CTS:

• MANAGED_SYSTEM: Classifying the system of a cluster as a managed system.

• OPERATION_MODE: Specifying the operating mode of a managed system to define the level of control that
the central CTS server has over this system and influence the import sequence of the transport requests in
the transport collection, if required.
• NON_ABAP_WBO_CLIENT: Specifying the logon client of Transport Organizer in all non-ABAP source
systems and source clusters to make sure that transport requests are created in the correct client.

 Note

The TMS parameter NON_ABAP_WBO_CLIENT is used when you configure non-ABAP systems for CTS
transports. You can set this parameter only in TMS. In the Central CTS Configuration Web UI, it is only
displayed.

Prerequisites

You have executed a validation in the Central CTS Configuration Web UI and the system tells you that TMS
parameters are invalid.

Procedure

Setting TMS Parameters for Systems in the Same Transport Domain

If the managed system belongs to the same transport domain as the central CTS server you can use the central
CTS Configuration Web UI to set the missing TMS parameters.

To do this, proceed as follows:

1. In the central CTS Configuration Web UI, choose the TMS Parameters invalid link.
2. Choose Display <-> Change.
3. The invalid TMS parameters have a red traffic light icon next to their value.
4. Select correct values for the invalid TMS parameters. If the value for NON_ABAP_WBO_CLIENT is invalid,
proceed as described under Setting TMS Parameters for Systems in a Foreign Transport Domain.
5. If you set the value for OPERATION_MODE to QUEUED or QUEUED_DYNAMIC, a job needs to be scheduled for
the program SCTS_QUEUE_IMPORT_CONTROL which is used for importing the transport requests in the
managed system. Choose Create to create this job in the managed system.

Change Control Management

424 PUBLIC Change Request Management
6. To check the values for completeness and consistency, choose Check.
7. If no errors are displayed, save your changes.

Setting TMS Parameters for Systems in a Foreign Transport Domain

If the managed system is not part of the transport domain of the central CTS server or of a linked domain,
you can only display the TMS parameters in the Central CTS Configuration Web UI. You cannot change them
there. In addition, if the system is not part of a linked transport domain, you must have performed the Managed
Systems Configuration in SAP Solution Manager Configuration (transaction SOLMAN_SETUP) to be able to
display them.

To set the TMS parameters, you must start TMS in the transport domain controller of the managed system.

To do this proceed as follows:

1. In the central CTS Configuration Web UI, choose See details for the managed system that has invalid TMS
parameters.
2. The dialog box displays a specific message for each invalid or missing TMS parameter. To set the invalid
or missing TMS parameters, follow the instructions described in the specific messages. The general
procedure is as follows:
1. Log on to the transport domain controller of the system that you want to classify as a managed
system.
2. Call transaction STMS.
3. Choose System Overview.
4. Select the required system by double-clicking it.
The screen Display TMS Configuration: System <SID> appears.
5. Choose the tab page Transport Tool and switch to change mode.
6. Add the parameters for the invalid or missing parameters and assign the appropriate values as
described under TMS Parameters for Central CTS [page 426].
7. Save the settings and distribute the configuration.
8. Repeat the previous steps for all managed systems that have invalid TMS parameters.

Schedule a Job for Operation Mode QUEUED or QUEUED_DYNAMIC for Systems in a Foreign
Transport Domain
If the managed system is not part of the transport domain of the central CTS server or of a linked domain, you
cannot use the central CTS Configuration Web UI to schedule a job on the managed system if you use one of
the operation modes QUEUED or QUEUED_DYNAMIC. Proceed as follows:

1. Log on to the managed system for which the operation mode is set, and use transaction SA38 to execute
program SCTS_SCHEDULE_IMPORT4QUEUED.
You can leave the default options unchanged. These are:

Program Options

Job Class C: Regular Priority

Delete existing jobs Selected

Schedule a job Selected

2. Execute the program.

If you left the default options unchanged, all existing jobs are deleted and a new job is scheduled called
SAP_CCTS_&<system name>&_QUEUED_IMPORT.

Change Control Management

Change Request Management PUBLIC 425
 Schedule exactly one job for every managed system with QUEUED or QUEUED_DYNAMIC.

Result

You have set the TMS parameters required to configure central CTS. By doing this, you have done the following:

• You have converted the systems involved into managed systems.

• You have defined the level of control that central CTS has for these managed systems.
• If you have set different operation modes for different systems, you have influenced the import sequence of
the transport requests in the system cluster.

4.4.13.1.2.4.2.1 TMS Parameters for Central CTS

Use

The following TMS parameters are required to work with central CTS.

MANAGED_SYSTEM

This parameter classifies the system as managed.

The following values are available:

Value Description

TRUE The system is managed by central CTS.

PARTLY The system is managed partially by central CTS.

You can control imports both using the central CTS server and using the local Transport
Management System. Transport requests that were created using central CTS are controlled by
central CTS. Transport requests that were created locally in the SAP system can be imported
using the local Transport Management System.

You can use this value if you want to introduce central CTS step-by-step or for test purposes.

 Note

To use Change Request Management or Quality Gate Management with central CTS, you must set this
parameter to PARTLY.

OPERATION_MODE

This parameter specifies the operating mode of the system. It defines the extent of import control that
the central CTS has for the managed systems. You can also use this parameter to define the extent of
parallelization of the import.

It must always be set in connection with the TMS parameter MANAGED_SYSTEM.

Change Control Management

426 PUBLIC Change Request Management
The following values are available:

 Note

The following description of the parameters is valid for all transport requests that were created using
central CTS if the TMS parameter MANAGED_SYSTEM is set to TRUE or PARTLY. However, it does not apply
to transport requests that were created locally in the system if MANAGED_SYSTEM is set to PARTLY.

Value Description

CONTROLLED The central CTS server controls the transports in the managed systems. Imports can no longer
be executed locally in the managed systems. The transport requests of the systems of a
system cluster for which the operation mode is set are imported into the target systems in
sequential order, one after another.

QUEUED The central CTS server controls the transports in the managed systems. Imports can no longer
be executed locally in the managed systems. The transport requests of all systems of a system
cluster for which the operation mode is set are imported into the target systems in parallel. All
imports are started at the same time.

This operation mode enables the parallel import of transport requests to all systems of a
system cluster for which this operation mode is set. This can reduce the overall import time
when importing into large clusters.

For this operation mode, you must schedule a job for the import of transport requests in the
managed system. For more information, see Setting TMS Parameters for Central CTS [page
424].

PROPOSED The central CTS server suggests imports for the managed systems by placing transports in the
import queue. Imports must be started locally in the system. We recommend that you schedule
regular import jobs.

MONITORED The central CTS server only has a monitoring function. Transports must be started locally in the
systems.

<value for The addition _DYNAMIC is used if process tools on top of central CTS, such as Change Request
OPERATION_MODE>_DY- Management, define the degree of control for the managed systems.
NAMIC

 Note

To use Change Request Management or Quality Gate Management with central CTS, you must set this
parameter to CONTROLLED_DYNAMIC, or QUEUED_DYNAMIC.

 Note

If a cluster contains systems where the operation mode is set to CONTROLLED_DYNAMIC as well
as QUEUED_DYNAMIC, the imports are processed (in sequential order) in systems with operation
mode CONTROLLED_DYNAMIC first. The imports in systems with operation mode QUEUED_DYNAMIC are
processed afterwards (in parallel). This means that you can use the parameter to define an import
sequence in your systems.

Change Control Management

Change Request Management PUBLIC 427
NON_ABAP_WBO_CLIENT

This parameter specifies the logon client of Transport Organizer. It is used for communication with the source
system. It is required for all non-ABAP source systems and for system clusters. If you have performed the
configuration steps for non-ABAP transports, this parameter already exists in your source systems.

 Note

You can only set this parameter in TMS. You cannot set it in the Central CTS Configuration Web UI.

The following values are available:

Value Description

000-999 Value of the logon client in Transport Organizer. This is the client in which your TMS was
configured and in which you are developing.

More Information

• Setting TMS Parameters for Central CTS [page 424]

• Parameters for Non-ABAP Transports

4.4.13.1.2.4.3 Configuring RFC Destinations for Central CTS

Use

To enable communication of the central CTS server with its managed systems RFC connections must exist
from the central CTS server to the managed systems. For managed non-ABAP systems, the RFC connection
must exist from the central CTS server to the ABAP communication system of the managed system.

This includes the following RFC destinations:

• Transport Organizer destination: Required for working with transport requests (creating, deleting,
changing transport requests). This destination is required for source systems only.
• Import destination: Required for importing the CTS plug-ins to the managed systems
• Deploy destination: The import process of a transport collection needs this destination to be able to
import transport requests that are assigned to a transport collection.

Prerequisites

• You have performed a validation in the Central CTS Configuration Web UI and the system tells you that RFC
connections are missing.

Change Control Management

428 PUBLIC Change Request Management
• You use Trusted System to log on to the managed system.
• You use Secure Network Connection (SNC) for RFC communication with managed systems.
• For the deploy destination, you need a technical user with specific authorizations in all managed systems.

Procedure

The Transport Organizer and import destinations can be re-used from existing SAP Solution Manager
destinations. These were created when performing Managed Systems Configuration in SAP Solution Manager
Configuration (transaction SOLMAN_SETUP). If the system tells you that either the Transport Organizer or the
Import destination is missing, check the SAP Solution Manager Configuration.

The following procedure applies if you want to configure the Deploy destination:

1. Log on to the central CTS server (SAP Solution Manager system) and call the RFC destination maintenance
using transaction code SM59.
2. Navigate to ABAP connections and create new ABAP R/3 Connections (Type 3).
3. Enter the data as described in Deploy Destination [page 430].
4. To create the destination, choose Save.
5. To make sure that the destination has been configured correctly, perform the tests available in transaction
SM59.

 Note

To perform the authorization test, the user that performs the test (logon user) must have the
authorizations as described for the individual RFC destinations. Otherwise, the test can fail even
though the RFC destination was correctly configured.

Result

You have configured an RFC connection to a managed system. Afterwards, validate the system again.

More Information

• For more information on configuring RFC destinations, see Displaying, Maintaining, and Testing
Destinations.
• For more information on Trusted System, see Maintaining Trust Relationships between SAP Systems.
• For more information on Secure Network Connection (SNC), see Secure Network Communications (SNC).
• For more information on how to create a user for the deploy destination, see Deploy Destination [page
430].

Change Control Management

Change Request Management PUBLIC 429
4.4.13.1.2.4.3.1 Deploy Destination

Use

The import process of a transport collection needs this destination to be able to import transport requests
that are assigned to a transport collection. This destination is required for all communication systems of target
clusters. It points from the communication system of the cluster (central CTS server) to a managed ABAP
system or to the communication system of a managed non-ABAP system.

Enter the following data:

• Name according to the following naming convention: TMSDPL@<SID>.<Domain_Name>

 Note

All entries are case-sensitive.

• Technical Settings tab: Target Host:

• For ABAP systems: Use the actual managed system as the Target Host for the destination.
• For non-ABAP systems: Use the communication system of the managed system as the Target Host for
the destination.
• Logon & Security tab: We strongly recommend that you use Trusted system with the technical user
described in the Prerequisites section.
• Language: Enter a language that is installed both in the central CTS Server and in the managed system.
We recommend that you use English (EN).
• Client: Enter the client of the managed system in which you have created the technical user.
• User: Enter the technical user that you created in the managed system.
• Trust Relationship: Select Yes.
In addition, to encrypt communication data, we recommend that you use Secure Network Connection
(SNC) for RFC communication with managed target systems.

Using this setup, you make sure that only user DDIC in client 000 is allowed to communicate using the deploy
destination.

 Example

The non-ABAP system NAT is configured as target system and uses system ABC as the communication
system in domain DOMAIN_ABC. System ABC is also the central CTS server. In this case you must create a
deploy destination [email protected]_ABC.

Prerequisites

For the deploy destination, you need a technical user with specific authorizations and roles assigned in all
managed systems. This user is used for communication between the central CTS server and the managed
system. You must create this user in the managed system. For non-ABAP systems, you must create it in the
communication system of the managed system.

Change Control Management

430 PUBLIC Change Request Management
To create this technical user including the necessary roles, proceed as follows:

1. Log on to the managed system for which you need the Deploy destination in any client.

 Note

Remember in which client you created the technical user since you must later enter this data for the
Deploy destination.

2. Create a copy of the role SAP_BC_TRANSPORT_OPERATOR, for example Z_BC_TRANSP_OP. We recommend

that you always assign copies of roles.
3. Create a new role, for example Z_TRANS_RFC_ACL. The new role must contain the authorization object
S_RFCACL. Use the following field values for the authorization object S_RFCACL:

Field Technical Name Value

Activity ACTVT Execute (16)

RFC client or domain RFC_CLIENT 000 (required for import process)

RFC same user ID RFC_EQUSER Call by the same user is not possible
(No)

RFC information RFC_INFO *

System ID (for SAP and External) RFC_SYSID <communication system of the clus-
ter>

RFC transaction code RFC_TCODE *

RFC User (SAP or External) RFC_USER DDIC

4. Create a technical user of type System, for example CCTSTRANS.

5. Assign the roles that you created before to this user.

More Information

Authorization Object S_RFCACL.

Change Control Management

Change Request Management PUBLIC 431
4.4.13.1.2.4.4 Distributing CTS Plug-Ins to the Managed
Systems

Prerequisites

• You have performed a validation in the central CTS Configuration Web UI and the system tells you that the
CTS plug-ins (CTS Service or CTS Bootstrapper plug-ins) in the managed system are not up-to-date.
• All prerequisites are fulfilled as described in Prerequisites for Configuring Central CTS. [page 411]
• The import destination exists for the distribution of CTS Service plug-ins.
• The managed system has the required version of the transport tools tp and R3trans.
For more information, see SAP Note 1665940 .

Context

Using the Central CTS Configuration Web UI you can distribute the CTS Service and CTS Bootstrapper plug-ins
from the central CTS server to the managed systems.

Procedure

1. In the Central Change and Transport System Configuration Web UI, choose the link Plug-In not up-to-date.
2. A dialog box opens where you must confirm that you want to distribute the plug-in to the relevant system.

On this dialog box, you can navigate to the validation details on the plug-in distribution status. This
provides an overview of the installed plug-in versions and the versions that are available for installation as
well as the import destination and transport tools functions.
3. Choose Distribute Plug-ins.

The CTS plug-ins which must be updated are distributed to the managed system.

Next Steps

• Technical Details on the CTS Plug-In [page 383]

• Central CTS Configuration Web UI - Configuring RFC Destinations [page 428]

Change Control Management

432 PUBLIC Change Request Management
4.4.13.1.2.4.5 Connecting System Clusters

Context

To enable transports between system clusters you need to define transport routes between the clusters. This is
done in the same way as for systems.

Procedure

1. To connect clusters, start Transport Management System (transaction STMS) in your central CTS server.

2. In the menu choose Overview Transport Routes .

3. Configure the transport routes for the system cluster just as you would for individual systems. That is,
define a consolidation transport route from the development cluster to the quality cluster and a delivery
transport route from the quality cluster to the production cluster.

 Caution

When you create the consolidation route, make sure that the standard transport layer is added.

Results

These transport routes determine the transport process of transport collections.

To define the transport process for transport requests of the individual systems, you must also define the
import targets of the individual systems.

Next Steps

Configuring the Transport Routes

Change Control Management

Change Request Management PUBLIC 433
4.4.13.1.2.4.6 Defining Import Targets

Prerequisites

You have defined the transport routes for the individual systems that belong to the cluster.

Context

After you have configured transport routes for the system clusters, you must define how the individual
transport requests are to be transported along these transport routes. To do this you must define the import
targets for the transport requests.

Procedure

1. Start Transport Management System (transaction STMS) in the central CTS server.
2. Choose Transport Routes.
3. Switch to change mode using Display <-> Change.
4. Double-click to select the target cluster for which you want to define import targets.
5. Choose the Import Targets tab.
6. In the Request Source column, enter the system from which the transport requests are to be exported
(source system for transport requests). This is always the development system, also if you have a three-
system track (DEV, TST, PRD) and you are defining import targets for the production cluster.
7. In the Source Client column, only enter a client if you use extended transport control and if you want to
make sure that the developments of a specific client in the source system reach a specific client in the
target system. In all other situations, especially for non-ABAP systems, do not enter any client. Leave the
field empty.
8. In the Target System column, enter the system into which the transport requests are to be imported (target
system for transport requests).
9. In the Target Client column, only enter a client if you use extended transport control and if you want to
make sure that the developments of a specific client in the source system reach a specific client in the
target system. In all other situations, especially for non-ABAP systems, do not enter any client. Leave the
field empty.
10. Choose Continue.

Ensure that the transport route for the import target runs along a cluster transport route that is already
defined. The system does not check your entries.
11. Repeat these steps for all systems that belong to target clusters in your system landscape. If you develop
in multiple clients of an ABAP system, repeat these steps for all clients in which you want to execute
transports.

Change Control Management

434 PUBLIC Change Request Management
Results

You have defined the import targets for the systems that are contained in clusters. If you have performed
all configuration steps for central CTS you can use it with Change Request Management or Quality Gate
Management.

Next Steps

Configuring Transport Routes

4.4.13.1.2.4.7 Deleting System Clusters

Prerequisites

• You are in the Central CTS Configuration Web UI.

• The cluster that you want to delete does not contain any open transport collections that must still be
transported through the system landscape. Otherwise, you will get an inconsistent system state.

Context

After you performed an initial configuration of central CTS, your systems are ready for work with central CTS.
After some time, you may want to make changes to this initial configuration. For example, you may want to
delete a system cluster because development of a project has ended.

 Caution

Delete system clusters only in the Central CTS Configuration Web UI. Do not delete any system clusters in
Transport Management System. Otherwise, you will get an inconsistent system state.

Procedure

1. To delete an existing cluster, select the cluster and choose Cluster Delete Cluster .
2. To confirm the deletion, choose Delete.

Change Control Management

Change Request Management PUBLIC 435
Results

You have deleted a system cluster.

If the system cluster was connected to other system clusters using transport routes, you must delete the
transport routes.

If you have defined import targets for the systems that are part of your cluster, you should delete these as well.

Next Steps

Deleting Transport Routes

4.4.13.1.3 Using Central Change and Transport System

Context

Central Change and Transport System (central CTS) is used as the technical infrastructure for the enhanced
flexibility functions for Change Request Management and Quality Gate Management (QGM). Usually, you do
not use central CTS directly. However, for special tasks, you may want or need to use central CTS functions
directly:

• Displaying information related to central CTS

• Displaying Transport Collections on the Central CTS Server
On the central CTS server, you can use CTS Transport Manager Web UI to display transport collections
including all transport requests, and objects, as well as assigned changes and project cycles that
belong to them.
• Displaying Assignments to Transport Collections in Managed Systems
In managed systems, you can display the transport collections to which a transport request is
assigned.
• Performing Imports into System Clusters
In specific situations, you can import transport collections in system clusters using Import Queue Web UI.
• Activating and Displaying the Application Log for Central CTS
You can activate an application log for actions triggered by central CTS.

See also:

• CTS Transport Manager Web UI - Layout [page 438]

• Displaying Transport Collections on the Central CTS Server [page 440]
• Displaying Assignments to Transport Collections in Managed Systems [page 441]
• Performing Imports into System Clusters [page 442]
• Activating and Displaying the Application Log for Central CTS [page 447]

Change Control Management

436 PUBLIC Change Request Management
4.4.13.1.3.1 Activating Services for CTS Transport Manager
Web UI

Prerequisites

• You have authorization for transaction SICF.

• All ICF services required to run an ABAP Web Dynpro application are activated.
For more information, see SAP Note 517484 .

Procedure

Activating Services for CTS Transport Organizer Web UI

1. Call transaction SICF. This transaction is a cross-client transaction.

2. Enter Service in the Hierarchy Type field and CTS_ZENUI_MANAGER in the Service Name field.
3. Choose Execute.
4. Select the CTS_ZENUI_MANAGER service on the Maintain Services screen.
5. Activate the service by opening the context menu (secondary mouse button) and choosing Activate
Service.
A dialog box for Activating ICF Services is displayed.
6. Choose Yes (with tree icon).

 Note

If you want to test the service, open the context menu (secondary mouse button) and choose Test
Service.

When you test the services for CTS Transport Manager Web UI, you can find its URL in the address bar
of the test system.

7. Repeat the previous steps for each of the following services:

• 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
• CTS_ORGANIZER_OBJECTLIST

Change Control Management

Change Request Management PUBLIC 437
4.4.13.1.3.2 CTS Transport Manager Web UI - Layout

Use

You can use CTS Transport Manager Web UI to display information related to central CTS, such as system
clusters, and transport collections including the transport requests that belong to them.

You do not use CTS Transport Manager Web UI to trigger actions related to central CTS. All actions related to
central CTS are usually triggered by Change Request Management or Quality Gate Management (QGM).

Prerequisites

You have activated the ICF Services for CTS Transport Manager Web UI.

Structure

Layout of CTS Transport Manager Web UI

The interface of CTS Transport Manager Web UI is divided into the following areas:

View Selection

Here you can select the view that you require, depending on the information you want to display.

You hide or display the view selection using the double arrow to get a larger detailed display of the views.

Below the view selection there are further selection options, such as Useful Links to Transport Organizer Web UI
and Transport Log Viewer.

Change Control Management

438 PUBLIC Change Request Management
Detailed Display of Views

The following views are available:

• Organize
In this view you can display transport collections for source clusters including assigned transport requests
and object lists. For systems that use Change Request Management or QGM, the assigned change and
project cycle are also displayed.
You can display the transport logs for transport collections.
In the Landscape area in the lower part of the screen, you see the system clusters of your transport
landscape in a graphical or list format, depending on your selection.
• Transport
In this view you can display import queues for target clusters. This view corresponds to the Import Queue
Web UI and the import overview of the Transport Management System (STMS) in the local systems. For
systems that use Change Request Management or QGM, the assigned change and project cycle are also
displayed.
In the Landscape area in the lower part of the screen, you see the system clusters of your transport
landscape in a graphical or list format, depending on your selection.
• Configuration
This view offers various functions on different tab pages:
• Systems and Landscape
This tab page displays clusters that you have configured using the Central CTS Configuration Web UI.
In the Landscape area in the lower part of the screen, you see the system clusters of your transport
landscape in a graphical format.
• Projects
When transport collections are created in Change Request Management or QGM, they are usually
assigned to a project cycle. Here you can display all changes and project cycles known in central CTS.
When you select a registered project type, all projects that belong to it are displayed including their IDs
and descriptions.
• Transport Locks
This tab page displays all active transport locks set for clusters by Change Request Management or
QGM.
• Application Log
The application log records all actions triggered in the central CTS area. On this tab page, you can
enable application logging and specify the logging detail level.

More Information

• Activating Services for CTS Transport Manager Web UI [page 437]

• Configuring Central Change and Transport System - Overview [page 407].
• For more information on Import Queue Web UI, see .
• Activating and Displaying the Application Log for Central CTS [page 447]

Change Control Management

Change Request Management PUBLIC 439
4.4.13.1.3.3 Displaying Transport Collections on the Central
CTS Server

Use

On the central CTS server (SAP Solution Manager), you can use CTS Transport Manager Web UI to display
transport collections together with their transport requests and further attributes, such as description, owner,
and return code. If the transport collection was created using Change Request Management or Quality Gate
Management, the assigned change and project cycles are also displayed.

Procedure

1. Start CTS Transport Manager Web UI using transaction code SZENTMS.

The Organize view is displayed by default.
2. Enter a source cluster for which you want to display transport collections.
3. To display transport collections for a specific user enter the user name as Owner. If you want to display all
transport collections of a selected cluster, enter an asterisk (*).
4. Optional: You can restrict the displayed transport collections to a specific status (Modifiable, or Exporting,
for example). To do this, select the respective option by clicking the small black arrow next to the Owner
input field.
This starts the search.
5. If the search is not started, choose Refresh to start the search.
The system displays all transport collections in a list that correspond to the search criteria.
6. You have the following options:
• You can expand the node for the transport collection to display the transport requests that belong to
the transport collection. Expanding the node further displays the objects contained in the transport
requests.
• You can navigate to the transport logs of the collection. To do this, select the transport collection and
choose Logs.
Transport Log Viewer opens in a new browser window.

More Information

CTS Transport Manager Web UI [page 438]

Change Control Management

440 PUBLIC Change Request Management
4.4.13.1.3.4 Displaying Assignments to Transport Collections
in Managed Systems

In the Transport Organizer Web UI, you see information about transport collection assignments of transport
requests in the systems managed by central CTS. You use this function if you have a transport request in the
managed system and want to know to which transport collection it belongs.

Prerequisites

The managed system or the communication system of the managed non-ABAP system is configured as
managed by central CTS. This means that in the managed system or in the communication system, the TMS
parameter MANAGED_SYSTEM is set to TRUE or PARTLY.

Context

Different versions of Transport Organizer Web UI are available depending on whether or not the CTS plug-in is
installed in the managed systems (or in the communication systems of the managed non-ABAP systems).

• In systems in which the CTS plug-in is not installed, the Web Dynpro ABAP applicationCTS_BROWSER is
available.
• In systems in which the CTS plug-in is installed, the Web Dynpro ABAP application CTS_ORGANIZER is
available (for SAP Solution Manager systems as of 7.1 and SAP NetWeaver systems as of 7.3 Enhancement
Package 1).

 Note

If you have distributed the CTS Service plug-in to the managed system, this does not mean that the CTS
plug-in is installed in this system. The CTS plug-in is installed as part of the initial installation of SAP
Solution Manager, or using SAP Add-On Installation Tool, or Software Update Manager.

Procedure

1. Start Transport Organizer Web UI on your managed development system or communication system of the
managed non-ABAP development system.
2. Depending on the Web Dynpro application you use, this is how you display the assignment to transport
collections:

• CTS_BROWSER
Select the link under Transport Collection to see the IDs of the corresponding transport collections and
further information.
If the transport request is part of exactly one transport collection, the link is the ID of this collection. If
the transport request is part of multiple collections, the link is labeled Multiple Collections and opens
the IDs of the corresponding transport collections.

Change Control Management

Change Request Management PUBLIC 441
 • CTS_ORGANIZER
1. To display an additional column, the Transport Collection column, personalize the Transport
Organizer Web UI.
The link under Transport Collection provides more information.
If the transport request is part of exactly one transport collection, the link is the ID of the
collection. If the transport request is part of multiple collections, the link is labeled Multiple (See
Details).
2. In the Details area of the transport request, open the Transport Collections tab page.
You see the IDs of the transport collections. If the transport collection is assigned to a project, you
can view more information about the project. If a URL has been assigned to the project, you can
select the link for more information.
3. To display the entire collection, select collection ID.

This opens CTS Transport Manager Web UI on the central CTS server, which displays the entire content of
the collection and its attributes, including projects, if the transport collection is assigned to a project.

Related Information

Setting TMS Parameters for Central CTS [page 424]

TMS Parameters for Central CTS [page 426]
Displaying Transport Collections on the Central CTS Server [page 440]

4.4.13.1.3.5 Performing Imports in System Clusters

Use

Usually, you import transport collections into system clusters using Change Request Management or Quality
Gate Management (QGM) and not using Import Queue Web UI. You use Import Queue Web UI only to display
import queues of system clusters.

However, in specific situations, you may also need to use Import Queue Web UI on SAP Solution Manager to
import transport collections into system clusters:

• In emergency situations, if functions of Change Request Management or QGM do not work.

• For transports into additional systems of your transport landscape where transports are not or not yet
controlled by Change Request Management or by QGM.
This applies to additional test, training, or sandbox systems, for example, for which process compliance is
not as important as for production systems.
These systems can be bundled as separate system clusters, and imports into these systems can be
performed in the central CTS server (SAP Solution Manager) using Import Queue Web UI.
• If you want to add new systems to an existing system landscape and you must therefore add a new cluster
to the related cluster landscape.
In this case, you must set up an initial import queue for the new system cluster using Import Queue Web UI.

If you are in such a situation, or if SAP support asks you to do so, you can activate Import Queue Web UI for
system clusters.

Change Control Management

442 PUBLIC Change Request Management
  Note

If SAP Solution Manager is not working at all, proceed as described under Performing Imports if SAP
Solution Manager is Not Working [page 445].

More Information

• Activating Import Queue Web UI for System Clusters [page 443]

• Importing Transport Collections into System Clusters [page 444]

4.4.13.1.3.5.1 Activating Import Queue Web UI for System

Clusters

Prerequisites

You are in one of the situations described in Performing Imports in System Clusters [page 442].

Context

If you use Change Request Management or QGM for transports, and if you need to perform imports into
clusters that are usually controlled by Change Request Management or QGM, you must switch off the import
locks for the target cluster that were set by Change Request Management or QGM before you can use Import
Queue Web UI.

Procedure

1. On the central CTS server (SAP Solution Manager), start Transport Management System using transaction
STMS.
2. Choose the target cluster from the System Overview.
3. On the TMS Configuration screen, choose the Transport Tools tab and add the parameter
watch_importlocks with the value false.
4. Save your entries.

Change Control Management

Change Request Management PUBLIC 443
Results

You can now use Import Queue Web UI on the central CTS server to perform imports of transport collections
into system clusters.

To de-activate Import Queue Web UI for imports into system clusters later on, delete parameter
watch_importlocks from the TMS configuration.

Next Steps

Importing Transport Collections into System Clusters [page 444]

4.4.13.1.3.5.2 Importing Transport Collections into System

Clusters

Use

The import of transport collections into system clusters works similar to the import of transport requests.

Prerequisites

You have activated Import Queue Web UI on your central CTS server (SAP Solution Manager) for the import of
transport collections using Import Queue Web UI.

Procedure

 Note

The following is an overview procedure of the steps involved in the import process. For detailed information
on how to perform imports using Import Queue Web UI, see the documentation reference in the More
Information section below.

1. On the central CTS server, start Import Queue Web UI using transaction code STMS_IMP.
2. Display the import queue of the required target cluster.
3. You have the following options:
• If you want to import all transport collections of the import queue, choose Import All and select the
required options for the import.
• If you want to import one or more transport collections, select the ones that you want to import.

Change Control Management

444 PUBLIC Change Request Management
 1. Optional: If you do not want to import all transport collections in the import queue, run the
dependency analysis.
To do this, choose Dependencies.
2. Optional: If the results of the dependency analysis show that you need to include more transport
collections in the import, select these as well.
3. Choose Import.
4. Select the required options for the import.
4. Choose Import.

Result

The imports are started or scheduled in the target cluster. This means that the transport requests belonging to
the transport collection are imported or scheduled in the respective target systems of the cluster. The relevant
status is displayed in Import Queue Web UI.

As long as the transport collection is in the import queue you can click the return code to open Transport Log
Viewer where you can see return codes and detailed logs of completed transport steps. After the transport
collection has disappeared from the queue you can display this information using Import History Web UI.

More Information

• Activating Import Queue Web UI for System Clusters [page 443]

4.4.13.1.3.6 Performing Imports if SAP Solution Manager is

Not Working

Context

In the following situation you may need to perform imports using the local Transport Management System
(TMS):

• You are using Change Request Management or Quality Gate Management (QGM).
• Your SAP Solution Manager (central CTS server) is currently not working.
• You urgently need to perform an import into a managed system.

In this case, you can temporarily switch on the local TMS to perform emergency imports.

This procedure is valid for ABAP transports only. It cannot be used for non-ABAP transports since SAP Solution
Manager is the communication system for managed non-ABAP systems.

Change Control Management

Change Request Management PUBLIC 445
Procedure

1. If your SAP Solution Manager system is configured as the domain controller for the managed system:
Activate the backup domain controller as the domain controller. The backup domain controller must have
the CTS plug-in (software component CTS_PLUG) installed. For more information on the CTS Plug-In, see
SAP Note 1665940 .
2. In the (new) domain controller, change the TMS parameter OPERATION_MODE to the value MONITORED for
the managed system into which you want to import the transport request. For more information, see the
link to Setting TMS Parameters for Central CTS in the More Information section below.

Distribute the configuration afterwards.

3. If the domain controller cannot be used or if you cannot install the CTS plug-in in the (backup) domain
controller you can change the TMS parameter directly by editing the transport profile in the managed
system.

 Caution

Only use this option if you are an expert user. If you edit the transport profile you do not have
to activate the backup domain controller. However, be aware of the fact that your changes to the
transport profile will be overwritten when the domain controller works again and the TMS configuration
is distributed. In addition, changes to the transport profile are not logged.

4. Start the import queue for the managed system and choose Refresh.

The transport requests that you want to import are still in status Inactive.

5. Select the transport requests that you want to import one after another and choose Extras Activate
Inactive Requests .
6. Select the transport requests that you want to import one after another and choose Import request.

The transport requests will be imported into the managed system.

7. After checking that your imports were successful, you can reset the configuration changes. To do this,
proceed as follows:
• Reset the TMS parameter OPERATION_MODE to the previous value (usually CONTROLLED_DYNAMIC).
• If you have moved the domain controller, re-activate SAP Solution Manager as the domain controller if
possible.
8. When SAP Solution Manager is available again we recommend that you change the status of the related
change document in Change Request Management or QGM so that it is consistent with the actual software
distribution status. The change tracking function will identify that the related imports were already
performed and will change the status without re-importing the request. Afterwards, Change Request
Management or QGM is consistent with the import status in the local systems.

Next Steps

• Activating the Backup Domain Controller

• Setting TMS Parameters for Central CTS [page 424]
• Transport Profile

Change Control Management

446 PUBLIC Change Request Management
• Change Request Management [page 21]

4.4.13.1.3.7 Activating and Displaying the Application Log for

Central CTS

Use

Central CTS comes with an application log that logs all actions triggered in the central CTS area. This also
includes any actions triggered in CTS. Unlike the transport log, the application log does not log the export or
import process itself, but all actions that lead to these processes including time stamps, users, and related
errors, such as authorization errors.

Procedure

Activating the Application Log for central CTS

To activate the application log for central CTS, proceed as follows:

1. Start CTS Transport Manager UI using transaction SZENTMS.

2. Select the Configuration view.
3. Choose the Application Log tab page.
4. Select the Enable application logging for CTS actions check box.
5. Select the logging detail level by choosing one of the radio buttons.

You have activated the application log for central CTS.

Displaying the Application Log for central CTS

When you have activated the application log for central CTS, you can display it as follows:

1. Start the analysis of application logs using transaction SLG1.

2. Enter CTS in the Object field.
3. Enter an asterisk (*) in the Subobject field.
4. The default time interval is the current day. You can change this interval.
5. Choose F8 .

The application log for central CTS displays the log information depending on the level of detail that you have
selected before.

More Information

CTS Transport Manager Web UI - Layout [page 438]

Change Control Management

Change Request Management PUBLIC 447
4.4.13.2 Enhanced Transport Functions with Central CTS

When you use the central Change and Transport System (central CTS) for Change Request Management or
QGM, some functions have enhanced features and specific prerequisites apply when working with them.

Prerequisites

You have activated central CTS for your change cycles. For more information, see Configuring Change Request
Management [page 473] and Setting Up Quality Gates and Assigning Phases [page 487].

Features

If you’re using central CTS for your scenario, the following functions work differently compared to standard
Change Request Management or QGM projects:

Change Request Management

• Decoupling a Transport Request [page 134]

• Assign Transport Requests [page 135]
• Reassigning Changes to Other Projects [page 141]
• Importing Transport Requests [page 127]
• Site-Specific Rollout of Changes [page 139]

Quality Gate Management

• Decoupling a Transport Request [page 525]

• Assigning a Transport Request [page 513]
• Importing Changes [page 514]

4.4.14 Change Control Management Using SAP Cloud

Transport Management

SAP Cloud Transport Management is the lifecycle management tool for SAP Cloud development. It controls the
content transport between different tenants.

To integrate the SAP Cloud Transport Management with Change Control Management, you have completed
the set-up steps described in Setting Up SAP Cloud Transport Management for Change Control Management
[page 451].

Change Control Management

448 PUBLIC Change Request Management
Use

You can use Change Control Management with SAP Cloud Transport Management to manage content
transports in the following scenarios:

• You have an SAP Business Technology Platform (BTP) transport landscape (a landscape with only SAP
BTP applications).
• You have a hybrid transport landscape for both SAP BTP and on-premise applications.
If you have hybrid landscapes, you can use Change Request Management as well as Quality Gate
Management together with SAP Cloud Transport Management to manage the transport processes for
SAP Cloud development.

For more information about the SAP Cloud Transport Management, see the documentation at SAP Cloud
Transport Management.

Differences to Change Control Management in On-Premise Landscapes

The change cycles work in SAP Cloud Transport Management landscapes in the same way as in on-premise
landscapes, but the central Change and Transport System (cCTS) infrastructure doesn’t support SAP Cloud
Transport Management landscapes. Also the default variant for task lists (SAP0) does not work for SAP Cloud
Transport Management landscapes, which means that you cannot leave transport requests in a queue for a
later import.

The change documents control only the import of transport requests in an SAP Cloud Transport Management
landscape, while the creation and release of transport requests is managed by SAP Cloud Transport
Management. The processing of change documents in an SAP Cloud Transport Management landscape is
mostly the same as in an on-premise landscape. There are only minor differences regarding the handling of
SAP Cloud Transport Management transport request for the following types of change documents:

Change Control Management

Change Request Management PUBLIC 449
 Process in the SAP Cloud Transport Management land-
Type of Change Document scape

Normal changes SAP Cloud Transport Management transport requests must

be assigned to normal changes when the normal changes
have the status In Development and the SAP Cloud Trans-
port Management transport requests have the status
Released.

The SAP Cloud Transport Management transport requests

are imported into the target system when the status of the
normal change is set to status To Be Tested. When a normal
change is then set to status Successfully Tested and Testing
for Preliminary Import nothing happens, because the trans-
port requests have already been released and imported into
the target system.

 Note
There is no transport of copies concept for SAP Cloud
Transport Management transport requests.

Urgent changes SAP Cloud Transport Management transport requests must

be assigned to urgent change when the urgent change has
the status In Development and the SAP Cloud Transport
Management transport requests have the status Released.

Defect corrections The SAP Cloud Transport Management transport requests

must be assigned to a defect correction when the defect
correction has the status In Correction and the transport
requests have the status Released. When the defect correc-
tion is then set to the status In Delivery, nothing happens
because the transport requests have already been released.

Standard changes Standard changes aren't supported in an SAP Cloud Trans-

port Management landscape because the standard change
process relies on the allowlist function, which cannot be ap-
plied to the SAP Cloud Transport Management.

 Note

Transport requests from the SAP Cloud Transport Management service are visible in various menus of the
administraction cockpit when they were assigned to change documents (normal change or urgent change).
If a transport request doesn't belong to a change document, it is not visible in the administration cockpit.

 Restriction

The following functions are not supported for SAP Cloud Transport Management landscapes:

• Transport-related checks
• Retrofit

Change Control Management

450 PUBLIC Change Request Management
 • Import feedback
• Task list variant SAP0
• Allowlist function
• Transport of copies

Related Information

Setting Up SAP Cloud Transport Management for Change Control Management [page 451]
SAP Cloud Transport Management
Change Documents [page 26]
Abandoning SAP Cloud Transport Management Transport Requests in Change Control Management [page 453]

4.4.14.1 Setting Up SAP Cloud Transport Management for

Change Control Management

An SAP Cloud Transport Management landscape is very different from an on-premise landscape and needs
specific configuration.

Context

To integrate the SAP Cloud Transport Management with Change Control Management, set up your system
landscape in the following way:

Configuration in the SAP Cloud Transport Management

Procedure

1. Create transport nodes for all tenants of the SAP Cloud applications.
2. Create transport routes for the SAP Cloud application landscape.
3. Create a service key for the SAP Cloud Transport Management.

 Note

Change Control Management supports cloud landscapes in which one transport node can have
multiple targets, but a development transport node can have only one target.

Change Control Management

Change Request Management PUBLIC 451
Configuration in the Change Control Management

Procedure

1. Create an RFC destination for SAP Cloud Transport Management authentication:

• Connection Type: HTTP Connection to External Serv (G)
• Target Host: <Cloud Transport Management URL>
• Path Prefix: /oauth/token/
• User: <Cloud Transport Management client ID>
• Password: <Cloud Transport Management client secret>
• SSL: Active
• SSL Certificate: ANONYM SSL Client (Anonymous)
2. Create an RFC connection for the SAP Cloud Transport Management REST APIs:
• Connection Type: HTTP Connection to External Serv (G)
• Target Host: <Cloud Transport Management URI>
• SSL: Active
• SSL Certificate: ANONYM SSL Client (Anonymous)

Configuration in the Landscape Management Database

(LMDB)

Procedure

1. Create an external service system in the LMDB to represent the transport nodes in the SAP Cloud
Transport Management:
• Technical System Type: External Service
• Extended System ID: The name for the external service system, for example DE1
• Application Domain: Others
• External Service ID: The same ID as the extended system ID, for example DE1
2. Assign the following mandatory attributes to LMDB external service system:

• Is Cloud TM Node: X
• Cloud TM Node Name: The transport node name, for example NE1
• Cloud TM Authentication RFC: The dedicated RFC, for example CLOUD_TM_AUTHENTICATION
• Cloud TM REST API RFC: The dedicated RFC, for example CLOUD_TM_API
3. Create an external service system for all transport nodes in the SAP Cloud Transport Management
landscape.
4. Check the configuration items created for the SAP Cloud Transport Management external systems in
transaction IB52.

Change Control Management

452 PUBLIC Change Request Management
Configuration in the Solution Administration (SLAN)

Procedure

1. Create a logical component group for the SAP Cloud Transport Management landscape and assign it to
your solution.
2. Assign dedicated external service systems to the related branches of the logical component group.

Next Steps

 Note

In SAP Solution Manager, set parameter icm/HTTPS/client_sni_enabled to TRUE.

For details, see SAP Note 510007 section 7: “Recommended Configuration of Available TLS Protocol
Versions” and KBA 2712590 .

4.4.14.2 Abandoning SAP Cloud Transport Management

Transport Requests in Change Control Management

You can abandon an SAP Cloud Transport Management transport request from its change. This transport
request is then no longer controlled by Change Request Management or Quality Gate Management.

Prerequisites

• SAP Cloud Transport Management transport request must be assigned to a modifiable change in Change
Request Management or Quality Gate Management.
• You have decided not to use the SAP Cloud Transport Management transport request, which means you do
not want to import the transport request in the SAP Cloud Transport Management landscape.
• The SAP Cloud Transport Management transport request has not been imported into the production
system. If the transport request has already been imported into the production system, you can no longer
abandon it from Change Control Management.

Change Control Management

Change Request Management PUBLIC 453
Procedure

You can use the report /TMWFLOW/CTMS_ABANDON_TR to trigger the abandon action for the SAP Cloud
Transport Management transport request. The program documentation of the report contains detailed
instructions.

Results

The SAP Cloud Transport Management transport request is decoupled from the change and deleted from the
import queues of all the systems on the SAP Cloud Transport Management service. The outcome of the action
is displayed after the execution of the report. This action is logged in the SLG1 transaction code.

Comparison Between Decoupling and Abandoning Transport Requests

Action Decoupling Transport Requests Abandoning Transport Requests

Valid Scenario All landscapes including SAP Cloud Only valid for SAP Cloud Transport
Transport Management service Management service

Prerequisite in SAP Cloud Transport The transport request must not be im- The transport request can be imported
Management service ported into any systems into the quality systems but must not
be imported into the production sys-
tems

Use case in SAP Cloud Transport Man- You still want to manage and import this You do not need the transport request
agement service transport via other changes anymore and will not import it in the
future

Action results in SAP Cloud Transport The transport request is decoupled The transport request is decoupled
Management service from the change and can be assigned from the change and deleted from the
to other changes later import queues of all the systems in
the SAP Cloud Transport Management
service. You cannot assign it to other
changes later

Related Information

Decoupling Transport Requests in Change Request Management [page 134]

Decoupling Transport Requests in Quality Gate Management [page 525]

Change Control Management

454 PUBLIC Change Request Management
4.4.15 Configuring Git-enabled CTS

When you configure Git-enabled CTS (gCTS) for Change Request Management, you set up the LMDB, the Git
server, and the gCTS app, create a specific track, and implement the required SAP Notes.

Prerequisites

• On the managed systems, you have installed SAP S/4HANA 2020 or higher releases.

Procedure

1. Set up the Landscape Management Database (LMDB).

a. In Landscape Management Database (LMDB), assign the additional attribute IS_GCTS_SYS with value
X for all Git-enabled CTS systems.
b. Assign the Git-enabled CTS systems to your Logical Component Group according to the system role
types.
2. Set up the Git server.
a. Create a dedicated repository.

The repository name must not be longer than 30 characters.

b. Create two branches for the repository, for example, feature branch and main branch.
c. Create a personal access token for the repository.
d. If the Git server is not GitHub, configure the custom parameter below in your SAP Solution Manager
system. Set the value of parameter AIC_GCTS_ENHANCE to X in table view AGS_WORK_CUSTOM.
3. Set up the SAP Fiori app for Git-Enabled Change and Transport System (gCTS app).
a. Maintain the mandatory configuration parameters for the system.
For more information, see Enable Git-Enabled Change and Transport System in an ABAP System.
b. Maintain the mandatory configuration parameters for the repository:
• VCS_RESTRICTED_PUSH: Set value X for the repository linked to the development system.
• VCS_AUTOMATIC_PUSH: Set value true for the repository linked to development system.
• VCS_AUTOMATIC_PULL: Set value false for the repository linked to the target system or
production system.
• Sub directory path: It replaces the parameter VCS_TARGET_DIR and enables you to specify in
which directory of the remote repository ABAP objects are stored, for example src/. For more
information, see Set the Repository Layout.
• CLIENT_VCS_COMMIT_MESSAGE: Keep the default value, do not customize.
• CLIENT_VCS_COMMIT_DESCRIPTION: Keep the default value, do not customize.
• CLIENT_VCS_AUTH_TOKEN: Enter the personal access token for internal and private
repositories.
c. Authenticate the Change Manager.

For more information, see Set User-Specific Authentification.

Change Control Management

Change Request Management PUBLIC 455
 d. Assign the feature branch to the development and target system, and assign the main branch to the
production system.
4. Set up a Git-enabled track for the change cycle.
a. Create a change cycle with the solution that contains your Git-enabled CTS systems.
b. Create a tasklist or redefine the landscape for your change cycle.
c. When you define the scope, select Add Git-enabled Tracks Add .
d. Assign the Git-enabled CTS systems to your track.

You can assign one system as development system, and multiple systems as target systems and
production systems.
e. Finish the guided procedure and save your Git-enabled track.
5. Implement the mandatory SAP Notes for the Git-enabled CTS system.
a. Implement the latest version of SAP Note 2945557 for all Git-enabled CTS systems.
b. Implement the latest version of SAP Note 2983745 for the development system of your Git-enabled
track and activate BAdI CTS_REQUEST_CHECK with implementation TMW_GIT_FORWARD.

Related Information

Git-Enabled Change and Transport System

Processing Git-enabled Changes [page 99]

4.4.16 Release Planning

Release management comprises release planning and the subsequent management, coordination, and
execution of the planned activities.

Use

Use the release planning function in SAP Solution Manager to plan major and minor releases, specify go-live
dates, and assign the release planning data to branches. Release cycles can be created only from the release
planning function for each release. Releases are defined for change control landscapes.

 Note

Change control landscapes are always required for release management because each release cycle is
assigned to a change control landscape. Change control landscapes consist of logical component groups,
and for each change control landscape, independent releases can be planned. You can use the same set
of logical component groups for defining several change control landscapes within the same solution. For
example, there can be a logical component group “CRM” with different releases for CRM Sales and CRM
Marketing.

Change Control Management

456 PUBLIC Change Request Management
When planned activities are performed for a release, IT requirements, requests for change, and change
documents are created and assigned to a release cycle. When a release goes live, only the changes that have
been successfully tested are imported into the production system, depending on their statuses.

Release management uses a predecessor – successor relationship. A successor release can only be imported
into the production system when the predecessor release has been imported. This means that a successor
release cycle can only be switched to phase Build when the predecessor release cycle has at least the phase
Hypercare.

If there’s no successor release cycle, a new release cycle is created automatically.

Reassigning Change Documents

Unfinished change documents are automatically reassigned to the successor release cycle when the release
cycle has moved to the Hypercare phase. They are imported into the production system with the go-live of the
successor release.

Change transactions (IT requirements, requests for change, change documents) with SAP PPM integration
that are assigned to the release cycle cannot be reassigned. In this case, you can’t move the release cycle to
the Hypercare phase and all change transactions stay assigned to this release cycle. To proceed, such change
transactions must be decoupled from the particular SAP PPM project: When the release cycle is moving to the
Hypercare phase, a dialog box displays unfinished change transactions of this release cycle. For every change
transaction, you see the assigned SAP PPM project and the SAP PPM project manager. With this information,
the release manager can contact the particular SAP PPM project manager to request the decoupling of the
change transaction from the SAP PPM project.

Defining Releases
You can define your releases in several ways:

• In a dual landscape, you can perform the activities for your minor releases in the maintenance landscape
(maintenance branch), and for your major releases in the development landscape. In a single landscape,
the activities for both major and minor releases must be performed in the same branch.
• For different change control landscapes (products, scenarios, or business contexts) you can define
different major and minor releases. You can define a release that contains features and changes of
a particular change control landscape or you can define individual releases for each change control
landscape.
• You can plan releases for different scenarios, for example, sales, marketing, and billing.

Change Control Management

Change Request Management PUBLIC 457
Graphical Overview of Major and Minor Releases Within Release Management

Differences Between Release-Based Change Management (Release Management) and

Change Request Management

 Note

We do not recommend that you use Change Request Management and release management (based on
phase or continual cycles) in the same landscape.

The following table shows the differences between release management and project-based change request
management:

Release Management Change Request Management

Differences • Defined dates for the go-live of new features as • Flexible go-live dates of new features and
part of a release changes: Changes are imported into production
• The scope of the new features is flexible. If as soon as development and testing is finished.
development and testing aren’t finished, the • The scope of the changes is fixed.
change can be assigned to the successor re- • Several cycles with several changes can be im-
lease. plemented in parallel. The go-live dates of these
• You can plan the releases before the changes cycles are independent from each other.
are executed.

Benefits • Fewer imports into the production system guar- • Flexible import of changes into the production
antee a high quality and stability of your solu- system. You can import your changes as soon
tion. as they’re finished.
• The test phases and test resources of releases
can be planned long term.
• When using a pre-production system in which
only those changes are imported that are also
imported into production after the tests, there
are fewer dependencies between the changes.

Change Control Management

458 PUBLIC Change Request Management
Prerequisites

• You have defined your solution landscapes, your change control landscape, and your branches, and
you have assigned your logical components to your branches. For more information, see Solution
Documentation.
• You have activated the ODATA Service for Release Planning Tool in the SAP Solution Manager
Configuration in scenario Cross-Scenario Configuration Mandatory Configuration Infrastructure
Preparation Enable Gateway Services .
In edit mode, you can either select the Select/Deselect all Gateway Services checkbox, which allows you
to enable/disable all Gateway Services at once. If you want to activate the ODATA Service for Release
Planning Tool activity only, unfold Change Request Management in the list of Gateway Services and select
the checkbox for the AIC_RELEASE_PLANNING_SRV activity in the Selected For Activation column. Save
your entries.
For more information about the SAP Gateway Service activation, see the help text of this configuration
step.
• For a selected change control landscape, at least one release cycle must be available. It is used as a copy
template for the cycle to be created. The system automatically adjusts go-live dates and other data of the
release cycle.
If there’s no release cycle for a change control landscape, you must create the first release cycle manually.

Features

You can use the following functions:

• Define major and minor releases with specific go-live dates

• Change release dates
You can change the go-live data of a release.
• Delete releases
• Create release cycles
• Filter by change control landscapes
Select Filter by Change Control Landscape and the change control landscapes you want to see, and choose
OK. The system keeps the filter settings for your next session.
• Display only open cycles or all cycles (including replaced and planned cycles)
The system keeps the filter setting for your next session.
• Select multiple lines
You can select multiple release entries to create or delete release planning data.
• Display Messages
The notification bar at the bottom of your screen displays the latest action you performed.
To view the complete list of actions that you have executed during the current session, select Enlarge.

 Note

Messages in the release planning tool are recorded in application log SLG1 with object /TMWFLOW/
CMSCV and subobject REL_PLAN

Change Control Management

Change Request Management PUBLIC 459
Procedure

1. For your change control landscape, plan the major and minor releases using the release planning function.
2. Create release cycles for your releases.
3. Perform the activities in the change documents assigned to the release cycle and set their status.
4. On the go-live date, the IT operator triggers that all changes with the required status are transported into
the production system.
5. Assign the unfinished change documents to a successor release.
When a release goes live, only the changes that have been successfully tested and that are assigned to the
release cycle are imported into the production system. Unfinished change documents can be reassigned to
the successor release, and will be imported into the production system with the next release cycle.

Related Information

Defining and Deleting Releases [page 460]

Release Cycle [page 44]
Reassigning Change Transactions [page 141]

4.4.16.1 Defining and Deleting Releases

You can create, edit, and delete releases in the Change Request Management WebClient UI.

 Tip

See the on-screen help for the release planning function.

Procedure

Defining Releases
To create, edit, or change releases, perform the following steps:

1. In the WebClient UI, choose Change Request Management Release Planning .

2. Choose Create to create the desired number of major and minor releases.
3. Enter the relevant information for the releases in the dialog window.

 Note

The system might have to adjust the data you entered:

• The go-live date of first major release might be changed according to the go-live day (Monday
through Sunday) of the major release.

Change Control Management

460 PUBLIC Change Request Management
 • The duration of major releases might be adjusted in response to the calculation of the go-live date
of a subsequent major release, which is computed as follows: The go-live date of first major release
+ duration (days) and then being modified by the entered go-live day (Monday through Sunday).
• The duration of a minor release might be adjusted due to the entered go-live day, for example, the
day of Sunday.
• The number of minor releases is adjusted if the duration of the major release is shorter than
the combined durations of all minor releases. For example, the duration of the major release is
defined with 21 days. The desired number of minor releases is 2, each with a duration of 14 days.
Consequently, the system can only create one minor release for each major release.

4. You can create new releases, or successors for existing change control landscapes, depending on the value
in the Change Control Landscape field.
5. Select a line and choose Create Minor Release as Successor to add minor releases to a major release.
6. To change a release date, select a date in the release table or by drag and drop a release bar in the calendar.
When changing a date, you can choose whether successor releases are to be postponed. If you would like
to postpone, the system moves the dates of all successor releases by the same number of days.

Deleting Releases
To delete, you can select one or more releases that are in status Planned at once.

You can delete a major release only if there’s no successor release assigned to it.

You can delete minor releases only if there’s no successor minor release assigned to the same major release.
For example, release 1.3 cannot be deleted if there's release 1.4. However, 1.4 can be deleted if the successor
release is the major release 2.0.

 Note

If a change transaction is assigned to a release cycle, you can decouple and reassign it, and delete the
release.

If an SAP PPM project is assigned to a release cycle, you can remove the assignment, and delete the
release.

1. To delete one or multiple releases, select the lines in the list.

2. Choose Delete Current Release.
The system displays a dialog window.
3. Choose Yes if you want to delete the selected releases.
When deleting a release, the system performs the following checks:
• Does the release have a successor release?
• Is the release cycle assigned to an SAP PPM project?
• Are change transactions (change documents, requests for change or IT requirements) assigned to the
release cycle?
If all checks are negative, the release can be deleted.

Related Information

Release Planning [page 456]

Change Control Management

Change Request Management PUBLIC 461
Reassigning Change Transactions [page 141]

4.4.17 Customizing Solution Documentation Integration for

Upgrades

For customers upgrading from SAP Solution Manager release 7.1 to release 7.2 and for customers who have
copied the transaction types prior to SAP Solution Manager 7.2, support package 3, the following tables provide
Customizing information on enabling the integration of Solution Documentation.

 Note

For more information about the Customizing activities, see the help texts in SAP Solution Manager
Configuration (transaction SOLMAN_SETUP) step Integrate Additional Functions Enable Solution
Documentation Integration , and the activity documentation.

Assign Change Request Management Actions and Consistency Checks

Activity Make Settings for Change Transaction Types

Actions Assigned to User Statuses

Transaction Type Status Profile Status Sequence Action

SMAD (Administrative SMADHEAD E0001 30 SOL_DOC_CREA

Change)
E0002 50

E0009 20 SOL_DOC_ACT

E0010 30

SMCG (General SMCGHEAD E0001 30 SOL_DOC_CREA

Change)
E0005 20 SOL_DOC_ACT

E0014 40 SOL_DOC_CREA

E0016 20 SOL_DOC_ACT

SMCR (Request for SMCRHEAD E0003 40 SOL_DOC_ACT

Change)
E0006 30

SMGH (Git-enabled SMGHHEAD E0001 30 SOL_DOC_CREA

Change)
E0002 50

Change Control Management

462 PUBLIC Change Request Management
 E0006 30 SOL_DOC_ACT

E0010 30

SMHF (Urgent SMHFHEAD E0001 40 SOL_DOC_CREA

Change)
E0002 50

E0006 30 SOL_DOC_ACT

E0008 30

E0010 40

SMMJ (Normal SMMJHEAD E0001 30 SOL_DOC_CREA

Change)
E0002 50

E0006 30 SOL_DOC_ACT

E0010 30

SMTM (Defect Correc- SMTMHEAD E0001 40 SOL_DOC_CREA

tion)
E0002 50

E0009 6 SOL_DOC_ACT

Late Actions

SOL_DOC_CREA and SOL_DOC_ACT

Transaction Type Status Profile Status Sequence Action

SMAD (Administrative SMADHEAD E0001 30 SOL_DOC_CREA

Change)
E0002 50

E0009 20 SOL_DOC_ACT

SMCG (General SMCGHEAD E0001 30 SOL_DOC_CREA

Change)
E0014 40

SMGH (Git-enabled SMGHHEAD E0001 30 SOL_DOC_CREA

Change)
E0002 50

E0006 30 SOL_DOC_ACT

E0010 30

Change Control Management

Change Request Management PUBLIC 463
SMHF (Urgent SMHFHEAD E0001 40 SOL_DOC_CREA
Change)
E0002 50

E0006 30 SOL_DOC_ACT

E0008 30

E0010 40

SMMJ (Normal SMMJHEAD E0001 30 SOL_DOC_CREA

Change)
E0002 50

E0006 30 SOL_DOC_ACT

SMTM (Defect Correc- SMTMHEAD E0001 40 SOL_DOC_CREA

tion)
E0002 50

E0009 6 SOL_DOC_ACT

E0010 6

Table: TSOCM_ACTION_O_S

For SAP Solution Manager 7.2 SPS 1 and 2 customers, delete the following:

Transaction Type Status Sequence Action

SMCR (Request for E0014 50 SOL_DOC_CREA

Change)
E0012 50

Table: TSOCM_COND_MAPP

Consistency Checks

Activity Make Settings for Change Transaction Types in area Assign Consistency Checks

Transaction Status Pro- Status Sequence Consistency Message Message No. Type
Type file Check Class

SMAD (Ad- SMADHEAD E0009 30 SOL_DOC_A AI_CRM_CM_ 109 E0004

ministrative CT_CHECK MESSAGE
Change)

SMCG (Gen- SMCGHEAD E0005 20 SOL_DOC_A AI_CRM_CM_ 109

eral Change) CT_CHECK MESSAGE

E0011 20 SOL_DOC_A AI_CRM_CM_ 113

CT_PRE- MESSAGE
CHECK

Change Control Management

464 PUBLIC Change Request Management
SMGH (Git- SMGHHEAD E0004 65 SOL_DOC_A AI_CRM_CM_ 113
enabled CT_PRE- MESSAGE
Change) CHECK

E0006 65 SOL_DOC_A AI_CRM_CM_ 113

CT_PRE- MESSAGE
CHECK

E0006 70 SOL_DOC_A AI_CRM_CM_ 109

CT_CHECK MESSAGE

E0009 65 SOL_DOC_A AI_CRM_CM_ 113

CT_PRE- MESSAGE
CHECK

E0010 70 SOL_DOC_C
HANGED

E0014 10 SOL_DOC_A AI_CRM_CM_ 113

CT_PRE- MESSAGE
CHECK

SMHF (Ur- SMHFHEAD E0006 25 SOL_DOC_A AI_CRM_CM_ 113

gent Change) CT_PRE- MESSAGE
CHECK

E0006 30 SOL_DOC_A AI_CRM_CM_ 109 E0009

CT_CHECK MESSAGE

E0009 20 SOL_DOC_A AI_CRM_CM_ 113

CT_PRE- MESSAGE
CHECK

SMMJ (Nor- SMMJHEAD E0006 65 SOL_DOC_A AI_CRM_CM_ 113

mal Change) CT_PRE- MESSAGE
CHECK

E0006 70 SOL_DOC_A AI_CRM_CM_ 109

CT_CHECK MESSAGE

E0010 70 SOL_DOC_A AI_CRM_CM_ 109

CT_CHECK MESSAGE

D0014 10 SOL_DOC_A AI_CRM_CM_ 113 E0013

CT_PRE- MESSAGE
CHECK

SMTM SMTMHEAD E0009 30 SOL_DOC_A AI_CRM_CM_ 109 E0004

CT_CHECK MESSAGE

Change Control Management

Change Request Management PUBLIC 465
Late Consistency Checks: SOL_DOC_ACT_CHECK

Activity Make Settings for Change Transaction Types in area Define Execution Time of Consistency Checks

Transaction Type Status Profile Status Sequence

SMAD (Administrative SMADHEAD E0009 30

Change)

SMCG (General Change) SMCGHEAD E0005 20

SMGH (Git-enabled Change) SMGHHEAD E0006 70

SMHF (Urgent Change) SMHFHEAD E0006 30

SMMJ (Normal Change) SMMJHEAD E0006 70

SMTM (Defect Correction) SMTMHEAD E0009 30

Configure UI Elements for Solution Documentation in Standard Customizing

Activity Configure Status-Dependent UI Element Control

For standard transaction types, the following entries are maintained:

Table: AIC_PROC_EDIT

Transac- Status Pro- UI Element User Sta- Editable/ Visible UI Control UI Control Active
tion Type file tus Executable Class Method

SMAD (Ad- SMAD- EN- E0001 X X X

ministrative HEAD HANCED_S
Change) COPE_BUT- E0002 X X X
TON
E0004 X X

E0009 X X

E0010 X X

SCOPE_BU E0001 X X X
TTON
E0002 X X X

E0004 X X

E0009 X X

E0010 X X

Change Control Management

466 PUBLIC Change Request Management
SMCG SMCGHEA EN- E0001 X X X
(General D HANCED_S
Change) COPE_BUT- E0003 X X X
TON
E0004 X X X

E0005 X X

E0006 X X

E0011 X X X

E0012 X X

E0014 X X X

E0015 X X X

E0016 X X

SCOPE_BU E0001 X X X
TTON
E0003 X X X

E0004 X X X

E0005 X X

E0006 X X

E0011 X X X

E0012 X X

E0014 X X X

E0015 X X X

E0016 X X

SMCR (Re- SMCRHEA EN- E0001 X X X

quest for D HANCED_S
Change) COPE_BUT- E0003 X X
TON
E0004 X X X

E0005 X X

E0006 X X

E0011 X X X

E0012 X X X

Change Control Management

Change Request Management PUBLIC 467
 E0014 X X X

E0015 X X X

SCOPE_BU E0001 X X X
TTON
E0003 X X

E0004 X X X

E0005 X X

E0006 X X

E0011 X X X

E0012 X X X

E0014 X X X

E0015 X X X

SMGH (Git- SMGHHEA EN- E0001 X X X

enabled D HANCED_S
Change) COPE_BUT- E0002 X X X
TON
E0004 X X X

E0006 X X

E0009 X X

E0010 X X

E0014 X X

SCOPE_BU E0001 X X X
TTON
E0002 X X X

E0004 X X X

E0006 X X

E0009 X X

E0010 X X

SMHF (Ur- SMHFHEAD EN- E0001 X X X

gent HANCED_S
Change) COPE_BUT- E0002 X X X
TON
E0004 X X

Change Control Management

468 PUBLIC Change Request Management
 E0005 X X

E0006 X X

E0007 X X

E0008 X X

E0009 X X

E0010 X X

SCOPE_BU E0001 X X X
TTON
E0002 X X X

E0004 X X

E0005 X X

E0006 X X

E0007 X X

E0008 X X

E0009 X X

E0010 X X

SMMJ SMMJHEA EN- E0001 X X X

(Normal D HANCED_S
Change) COPE_BUT- E0002 X X X
TON
E0004 X X

E0006 X X

E0009 X X

E0010 X X

E0011 X X

E0012 X X

E0013 X X

E0014 X X

SCOPE_BU E0001 X X X
TTON
E0002 X X X

Change Control Management

Change Request Management PUBLIC 469
 E0004 X X

E0006 X X

E0009 X X

E0010 X X

E0011 X X

E0012 X X

E0013 X X

E0014 X X

SMTM (De- SMTMHEA EN- E0001 X X X

fect Correc- D HANCED_S
tion) COPE_BUT- E0002 X X X
TON
E0004 X X

E0009 X X

E0010 X X

SCOPE_BU E0001 X X X
TTON
E0002 X X X

E0004 X X

E0009 X X

E0010 X X

4.4.18 Configuring the Notification Framework of SAP CRM

for Change Request Management

You can set up the Notification Framework of SAP Customer Relationship Management to create e-mail
notifications that keep your business partners informed about the status and the progress of change
transactions.

You can use the Notification Framework as an alternative to the e-mail notifications created by Post-Processing
Framework (PPF) actions. The Notification Framework allows the users to create subscriptions to change
transactions and to define conditions for these subscriptions.

Change Control Management

470 PUBLIC Change Request Management
Preparatory Steps

To use the Notification Framework of SAP CRM with Change Request Management, make sure that the
following preparatory steps are completed:

1. Check that in transaction SFW5 the business function CRM_ITSM_ALERTS is activated.

2. Call transaction SM30 and open the view AGS_WORK_CUSTOM. In this view, add a new entry for the
parameter IM_ALLOW_BUS20001_UPLOAD and activate this parameter by entering an X as the parameter
value.
3. Check that in the transaction SNUM or in the transaction SNRO number ranges are maintained for the
Notification Framework.
4. Check the transaction category and the notification filters for the Notification Framework:
1. In the Customizing (IMG) at Customer Relationship Management Transactions Settings for
Service Requests Notification Framework Define Conditions of Subscription Processing , add a
new entry for the object type BUS2000116.
2. In the Class/Interface field, enter CL_CRM_CM_NF_CORE_OTYP_HNDL_1O.
3. At For Send Notification on Change, select the option Active.
4. Select object type BUS2000116 and double-click Notification Filters.
5. Check that the table contains the standard entries.
5. Check the output channels for the Notification Framework:
In the Customizing (IMG) at Customer Relationship Management Transactions Settings for Service
Requests Notification Framework Change Processing of Communication Channels , go to the channel
type EMAIL and enter CL_CRM_CM_NF_HNDL_CHN_MFORMS in the in Class / Interface field.
6. Activate BDoc for the Notification Framework:
In the Customizing (IMG) at Customer Relationship Management CRM Middleware and Related
Components Message Flow Setup BDoc Type Settings, , go to the entry BUS_TRANS_MSG . In the
XML field, select Default and remove the check mark in the Do Not Send column.
7. Activate the BDoc queue for the Notification Framework:
1. To check status for the BDoc queue, call transaction SMW01.
2. Enter the BDoc type BUS_TRANS_MSG and execute the transaction.
3. Check the status of for BUS_TRANS_MSG:
• If it is green, the BDoc queue is active.
• If it is yellow, do the following:
1. Display the details of the status message and note the queue names, for example
CSA_ORDER_XXX.
2. Call transaction SMQR and choose Registration and enter the following:
• Queue name (for example CSA_ORDER_*)
• Mode D
• Max.. runtime 30
• Attempts 10
• Pause 120.
8. Schedule the queue processing report for the Notification Framework:
1. Call transaction SM36 .
2. Schedule a periodic job with the report CRM_NF_CORE_QOUT_PROCESSING with the variant channel
type EMAIL and the business object type BUS2000116.

Change Control Management

Change Request Management PUBLIC 471
9. Optionally, you can configure that a predefined mail form is used for the e-mail notifications for your
change transaction types:
In the Customizing (IMG) at Customer Relationship Management Transactions Settings for Service
Requests Notification Framework Define Defaults for Direct Subscribing , create subscriptions for your
transaction types, assign the channel type EMAIL as the default channel, and enter the ID of the mail form
that you want to use as the default mail form.
10. Configure the subscription type for the Notification Framework:
1. In the customizing (IMG) at Customer Relationship Management- Transactions Settings for
Service Requests Notification Framework Change Processing of Subscribers , go to the subscriber
type DR.
2. Change the entry in the Class / Interface field to CL_CM_NF_API_SUBS_TYPE_HNDL.
11. Check navigation links for service operations:
In the Customizing (IMG) at Customer Relationship Management UI Framework- Business Roles
Define Business Role , go to the business role SOLMANPRO and switch to the Adjust Work Center Group
Links tab.
Make sure that the logical link IDs CT-NF-CR and CT-NF-SR are set to visible.
12. Check that the authorization objects CRM_NF_API, CRM_NF_SUB, and CRM_NF_SUP are assigned to the
Change Request Management administrator role.

Creating Mail Forms and Subscriptions to Change Transactions

When the preparation is completed, you configure mail forms that are used as templates for the notification
e-mails. To be notified about status changes of these transactions, you create subscriptions for the change
transactions.

To create a mail form as a template for the e-mail notifications in the Notification Framework, do the following:

1. In the WebClient UI, choose Service Operations.

2. Under Create, choose Mail Form and create a mail form.

To create a subscription for change transactions in the Notification Framework, do the following:

1. In the WebClient UI, choose Service Operations.

2. Under Create, choose Subscription and create a subscription.

Related Information

E-Mail Notifications [page 286]

PPF Actions in Change Request Management [page 168]

Change Control Management

472 PUBLIC Change Request Management
4.4.19 Linking IMG Projects to Change Cycles

You can link IMG projects to change cycles.

Prerequisites:

• The IMG project must not yet be assigned to a CTS project.

• The change cycle has an active task list.

To link IMG projects to change cycles, use the activity Assign IMG Project to Change Cycle in the IMG
Customizing for SAP Solution Manager (transaction SPRO) in Capabilities (optional) Change Control
Management Change Request Management Framework Change Cycles .

To link an IMG project that you have newly created in transaction SPRO_ADMIN to a change cycle, you can also
use transaction //TMWFLOW/ASSIGN_IMG.

For more information about using this feature with SAP Solution Manager 7.2 SPS 3 to SPS 6, see also SAP
note 2516652 .

4.5 Configuring Change Request Management

Set up your systems to use Change Request Management in SAP Solution Manager.

If you’re setting up Change Request Management for the first time, in the solution landscape (transaction
SLAN), you choose technical systems and assign them to logical components, which in turn are assigned
to logical component groups. Branches are assigned to logical components and change control landscapes
are defined. These are activated for Change Request Management. As a last step, you create change
cycles and task lists, which contain more settings. For more information, see the help texts and activity
documentation in SAP Solution Manager Configuration (transaction SOLMAN_SETUP), Change Control
Management Managed System Setup step Create Landscape and Change Cycle.

If you’re upgrading from SAP Solution Manager 7.1 to SAP Solution Manager 7.2, see the documentation for
content activation at http://support.sap.com/solutionmanager First Steps Technical Guides .

Configuring Change Request Management with SAP Solution Manager

Configuration

To configure Change Request Management, complete the following guided procedures in SAP Solution
Manager Configuration (transaction SOLMAN_SETUP).

Mandatory Configuration - System Preparation

After installing SAP Solution Manager or upgrading your system from SAP Solution Manager 7.0 or 7.1,
complete all steps.

After installing a new Support Package Stack, update the activities marked in column Updates Needed.

Change Control Management

Change Request Management PUBLIC 473
Mandatory Configuration - Infrastructure Preparation
After installing SAP Solution Manager or upgrading your system from SAP Solution Manager 7.0 or 7.1, you
must complete all steps, apart from step Define CA Introscope.

After installing a new Support Package Stack, update the activities marked in column Updates Needed.

Mandatory Configuration - Basic Configuration

After a new installation or after installing a Support Package Stack, complete the following to perform delta
configuration.

Step Configure Basic Functions

• Activity Activate Piece Lists

After installing a new Support Package Stack, you must perform this activity again to get the latest
standard Customizing settings. Therefore, you must ensure that you copy all transaction types, status
profiles, action profiles, and so on, into your own namespace before you start using Change Request
Management. If you don't, your changes are overwritten when the next Support Package Stack is installed.
• Activity Activate ICF Services
Activate the services for Web Dynpro and BSP applications that are needed by all scenarios in SAP Solution
Manager.

Step Schedule Jobs

Schedule job SM:TMWFLOW_CMSSYSCOL (report /TMWFLOW/CMSSYSCOL2) to run on a daily basis. The job
collects data of transports, SAP Notes, and Support Package Stacks of each system defined in table /
TMWFLOW/CMSCONF using asynchronous remote function calls. You can use this job to remove obsolete
transport tracking data that is collected by the import feedback mechanism. For more information, check
the parameter CM_IMPORT_FEEDBACK_RETENTION_DAY in SAP Note 1483276 .

Managed Systems Configuration

In this guided procedure, you connect the managed systems to SAP Solution Manager.

• To configure a single system, choose Technical Systems.

• To configure a double (ABAP and Java) stack system, choose Technical Scenarios.
• To configure a standalone database, choose Databases.

You must create the RFC destinations from SAP Solution Manager to those systems in your managed
landscape where you want to control the software changes via Change Request Management. Change Request
Management needs a READ, TMW, and a trusted RFC connection to every managed system and client. To
ensure that Change Request Management works perfectly with the managed systems, a minimum support
package level is needed.

 Note

You configure specific managed systems for Change Request Management under Change Control
Management Managed System Setup .

For Change Request Management, you only have to create connections from the managed systems to SAP
Solution Manager if you want to use the cross-system object lock or retrofit functions.

Change Control Management

Follow the guided procedures Change Request Management and Managed System Setup. Most Change Request
Management steps contain a substep called Finalize Step, which leads you to the corresponding settings

Change Control Management

474 PUBLIC Change Request Management
under Managed System Setup, so you can start using Change Request Management, including the configured
functions.

The guided procedures for Change Request Management and Managed System Setup follow a predefined
sequence, as recommend by SAP and according to industry best practices. The following graphics show the
steps, their contents, and their relation to each other.

Change Request Management Guided Procedure

Managed System Setup Guided Procedure

 Note

Alternatively, you can configure all settings for Change Request Management in Customizing (transaction
SPRO) under SAP Solution Manager Capabilities (Optional) Change Control Management .

Change Control Management

Change Request Management PUBLIC 475
Related Information

Configuration
Solution Documentation
Change Cycles [page 28]
Task List [page 53]
Configuring the Preliminary Import Function [page 73]

4.6 Reporting in Change Control Management - Change

Request Management

Use

Change Control Management dashboards provide insights into IT processes managed by SAP Solution
Manager, including:

• Change Control Management

• Incident Management
• Problem Management

Prerequisites

In SAP Solution Manager Configuration, complete the following steps:

• In the Infrastructure Preparation scenario, step Set Up SAP BW.

• In the Change Control Management scenario, under Change Request Management, step Define Reporting.
• In the Change Control Management scenario, under Change Request Management, step Define Settings
for Template Users Create Template Users .

Features

Dashboards
• Change Control Management - Analytics
This dashboard gives analytical insights into request for changes and change documents, focusing on the
change handling. It provides many KPIs, such as the total number of request for changes and change
documents in the system, or the average duration until the fulfillment of the changes (duration in average,
implementation in average/total). You can filter by calendar week.
• IT Service and Change Management - Dashboard

Change Control Management

476 PUBLIC Change Request Management
 This dashboard provides a “cross-topic” view on incidents, problems, and change requests. It provides
insights on the integrated progress. It provides the most important KPIs of incidents, problems and change
requests, such as how many issues are there, and whether issues are resolved in accordance with the
defined service level agreement (SLA), or the average duration of each process.

KPI Definition in KPI Catalog

Select a tile in a dashboard to open the KPI Catalog to view KPI definitions.

More Information

• Dashboard Builder
You can use various dashboards delivered by SAP as templates for your own tasks.
• Change Management Dashboard - Change Control Management Analytics
• KPI Catalog
You can view and download KPIs from the KPI Catalog.

Change Control Management

Change Request Management PUBLIC 477
5 Quality Gate Management

Quality gate management (QGM) provides an integrated and consistent quality process to manage changes
and their deployment over all operational units across the various organizations of a company.

Use

You can access quality gate management from the SAP Fiori launchpad using the corresponding tile in the
Change Management group.

In quality gate management, you can do the following:

• Monitor all software change processes and obtain full transparency of these processes
• Use a project-based or release-based approach to distribute software across systems and technology
stacks
• Gain an integrated and consistent overview of the implementation of changes to your SAP software
solution

Before you can use quality gate management for a scenario or change cycle, you must provide certain
information such as the quality manager responsible, the quality advisory board member responsible, and
the quality gate data.

The quality manager and a member of the quality advisory board must approve a quality gate for its overall
status to be passed. Only specified users in a company are authorized to give quality gates the status Passed.

Integration

Technically based on the Change and Transport System (CTS), quality gate management integrates the various
development workbenches into one central transport and change control system. It also synchronizes the
software distribution in the different software stacks.

For each QGM scenario, you can also activate the central Change and Transport System (cCTS), which provides
a technical infrastructure for the enhanced flexibility functions in Change Control Management.

 Note

Quality Gate Management does not support an integration with Change Request Management.

Change Control Management

478 PUBLIC Quality Gate Management
Features

Quality gate management ensures that all software change processes are fully transparent: It centrally
manages the software distribution in complex system landscapes across technology stacks and application
components.

Quality gate management combines different software developments into one logical structure. These
developments are, in turn, collected in “QGM scenarios”. You can organize and monitor how software is
distributed according to individual scenarios or change cycles, as well as the changes made for them. Each
QGM scenario comprises four phases: Scope, Build, Test, and Deploy.

Each of these phases is separated by quality gates (“Q-Gates”). A quality gate is a milestone that controls
whether data can be imported into the follow-on systems assigned to the gate. You can import data into a
follow-on system only after a quality gate has been passed.

Quality gates give you a quick overview of each scenario or change cycle, as well as its status. Within the
overview, you see the time schedule for the different scenarios or change cycles along with the ratings of any
quality gates that have already been passed. Deadlines are displayed either graphically or in list form.

In addition to quality gates, you can specify milestones for your QGM scenario. Like a quality gate, a milestone
is the end of a work step, but unlike a quality gate, a milestone does not control whether data can be imported
into a follow-on system.

Related Information

QGM Data for a Scenario [page 499]

Change Control Management Using Central CTS [page 399]
Phases in Quality Gate Management [page 483]

5.1 Change Management Using Quality Gate Management

Use

You can manage the quality gate (Q-Gate) data of your scenarios or change cycles in the Quality Gate
Management tile of the Fiori launchpad.

Integration

Quality gate management is part of SAP Solution Manager.

Change Control Management

Quality Gate Management PUBLIC 479
Features

A standard scenario involves four phases: scope, build, test, and deploy. Each of these phases is separated by
a quality gate, the name of which indicates the phases that the gate separates (for example, “Scope to Build”).
There are also quality gates before the start of the scope phase and at the end of the deploy phase, as shown in
the graphic below.

Quality Gates and Phases

You can also create your own quality gates in addition to those delivered as standard. For more information, see
Setting Up Quality Gates and Assigning Phases [page 487].

Change Control Management

480 PUBLIC Quality Gate Management
Change Cycles

When you work with a QGM scenario, you can create change cycles. In this case, instead of having the End of
Deployment quality gate, you have a quality gate called Deploy to Scope. The End of Deployment quality gate is
not applicable until there are no more change cycles.

The graphic below shows an example of a scenario that comprises two change cycles. Note that the quality
gate between cycle 1 and cycle 2 is Deploy to Scope, and that the End of Deployment quality gate does not
occur until the scenario is complete (that is, at the end of cycle 2).

Change Control Management

Quality Gate Management PUBLIC 481
 QGM Scenario with Two Change Cycles

Change Control Management

482 PUBLIC Quality Gate Management
For more information, see Change Cycles [page 493].

Activities

You manage the data for your scenario in several work steps:

• Specify the name and description of the scenario, the quality manager, and the quality advisory board
members.
• Specify the quality gates and milestones.
• Specify the change control landscape and branch to determine the transport landscape that is to be used.
• Check the transport landscape and systems.
• Assign the quality gates to system roles.
• Specify whether to allow transports of copies to be imported during the build phase and transports to be
released in the scope phase
• Confirm the system data.

These steps are described in detail under Setting Up Quality Gates and Assigning Phases [page 487].

More Information

For more information about the meaning of the phases, see Phases in Quality Gate Management [page 483].

5.1.1 Phases in Quality Gate Management

Quality gate management scenarios have the following four phases:

1. During the Scope phase, you plan the tasks that are required to complete the scenario. In this phase, you
also verify the system landscape and the technical prerequisites of the systems for a scenario.
In the Scope phase, you carry out the following activities:
• You document the functional or technical design.
• You document the requirements of individual departments.
• You evaluate the technical viability of a scenario.
The Scope phase begins at the quality gate Start of Scope.
2. The Build phase refers to the actual development process. In all of the systems used in the scenario, you
create the necessary transport requests, which are attached to the software development objects. The
transports are imported into the follow-on systems together to ensure that functions remain stable if the
transport requests are interdependent.
The Build phase begins at the quality gate Scope to Build.
3. In the Test phase, new developments and Customizing settings are imported and activated in the test
systems. The quality assurance team completes any test cases that have been created (for example,
integration and user acceptance testing). If the test cases identify errors, the necessary corrections must
be made in the development systems. The changes are then assigned to new transports, which are
imported to the test system.

Change Control Management

Quality Gate Management PUBLIC 483
 The Test phase begins at the quality gate Build to Test.
4. Only the entire scenario, including all changes and corrections, can be imported during the Deploy phase.
This process ensures that all transport requests for a scenario are imported into the production system in
full and in the correct sequence. The Deploy phase, also know as “go-live”, is the last phase of the scenario.
The Deploy phase begins at the quality gate Test to Deploy.

 Note

When you work with a QGM scenario, you can create change cycles. In this case, instead of having the
End of Deployment quality gate, you have a quality gate called Deploy to Scope. The End of Deployment
quality gate is not applicable until there are no more change cycles. For more information, see Change
Cycles [page 493].

5.1.2 Quality Gate Management Prerequisites

You must ensure that the following prerequisites have been met if you want to use quality gate management:

• Quality gate management roles are assigned to the respective users.

• Business partners have been created for the quality manager and quality advisory board.
• The system landscape is configured in the Transport Management System (TMS). For more information,
see Change and Transport System.

 Note

For more information, see SAP Note 2077243 .

Roles in Quality Gate Management

The following roles are required to use quality gate management:

• Quality manager (QM): A quality manager sets the first status in quality gate management to determine
whether a quality gate is passed.
• Quality advisory board (QAB): A member of the quality advisory board sets the second status in quality
gate management to determine whether a quality gate is passed.

 Note

The quality advisory board is a group of team members who are responsible for the quality of the
customer system landscape. The members of the quality advisory board can be, for example, the
quality managers of a business area, with their manager or IT director. However, the QAB user must be
a different user than the QM.

Change Control Management

484 PUBLIC Quality Gate Management
Configure the System Landscape

You must ensure that the logical components that you use in scenarios match the system landscape
configuration in the transport management system.

 Caution

Because transport requests created outside of QGM cannot be identified by QGM as belonging to a
scenario, users must not be permitted to create, maintain, or release transport requests or tasks directly
in the Transport Organizer. Requests and tasks are therefore always created and released in the QGM
application itself, either by a project lead or by the developers themselves.

Landscape Management

To use quality gate management, you must carry out the following steps:

1. You create a logical component from the Administration tile in the SAP Solution Manager Administration
group of the Fiori launchpad. To do so, you choose Landscape Logical Components . For more
information, see Managing Logical Components.
2. You create a change control landscape and branch in Solution Documentation (transaction SLAN). For
more information, see Solution Documentation.

5.2 QGM Scenario Overview

In the overview, you see your QGM scenarios together with some related functions. You can navigate to more
detailed information and monitor the progress of one or more scenarios in a calendar and in the system
landscape.

Features

You can add a new scenario and search for existing scenarios.

You can perform a transport analysis and export the scenario table to Microsoft Excel.

If you select one or more scenarios in the table, you see more information in the calendar view and landscape
view.

Change Control Management

Quality Gate Management PUBLIC 485
Scenario Table
The scenario table provides the following information and functions:

Column Meaning

Scenario The ID of the QGM scenario. Select the link to see the sce-
nario details screen, where you can monitor and maintain
create changes and transport requests.

Description The description of the QGM scenario

Quality Manager The business partner of the assigned quality manager who
sets the first status for the quality gate. Select the link for
more information about the business partner.

Quality Advisory Board The business partner of the quality advisory board member
who sets the second status for the quality gate. Select the
link for more information about the business partner.

Phase The current phase of the scenario

Next Gate The date on which the next quality gate is due to start. Select
the link for more information about the quality gate.

Transport-Related Checks An icon indicates whether transport-related checks have

been carried out, and whether conflicts were identified for

the scenario. For more information, select Actions...

Transport-Related Checks .

Actions Depending on the status of the scenario, you can use the
following actions:

• Set Up Cycle: Create a new change cycle and edit active

change cycles.
• Set Up Scenario: Assign deadlines to quality gates and
assign quality gates to systems.
• Configuration Check: Check whether your scenario is
configured correctly.
• Change CTS Status Switch: You can manually override
the standard behavior of the CTS status switch.
• Transport-Related Checks: Check the results of the
transport-related checks.
• Display Change Log: See a history of status changes.
• Delete Scenario: Delete the scenario.

 Tip

To change the sequence of columns, drag and drop them.

To select which columns you want to see, use Open Settings Dialog.

Change Control Management

486 PUBLIC Quality Gate Management
Calendar View
In the calendar view, the quality gates and phases are displayed linearly. You can view up to 10 scenarios at a
time. Colors indicate the status of a phase or quality gate.

Landscape View
In the landscape view, you can view the system landscape and the quality gates between each of the systems.
You can also navigate to the quality gate details and manage transports from here.

Related Information

Working with Quality Gates [page 501]

Transport-Related Checks in QGM [page 530]
Creating and Editing Cycles [page 493]
Setting Up Quality Gates and Assigning Phases [page 487]
Checking the Quality Gate Configuration [page 492]
Changing the CTS Status Switch [page 495]
Application Log [page 251]
Change Log [page 497]
Calendar View [page 500]
Landscape View [page 503]

5.2.1 Setting Up Quality Gates and Assigning Phases

Prerequisites

• You have connected your managed systems to SAP Solution Manager.

• You have defined a logical component group that contains the transport landscape, and you have
defined a change control landscape and branch. For more information, see Managing System Landscape
Information.

Context

You use quality gates (“Q-Gates”) to indicate the end of a phase in quality gate management and to release the
next phase of your scenario. Quality gates ensure that transport requests cannot be imported into the system
assigned to the quality gate until the quality gate immediately preceding the system has been successfully
passed.

Change Control Management

Quality Gate Management PUBLIC 487
Procedure

1. Open the Quality Gate Management tile from the SAP Fiori launchpad.
2. To create a new scenario, click the New Scenario button or to change an existing scenario, choose
Actions Set Up Scenario .

In both cases, a guided procedure appears.

 Note

You can view additional help documentation by clicking the question mark icon (?). You can then
expand or collapse the help by clicking the tray.

3. In the header data, enter a name and description for your scenario along with the business partners of the
quality manager and the member of the quality advisory board.

If you are making changes to an existing scenario, you can click the Change Log button to view any changes
that have been made to either of the manager fields.
4. In the Define Milestones area, specify the quality gate and milestone data for the scenario.
• Enter the planned deadlines for all quality gates and milestones. The deadlines for each quality gate
must be in the correct sequence.
• To create your own milestones as quality gates, choose Add Milestone, enter a name and a date for the
milestone, and select the Quality Gate checkbox.
• You can upload template documents for each quality gate. Select the row containing the quality gate
and click Upload Template.

 Note

The system administrator uploads templates to the system. These documents can be used by
team members, who can download and upload them from the Open Q-Gate window.

5. In the Define System Landscape step, enter the change control landscape and branch that were previously
defined for the system landscape (in transaction SLAN). The system uses these to calculate the transport
track.

You can also change the order of your system roles here.

 Recommendation

If you use multiple transport tracks, you must ensure that your quality gates are correctly assigned
to your system roles. To get the best use from your entire scenario, we recommend that you use
different system roles even if the systems have a similar purpose. For example, if your system role is
the development system, use the system roles “DEV1”, “DEV2”, and so on. For more information, see
Landscape View [page 503].

6. In the Preview Transport Track step, you can see the transport track that is generated by the system. You
can remove individual systems from the transport track by deselecting the checkbox. Depending on your
transport track, other systems may then be deselected automatically.

If inconsistencies are found in the transport landscape, the system displays the relevant messages at this
point.

Change Control Management

488 PUBLIC Quality Gate Management
7. In the Assign Retrofit Systems (Advanced) step, you define the relationship between the retrofit systems
and the source systems. If you first select the source system, the possible values for the retrofit system are
calculated dynamically and vice versa.
8. In the Assign cCTS Cluster (Advanced) step, you can view the transport track that is assigned to your
scenario.

The corresponding system information (system, client, and system role) is displayed in the lower section. If
you activate the central change and transport system infrastructure, the system searches for appropriate
default clusters and assigns them. The clusters are displayed in the Systems table. If the system does not
find appropriate clusters, it issues a message saying that no cluster can be found for all of the systems in
your transport track. In this case, you must assign the cluster to the system manually.

 Note

If a scenario includes transport requests, the cluster assignment cannot be changed.

If your system landscape changes, the cluster assignment is automatically recovered from historical
transport tracks and this assignment cannot be changed. You can assign new clusters only to newly
added systems.

For more information about system clusters, see System Cluster [page 403].
9. In the Assign Quality Gates to System Roles step, you specify which quality gate is to be passed for which
system. When you specified the branch and landscape in the previous step, each system was assigned to
a system role. By connecting system roles to quality gates, you define which quality gate has to be passed
before transports into the respective systems are allowed. The corresponding QGM phases are displayed
as they are related to the quality gates in the Phase column.

Select the Enable the Transport of Copies Import in Build Phase checkbox as required:
• If the quality gate assigned to the system role of the target system is passed, the system ignores the
Enable the Transport of Copies Import in Build Phase setting because both the transport request and
the transport of copies are imported in any case.
• If the quality gate assigned to the system role of the target system is not passed, you can import a
transport of copies provided that the project is in the “Build” phase, you have selected the Enable the
Transport of Copies Import in Build Phase checkbox, and the target system is in the “Test” phase. If any
of these conditions are not met, you cannot import a transport request or a transport of copies into the
target system.

 Note

This option is relevant only for systems that are assigned as the “Test” phase. It does not affect
systems in any other phase (such as “Build” or “Deploy”).

Select the Disable Transport Release in Scope Phase checkbox if you want to prevent users from releasing
transport requests when the scenario is in the scope phase. This checkbox is selected by default when you
set up a new scenario.
10. In the Confirm Data step, you can check that your data is correct. If it is, choose Finish to create the
scenario. Otherwise, choose Back to correct your data.

Change Control Management

Quality Gate Management PUBLIC 489
Results

Your scenario is now activated and ready for use in quality gate management.

Example

You have a four-tier system landscape that includes a development, quality, preproduction, and production
system. You have the following options:

• To put the preproduction system in the test phase, assign the Test to Deploy quality gate to the Production
System role.

• To put the preproduction system in the deploy phase, assign the Test to Deploy quality gate to the
Preproduction System role.

 Caution

You assign quality gates by entering them sequentially for each system. The sequence is based on the
dates of the quality gates, from the earliest date to the latest date.

5.2.1.1 Assigning Groups of Business Partners

Use

When you set up a QGM scenario, you can assign the business partner number of a group of users that you
have technically set up as an organizational unit, as the quality manager or the quality advisory board. Any
person assigned to the group (organizational unit) can then approve a quality gate. The details of the user who
passed the quality gate are logged in the system for later reference.

Note that if you enter a business partner number for an organizational unit, you cannot call up the details of
each individual user assigned to organizational unit in the Business Partner dialog box.

 Caution

According to the principle of dual control, the quality manager and the member of the quality advisory
board must not be the same person. If you use business partner groups (organizational units), the system
checks only whether the group number for the quality manager is identical to the group number for the
quality advisory board. It does not check the business partner numbers for the individuals assigned to the
organizational units.

Change Control Management

490 PUBLIC Quality Gate Management
Prerequisites

• You have created a group of the type “Organizational Unit” and all members of the group are assigned with
the relationship Is Employee of.
• Everyone in the group has the Quality Manager or Quality Advisory Board role.

Creating Organizational Units as Groups of Individual Business Partners

1. Enter the transaction code PPOCA_CRM (Change Organizational Model).
2. Enter and confirm the validity period.
3. Enter a name and a description for the organizational unit.
4. Select the new organizational unit in the Assignment Plan list and choose the Create icon.
5. In the Choose Relationship dialog box, select Incorporates / Position.
A new position is created.
6. In the details for the new position, rename the position, for example to QM for quality manager.
7. Select the new position in the Assignment Plan and choose the Assign icon.
8. In the Choose Relationship dialog box, choose Owner / Business Partner.
9. In the Business Partner dialog box search and select the business partner of the user that you want to
assign to the organizational unit.
10. To add additional business partners to the organizational unit, create additional new positions and assign
the business partners to them.
11. Save your settings.

To find out the business partner number of the newly created organization unit, you can do the following:

• In transaction PPOCA_CRM (Change Organizational Model), search for organizational unit by name or
description.
Then double-click on the search result to display the details of the organization unit, including the business
partner number, in the assignment plan table.
• Alternatively, you can also use transaction bp to check the relationships of a business partner of a user that
you have assigned to the organization unit. The business partner should be assigned to the organizational
unit with the relationship Is Employee of.

Assigning the Business Partner ID of an Organization as Quality Manager or

Quality Advisory Board

When you set up a scenario, you can you can select the business partner of a group, that is an organizational
unit that you have created in transaction PPOCA_CRM (Change Organizational Model) as the quality manager or
quality advisory board of the scenario when you are defining the header data of the scenario,

5.2.1.2 Disabling Segregation of Duties

When you set up your scenario, you can select the Disable Segregation of Duties checkbox in step 1 (Define
Header Data and Milestones) of the guided procedure. By selecting the checkbox, you can disable the

Change Control Management

Quality Gate Management PUBLIC 491
mandatory segregation of duties, which means you don’t have to enter two different business partners for
the Quality Manager (QM) and the Quality Advisory Board (QAB). Instead, the QM field and QAB field are
combined into one field. You enter one business partner representing both QM and QAB. After setting up the
scenario, the Q-Gate approval / rejection and urgent change approval / rejection can be done by one person.
You can change the Disable Segregation of Duties setting during resetting up the scenario with the help of a
change log.

5.2.1.3 Disabling Quality Gates

When you set up your scenario, you can select the Disable Quality Gate checkbox in step 1 (Define Header Data
and Milestones) of the guided procedure. By selecting the checkbox, you can disable the quality gate function
for your scenario, which has the following effects on your scenario:

• Quality gates will not be assigned to the system landscapes. A transport request import can only be
protected by the import lock of the system.
• Only the Deploy phase and the End of Deployment quality gate are available.
• Once the quality gate function is disabled, the scenario can only have one cycle.
• Once you have set up the new scenario, you cannot change the setting of the Disable Quality Gate
checkbox anymore.

5.2.2 Checking the Quality Gate Configuration

Context

Before you work with quality gates, we recommend ensuring that the configuration check works correctly.

Procedure

1. You can check the configuration of the quality gate configuration in the Quality Gate Management Overview
or in the Administration Cockpit:

• In the Quality Gate Management Overview, scenario overview, select your QGM scenario, open the
Actions dropdown list, and choose Configuration Check.
• In the Administration Cockpit on the Task Lists tab, choose QGM Scenarios. Then select the task list
your QGM scenario and then choose Configuration Check.

The system checks that the following areas are configured correctly for your scenario:

• Global configuration

Change Control Management

492 PUBLIC Quality Gate Management
 • Systems overview
• QGM scenario configuration
2. Expand each node to check the configuration results. Each node contains a list of items that must all be
green. If there is an error, open the corresponding long text and follow the instructions to correct it.

Results

Your scenario is configured correctly and is ready for use with quality gate management.

5.2.3 Change Cycles

Use

The lifecycle of a QGM scenario is divided into change cycles. When a change cycle comes to an end, you can
start a new one so that you can continue to use the scenario for further software changes.

Features

All software corrections must be tested and implemented within one change cycle. At the end of the cycle,
corrections are imported into the production system. Open changes, open transport requests, and transport
requests that have not been imported into the production systems are moved to the new change cycle. The
switch from an old change cycle to a new one is safeguarded by the Deploy to Scope quality gate.

More Information

Creating and Editing a Cycle [page 493]

5.2.3.1 Creating and Editing Cycles

Use

When a cycle comes to an end, you can start a new one so that the same QGM scenario can continue to be
used.

Change Control Management

Quality Gate Management PUBLIC 493
Procedure

To work with cycles, proceed as follows:

Creating a Cycle

1. On the Quality Gate Management Overview screen, select your scenario and choose Actions Set Up
Cycle .
The cycle dialog box appears in which you can create or delete cycles.
2. Choose the Create Cycle pushbutton and enter a name for the cycle.
3. Enter dates for each of the quality gates and milestones.

 Note

For the new cycle, the first milestone name is Deploy to Scope and not Start of Scope. The date for the
Deploy to Scope milestone is set to the End of Deployment date from the previous cycle.

4. If necessary, choose Add Milestone to add milestone dates.

5. You can also upload templates or files for a milestone that is defined as a quality gate.
6. When you have finished, choose Save to create the cycle.

Deleting a Cycle

1. To delete a cycle, choose Actions Set up Cycle to open the cycle dialog box .
2. Select the cycle that you want to delete and choose Delete Cycle.
3. Confirm that you want to delete the cycle.
The cycle is deleted and is no longer displayed in the list.

 Note

You cannot delete a cycle if its status is Active.

5.2.3.2 Switching a Cycle

When a cycle ends, you can close it and start a new one by successfully passing the Deploy to Scope quality
gate.

Prerequisites

You have passed all of the quality gates for the active cycle before the Deploy to Scope quality gate.

Change Control Management

494 PUBLIC Quality Gate Management
Procedure

To switch a cycle, proceed as follows:

1. Select your QGM scenario and open the Quality Gate dialog box, for example, by clicking the quality gate in
the calendar view.
2. Select the Deploy to Scope quality gate. The quality gate must be approved by the Quality Manager and the
Quality Advisory Board member before the overall status is set to “Passed”.
3. After the quality gate has been passed by both, choose OK.
The Open Issues dialog box warns you about:
• Open changes
• Open transport requests
• Transport requests that have not been imported to production systems
4. To start a new change cycle and move the open issues to the new change cycle, choose Continue.
5. Set the overall status to Passed and choose OK.

Result

The Deploy to Scope quality gate has been passed and your scenario has been switched to the next cycle.

Related Information

Handling Import Jobs During Cycle Switch [page 336]

Working with Quality Gates [page 501]
Creating and Editing Cycles [page 493]

5.2.4 Changing the CTS Status Switch

Prerequisites

You have specified that the CTS project assignment is mandatory for your managed systems in the central SAP
Solution Manager system or in the local managed system.

Context

CTS status switches are used to control transport operations for a specific QGM scenario, such as creating,
exporting, or importing transport requests. The switches are closed in QGM and are opened automatically

Change Control Management

Quality Gate Management PUBLIC 495
only for operations that are triggered from QGM. After the operation has been completed, the switches are
closed automatically again. This process ensures that users can change their system landscape only using the
standard change control processes and tools.

CTS status switches are activated when a CTS project is generated for a QGM scenario with the following
result:

• A transport request cannot be created under the CTS project using the development workbench.
• A transport request that is assigned to the CTS project cannot be released.
• A transport request that is assigned to the CTS project cannot be imported into any system in the
landscape that lies on the transport track.

 Caution

Use this procedure to change the CTS status switch only in exceptional cases, for example, if you want to
bypass change control. This procedure is not intended to be used as a regular operation.

Procedure

1. In the scenario overview, find the QGM scenario for which you want to change the CTS status switch and
choose Actions... Change CTS Status Switch .
2. Find the switch that you want to change and click the Edit button.
3. Set the relevant status for the switch.

Results

The icon in the Status column changes from a red cross to a green checkmark to indicate that the switch is now
open. Choose Display Application Log in the dialog to check recent logs of the CTS status switch changes that
were made here.

 Note

If you want to use SAP Solution Manager to control the transport activities of your landscape, we
recommend that you close the CTS status switch for all the systems and the clients of the landscape.
In addition, before transport activities are triggered from SAP Solution Manager, the corresponding CTS
project status switches will open beforehand and close afterwards automatically.

To track all the operations of the CTS status switches, in the application log transaction code SLG1, search
using the following criteria:

• For the Object enter /TMWFLOW/CMSCV.

• For the Subobject enter DRPS.
• For the External ID enter your task list ID.
• For Job Creation:
• If the action is triggered in the dialog, choose Dialog.

Change Control Management

496 PUBLIC Quality Gate Management
 • If the action is triggered in the background via transport activities, choose In batch mode.

5.2.5 Application Log

Use

The application log documents business and technical information that is relevant for processing a change
document or a change cycle.

Features

• Displays various activities, such as creation and release of transport requests, and supports navigation to
the related detail information
• Displays the status for activities, for example, that a transport request has been created
• Display activity type, such as program, job or transaction
• Displays who triggered the activity, for example, a user, transaction, or program
• Display start and end of an activity (date and time)
• Trigger of the activity, such as a task list or change document
• Integrates messages from the task list

5.2.6 Change Log

Context

The system logs each change performed within a scenario. These changes can include setting the status of a
quality gate, setting an urgent change status, and uploading a document.

Procedure

1. To view the change log, choose Actions Display Change Log for your scenario from the overview
screen.

A window appears containing all the logged system information. The Action column contains a list of all
changes that were made to the quality gates, along with detailed data about each change.

Change Control Management

Quality Gate Management PUBLIC 497
2. Optional: If you want to export the information, choose Export Export to Microsoft Excel and save
the file locally.

5.2.7 Using the Search Function

On the quality gate management overview, you can search for scenarios or changes by entering a keyword such
as the transport request number or the name of a business partner.

Prerequisites

In SAP Solution Manager Configuration (transaction SOLMAN_SETUP) scenario Quality Gate Management, step
Configure Embedded Search, you have completed the following activities:

• You have connected the embedded search using TREX or SAP HANA.
• You have created the corresponding search connector.

For more information about these steps, see the on-screen help in SAP Solution Manager Configuration.

Features

The search returns a list of all changes that meet your search criteria. By clicking the change ID number, you
can navigate directly to the relevant change and any associated transport requests.

The search takes the following information into account:

• QGM scenario name

• Change control landscape name
• Branch name
• Cycle name
• Change object ID
• Change transaction type
• Change description
• Change status description
• Change created by (user name)
• Change manager (full user name)
• Transport request ID
• Transport request description
• Transport request owner (user name)

 Tip

You can display hidden columns in the search results table with the settings dialog.

Change Control Management

498 PUBLIC Quality Gate Management
Related Information

Changes [page 505]

Transports [page 518]

5.3 QGM Data for a Scenario

Use

For each scenario, you have the following options:

• You can click the scenario link to access the screen for changes and transport requests.
• You can select a scenario to display the details in the lower part of the screen in either the Calendar View or
Landscape View.

 Note

You can also select more than one scenario. When you do so, the phases and quality gates for all of the
selected scenarios are displayed on the Calendar View tab page. However, the Landscape View tab page
displays the system landscape graphic for one scenario only.

Features

You can display or change the data in the following areas in quality gate management:

• You can create and manage changes in the Changes table (see Changes [page 505]).
• You can create and manage transports in the Transport Requests table (see Transports [page 518]).
• You can obtain an overview of the quality gate data maintained for your scenario (see Quality Gates [page
501]).
• You can display and edit your quality gates and phases graphically (see Calendar View [page 500]).
• You can obtain an overview of the risks that have arisen in your transport landscape during transport (see
Risks [page 526]).
• You can view the various systems used in your system landscape together with the transport paths (see
Landscape View [page 503]).
• You can track objects in transport requests, and report conflicts in scenarios when an object that is saved
in two or more transport requests is released, reassigned, or imported (see Downgrade Protection [page
360]).

Change Control Management

Quality Gate Management PUBLIC 499
5.3.1 Calendar View

The Calendar View provides a graphical display of each scenario with an overview of all the deadlines, quality
gates, and milestones.

Prerequisites

You have created and maintained the scenarios in Quality Gate Management.

Context

In the calendar view, the quality gates and phases of one or more selected scenarios are displayed linearly. You
can see up to 10 scenarios at a time.

The phases and quality gates have the following color coding:

• Phases that have been passed successfully are green, the current phase is orange, and phases that are yet
to be completed are shown in gray.
• Similarly, quality gates that have been passed are shown as green icons, quality gates that are in process
are yellow, and quality gates that are still initial are gray. Any quality gates that are overdue are shown as
red icons.

In addition, you can identify quality gates by different quality gates icons.

Procedure

• Navigate to the previous or next page (if you have selected more than 10 scenarios from the overview
table)
• Navigate to the start or end date
• Navigate to the previous or following week
• Navigate to the previous or following day
• Zoom in or out to change the calendar view
• Open the IT calendar
• Mouse over a phase for more information
• Mouse over a quality gate (diamond icon) or milestone (star icon) for more information
• Click a quality gate to open the quality gate dialog box

Related Information

Change Control Management

500 PUBLIC Quality Gate Management
Setting Up Quality Gates and Assigning Phases [page 487]
Working with Quality Gates [page 501]
Opening the IT Calendar [page 266]

5.3.1.1 Quality Gates

Use

For each of the scenarios on the scenario overview screen, you can display details about a specific quality
gate by hovering the mouse over the icon in either the calendar view or the landscape view. From the calendar
view, you can also access the Quality Gate dialog box, where you can set the status for a quality gate, enter
comments, and upload or download documents.

Features

The Quality Gate dialog box provides the following functions:

• You can view the log of status changes.

• You can upload and download supporting documents for the quality gate (see also Creating and Editing
Cycles [page 493]).
• You can change the status of a quality gate.

5.3.1.1.1 Working with Quality Gates

Prerequisites

You have defined the quality gates that you want to manage with quality gate management. For more
information, see Setting Up Quality Gates and Assigning Phases [page 487].

Procedure

To work with quality gates, proceed as follows:

1. In the scenario overview table, select the scenario for which you want to display or change quality gate
data.
2. Open the quality gate dialog box in one of the following ways:
• On the Calendar View tab page, click the colored icon in the timeline.
• To open the active quality gate, click the date in the Next Gate column in the overview table.

Change Control Management

Quality Gate Management PUBLIC 501
3. Change the value for your role (either QM or QAB).
4. Optional: Enter any supporting information regarding your decision in the comments box and upload
supporting documents. This information is visible to anyone who can view the quality gate status.
5. Optional: Choose the Status Change Log pushbutton to view individual changes.
6. Save your settings by choosing the OK pushbutton.

Quality Gate Statuses

When you change the status of a quality gate, the fields that are ready for input change dynamically. Both the
quality manager (QM) and the member of the quality advisory board (QAB) must set the quality gate to Passed
before the process can continue.

The following statuses can be set by the quality manager and the quality advisory board member for each
quality gate:

Status Meaning

Initial No status has been set yet.

Partially Passed Some minor points are still open in this phase but they are
not expected to delay the change cycle or release.

Passed The process can continue to the next phase.

Not Passed The process cannot continue to the next phase and the en-
suing problems must be resolved first.

The system sets the overall status for the quality gate based on the statuses set by the quality manager and the
member of the quality advisory board. The following matrix shows the various combinations of status values
that the persons responsible can set, and the result calculated by the system.

Q-Gate Statuses Set by System

5.3.1.1.1.1 Resetting Quality Gates

Use

The quality manager and quality advisory board member can reset a quality gate to the Initial status by
choosing the Reset status if required. The previous status is logged in the status change log. If the quality
gate that has been reset has been used to switch phases (for example, Deploy to Scope), QGM reverts to the
previous phase.

Change Control Management

502 PUBLIC Quality Gate Management
  Note

Only the last quality gate with the status Passed can be reset.

Procedure

To reset a quality gate, proceed as follows:

1. On the Calendar View tab page, select the quality gate that you want to reset.
2. Change the status of the quality gate from Passed to Reset.
3. Choose the OK pushbutton.

After the first processor has reset the status, the quality gate is set to In Process. This means that imports into
systems after this quality gate are no longer possible. Once the second processor has also reset the status, it is
initial.

Result

After both business partners have reset the quality gate, its status is set to Initial.

 Note

If the quality gate is a standard quality gate, the phase is rolled back to the previous phase.

5.3.2 Landscape View

The Landscape View gives an overview of the quality gates for a scenario together with the systems and the
transport paths. You can also see the status of your software distribution.

Prerequisites

To use multiple system roles within the same track, your quality gates must be correctly assigned to system
roles. Otherwise, transport functions may be affected.

 Recommendation

To ensure that the quality gates and phase control function smoothly, use different system roles even if the
systems have a similar function. For example, if you have multiple development systems in your transport
track, use the system roles “DEV1”, “DEV2”, and so on.

Change Control Management

Quality Gate Management PUBLIC 503
Features

Drag the transport landscape to navigate around it, and use the mouse wheel to zoom in and out. To see your
landscape in more detail, switch to full-screen mode.

Use the search function to find specific systems in your landscape. The advanced search mode filters for
systems, quality gates, and phases, and suggests keywords.

Quality Gate and Phase Information

Above the system landscape, the user-defined quality gates and phases represent the scenario progress.
Tooltips give detailed information, such as icon, name, planned date, and status.

System Information
Each system in your transport landscape is represented by a box with the following areas:

• Legend Area
The legend area indicates the system type, the system ID, and the cluster name of the central change and
transport system (if you have enabled it). By clicking anywhere in this area, you open a context menu to
manage transport requests and enable or disable transport locks.
A quality gate icon indicates what quality gate is assigned to the system role of this system and its current
status. A tooltip over the quality gate icon gives information, such as name of the quality gate, planned
date, and status.
• Info Area
The info area contains the system role, the transport status, and the downgrade protection (DGP) conflict
status. Click an icon to see further details, for example, about missing transports, risks, or downgrade
protection checks.

Related Information

Enabling and Disabling Locks for the Import, Creation, or Export of Transport Requests [page 504]
Transport of Changes [page 510]

5.3.2.1 Enabling and Disabling Locks for the Import,

Creation, or Export of Transport Requests

Use

By default, you can import transport requests into a system once the corresponding quality gate has been
passed. By enabling the import lock, you can prevent transport requests from being imported into a specific
system. You can remove the import lock when it is no longer needed.

For development systems, you can also enable a transport creation lock or an export lock. If the transport
creation system is enabled, the creation of transport requests is blocked. If the export lock is enabled, no
transports can be exported from the system. You can use this feature, for example, during a cutover when you

Change Control Management

504 PUBLIC Quality Gate Management
are switching to a new development system. In this case, you can lock the old development system for the
creation and export of transport requests when you start using the new development system.

 Note

This feature can be used only by IT operators and administrators.

Procedure

You can enable a transport creation lock or an export lock for development systems. For follow-on systems, you
can enable an import lock. To enable a lock for a system, proceed as follows:

1. Select a scenario and choose the Landscape View tab page.

2. Click the legend area for the system for which you want to enable the lock.
3. In the menu, choose the option to enable the required lock.

In the Landscape View, a system for which a lock is enabled is marked with a lock icon.

To remove an import, creation, or export lock for a system, proceed as follows:

1. Select a scenario and choose the Landscape View tab page.

2. Click the legend area for the system for which the lock is enabled.
3. In the menu, choose the option to disable the lock.

5.3.3 Changes

The Changes area contains information about all of the software changes to be made as part of a QGM
scenario.

Features

By default, the Changes area shows the following columns. You can show or hide columns with Open Settings
Dialog.

To filter the data in any given column, select the column and choose User-Defined Filter.

Column Meaning

Change The unique ID number of the change

Description The description of the change

Change Control Management

Quality Gate Management PUBLIC 505
Column Meaning

Status Changes can have one of the following statuses:

• Withdrawn
• Open
• Completed

Urgent changes can also have the statuses To Be Approved

and Rejected.

Type The type of change involved (for example, a change or ur-

gent change)

Owner The owner of the change

Transport The number of transport requests within a change

Cycle Name The name of the cycle to which the changes belong

Risk The number of risks identified within the changed

Transport-Related Checks The most severe issue detected within the change

Actions... A dropdown list offering further actions for the change

Activities

In the Changes area, you can carry out the following activities:

• Create and change details of a change, as well as reassign a change

• Delete empty changes. To delete a change, find the row that contains the change you want to delete and
choose Actions... Delete Change .
• Set the status of a change
• Transport actions, such as:
• Create transport requests for changes
• Release transport requests
• Import transport requests and transports of copies
• Assign transport requests from changes
• Decouple transport requests from changes

 Note

If you release an empty transport request, the request is deleted automatically.

• Create transports of copies

• Perform a downgrade check

Change Control Management

506 PUBLIC Quality Gate Management
Related Information

Creating Changes [page 507]

Maintaining Changes [page 508]
Setting the Status of a Change [page 509]
Creating and Releasing Transport Requests [page 511]
Assigning Transport Requests [page 513]
Decoupling Transport Requests in Quality Gate Management [page 525]
Creating Transports of Copies [page 521]
Downgrade Protection [page 360]

5.3.3.1 Creating Changes

Use

You can create as many changes as you require in each QGM scenario. Each change contains one or more
transport requests, which are used to transport changed software objects as listed in back-end transaction
SE09 in the managed system.

You can also create urgent changes. An urgent change is mainly used for fast implementation, for example, if
you want to fix an error in existing functionality. The change is transported into the production system faster
than a normal change.

Procedure

To create a change, proceed as follows:

1. From the scenario overview, navigate to the changes and transports screen by choosing the QGM scenario
link.
2. Choose the Create Change or Create Urgent Change pushbutton.
3. Enter the description of the change.
4. Choose OK.

The new change is displayed in the list.

 Note

The person creating the change is automatically the owner of the change. However, you can change the
owner if necessary. For more information, see Maintaining Changes [page 508].

Change Control Management

Quality Gate Management PUBLIC 507
5.3.3.2 Maintaining Changes

Use

For each change, you have the following options:

• You can change the description and the owner.

• You can reassign a change with all its transport requests to another scenario.
• You can delete an empty change.

Procedure

Maintaining Details of a Change

You can change the description and the owner of a change, provided you are authorized to do so. To modify a
change, proceed as follows:

1. Click the change number in the Change column.

2. In the dialog box that appears, change the description and/or the owner of the change.
3. Choose OK to save the change data.

Reassigning a Change

You can reassign a change to another QGM scenario. However, the change must have the status Open.
Reassign changes to other scenarios with caution because doing so can result in dependency issues in the
source and target scenarios.

You can reassign a change only to a QGM scenario that meets the following conditions:

• The scenario contains all development systems of the transport requests for the selected source change.
• The scenario is not the source scenario itself.
• If the source scenario is enabled for cCTS, the target scenario must also be enabled for cCTS. If the source
scenario is disabled for cCTS, the target scenario must also be disabled for cCTS.
• The reassignment of released transport requests in the change is only possible if the source and target
scenario are enabled for cCTS, and the target landscape and its cluster assignment correspond to the
source scenario.

To reassign a change to another scenario, proceed as follows:

1. Find the row containing the change you want to reassign and choose Actions... Reassign Change .
2. In the dialog box that appears, select the scenario to which you want to reassign the change. If you select a
scenario that does not meet the requirements for reassignment, the system displays an error message.
3. Choose OK to reassign the change.

Deleting a Change

To delete an empty change that has no transport requests assigned to it, find the row containing the change
you want to delete and choose Actions... Delete Change .

Change Control Management

508 PUBLIC Quality Gate Management
5.3.3.3 Setting the Status of a Change

Context

Statuses for Normal Changes

When a normal change is created, it is automatically assigned the status Open. The change manager can set
the status of the normal change to either Completed or Withdrawn as required.

The following change statuses are available for normal changes:

Status Description

Open The normal change is in its initial status.

Completed The change has been carried out and is finished. This means
that this change will not be transferred to a new cycle during
a cycle switch. Changes can be completed only if all of the
transport requests have been imported successfully into a
production system.

Withdrawn If this status is set, the change is withdrawn. Changes that

contain non-empty transport requests cannot be withdrawn.

Statuses for Urgent Changes

In additional to the change statuses, urgent changes are submitted to an approval processes and so also have
an approval status. When an urgent change is created, it is automatically assigned the approval status To Be
Approved. Before the urgent change can be set to Open, it must be approved by both the quality manager and a
member of the quality advisory board. If either of these business partners reject the change, it is automatically
assigned the status Rejected.

The following approval statuses are available for urgent changes:

Status Description

To Be Approved The urgent change is in its initial status.

Approved The quality manager and the quality advisory board member
must approve an urgent change to change the overall status
to Approved. The QM and QAB can upload documents if
required.

Rejected If either the quality manager or the quality advisory board

member reject an urgent change, it is automatically set to
Rejected.

Change Control Management

Quality Gate Management PUBLIC 509
If both the quality manager and the quality advisory board member approve the urgent change, it is
automatically assigned the status Open. From there, the change manager can change the status to the
following values:

Status Description

Completed The change has been carried out and is finished. This means
that this change will not be transferred to a new cycle during
a cycle switch. Changes can be completed only if all of the
transport requests have been imported successfully into a
production system.

Withdrawn If you set this status, the change is withdrawn. Changes that
contain non-empty transport requests cannot be withdrawn.

Procedure

1. Click the change number in the Change column.

2. In the dialog box that appears, select the new status from the dropdown box for the change status or the
approval status.
3. Optional: Enter any supporting information regarding your decision in the comments box and upload
supporting documents. This information is visible to anyone who can view the change.

5.3.3.4 Transport of Changes

Use

Changes in one system must be imported into the next system in your system landscape before they can be
used productively.

 Note

You can activate the cross-system object lock for objects in transport requests associated with QGM
scenarios. For more information, see Cross-System Object Lock [page 363].

Prerequisites

The corresponding quality gate must have been passed before you can import a change into the next system.

Change Control Management

510 PUBLIC Quality Gate Management
  Note

For urgent changes, the quality gates do not have to be passed so that the transport request can be
imported into the production system as quickly as possible. However, the status of the urgent change must
be Approved.

Features

The following functions are available:

• Creating and Releasing Transport Requests [page 511]

• Creating and Distributing Transports of Copies [page 521]
• Importing Changes [page 514]
• Decoupling Transport Requests [page 525]

5.3.3.4.1 Creating and Releasing Transport Requests

In QGM, you can create and release transport requests in the WebClient UI. Transport requests created in the
managed system should be assigned to a change document.

 Caution

Because transport actions performed out of Solution Manager cannot be identified by the application log
as belonging to a scenario, users should not create, maintain or release transport requests in the Transport
Organizer (transaction SE09) of the managed system.

If you want to allow locally creating transport requests in a managed system, we recommend to configure
change document assignment for the system.

Creating Transport Requests

Prerequisite: You have created one or more changes.

1. Within your scenario, on the changes and transports screen, select a change and choose Actions...
Create Transport Requests .
A dialog box appears.
2. Specify whether you want to create a workbench request, a Customizing request, or both.
3. Select the source system.
4. If required, adjust the description, the owner, and assign additional users (developers).

 Recommendation

In the description, do not overwrite the default scenario name and change number.

Change Control Management

Quality Gate Management PUBLIC 511
5. Choose OK.
The transport request is created and listed in the transport requests table.

Releasing Transport Requests

You can release transport requests at transport level, change level, or scenario level. If you select a change, all
transport requests within this change are released. At scenario level, all transport requests within all changes
are released.

If you choose to release transport requests from change or scenario level, you can select specific transport
requests in the Release Transport Requests dialog box. By default, all transport requests associated with a
change are selected.

If your scenario is cCTS-enabled, you cannot release individual transport requests. Instead, you must release
the transport requests collectively at change or scenario level.

1. Within your scenario, on the changes and transports screen, select the transport requests that you want to
release:
• To release transport requests associated with all changes of the scenario, in the header area, choose
Scenario Transport Release Transport Requests .
• To release transport requests associated with a specific change, select the change and in the changes
table, choose Actions... Release Transport Requests .
• To release a specific transport request, select the transport request and and in the transports table,
choose Actions... Release Transport Request .
2. In the dialog box, select the transport requests that you want to release and choose Release.

You can view the current status (released or changeable) of all transports associated with the change in the
Status column of the transport requests table.

Assigning Change Documents to Create Transport Requests in Managed

Systems

In QGM, you can assign change documents to create transport requests locally in a managed ABAP
development system.

Related Information

Creating Changes [page 507]

Assigning a Change Document to Transport Requests Created Outside SAP Solution Manager [page 394]

Change Control Management

512 PUBLIC Quality Gate Management
5.3.3.4.2 Assigning Transport Requests

Use

You can assign a transport request to a change in either the same QGM scenario or in another scenario.

Procedure

Assigning Decoupled and Freely Created Transport Requests

Prerequisites

To assign released transport requests, you have activated the central Change and Transport System (central
CTS) for your project. Otherwise, you can assign only changeable transport requests.

Procedure

To assign a transport request to a change, proceed as follows:

1. Select the change from the table and choose Actions... Assign Transport Requests .
2. In the dialog box, select a source system from the dropdown list.
3. Select one or more transport requests and choose the Assign pushbutton.

 Note

You can also assign transport requests to changes by choosing Scenario Transport Assign Transport
Requests from the header area. In this case, you must select the target change as well as the source
system.

 Note

When the transport request is assigned to the document, the description of the transport request can be
updated automatically by the system.

The description can be set up by BAdI: Change Description after Assign Transport Request to Change
Document (TMWFLOW/ASSIGN_TRANS_DESC_UPD).

For updating the description of the transport request in the managed system, use SAP Note 2809667 .

Assigning External Transport Requests

Prerequisites

You have activated the central Change and Transport System (central CTS) for your QGM scenario.

Procedure

1. In the development system of the landscape from which you want to import a transport request, open the
transport management system (transaction STMS) and choose Import Overview.
2. Double-click the development system in the list.

Change Control Management

Quality Gate Management PUBLIC 513
3. Choose Extras Other Requests Add .
4. In the dialog box, enter the transport request ID and the target client of the system to which you want to
import.
5. Select the transport request and choose Request Import .
6. In the dialog box, confirm the import to the development system.
The transport request is now available in the import buffer of the quality system in the new target system
landscape.
7. Select your change on the QGM user interface.
8. Choose Actions... Assign Transport Requests to display the dialog box for assigning transport
requests.
9. In the dialog box, select a source system from the dropdown list.
10. Select the transport request that you just imported to the development system and choose the Assign
pushbutton.

 Note

You can assign only original transport requests as external requests. Assigning transports of copies is
not supported.

5.3.3.4.3 Importing Changes

Use

You can import changes into a target system in the form of transport requests or transports of copies. However,
doing so means that the sequence in which the transport requests are imported may be altered. In other
words, the sequence in which transport requests are imported may differ from the sequence in which they
were exported. Because the import into a system controls the order of the content in the buffers of the
follow-on systems, the transport requests are imported in the changed sequence into all follow-on systems,
including the production system.

You can use the Start Import function for all systems in a transport track. This means that in the dialog box for
importing changes, you can select all of the target systems in the track and not just the consolidation system.

 Recommendation

Always import a scenario in its entirety.

Procedure

To import changes into a follow-on system, proceed as follows:

1. Choose one of the following options to import the transport requests containing your changes:
• To import the transport requests for a particular change, choose Actions... Import Transport
Requests .

Change Control Management

514 PUBLIC Quality Gate Management
 • To import the transport requests for an entire scenario, choose Scenario Transport Import
Transport Requests from the header area.
The dialog box that appears lists all transports that have not been imported into the corresponding target
systems.

 Note

When you import a change, you must import all of the transport requests that are associated with the
change. You cannot select individual transport requests are import those requests only.

2. Choose one of the following options:

• If you want to import a transport request, specify the source and target systems.
• If you want to import transports of copies, select the Transport of Copy Only checkbox.

 Note

If you have activated the central Change and Transport System (cCTS) for your scenario, you can
select a source and target cluster. If the target of the transport of copies is a target group, the
group will automatically be resolved to its various systems. As a result, the transport of copies is
listed several times, that is, once for each target system.

For central CTS-enabled cycles, the import function supports “uneven” cluster tracks, that is, not
all system clusters in the cluster track contain the same number of systems with the same roles.

3. Select the transport requests or transports of copies that you want to import.
4. On the Date tab page, specify the time when you want the transport requests or transports of copies to be
imported into the target systems.
5. On the Execution tab page, specify whether you want the import to take place synchronously or
asynchronously.
6. On the Options tab page, set the required import options.
7. On the Systems tab page (for cCTS projects only), specify to which target systems in the target cluster you
want to import the transport requests or transports of copies.
8. Confirm with OK.

Result

The transport requests or transports of copies for the change you have selected are imported into the follow-on
systems.

If the active import feedback job SM: AI_CRM_CM_COM_IMPORT_FEEDBACK has been set up, the following
happens:

• Fully imported transport requests are removed from the STMS import queue after the import is
successfully done.
• In the Transport Requests area, the Import Status column of the transport request associated with the
change is updated.

For more information about the active import feedback job, see the activity documentation under SAP
Solution Manager Configuration Change Request Management Prepare System Schedule Background
Jobs .

Change Control Management

Quality Gate Management PUBLIC 515
  Note

You need to install the latest SAP Solution Tools Plug-in (the ST-PI) onto the managed systems.

Related Information

Central Change and Transport System [page 400]

System Cluster [page 403]

5.3.3.4.4 Transporting to a Sandbox System

You can create a transport of copies and release it to a sandbox system where you can try out client-specific
Customizing settings.

Prerequisites

• An import lock is not set in the sandbox system.

• The relevant quality gates have been passed.

Context

Sandbox systems have the role type “O” (target system) and are part of the transport track that starts with the
source system, or they have the role type “S” (single system) and are not included in the transport track.

Procedure

1. In the table of changes, choose Actions... Transport to Sandbox System .

2. Select the source and target systems from the dropdown boxes.
3. If the change document has several transport requests, select which transport requests are to be
transported.
4. Click OK.

Change Control Management

516 PUBLIC Quality Gate Management
Related Information

5.3.3.5 Task Lists in Quality Gate Management

Use

When you set up a QGM scenario, the system automatically creates a task list, which is used to handle all
transport-related operations for QGM. The task list is part of the scheduling tool. It is used by IT operators and
system administrators.

The QGM task lists are similar to the task lists for Change Request Management but have the following
differences:

• The Status and Phase pushbuttons are not available because you perform the related tasks on the QGM
user interface.
• All tasks in the task list are unlocked by default.
• The task list contains only tasks that are relevant for QGM. That is, the scope is restricted.

Features

• You can call up the QGM task list using transaction SCMA.
• For each scenario, the corresponding task list is displayed in the Task List column (hidden by default).
• In the QGM task lists, you can only display tasks. If you want to execute the tasks, you do so from the QGM
user interface.
• You can lock a task in the task list to prevent the action from being carried out on the QGM user interface.
• You can display the tasks performed within the task list application log in QGM.

More Information

Task Lists Tab for Quality Gate Management [page 537]

Scheduling Tool [page 294]

Task List [page 53]

Change Control Management

Quality Gate Management PUBLIC 517
5.3.4 Transports

Use

The Transport Requests area contains information about all of the transport requests in your QGM scenario.

 Note

You can activate the cross-system object lock for objects in transport requests to prevent changes from
being made to an object in another transport request.

Features

By default, the Transport Requests area contains the following columns:

Column Meaning

Transport ID of the transport request

Description Textual description of the transport request

Owner Name of the request owner

Status Status of the transport request (changeable or released)

Transport of Copy Number of copies of the transport request. Choose the link
to display all transports of copies that have been generated,
including detailed data for the transport requests involved.

Type Type of transport request (workbench or Customizing)

Critical Objects Status and number of critical objects in the transport re-
quest

Import Status Status of the latest import. Choose the link to see details.

Actions... A dropdown list that enables you to carry out further actions
for the requests

You can use the following functions in the Transport Requests area:

• Open the transport organizer (transaction SE09) in the back end by choosing the link in the Transport
column.
• Create transports of copies
• Change the description and the owner of the transport request.
• Assign further developers to the transport request.
• Release an open transport request. Once you have released a transport request, it is locked in the Status
column and can no longer be changed.

Change Control Management

518 PUBLIC Quality Gate Management
• Separate a changeable transport request from its change. These transport requests are not controlled by
QGM anymore.
• Delete empty transport requests
• Display critical objects, and approve or reject their export
• Display the latest import status for the transport request, and the tranport log

 Note

The transport logs displayed when you choose the Import Status icon are collected via the
import feedback mechanism. If you want to remove the obsolete data here, check the parameter
CM_IMPORT_FEEDBACK_RETENTION_DAY in SAP Note 1483276 . You can select the transport ID in the
transport log popup to remotely display the transport logs on the respective managed systems or in the
SAP Cloud Transport Management service.

Related Information

Transport of Changes [page 510]

Cross-System Object Lock [page 363]
Creating Transports of Copies [page 521]
Working with Transport Requests [page 519]
Decoupling Transport Requests in Quality Gate Management [page 525]
Processing Critical Objects [page 524]
Dual Landscape Synchronization (Retrofit) [page 338]

5.3.4.1 Working with Transport Requests

Use

The following functions are available when working with transport requests:

• Maintain detailed information for a transport request

• Create tasks for developers in a transport request
• Release a transport request
• Delete an empty transport request
• Assign a transport request
• Decouple a transport request

Change Control Management

Quality Gate Management PUBLIC 519
Prerequisites

You have created a transport request based on a change. For more information, see Creating and Releasing
Transport Requests [page 511].

Procedure

Maintaining a Transport Request

If you want to change the description or the owner of the transport request, choose Actions... Maintain
Transport Request Detail . You can then change the data as required.

Creating a Task in a Transport Request

If you want to create tasks for developers within a transport request, choose Actions... Maintain Transport
Request Task . The dialog box that appears shows the existing tasks in the upper table, and allows you to
enter the names of the task owners in the lower table.

Releasing a Transport Request

1. Find the transport request with the status Changeable from the list and choose Actions... Release
Transport Request .
2. Select the transport requests that you want to release.
3. Specify when you want the transport requests to be released. You can choose to release them immediately
or you can enter a date on which the release is to take place.
4. Click Release to release the transport requests or confirm the date on which the release is to take place.

 Note

If your scenario is cCTS-enabled, you cannot release transport requests from the transport request table. In
this case, all of the transport requests must be released together.

If your scenario is not cCTS-enabled, you can release transport requests from the transport request table
and select individual transport requests for release at change or scenario level.

Deleting a Transport Request

1. Select a specific transport request with the status Changeable from the list and choose Actions...
Delete Transport Request .
2. Confirm that you want to delete the selected transport request.

 Note

You can only delete empty transport requests.

Assigning a Transport Request

See Assigning a Transport Request [page 513].

Decoupling a Transport Request

Change Control Management

520 PUBLIC Quality Gate Management
See Decoupling a Transport Request [page 525].

5.3.4.2 Creating Transports of Copies

Use

If you want to test your software changes in one system without having them transported automatically to
other systems in your transport track, you can create a transport of copies. Transports of copies are not
transported across your system landscape, and so are not imported into your production system. This means
that you can use them to test your developments.

 Note

Transports of copies can be created for a non-ABAP system only if SAP Note 1293449 has been applied
in your system.

 Recommendation

Use transports of copies to transport changes to the quality assurance system. Doing so has the following
advantages:

• Repository objects are locked for as long as possible in the development system.
• The number of transports in production is reduced. which means that the required import time is
reduced and any potential downgrade risks are minimized.
• Transports of copies are periodically imported into the quality assurance system but do not follow the
transport routes into follow-on systems.
• Only the original transports can reach production.

Prerequisites

All tasks have been released in the original transport request.

Procedure

To create a transport of copies, proceed as follows:

1. In the Transport Requests screen area, choose Actions... Create Transport of Copy .
2. In the dialog box that appears, select one or more transport requests and choose the Create pushbutton.
The system displays a message to confirm that the transport request has been created.

If the transports of copies have been tested successfully, you can release the original transports, which can
then be transported across your system landscape.

Change Control Management

Quality Gate Management PUBLIC 521
More Information

For more information about how to create transports of copies in SAP Solution Manager, see Creating
Transports of Copies [page 123].

For information about testing your developments in a sandbox system using transports of copies, see
Transporting to a Sandbox System [page 516].

5.3.4.3 Assigning a Change Document to Transport

Requests Created Outside SAP Solution Manager

In Change Request Management and Quality Gate Management (QGM), you can assign a change document to
transport requests created in a managed ABAP development system or in Eclipse ADT.

Prerequisites

• In the managed development system, you have implemented SAP Note 2471766 , or you have installed a
support package stack containing this SAP Note.
• In the managed development system, you have installed the latest SAP Solution Tools Plug-in (ST-PI) in
alignment with SAP Solution Manager 7.2 SPS 6.
• If you are using central CTS, you have customized the role SAP_CM_SMAN_BACK and applied it to the back
RFC user for the correct authorization.
• To support transport requests created in Eclipse ADT, you have installed SAP BASIS release is NW 750 and
ADT 3.14.
• To configure whether a change document must be assigned, in the SAP Solution Manager system, go
to the Administration Cockpit Landscape Overview . For each managed development system, under
Change Document Assignment you choose whether an additional change document attribute is needed
when creating a transport request in the transport organizer of the managed development system. You can
select the option “required”, “optional”, or “not required”.
• To assign a change document to transport requests created in Eclipse, you have installed the latest ST-PI
in alignment with SAP Solution Manager 7.2 SP12, and you have implemented SAP Note 2958393 in the
SAP Solution Manager system.

Activities

Creating Transport Requests in the Managed System

1. In your managed development system, call transaction SE09.

2. To create a transport request, choose Create and enter the required information.

Change Control Management

522 PUBLIC Quality Gate Management
 Depending on the selected option for change document assignment, the transport request creation dialog
offers different fields:
• If change document assignment is required, you must enter a change document ID.
• If change document assignment is optional, you can choose to leave the change document ID field
empty and instead fill out the fields Project and Target. If you assign a change document ID, the Project
field and Target field are ignored.
• If change document assignment is not required, you cannot assign a change document.

 Note

To search for the change document, use the F4 value help. You can use the search criteria of change
description, change ID, user name (only for Change Request Management), transaction type, and
cycle / QGM scenario.

The fields “Change Description”, “Change ID”, “Transaction Type”，“Cycle / QGM Scenario” support
wildcards (‘*’) in the search value. For example, you can enter ZM* as transaction type.

The search results offer only change documents with a status that allows transport request creation:
For Change Request Management, this means UI object CREATE_REQ in the Customizing table
AIC_PROC_EDIT. QGM change documents must have an “open” status.

3. Save the transport request. The transport request is created and, if applicable, assigned to the change
document.
4. If the transport request is created but fails to be registered to the SAP Solution Manager system, the
local transport request stays as it is. For trouble shooting, go to the SAP Solution Manager system to
see the application log. Call transaction SLG1 and search for the object /TMWFLOW/CMSCV and sub-object
CHNG_ASSI_TR_CREATE for your application log. After solving the issue, manually reassign the transport
request to the change document in the SAP Solution Manager system.

Creating Transport Requests in Eclipse ADT

In Eclipse, when you save an object you created or edited, you can choose an existing transport request or
create a new transport request.

When you create a new transport request to save the object, select a change document ID by browsing the list.

Related Information

SAP Note 2745405

Landscape Overview [page 323]

Change Control Management

Quality Gate Management PUBLIC 523
5.3.4.4 Processing Critical Objects

Use

A transport request containing critical objects cannot be exported if the critical object function has been
enabled in the system. If you try to export a transport request containing critical objects, the system displays
an error message.

In addition, the system displays an icon to show the status of the critical objects. To export a request that
contains critical objects, you must approve the transport.

This procedure describes how to approve the transport of critical objects for export.

Prerequisites

You are the change manager and you approved the creation of the preceding change transaction.

Procedure

To approve critical objects for export, proceed as follows:

1. In the transport requests table, choose Actions... Process Critical Object . Alternatively, click the
number displayed in the Critical Objects column.
2. Select the transport requests (both workbench and Customizing requests) containing the critical objects.
3. Optional: Enter any supporting information regarding your decision in the comments box and upload
supporting documents. This information is visible to anyone who can view the critical objects.
4. Choose the Approve pushbutton.

 Note

If objects have already been approved, you can choose the Reject pushbutton to revert them to their
original (that is, “to be approved”) status.

Result

The status of the critical objects that are displayed in the dialog box changes to Approved or Unapproved. The
system displays the corresponding information. In addition, this information is saved to the application log.

Change Control Management

524 PUBLIC Quality Gate Management
5.3.4.5 Decoupling Transport Requests in Quality Gate
Management

You can separate a transport request from its scenario and change it. This transport request is then no longer
controlled by QGM.

Prerequisites

If you want to decouple released transport requests, you have activated the central Change and Transport
System (cCTS) for your scenario. Otherwise, you can decouple only modifiable transport requests.

Context

 Caution

Although the software changes you have made are no longer controlled by QGM, they remain in the system
and may impact later developments that use the same objects. We therefore recommend that you restore
the changes and do not decouple them.

Procedure

1. In the transport requests table, choose Actions... Decouple Transport Request .

2. Select the transport requests that you want to decouple.
3. Choose the Decouple pushbutton.

Results

The transport requests are decoupled from your QGM scenario.

If you want to manage a decoupled transport request again, you must reassign the request to a QGM scenario.

Example

You have performed software changes that you no longer need. The recommended way of handling these
changes is to restore the changed objects to their original state. However, due to project or time restrictions,

Change Control Management

Quality Gate Management PUBLIC 525
you can’t reset the changes. You therefore decide to decouple the changes from your scenario, so that you can
focus on finalizing the other parts of your scenario.

Related Information

Assigning Transport Requests [page 513]

5.3.5 Risks

Use

The Risks column in the changes overview shows the risks associated with transports in your change. This
enables the quality manager to take action and react to critical situations appropriately.

Prerequisites

You have created a scenario with the data required for quality gate management.

Features

Before each phase or phase completion, the quality manager can assess whether all transports have been
imported correctly into the next system, or whether measures must be undertaken to ensure that they do so.

To view the risks, proceed as follows:

1. Open the scenario for which you want to review the risks by clicking the link in the Scenario column.
2. Choose the link in the Risks column, or choose Scenario Transport Open Transport Risks from the
header area.
3. The upper table shows the systems for which there is a risk. It contains the following information:

Column Meaning

System The logical system and client involved

Risk Type The transport risk type (see below)

Number of Risks The number of transport risks in this system

Change Control Management

526 PUBLIC Quality Gate Management
 Column Meaning

Date/Time The date and time when the data was last read from the
remote system.

4. Choose a system.
In the lower table, the transport requests for a risk type in this system are displayed.
The following transport risk types may be displayed:

Transport Risk Type Meaning

Transport error (return code ≥ 8) If an error occurs when importing a transport request,
the transport error is reported as a transport risk for this
target system.

Open transports If a transport request is not released, it is reported as an

open transport for the source system.

Missing transports This applies only to released transport requests. A re-

leased transport request is reported as a missing trans-
port for a target system if it is supposed to be imported
into this system but has not been imported so far. Missing
transports are calculated for the respective system track
but are not reported for the source system.

Synchronization errors Refers to transports that did not run synchronously (for
example, synchronization errors in scenarios with more
than one export system)

More Information

For more information about how to work with transport risks, see Declaring a Transport Error as Repaired [page
527].

5.3.5.1 Declaring a Transport Error as Repaired

Use

Importing scenario data may result in import errors in the managed system.

Return code 8 import errors in particular can be fixed manually or by applying an additional transport request.
As a result, even if the error is fixed, the return code 8 error is still displayed as a transport error risk. To
ensure that transport risks are displayed correctly, you can declare that the transport error has been repaired
manually. By choosing the Declare Error as Repaired pushbutton, you confirm that the import status in SAP
Solution Manager import tracking is repaired.

Change Control Management

Quality Gate Management PUBLIC 527
  Note

The Declare Error as Repaired pushbutton does not repair inconsistencies in your transports. It only cleans
up the display of the transport risks in the Transport Risk Overview dialog box. Consequently, choose this
pushbutton only if you have already repaired the transport error.

Procedure

Proceed as follows:

1. Open the Transport Risk Overview dialog box and select a system that contains transport errors.
2. Select a transport request that was imported with an error in the lower screen section.
3. Choose the Declare Error as Repaired pushbutton to display the dialog box for declaring the error as
repaired.
4. Choose the Error Corrected pushbutton.

 Note

To view the transport log for this transport request, choose the Log pushbutton.

Result

The error is no longer reported as a risk.

5.3.6 Transport Analysis

Scenario Analysis

For the scenario analysis, choose a QGM scenario on the Quality Gate Management Overview screen. You can
trigger the analysis choosing Scenario Transport. Select Transport Analysis. A table of analysis results will
appear based on the transport track system belonging to the respective scenario.

On the transport analysis UI, for each transport track, the statistics include the following:

Open Transports: All modifiable transport requests in the development system

Released Transports: All transport requests released in the development system

Waiting for Import: All transport requests that are in the import buffer of the target system and have not been
imported yet

Imported Transports: All transport requests that are imported into the target system and that have been
imported at least once regardless of being in the buffer or not

Import Errors: All transport requests import with errors in the target system

Change Control Management

528 PUBLIC Quality Gate Management
Sequence Violations: All transport requests that are imported without following the sequence of release

Missing Imports: All transport requests that are released but not imported into the target system. Those
transport requests may or may not be in the buffer of target system yet.

To view the individual transport details, click on the corresponding statistics number (except Sequence
Violations). From here, you can navigate to the transport overview on SAP GUI by choosing the link of the
transport number.

When you click on the number in the Sequence Violations column, a comparisons view appears. All released
transport requests are displayed in the left table, while all imported transport requests for that target system
are displayed in the right table. If a sequence violation exists, the corresponding records should be highlighted
in orange in both tables.

System Analysis and Request Analysis

On the Quality Gate Management Overview screen, you can perform a system analysis and a request analysis
by choosing the Transport Analysis pushbutton above the scenario list table.

System Analysis:

• Select a source system and a target system to compare. The provided dropdown list contains all active
track systems in the transport track table. After selecting a source system, the target system will be
automatically filtered, which means that only subsequent systems connected with transport routes are
kept. The same applies the other way around.
• You can also specify the start date of the analysis. The default value is 2 months prior to today. If no start
date is entered, the analysis results display the comparison between the systems without time restrictions.
• The system analysis result statistics are similar to the scenario analysis. However, the result is restricted by
the start date if entered. The rules on how the time restriction works for each statistic are as follows:
a) Open Transports: Restricting that the transport requests must be created between the start date and
today and are currently in open status
b) Release Transports and Waiting for Import: Restricting that the transport requests must be released
between the start date and today (regardless of when they were created)
c) Imported Transports and Import Errors: Restricting that the transport requests must be imported
between the start date and today (regardless of when they were created or released)
d) Sequence Violations and Missing Imports: When counting released transport requests, it uses rule b)
and when counting imported transport requests, it uses rule c)

Request Analysis:

Enter a transport request number or search a transport request using the search help for the analysis. The
analysis result list contains two parts: basic information and a tracking analysis. The tracking data of the
transport request indicates when the transport request is released / imported into the entire transport track.

Change Control Management

Quality Gate Management PUBLIC 529
5.3.7 Overview of Scheduled Import Jobs

To have an overview of the scheduled import jobs from your scenario, proceed as follows:

1. Choose a scenario on the Quality Gate Management Overview screen.

2. Choose Scenario Transport.
3. Select Scheduled Import Jobs from the dropdown list.

The search criteria Target System, Job Status, Job Scheduled Date and Time and Job Executed Date and Time
help you filter and narrow down the number of results. Regarding the different statuses of the scheduled import
jobs, you can perform various actions on those jobs. The following is a matrix table for the job status and
actions:

Show Variant Show Job Log Delete Job Cancel Job Redefine Job

Scheduled X - X - X

Released X - X - X

Ready X - X - X

Active X - X X -

Finished X X - - -

Canceled X X - - -

(-) Not available

(X) Available

5.3.8 Transport-Related Checks in QGM

Use

Transport-related checks include the following checks:

• Cross-system object lock (CSOL) check

• Downgrade protection (DGP) check
• Critical object check
• ABAP test cockpit (ATC) check
• Code inspector check
• Customer-specific check (BAdI implementation)

Change Control Management

530 PUBLIC Quality Gate Management
Features

To learn about automatic checks and manual checks as well as implementing custom-specific checks, see
Transport-Related Checks [page 150].

 Note

• Automatic checks in Quality Gate Management: Transport operations are triggered from the QGM Web
Dynpro UI.
• Manual checks in Quality Gate Management: Manual checks are triggered in the Transport-Related
Checks dialog box using the Transport-Related Checks action in the QGM scenatio or change.

Related Information

Automatic and Manual Check [page 159]

Implementing Custom-Specific Checks [page 163]

5.3.9 Opening the IT Calendar

To optimize your IT planning activities, you can display several Change Request Management and Quality Gate
Management objects in the IT calendar.

Use

You can see the following objects:

• Change cycle phases

• Change transactions
• QGM phases
• QGM Q-Gates and milestones

During planned downtimes, transports to the affected systems are not possible. This is because the system
availability check during the transport process also considers the system status as defined in WMM (Work
Mode Management).

Prerequisites

You have made the following settings in SAP Solution Manager Configuration (transaction SOLMAN_SETUP):

• You defined the display colors for your objects in the IT calendar.

Change Control Management

Quality Gate Management PUBLIC 531
• For change cycle phases and QGM phases, you specified for which system roles the entries are created in
the IT calendar.
• You specified a threshold for the grouping of similar objects. For example, you can specify that all requests
for change on a particular date are displayed as a group in the IT calendar, if their number exceeds 5.

 Note

Existing objects cannot be migrated to the IT calendar. Only after you have performed the Customizing for
the required objects, entries are created in the IT calendar every time you save an object.

You can initially load calendar entries into the IT calendar, and delete entries, if necessary. To do so, in
Customizing, choose SAP Solution Manager Capabilities (Optional) Change Control Management
Change Request Management Framework IT Calendar Integration .

Features

• The IT calendar is a tool in SAP Solution Manager that is used in various scenarios. You can display specific
events, according to event categories. For Change Request Management and Quality Gate Management,
the following event categories are displayed:

Object Event categories Navigation to IT Calendar Displayed contents

Change transaction Request for change, urgent • Via More Open IT Transactions are displayed
change, normal change, ad- Calendar . with their due dates. The
ministrative change, general system displays bars for the
• Change documents:
change, defect correction specific date (one day), and
From the Landscape
only for the productive sys-
assignment block. Only
tem.
the selected system is
displayed.

 Note
From urgent changes,
you can display the IT
calendar only from the
Landscape assignment
block.

Change Control Management

532 PUBLIC Quality Gate Management
 Object Event categories Navigation to IT Calendar Displayed contents

Change cycle phases Phases assigned to the • Via More Open Phases are displayed with
change cycle, for example, IT Calendar . All sys- their start and end time
Created, Scope, Build, Test, tems are displayed, re- stamp, for the system roles
Go Live, Being Completed, gardless of the client. maintained in Customizing.
Completed
• From the Landscape
assignment block. Only
the selected system is
displayed.

QGM phases Scope, Build, Test, Deploy From the Calendar View tab Phases are displayed with
page their start and end dates,
for the system roles main-
tained in Customizing.

QGM Q-Gates and mile- For example, Start of From the Calendar View tab Displayed for a specific
stones project, Scope to Build, page (due) date.
Build to Test, Test to Deploy,
or Milestones

 Note

Events are the actual displayed events in the IT calendar, for example, a QGM milestone on a specific
date.

• You can display the IT calendar on the Technical Administration launchpad group. There, you have the
following options:
• From the displayed contents, you can navigate directly to the change transactions in the WebClient UI
or to the QGM objects.
• Under Categories, you can select which event categories are displayed. For example, you can only
display certain phases or change documents.
• The system displays details for each object and date. You can switch between a monthly, weekly, and
daily display mode.

More Information

IT Calendar

Change Control Management

Quality Gate Management PUBLIC 533
5.4 Closing Scenarios

Use

When your scenario or change cycle has come to an end, you can close the scenario by passing the End of
Deployment quality gate. In this case, you close the final change cycle without switching it.

Prerequisites

• All changes in the scenario are either Completed or Withdrawn. All other changes, which are neither
Completed nor Withdrawn, must be reassigned to another scenario. In special cases they can also be
decoupled, although this is not recommended.
• For all milestones and quality gates before the End of Deployment quality gate, the status has been set to
Passed by both processors.

Procedure

To close a scenario, proceed as follows

1. Select your scenario and open the Quality Gates dialog box for the End of Deployment quality gate.
2. In the window, set the overall status to Passed and choose OK.
3. Continue with the confirmation dialog box.

 Note

QGM scenarios are archived or deleted together with the last QGM change. This is not possible for
scenarios that do not contain any QGM change. For such empty scenarios, if they are in phase Not Started
or Finished, admin users can choose the Delete option.

Related Information

Maintaining Changes [page 508]

Decoupling Transport Requests in Quality Gate Management [page 525]

Change Control Management

534 PUBLIC Quality Gate Management
5.5 Administration Cockpit for Quality Gate Management

The administration cockpit provides a central entry point to all administrative activities for Change Control
Management.

Use

Depending on business role, the following tab pages can be displayed or edited:

• Task Lists: You see the details of task lists.

• Landscape Overview: You see information about the managed systems contained in the logical component
groups that are connected to Quality Gate Management (QGM), via the solution landscape (transaction
SLAN) or the change control landscape assignment. Each managed system in the logical component
groups is listed along with the communication systems.
• Critical Objects: You can define and edit critical transport objects. You can activate and deactivate the
modification check.
• Cross-System Object Lock and Downgrade Protection: You can manage cross-system object lock entries.
You can display lock entries according to defined criteria, remove them or register lock entries for
transport requests that are managed by Quality Gate Management.
• Cross-Reference Check: You can activate, deactivate, and configure the cross-reference check, which
detects inconsistencies for objects that are referenced in transport requests.
• Transport Analysis: You can analyze the transport requests in your landscape in different views.
• Search: You can search for QGM change objects based on your search criteria. You can also do a full-text
search. You can activate and deactivate object reporting.

 Note

Non-ABAP objects are not supported.

The link in the Change ID column leads directly to the transactions in the WebClient UI.
• Scheduled Import Jobs: You get an overview of the scheduled import jobs. You can filter the background
jobs scheduled for importing transport requests.

Prerequisites

Your business role must be authorized to display or edit the tab pages.

The following table specifies the functions for which each Quality Gate Management role is authorized in the
administration cockpit tab pages.

Note: An administrator has access to all functions.

Change Control Management

Quality Gate Management PUBLIC 535
Authorizations for Roles in Quality Gate Management

Quality Advisory Board Member

Change Manager

Quality Manager
Administrator

IT Operator
Function

TSKLT_DISP     

Display task lists

SYSTM_DISP     

Display landscape
overview

SYSTM_EDIT     

Make changes
in landscape over-
view

CRIT_DISP     

Display critical
object configura-
tion

CRIT_EDIT     

Change critical
object configura-
tion

CSOL_DISP     

Display cross-sys-
tem object lock
entries

CSOL_EDIT     

Change cross-
system object
lock entries

CRF_DISP     

Change Control Management

536 PUBLIC Quality Gate Management
 Quality Advisory Board Member
Change Manager

Quality Manager
Administrator

IT Operator
Function

Display cross-ref-
erence check en-
tries

CRF_EDIT     

Change cross-ref-
erence check en-
tries

TRACK_DISP     

Display transport
analysis

SEARCH_DISP     

Perform search

SCIMP_DISP     

Display Sched-
uled Import Jobs

5.5.1 Task Lists Tab for Quality Gate Management

Use

On the Task Lists tab, you can select QGM Scenarios to display information about the activities for distributing
software in your system landscape.

Change Control Management

Quality Gate Management PUBLIC 537
Prerequisites

You have created QGM scenarios.

Features

You can display the following information about your task lists:

• Assignment of task lists to QGM scenarios

• Task list structure including the task status such as Locked, Unlocked, Active
• Monitor tab showing the overall view of the task execution
• Daily Overview of task execution in a task list
• Transport Requests belonging to a task list including the following information:
• Name and status of the transport request in the source system
• Transport request type
• System in which the request was created
From the Transport Requests tab, you can directly navigate to the QGM scenario in the Quality Gate
Management Overview.
• Landscape View of a task list

You can perform the following activities:

• Lock or activate task lists

• Lock or unlock task groups
• Change task status
• Perform a configuration check
• Change the CTS status switches
Usually, the CTS status switches are switched on. You should switch them off only in the following cases:
• You want to schedule an import in the transport management system.
• The SAP Solution Manager system is not available and you would like to perform a local import.

More Information

Task Lists in Quality Gate Management [page 517]

Change Control Management

538 PUBLIC Quality Gate Management
5.5.1.1 Configuration Check for Quality Gate Management

Use

You can check whether a task list is correctly configured with respect to Quality Gate Management.

Prerequisites

• You have configured your system for Quality Gate Management.

• You have created a QGM scenario.

Features

You can check the following:

• Global configuration
• System landscape
• Number ranges
• Business partner configuration

Activities

1. In the administration cockpit, on the Task Lists tab, choose QGM Scenarios.
2. Select the task list of your QGM scenario.
3. Choose Check Configuration.
The check results are presented as a list of nodes, which you can expand for more details. Items with
configuration error are marked in red. To correct an error, open the corresponding long text and follow the
instructions.

Change Control Management

Quality Gate Management PUBLIC 539
5.5.1.2 Changing CTS Status Switches

Prerequisites

• You have been assigned the SAP_CM_ADMINISTRATOR_COMP role.

• You have generated a change cycle.
• A task list exists for the change cycle.

Context

Once you have created a change cycle for a managed landscape, a CTS project is created automatically for
each of the development systems and clients that act as source systems in the landscape. By default, the CTS
status switches are closed. This means that the tools of the Change and Transport System cannot be used to
create, release, or import transport requests. For troubleshooting purposes, however, system administrators
are allowed to open the switches. You should only open the switches in the following cases:

• You want to perform a transport action directly in the transport management system, for example,
schedule an import in the transport management system.
• The SAP Solution Manager system is not available and you would like to perform a transport action.

 Note

If the SAP Solution Manager system is not available, go to transaction SE01 and enter any transport
request. Choose Go to Edit Project Project Status Switch and open the switch.

For change cycles that have been enabled for central CTS, the import status switches no longer control
imports. The imports are locked on central CTS level. In case of an emergency (for example, if the SAP
Solution Manager system is not available), perform the steps as described under Performing Imports in
System Clusters [page 442].

Procedure

1. On the Task Lists tab page, select a task list and choose Change CTS Status Switch.
2. You have the following options for changing the CTS status switch:

• To change the CTS status switch for all systems and clients of the landscape, choose Select All and
then change the CTS status switch.
• To change the CTS status switch for selected systems, expand the structure tree and select the
systems. Then change the CTS status switch.
3. Choose Display Application Log in the dialog to check the recent logs of the CTS status switch changes that
were made here.

Change Control Management

540 PUBLIC Quality Gate Management
  Note

If you want to use SAP Solution Manager to control the transport activities of your landscape, we
recommend that you close the CTS status switch for all the systems and the clients of the landscape. In
addition, before transport activities are triggered from SAP Solution Manager, the corresponding CTS
project status switches will open beforehand and close afterwards automatically.

To track all the operations of the CTS status switches, in the application log transaction code SLG1,
search using the following criteria:

• For the Object enter /TMWFLOW/CMSCV.

• For the Subobject enter DRPS.
• For the External ID enter your task list ID.
• For Job Creation:
• If the action is triggered in the dialog, choose Dialog.
• If the action is triggered in the background via transport activities, choose In batch mode.

5.5.2 Landscape Overview

The Landscape Overview tab displays information on the managed systems contained in the logical component
groups that are connected to Change Request Management or QGM via the solution landscape (transaction
SLAN) or the change control landscape assignment. Each managed system in the logical component groups is
listed together with its communication systems.

Features

The following functions are available:

• From the System Status column, you see details of the configuration check result.
• From the Technical System column, you see and edit the system in LMDB.
• From the Work Mode column, you see the work mode status in the IT calendar. You can navigate directly to
the IT calendar.
• The Lifecycle Status displays the status set in the landscape management database (transaction LMDB).
You can navigate directly to LMDB.
• In the Upon-Saving Checks column, you can activate the upon-saving transport-related checks framework
for each managed ABAP development system. In the dropdown list, select Off, On, or On (Legacy CSOL).
To enable single checks in this framework, you must switch on each check individually. For example, to
activate the cross-system object lock check, call transaction SOLMAN_SETUP and in your scenario Change
Request Management or QGM, select Set up Downgrade Protection and Retrofit Configure CSOL and
DGP Globally Activate CSOL and DGP (Master Data) .
• In the CTS Project Assignment column, you can check and edit the entries. You can directly navigate to the
managed system.

Change Control Management

Quality Gate Management PUBLIC 541
 For each system in which you want to create transport requests, select the project assignment attribute
(SAP_CTS_PROJECT):
We recommend that you set the CTS project assignment as mandatory to prevent the creation of transport
requests outside Change Control Management. Note that if it is mandatory, you cannot release transport
requests without CTS projects. If you set up CTS projects during a transition period, you may have
to create dummy CTS projects so that developments made before the availability of Change Request
Management can still be transported.

 Note

Note: If your Solution Manager system is not available, you can make these settings in transaction
SE03 of the managed development system.

• Change Document Assignment: You can allow your developers the manual creation of transport requests
directly in the managed ABAP development system and the assignment of these transport requests to
a change document that is managed in the SAP Solution Manager. Depending on the option you select,
developers see different fields in WBO, in the transport request creation dialog. You can select one of the
following options:

Not Required Developers can assign the transport request to a local CTS Project or leave the CTS
Project unassigned.
(This is the default option and
deactivates the change docu- They cannot select a change document ID.
ment assignment functionality.)

Required Developers must select a change document ID. They can only select change docu-
ments that have a status that allows transport request creation and for which they
are assigned as developer (business partner role).

They cannot assign the transport request to a CTS Project.

These transport requests are managed inside SAP Solution Manager, in the change
document.

Optional Developers can either select a change document ID or assign the transport to a CTS
Project or leave the project unassigned.

 Note

To assign a transport request to a CTS project that was created from a Change Request Management
cycle, the CTS Project switches must allow transport request creation.

To allow creating a transport request without a mandatory project assignment, set attribute
SAP_CTS_PROJECT to Not mandatory.

• If a trusted RFC destination has been configured, you can log on to an ABAP system. If host and port data
is provided for the Java system in transaction LMDB, you can log on to the SAP NetWeaver Java starting
page.
• Display the defined RFC connections. You can directly navigate to LMDB to configure the connections.
• To perform a check for selected systems, choose Perform Check. The Last Check column indicates the
date or time of the system check.

Change Control Management

542 PUBLIC Quality Gate Management
• To delete the transport tracking data of one or more selected systems, select Delete Transport Tracking
Data. If you want to copy a managed system but the transport history of the central SAP Solution Manager
system already contains transport data (for example, transport statuses and objects), use this function to
delete the buffered transport data information contained in the SAP Solution Manager system.
• You can re-read the transport tracking data of a single system, a change cycle, or a QGM scenario.

Related Information

Managing Logical Component Groups

Upon-Saving Transport-Related Checks [page 161]
Assigning a Change Document to Transport Requests Created Outside SAP Solution Manager [page 394]

5.5.3 Defining Critical Objects

To prevent improper modification of objects that are especially important for your core business processes,
you can define such objects as critical and monitor any changes.

Use

The change and transport process across your solution landscape may include objects that are especially
important for your core business processes. Improper modification of those objects may result in serious
business impact on the whole solution’s stability. Therefore, a strict monitoring mechanism is needed to
control those objects’ change and transport.

You can activate a check to determine if transport requests contain critical transport objects, which require
approval before they can be exported from the development system. This check can be activated both on
system and client level.

Critical object checks are available for Quality Gate Management and Change Request Management.

 Note

Critical object checks are available only for ABAP systems. Critical object definitions are applicable only to
development systems.

In Change Request Management, approval for critical objects conflicts is requested in the following ways -
depending on the status of the upon-saving transport-related check:

• If the check is active: When developers save a transport request even though there is a critical object
conflict, the change manager (or other designated partner function) receives an e-mail notification.
• If the check is inactive: When developers set a change document to status To Be Tested, or release the
transport requests in normal changes and defect corrections, they can manually request approval.

Change Control Management

Quality Gate Management PUBLIC 543
Prerequisites

To define critical objects, you have one of the following roles:

• SAP_CM_ADMINISTRATOR_COMP or SAP_CM_CHANGE_MANAGER_COMP (for Change Request Management)

• SAP_QGM_ADMIN_COMP or SAP_QGM_CHANGE_MANAGER_COMP (for Quality Gate Management)

Activities

 Note

You can define generic critical objects by entering wildcards in the fields.

1. You have the following options:

• To create a critical object manually for selected systems and clients, choose Add and in the menu,
choose New.
• To create a new critical object based on an existing one, select a critical object, choose Add
From Selected Object . Adapt the data as needed. You must assign another system or object name
because duplicate objects are not allowed.
• You can also select objects in a transport request and flag them as critical objects: Choose Add
From Transport Request . Select the system and the transport request and then select the objects
that you want to flag as critical objects.
• To copy multiple critical objects across your systems, select all required critical objects, choose Copy
and select one or more target systems.

 Note

To ensure consistency, we recommend that you choose one logical system (system/client) as the
“original” system. Only in this system, you should create, change, or delete objects, and then copy
them to other systems.

2. Activate the check for specific critical objects.

To specify the start and end date of the "active" status for one or more critical objects, you have the
following options:
• When creating or editing a critical object, change the values in the respective fields. Per default, start
date is the current day, with unlimited validity.
• In the critical objects list, select one or more critical objects and activate or deactivate them.
Define whether the check is to be active at global level or at system level. The global switch controls
whether the check is off for all managed systems. The system switch controls whether the check is off for
specific systems. The check is only performed if both the global and the system switch are on.
3. In the change log, you see all critical object-related changes.
4. While a transport request is being exported, the source and target system and the source and target client
are determined. If the transport object checks are active for the relevant client and system, the export
program checks whether the transport request contains critical transport objects, or subobjects of critical
transport objects. The export does not take place if the transport request contains critical objects but has
to be approved by the change manager.

Change Control Management

544 PUBLIC Quality Gate Management
Related Information

Performing Transport-Related Checks [page 150]

Generic Critical Objects [page 327]
Approving and Exporting Critical Objects [page 147]

5.5.3.1 Generic Critical Objects

You can use asterisks as “wildcards” to specify generic critical Customizing and Workbench objects.

 Tip

If you are not sure which object type and object name to enter, check the object list of your transport
request, and check the Object Type and Object Name columns.

Generic Critical Customizing Objects

For Customizing objects, you can flag generic critical objects based on:

• Generic Table Key

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TABU

Object Name: UST04

Table Key: 100*

In this case, the entries in table UST04 that have a table key beginning with “100” must be approved
before they can be transported.

• Generic Table Name

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Change Control Management

Quality Gate Management PUBLIC 545
 Object Type: TDAT

Object Name: UST*

Table Key: 100ENK1

In this case, Customizing content of tables with a name beginning with “UST” must be approved before
they can be transported.

• Generic View Name

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: CDAT

Object Name: SCMGV_ATTR*

Table Key: *

In this case, Customizing objects of the views in the view cluster with names beginning with
“SCMGV_ATTR” must be approved before they can be transported.

• Generic Object Type

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: CD*

Object Name: SCMGV_ATTR*

Table Key: *

In this case, Customizing objects with types beginning with “CD” and names beginning with
“SCMGV_ATTR” must be approved before they can be transported.

Generic Critical Workbench Objects

For Workbench objects, you can flag generic critical objects based on:

• Generic Object Name

Change Control Management

546 PUBLIC Quality Gate Management
  Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TABL

Object Name: ZCUST*

In this case, all tables with a name beginning with “ZCUST” must be approved before they can be
transported.

• Generic Object Type

 Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TA*

Object Name: ZCUST*

In this case, all Workbench objects with types beginning with “TA” and names beginning with “ZCUST”
must be approved before they can be transported.

5.5.4 Creating Cross-System Object Lock Entries

You can manage cross-system object lock entries in the administration cockpit.

Procedure

1. In the administration cockpit, go to Cross-System Object Locks Register .

2. Select a development system or choose all systems. You can also use the following options:

• You can restrict the range of transport requests by request number. For external requests, the
transport request number prefix (containing the external system name) can be different from the
real (internal) source system name.
• You can choose to send e-mail notifications if conflicts are detected: Default recipients are the change
managers (and for Change Control Management, also IT operators) of the change documents or QGM
changes that contain the transport requests with conflicts. You can also enter an additional e-mail
address.

Change Control Management

Quality Gate Management PUBLIC 547
  Note

To send a notification to the change manager and IT operator, the e-mail addresses must be
maintained for their business partners.

The system does not send any e-mail notifications to the transport request owners.

• You can specify the execution time (immediate or scheduled).

3. After you have registered the lock entries, to see the progress, monitor the job log.
a. Call transaction SM36 (Define Background Job) and select Own jobs.
b. Find job CM_CROSS_SYS_OBJ_LOCK_REGISTER, scheduled to run at the time you specified, and open
Job Log.

When the job is finished, the job log refers to the application log. The application log contains detailed
messages, whereas the job log shows only the job progress.

Results

For each system, the application log displays the final processing result. You see warning messages for
transport requests that cannot be processed, and, for example, if the system does not find an e-mail address.

Next Steps

To check the application log, call transaction SLG1 with object /TMWFLOW/CMSCV and subobject
CROSS_SYS_OBJ_LOCK.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Downgrade Protection [page 360]

5.5.5 Cross-Reference Check

You can use the cross-reference check to detect inconsistencies for objects that are referenced in transport
requests.

Objects in transport requests sometimes refer to other objects that are not included in the transport. The
cross-reference check applies a where-used-analysis to check the referenced objects in transport requests. If
a referenced object doesn’t exist in the target system or if the referenced object in the source system has a
different version than in the target system, the check indicates a potential error. In addition, the check shows
the last transport requests for the missing object versions.

Change Control Management

548 PUBLIC Quality Gate Management
The cross-reference check can handle the following type of data:

• ABAP repository data.

• Dictionary objects
• Customizing objects

Logical transport objects and SAP HANA objects are not supported.

Git-enabled changes (SMGH) don’t use the cross-reference check.

The cross-reference check is triggered automatically when a transport request is exported from the
development system to follow-up systems or when a transport request is imported into a system. You can
also perform the check manually in the Transport-Related Checks assignment block on the WebClient UI.

It depends on the authorizations of the users whether they can ignore the error messages or warnings and
continue the action:

• Change Request Management: Administrators, change managers, and IT operators can ignore both errors
and warnings. Developers can ignore warnings.
• Quality Gate Management: QGM administrators, QGM change managers, and QGM IT operators can ignore
both errors and warnings. Developers can ignore warnings.

Prerequisites

• You have the installed the ST-PI plug in ST-PI 740 or ST-PI 2008.1 SP16 in the managed systems.
• You have implemented the SAP Notes listed in the collective note 2475591
• To display the Cross-Reference Check tab and change the settings for the cross-reference check, you have
the role administrator, change manager, or IT operator.

Configuring the Cross-Reference Check

In the Administration Cockpit, on the Cross-Reference Check tab, you can do the following:

• Deactivate or activate the check

• Configure general settings for the check
• Configure track-specific settings

You can specify the check mode that determines what happens when the check detects a potential error in a
transport request:

• In the default mode, only a warning is issued when you release the transport request and an error message
is issued and the import is blocked when you import a transport request.
• If you select the Stop at Error mode, the system always issues an error message and blocks the release or
import of the transport request.
• If you select the Warning Only mode, the system always only issues a warning.
• If you select Silent, you must check the transport request manually to get a conflict warning. There’s no
automatic check during release or import

Change Control Management

Quality Gate Management PUBLIC 549
  Note

Any settings that you make on the Cross-Reference Check tab in the Administration Cockpit are active
immediately.

Related Information

Performing Transport-Related Checks [page 150]

Administration Cockpit for Change Request Management [page 291]
Administration Cockpit for Quality Gate Management [page 535]

5.5.6 Transport Analysis Tab for Quality Gate Management

Use

You can use the Transport Analysis tab to analyze the transport requests in QGM scenarios using different
views.

Prerequisites

You have created a QGM scenario.

Features

In the administration cockpit, on the Transport Analysis tab, you can use the following views:

• QGM Scenario Analysis

Display an analysis of all transport requests in a QGM scenario
• System analysis
Analyze all transport requests between two systems. You can compare two systems (for example, a
development system with a consolidation system, or two target systems) to check which transport
requests have been imported or exported.
• Request analysis
Display the transport logs for a transport request

When you click the links in the overview results, the system displays details about the transport requests at the
bottom of the screen.

Change Control Management

550 PUBLIC Quality Gate Management
The views display the number of transport requests and their statuses:

• Transport requests in the development system:

• Open: Modifiable transport requests
• Released: Released transport requests
• Transport requests in the target system:
• Waiting for Import: Released transport requests that have already reached the queue of the current
system. It includes the ones that have been preliminary imported but left in the queue.
• Imported: Released transport requests that have been imported into the current system
• Import Error: Released transport requests that have been imported into the current system, but the
import resulted in an error.
• Missing Imports: Released transport requests that haven’t yet been finally imported into the current
system. These requests may or may not be in the queue of the current system.
• Sequence Violation: Transport requests that have been imported into the current system, but not in
the sequence in which they were released.

5.5.7 Scheduled Import Jobs

Use

You can display background jobs scheduled for importing transport requests independent of task lists, change
cycles, and target systems.

You can also display jobs from batch imports in Change Request Management. Jobs from batch imports do not
display a target system in the result list.

Procedure

To filter the background jobs scheduled for importing transport requests, use the following criteria:

• Target System
Select a system into which the transport request is to be imported.
• Cycle
Select the change cycle to which the transport request belongs (Change Request Management only).
• QGM Scenario
Select the scenario in which the transport request is imported (Quality Gate Management only).
• Task List
Select a task list that triggers the transport request import.
• Job Type
Select whether you want to see only import jobs or, for Change Request Management, status shift jobs for
batch reports.
• Job Status
Select one or more status the import jobs can have.

Change Control Management

Quality Gate Management PUBLIC 551
• Job Scheduled Date and Time
Filter for the time period in which the import job is scheduled to be executed.
• To see all jobs of every scheduled date and time, leave the date and time blank.
• To see all jobs scheduled for a specific time of day, define only the time and leave the date blank.
• To see all jobs scheduled after a specific point in time, define date and time only for the From criterion.
• To see all jobs scheduled prior to a specific point in time, define date and time only for the To criterion.
• Job Executed Date and Time
Filter for the time period in which the import job is actually executed. Import jobs may be delayed due to
system resources or system environment, so they will not be executed exactly as scheduled.

 Note

If you tick the checkboxes Finished and Canceled in the Job Status section, you can select all change
cycles, QGM scenarios, or task lists in the respective dropdown menus. Otherwise, the system only
displays the active ones.

In the search result list, you can perform the following activities for the background jobs:

• Display variant of a job (for single selection only)

• Show log of an import job (with status Finished)
• Delete an import job (excluding status Finished and Canceled)
• Cancel an import job (with status Active).
• Redefine an import job based on an existing one (excluding status Finished and Canceled; for non-multi
selection). A dialog box appears in which you can reschedule the job.

5.5.7.1 Handling Import Jobs During Cycle Switch

When you switch a current cycle to a new cycle or close a current cycle, the active import jobs assigned to the
current cycle are handled automatically.

For continual cycles and phase cycles:

• When you swich cycles, all ongoing scheduled import jobs of the current active cycle are removed. New
import jobs with the same job variants are rescheduled in the new cycle.
• When you close a cycle, all ongoing scheduled import jobs of the cycle are removed.

For release cycles:

• When you set the release cycle to the Hypercare phase, all ongoing scheduled import jobs are kept in the
current release cycle.
If a successor release cycle follows a cycle switch, new import jobs with the same job variant are scheduled
for the successor release cycle.
• When you set the release cycle to the Retired phase, all ongoing scheduled import jobs in the current
release cycle are removed.

Change Control Management

552 PUBLIC Quality Gate Management
Related Information

Scheduled Import Jobs [page 335]

Overview of Scheduled Import Jobs [page 530]

5.6 Dual Landscape Synchronization (Retrofit)

Retrofit helps to synchronize changed objects (both customizing and workbench) from maintenance
development system to project or upgrade development system in dual track landscapes (also known as N
1 landscapes). In contrast to manual synchronization of transport requests with changed objects between
development systems, retrofit allows to detect and manage conflicts when the same object changed in both
systems. You can use the retrofit functions with a Change Control Management scenario (Change Request
Management or Quality Gate Management), or standalone.

Use

In system landscapes in which several releases are processed at the same time, similar changes can be made
in different development systems. For example, new developments can be made in the new implementation
development system, while at the same time, errors are corrected or improvements are made in a maintenance
system for the production system landscape. The system release levels must be adjusted regularly to ensure
that changes are synchronized in parallel across different system landscapes. This synchronization is called
retrofitting.

Change Control Management

Quality Gate Management PUBLIC 553
 A Phased System Landscape as an Example of System Relationships

Related Information

Setting Up Retrofit [page 354]

Performing the Retrofit [page 345]
Standalone Retrofit [page 356]
Tool-Assisted Retrofit [page 348]
Displaying Import Information from the TMS [page 316]

5.6.1 Retrofit Categories

Retrofit categorizes transport objects for automatic (green), tool-assisted (yellow), and manual (red)
processing.

You can see the processing mode and categorization reason for each object on the transport request in the
object list.

For more information about the objects in the transport request, select the traffic light icon. The system
displays the log for this transport request, as well as SAP Notes in the transport requests, because they are
transport-critical, and can cause problems in the retrofit system.

Change Control Management

554 PUBLIC Quality Gate Management
  Tip

In Customizing, you can define object types for specific scenarios (retrofit scenario for Business
Warehouse objects, retrofit scenario for manual processing). Objects of these object types are always
retrofitted manually. Use the retrofit scenario for manual processing (parameter SCEN_MAN) to define the
objects that you want to exclude from automatic retrofit.

Retrofit Processes According to Categorization

Category Process Object Types Supported Can Be Used For

Green Automatic All object types (Business • Objects without cross-

Warehouse objects are parti- system object lock in the
The object can be imported
ally supported) retrofit system
automatically using ToC
(transports of copies).
• Objects that weren’t
changed in the retrofit
system

Yellow Tool-Assisted Correction Workbench: • Objects with cross-sys-

Workbench objects tem object lock in the
The object can be retrofitted
retrofit system
with post-processing tools, Business Configuration Sets:
either SCWB (workbench) or Customizing objects
• Objects that were
changed in the retrofit
the BC set (Customizing).
system

Change Control Management

Quality Gate Management PUBLIC 555
Category Process Object Types Supported Can Be Used For

Red Manual Objects that cannot be im- All other objects:

ported automatically and
The object must be proc- • Objects locked in the
that aren’t supported by the
essed manually. target system
postprocessing tools
• Objects not suitable for
a tool-assisted synchro-
nization
• Objects containing an
SAP Note
• Objects containing spe-
cial content (for exam-
ple, PFCG)
• it does not exist but is
critical for activating a
BC set
• the scenario check re-
calculation was not suc-
cessful
• the scenario check re-
calculation FM was not
specified
• the cross scenario check
detected an SAP object
• the cross-scenario
check detected changes
in a view
• the cross-scenario
check detected changes
in a table
• the ATC (ABAP Test
Cockpit) Central Check
System detected a
change affecting SAP S/
4HANA
• an error had occurred
generating the BC set
• no RFC destination was
found
• a general internal error
had occurred during the
object check

Change Control Management

556 PUBLIC Quality Gate Management
  Note

If an object has been changed in the maintenance development landscape, but the same object has not
been changed in the implementation development landscape, in the retrofit system, a cross-system object
lock is not created, and you can use the auto import option for retrofitting.

The system collects all objects that do not have any conflicts in a transport of copies. The system imports
the transport of copies directly into the retrofit development system and copies the objects to the target
transport request, in order to distribute them to the development-implementation system landscape.

Related Information

Dual Landscape Synchronization (Retrofit) [page 338]

Performing the Retrofit [page 345]

5.6.2 Retrofit Checks

You can perform retrofits for systems that are on different support package, enhancement package, or release
levels (cross-release retrofit). The system performs several checks to ensure that no downgrade occurs.

Check for Customizing objects

If table structures, views, or view structures have changed, the object is set to “manual retrofit”.

 Note

If you retrofit ERP to SAP S/4HANA and you have set up an ATC (ABAP Test Cockpit) Central Check
System, SAP S/4HANA objects are set to“manual retrofit”.

As a development user, you can manually select “automatic import” for each object.

Check for Workbench objects

SAP objects are set to “manual retrofit”.

Check for SAP Notes

SAP Notes cannot be retrofitted.

Check for conflicts in PFCG roles

If there are conflicts for some of the dependent objects of a role, the role and all of the dependent objects of the
role are set to “manual retrofit”.

 Note

The table AGR_DEFINE (logical object ACGR, role definition) has been chosen to represent all dependent
objects. Instead of checking all dependent objects of a role separately, the cross-system object lock checks
if the table AGR_DEFINE and the personalization data (table /TMWFLOW/CSOLPER) exist for the role, and if

Change Control Management

Quality Gate Management PUBLIC 557
 they can be released for an automatic retrofit. If not, the role and all dependent objects must be imported
with a manual retrofit.

For the transport of a derived role, not only the derived role but also the root role is checked. If the root role has
a conflict, you must perform a manual retrofit to transport the derived role.

5.6.3 Additional Functions in Retrofit

You can use additional functions to prepare and process the retrofit.

Retrofit Status
See the status of the transport request and its objects. You can filter the objects according to their status.

• Process Retrofit: Transports that haven’t been processed yet

• Manual Retrofit: Transports that were manually retrofitted
• Retrofitted: Transports that have been processed
• Retrofit Rejected: Transports that have been rejected for retrofit

Object List of the Transport Request

See the objects included in the transport request that you want to retrofit, including the object types and the
specific target transport request of each object.

Sequence Dependency
Indicates whether a transport request is dependent on other transport requests. If you choose the icon in the
field, the system lists the transport requests that belong to the sequence-dependent requests. If there’s no
sequence dependency, for example, several users can process a retrofit.

 Example

Transport request A contains object X, which is already in transport request B. Thus, there’s a sequence
dependency between transport requests A and B.

The sequence dependency implies the following:

• A transport request can have a sequence dependency to more than one other transport request, that is,
different objects are in different transport requests.
• There’s just one sequence dependency for an object X between transport request A and transport request
B if transport request B is the only request with object X or is the request that was last released. There can
also be a sequence dependency between transport request B and a third transport request.
• The sequence dependency is based on the objects in the object list for the entire retrofit queue. It’s
updated or deleted as soon as the retrofit for a transport request is completed.
• If there’s no sequence dependency, and some requests haven’t yet been processed, the system displays a
message. You can specify in the Customizing settings whether the message is to be displayed as a warning
or as an error.
• For customizing objects, sequence dependency will be calculated only on object level but not on table key
level.

Change Control Management

558 PUBLIC Quality Gate Management
Consistency Check
The system checks whether the retrofit was prepared correctly:

• Have transport requests been created in the retrofit system into which you want to import the changes
from the maintenance system?
• Has the execution sequence of the transport requests to be imported been observed?
• Does the transport request contain objects from SAP Notes that could cause conflicts during the import?

Display Logs and Display Old Logs

Read messages for the transport requests.

If a log exists, it is displayed automatically in the following situations:

• When you select a retrofit entry in the retrofit overview (same functionality as “Display Log”).
• When you process an action

Select Display old Logs to see old logs sorted by timestamp, and select one for details.

Display and Edit BC Sets

See and process transport requests that contain Customizing objects. For more information, see Copying
Changes Using the Correction Workbench and BC Sets [page 348].

TMS Alert Viewer

See import information from the Transport Management System. For more information, see Displaying the
TMS Alert Viewer [page 316].

Show Requests
• To see the source transport request in the development system of the maintenance landscape, select
Request / Task.
• To see the target transport request in the development system of the project landscape, select Retrofit
Request.

Add Note
You can add a note with information to a transport request, for example, the reasons for manually processing
objects.

Implement SAP Notes

Find SAP Notes relevant to the selected retrofit entry and open the Note Assistant (transaction SNOTE) to
implement them.

Create Retrofit Data Again

If an error occurred during the creation of the retrofit data (for example, because no categorization is done,
or the RFC connection wasn’t available), you can use this option to create new retrofit data for the selected
transport request. Note that the latest versions of the relevant objects are used.

Set/Reset Manual Status

Flag transport requests that haven’t been processed by the retrofit process tools, as completed. The status of
the selected transport request in the overview changes to Manual Retrofit. When you re-execute this step, the
previous action is undone.

Change Control Management

Quality Gate Management PUBLIC 559
Set/Reset Rejected Status
Prevent transport requests from being processed, for example, because the change is no longer required. The
status of the selected transport request in the overview changes to Retrofit Rejected. When you re-execute this
step, the previous action is undone.

Structure Comparison
This additional function is only visible in the SAP S/4HANA upgrade scenario.

The system analyzes the selected transport request. The system compares the structure for all included tables
and views and identifies the differences. The following status values are possible for the field differences:

• Added: The field has been added in the retrofit target system
• Removed: The field has been removed in the retrofit target system
• Shorter: The field is shorter in the retrofit target system
• Longer: The field is longer in the retrofit target system
• Typediff: The field has a different type in the retrofit source and target system
• Keydiff: The table key is different in the retrofit source and target system

Check Customizing Objects

This additional function is only visible in the SAP S/4HANA upgrade scenario.

The system shows the possible impact on the customizing objects in a transport request. This helps to
understand whether a customizing object can be retrofitted automatically (green rating) or not (red rating).
The displayed table includes the following columns:

• STRU: Uncritical structure difference in table or view (without impact on transportability)

• STRUCRIT: Critical structure difference in table or view
• SDB: Object is in the simplification database
• BL: Object is on the exclude list
• WL: Object is on the include list
• RES: Overall result ("X" means not transportable and manual retrofit)

5.6.4 Performing the Retrofit

Use this process to find transport requests available for retrofit, check the status of each transport request and
the objects in the requests, and perform the retrofit.

Prerequisites

• Your systems are set up to support the retrofit function, see Setting Up Retrofit [page 354].
• In both development systems and in the 000 clients of these systems, you have the required
authorizations.
• You have created transport requests for the retrofit in the retrofit system into which you want to import the
changes from the maintenance system.

Change Control Management

560 PUBLIC Quality Gate Management
• For Change Request Management: Your change document has the status Successfully Tested, Authorized
for Production, Imported into Production or Confirmed (urgent change) or Successfully Tested (normal
change, standard change).
• For standalone retrofit: You have performed the preparation as explained in Standalone Retrofit [page
356].

Context

You can use retrofit with a Change Control Management scenario (Change Request Management or Quality
Gate Management) or standalone.

 Note

To see explanations for all symbols used on the screen, select Legend. For more information, see Additional
Functions in Retrofit [page 343].

Procedure

1. To see the transport requests available for the selected retrofit system, start the retrofit process.

• For Change Request Management: In your change document, select Actions Start Retrofit .
• For Quality Gate Management: Select Scenario Transport Start Retrofit .
• For Standalone Retrofit (without Change Control Management scenario), you start the retrofit in the
administration cockpit, directly from the task list.

By default, the system only displays transport requests that are released and those for which the retrofit
isn’t finished yet.

Transport requests are categorized (green, yellow, red) according to the objects on the transport.

 Note

You must process the transport requests in the specified sequence, matching the release date of the
source transport request.

2. For each transport request, specify the retrofit request in the retrofit system into which the changes are to
be imported.

You see the transport requests owned by you and the transports requests in which you have a task. The
transport request in the system determines the adjustment.
3. Open the respective object list of a transport request and check the retrofit status for each of the objects.

The color (green, yellow, and red) indicates the status of the object. If the retrofit has been implemented,
the implementation status is “I”. You can set a status for multiple objects.

You can filter the objects according to their status. You can also compare the objects in the source and
retrofit systems. The object list shows the specific target transport request into which an object was

Change Control Management

Quality Gate Management PUBLIC 561
 transported. Correction workbench objects (SCWB scenario) can have a different target transport request
depending on the transport requests in which the objects were locked in the retrofit system.
4. Select the transport request you want to process, and choose a retrofit method.

• Retrofit for All Categories: The retrofit is performed for all objects in this transport request. The relevant
method is applied based on the object type and status.
• Auto-Import: The retrofit is performed for the objects that can be imported automatically. The system
collects all objects that don’t have any conflicts in a transport of copies. The system imports the
transport of copies directly into the retrofit development system and copies them to the target
transport request, in order to distribute them to the development implementation system landscape.
• Transfer with SCWB: The retrofit is performed for the objects supported by the Correction Workbench.
• Transfer with BC Set: The retrofit is performed for the objects supported by BC Sets.

For transport requests containing green, yellow, and red objects, use the functionalities and procedures in
the following order:
a. Green objects can be imported automatically.
b. Yellow objects can be retrofitted with BC-Sets or the SCWB.
c. Red object must be retrofitted manually.
5. Before an automatic import, the system always rechecks the retrofit classification to ensure consistency
and security. If there are any cross-system object locks that were not detected before (that is, a former
conflict-free object now causes a conflict with the retrofit system), a popup informs you that a repeated
check of retrofit data has returned differences in categorization. In this popup, you have the following
options to proceed:
• Close/Display object list – Toggle list with changed classification objects
• Help  – Shows a help text explaining the issue shown here in more detail
• Recalculate category and proceed – Recreate the retrofit data to resolve the conflicts shown and
continue with the retrofit process.
• Ignore warnings and proceed – Ignore the conflicts shown and continue with retrofit process. You may
risk unwanted overwriting of objects in target system.
• Cancel  – Cancel retrofit process and return to retrofit overview screen with the processing log. All
activities you made on this popup are logged here.
6. Use the retrofit status inquiry to state whether the retrofit was completed successfully.

You must specify this because the absence of object transfer warnings only means that there were no
technical system errors. Cancelled procedures don’t cause errors, so you must confirm that you have
completed the procedure successfully, manually.
• When you set the retrofit to completed successfully, the transport requests no longer appear in the
transport request overview for the retrofit.
• If you specify the retrofit as not completed successfully, the transport requests remain in the transport
request overview for the retrofit, and continue to show the retrofit status Process Retrofit.

Results

• The monitored transport from the maintenance system into the development system is completed.
• In the task list daily overview, the system shows the entry Start Retrofit at the time that you executed the
retrofit.

Change Control Management

562 PUBLIC Quality Gate Management
Next Steps

To leave the retrofit transport request window, choose End.

To display the retrofit application log, double-click on Start Retrofit in the daily overview. The log displays all
messages for the retrofit steps. You can also display the retrofit status in the WebClient UI, in the Transport
Management assignment block.

If an error occurred during the creation of the retrofit data (for example, because no categorization is done, or
the RFC connection wasn’t available), you can choose Additional Functions Create Retrofit Data Again to
create new retrofit data for the selected transport request. Note that the latest versions of the relevant objects
are used.

 Note

You can change the recheck settings in Customizing under SAP Solution Manager Capabilities
Change Request Management Retrofit Maintenance of Retrofit Parameters .

Related Information

Change Documents [page 26]

Managing Transport Requests [page 118]

5.6.5 Tool-Assisted Retrofit

Objects with cross-system object locks in the retrofit system, or that were changed in the retrofit system, can
be retrofitted with postprocessing tools.

For such semi-automatic retrofit, you can use the following tools:

• Correction Workbench (transaction SCWB): For changes to program, dictionary, and documentation
objects (in transport requests of type “Workbench”)
• Business Configuration Sets (BC Sets): For changes to Customizing content (in transport requests of type
“Customizing”)

Features

• Detailed change display in the merge editor, comprising the split-screen editor and the table changes
display
• Traffic light icons that indicate which objects are changed when the changes are copied, and whether the
changes can be copied completely, partially, or not at all

Change Control Management

Quality Gate Management PUBLIC 563
More Information

• Merge Editor [page 352]

• Split-Screen Editor [page 353]
• Business Configuration Sets

5.6.5.1 Retrofit Using the Correction Workbench (SCWB)

Use the Correction Workbench for changes to program, dictionary, and documentation objects.

Prerequisites

• A trusted RFC connection has been established from the retrofit system to the development system.

 Note

The user performing the retrofit needs sufficient authorization to create RFC connections on the
managed systems, because the RFC connection is generated automatically when the first retrofit
activity is performed with the Correction Workbench.

• You have prepared the retrofit. For more information, see Retrofitting Transport Requests [page 345].
• The selection screen for transport requests is currently displayed.

Context

You can use the Correction Workbench to copy changes that you made in the development or maintenance
systems and that are not imported automatically. The Correction Workbench performs a remote delta
comparison between the retrofit system and the development system.

Procedure

1. Select your change request or task and choose Transfer with SCWB.

The Confirm Changes dialog box appears, containing a list of all changed repository objects.

 Note

A traffic light symbol indicates whether or not the system can copy the change automatically. You can
find more information about the traffic light icons under Confirm Changes [page 351].

Change Control Management

564 PUBLIC Quality Gate Management
  Caution

A green traffic light does not mean that the system can copy the changes completely. If the starting
status is different in the source system and the retrofit system, the green traffic light does not
guarantee that copying the changes result in a program that is syntactically and semantically correct.

You must check the accuracy of the program yourself after copying the changes. This is your
responsibility.

2. Note the detailed change display (Merge Editor [page 352]) and the messages displayed for the object.

To access the detailed change display for an object, click the object name in question.

 Note

If necessary, you can make manual adjustments to source code changes here (see Splitscreen Editor
[page 353]). This type of adjustment isn’t possible for non-source code type repository objects (such
as function modules).

3. If you want to copy the changes, select all objects to be changed that have either a green traffic light
(complete copy possible) or a yellow one (limited copy possible). Confirm the dialog with the list of objects
to be changed.

 Caution

The system only changes objects that you have selected.

At first, the system saves the changed objects as inactive versions in the database.

The Inactive Objects Belonging to <USERNAME> dialog box appears.

4. Activate the changed objects and confirm by choosing Continue.

The system checks the syntax in the changed objects. If it finds any syntax errors, the system cancels
activation.
5. Confirm the syntax check.

The Retrofit Status Query dialog box appears.

6. Choose Yes, No or Cancel.

Using a traffic light display, the system creates a log of the status of the change copy and the retrofit in the
task list.

Results

You can now test the semantic and syntactical accuracy of the change that you’ve copied in the retrofit system.
If you don’t find any errors, you can release the change request previously created in the retrofit system.

Change Control Management

Quality Gate Management PUBLIC 565
Next Steps

If not all objects were processed successfully with Transfer with SCWB, repeat the procedure with the different
target requests in which the target objects were locked in the retrofit system until all objects are successfully
transferred into the retrofit system.

5.6.5.2 Retrofit Using Business Configuration Sets

The system creates the Business Configuration set (BC-Set) locally on the development system. During the
retrofit process, the system transfers it to the retrofit system and it gets activated there.

Prerequisites

• You have established a trusted RFC connection from the development system to the retrofit system.

 Note

The user performing the retrofit needs sufficient authorization to create RFC connections on the
managed systems, because the RFC connection is generated automatically when the first retrofit
activity is performed with BC sets.

• You have switched on the deletion functionality for BC sets. Call transaction SCPR20 and go to Utilities
User Settings Maint. Transaction .

5.6.5.3 Confirm Changes

This dialog box indicates which objects will be changed by copying the changes, and whether the changes can
be copied completely, in part or not at all. If you confirm this dialog, the system copies the changes to the
specified objects. If you cancel, the system will not make any changes.

Features

Traffic light icons show you whether the system can copy the changes:

• Green traffic light: The system can copy the changes completely as they are.
• Yellow traffic light: The system can only copy the changes in part.
To ensure that the object changes are implemented correctly, you can use the split-screen editor to adjust
corrections to the source text in a repository object. Corrections to other types of data, such as the
properties and parameters of a repository object, can be displayed but not changed.
To open the the object change display screen and check object changes or edit the source code, click the
object name or the traffic light icon.

Change Control Management

566 PUBLIC Quality Gate Management
• Red traffic light: The system cannot copy the object changes.
This can have various causes, such as the object not being supported by this function, being locked in
another change request, or not existing.

There’s a message text for each object (for example, “changes have not been copied completely”). Select this
message to read a long text with detailed information.

5.6.5.4 Merge Editor

The merge editor shows the changes made to a repository object when you copy an object change. If the
changes are already in your system, completely or partially, the system tells you so. The system also tells you if
it can’t copy the change because of differences between the source and retrofit systems.

Features

The Merge Editor has two subfunctions:

• Split-screen editor:
This function provides a detailed display of all changes to the source text in a repository object. You can
also adjust the changes manually here.
• Display table changes:
This function provides a detailed display of all changes to the table entries for a repository object. Unlike in
the split-screen editor, you can’t make manual changes here.

 Caution

This is an expert function that requires detailed knowledge of ABAP Workbench. The main purpose of
this function is for troubleshooting by SAP support.

Activities

Source text changes

Source text changes are shown in the split-screen editor [page 353].

Table content changes

The non-source text parts of a repository object are put in database tables. The change display shows the table
contents for a repository object, with the changes to be made to it. This display helps experts to troubleshoot
when problems arise while copying changes. You can’t change table contents manually. The change display for
a table contains the entire table contents plus additional information about changes made or not made. The
first column in the display contains a symbol specifying which operation is to be performed on a table entry.

Change Control Management

Quality Gate Management PUBLIC 567
You can do the following:

• Insert a row
• Delete a row
• Change non-key fields
• Move a row and change non-key fields. (In this case, the first two columns are used for the operation.)
• Make no changes to the row

A traffic light symbol in the second column indicates whether the operation is possible. The remaining columns
contain the table content. The display contains rows with additional information about the changes to be
made, as well as the table contents rows. If you copy changes, this additional information is not written to the
database.

• For non-key field changes, the old field value is displayed in an additional row directly below the changed
table row. If you can’t change the field value, the unchanged row is displayed in the table row, and the old
row to be deleted and the new value in two rows below it.
• If a row can’t be inserted because the insertion position - the row that should be directly before the
insertion position - can’t be found, the system displays the row to be inserted and the key values of the row
that couldn’t be found, in two additional rows at the end of the table.
• Rows to be deleted are displayed in additional rows.

Changes to files
Files in repository objects are not changed when changes are copied, they’re just created or switched.
Examples of this are Mime objects or files used by Internet Transaction Server as Mime objects. Whenever
you copy changes, the system displays the files to be deleted or created. To display the files, double-click on
the entry in the navigation area, or select the entry and choose F2.

5.6.5.5 Split-Screen Editor

In the split-screen editor, you see the details of all changes to the source text of a repository object. You can
adjust the changes to your own modifications here.

Features

The split-screen editor has two areas:

On the left-hand side, you see the source text as it appears after copying changes. Next to the source text rows,
symbols indicate the changes:

• Context rows, that is, unchanged rows that system used to find the position at which to make changes.

• Inserted rows

• Deleted rows

• Unchanged rows

On the right-hand side, you see deleted program components and corrections that the system cannot
automatically take over. These are flagged by symbols as context, delete, and inset blocks.

Change Control Management

568 PUBLIC Quality Gate Management
Activities

On the left-hand side, you can:

• Edit manually
• Select, delete, copy, and insert blocks
To select a block and highlight it, position the cursor on the header row and choose Select.
You can also select rows. Position the cursor on the first row of the block you want to select, and choose
Select. Then position the cursor on the last row and choose Select again.
• Reset all changes that you have made in the split-screen editor, one-by-one, with Reset Changes (Undo)
• Restore changes that have been reset, with Restore Previous Status (Redo)
• Navigate forward to the next change, or back to the last one, with the arrow keys
• Merge two rows with Concatenate
The Undo/Redo function appears between the left and right-hand side of the editor, whenever a block is
inserted or deleted. You can use these functions to reset or restore individual changes. When you do this,
individual delete and insert blocks are swapped over.

5.6.6 Setting Up Retrofit

Your system must be configured to use retrofit.

Procedure

1. In the managed systems, implement SAP Note 1703391 .

2. Open SAP Solution Manager Configuration (transaction SOLMAN_SETUP) scenario Change Control
Management and perform the required settings in the following guided procedures:

a. Change Request Management Configure Retrofit

b. Managed System Setup Configure Retrofit

 Note

If you want to use cross-release retrofit, ensure that you have activated the Cross-Release Retrofit
parameter and that you have defined for which systems the cross-release retrofit is to be allowed,
under Define System-Specific Retrofit Settings.

Do not activate the Cross-Release Retrofit parameter and the Cross Release Checks for S/4HANA
parameter in parallel for the same retrofit target system.

 Note

If you want to use the SAP S/4 HANA conversion check enhancement, ensure that you have
activated the Cross Release Checks for S/4 HANA parameter, under Define Retrofit Parameters. For
more information, see SAP S/4HANA Upgrade Scenario [page 358].

Change Control Management

Quality Gate Management PUBLIC 569
 To know more about the checks that are performed if this option is chosen, uncollapse the Checks
Performed table:

Checks Performed
Conflict check Check if the table key was already changed in S/
4HANA (customizing conflict).

Simplification DB check Check if the customizing object is listed in the SAP S/

4HANA simplification DB as part of a relevant release
(between the retrofit source and target release).

Exclusion check Check if the object is added in the customer-individ-

ual exclude list.

Inclusion check Check if the object is included in the customer-indi-

vidual allow list. The allow list can overrule the previ-
ous checks (except for the conflict check) if a test
shows that the object can be retrofitted automati-
cally. This can be evaluated for frequently changed
customizing tables.

Structure check Check if the technical structure of the table or view is

different in source and target (for object types: TABU,
VDAT, CDAT, TDAT, TLOGO).

3. Make sure both systems that are to be part of the retrofit scenario are in the same transport management
system (TMS) domain or in linked TMS domains.
4. Activate the retrofit function in SAP Solution Manager. For more information about using an RFC trusted/
trusting relationship between two SAP systems, see System Users and RFC Destinations with Trusted
Systems.
5. Activate the cross-system object lock globally. In the administration cockpit navigate to Cross-System
Object Lock and Downgrade Protection Cross-System Object Lock and Downgrade Protection Settings
Activate Cross-System Object Lock .
6. Activate cross-system object lock for the retrofit target system. In the administration cockpit, navigate to
Landscape Overview and activate the Upon-Saving Check for the retrofit target system. Add BACK RFC
user authorizations as described in SAP Note 2745405 .
7. Set up the following RFC connections in SAP Solution Manager, for each working client specified in the
logical components used to represent each system landscape, the maintenance landscape, and the new
development landscape. This includes the TMS landscape domain controller systems.
• SM_<SID>CLNT<...>_TMW
• SM_<SID>CLNT<...>_TRUSTED

These RFC connections must be established from SAP Solution Manager to the development landscape
and from SAP Solution Manager to the maintenance landscape.

 Note

Additional RFC connections are created automatically when the retrofit scenario is activated in SAP
Solution Manager.

For more information, see SAP Note 1175098 .

Change Control Management

570 PUBLIC Quality Gate Management
8. In both development systems, assign the following authorization objects to the users who are going to
perform retrofit:
• S_RFC_ADM
• S_TRANSPORT
• S_SYS_RWBO
9. Define a change control landscape that contains development systems and retrofit systems.
10. For managed systems used as retrofit systems, be aware of the following conditions:

If a client is assigned to a productive client role, the BC Set function is disabled for all system clients. You
can avoid this by selecting a nonproductive client role in the system.

In addition, if a client is not assigned to any client role, set the role to “Customizing” to activate the BC Set
for retrofit. To activate the BC Set function for the logical system, proceed as follows:
a. Call transaction SCC4.
b. In edit mode, double-click on the respective client to open the Details screen.
c. Set the client role to Customizing.
d. Save your changes.

Next Steps

If you want to use the standalone retrofit function without Change Request Management or Quality Gate
Management, proceed as explained in Standalone Retrofit [page 356].

If you want to use retrofit for SAP S/4HANA in your SAP S/4HANA landscape with additional functionality,
proceed as explained in SAP S/4HANA Upgrade Scenario [page 358].

To check your retrofit configuration for your entire landscape, you can use the
RETRO_SERVICE_CONFIG_CHECK report. For more information, see the report documentation.

5.6.7 Standalone Retrofit

You can use the retrofit functions without the Change Control Management scenarios (Change Request
Management or Quality Gate Management). This approach includes all standard retrofit functions, however,
you handle the retrofit functions via the task list.

Prerequisites

You made the settings as explained in Setting Up Retrofit [page 354].

For standalone retrofit, perform the following additional preparatory steps:

1. In SAP Solution Manager Configuration (transaction SOLMAN_SETUP), configure the required settings
under Change Control Management Managed System Setup Configure Extended Functions
Configure Retrofit .

Change Control Management

Quality Gate Management PUBLIC 571
2. In SAP Solution Manager Configuration, under Change Control Management Change Request
Management Setup Downgrade Protection and Retrofit Configure Retrofit Define Retrofit
Parameters , activate the STANDALONE parameter.
3. Create a change cycle for the implementation landscape for assigning transport requests that are not
yet assigned to a cycle. You do this so that you can use them within the Change Request Management
framework.
4. Create a change cycle for the maintenance landscape for assigning transport requests that are not yet
assigned to a change cycle.
5. Implement the Business Add-In CTS_EXPORT_FEEDBACK in accordance with SAP Note 2179147 .
6. In SAP Solution Manager Configuration, under Change Control Management Managed System Setup
Configure Extended Functions Configure Retrofit Prepare Implementation Landscape for Retrofit ,
select the already existing transport requests created in the development system of the implementation
landscape that you want to be included in the standalone retrofit scenario and register them to the cycle
created for the implementation landscape.
This creates the entries in table /TMWFLOW/CTS_MAP for the mapped CTS projects to the CTS project
created for the implementation cycle and also the CSOL entries for the corresponding objects in these
transport requests. These CSOL entries are needed for retrofit.
7. In SAP Solution Manager Configuration, under Change Control Management Managed System Setup
Configure Extended Functions Configure Retrofit Prepare Maintenance Landscape for Retrofit , select
the already existing transport requests created in the development system of the maintenance landscape
that you want to be included in the standalone retrofit scenario and register them to the cycle created for
the Maintenance landscape.
This creates the entries in table /TMWFLOW/CTS_MAP for the mapped CTS projects to the CTS project
created for the maintenance cycle and also the retrofit data for the corresponding objects in these released
transport requests.
Note that for the creation of retrofit entries, the active version of the object is used.

Context

You can use this approach and start using Change Control Management later on.

Procedure

1. In the Administration Cockpit, in the task list, create and release transport requests.
2. In the relevant system, for example, in the implementation system, create the target transport request.

The system creates the data for the retrofit process.

3. Start the retrofit by executing the relevant task in the cycle that was created for the maintenance
landscape.

Change Control Management

572 PUBLIC Quality Gate Management
Next Steps

Performing the Retrofit [page 345]

If you want to use retrofit for SAP S/4HANA in your SAP S/4HANA landscape with additional functionality,
proceed as explained in SAP S/4HANA Upgrade Scenario [page 358].

5.6.8 SAP S/4HANA Upgrade Scenario

Use retrofit for SAP S/4HANA in your SAP S/4HANA landscape with additional functionality. This includes
advanced checks (ATC checks and customizing checks) for compatibility when synchronizing workbench and
customizing objects from a lower to a higher SAP S/4HANA release or support package level.

Prerequisites

• You have set up retrofit either as part of a Change Control Management scenario as explained in Setting Up
Retrofit [page 354] or as a standalone function as explained in Standalone Retrofit [page 356].
• All the included systems are SAP S/4HANA systems (source and target).
• The landscape management database (LMDB) contains the correct information of the retrofit system.
Therefore, the product version (SAP S/4HANA <target release>) and product instance (SAP S/
4HANA server) must be maintained.
• You have configured an ATC Hub (central scenario) and connected the development system (retrofit
source system) as an Object Provider (as described in the document Custom Code Migration Guide for SAP
S/4HANA available in the SAP Help Portal in the section Conversion & Upgrade Assets).

Procedure

Configuring ATC Hub Checks for Custom Code

1. Connect SAP Solution Manager to the ATC Hub.

1. In SAP Solution Manager, use transaction DNO_CUST04.
2. Specify the field name and field value. Entries for name, description and seq. No. are optional.
3. As the field name, enter ATC_HUB_RFC.
4. For the field value, enter a connection that has enough authorizations to start remote ATC checks in
the ATC Hub system (for example the SAP TMW connection SM_<SID>CLNT<CLNT>_TMW).
5. Use transaction SM30 to maintain the table /TMWFLOW/RSCENS4 with the following values:
1. ExtSID: Enter the SID of your retrofit target system.
2. ATC Check: X
3. Check Variant: If left empty, the standard variant S4HANA_READINESS_<target_release> is
used for the ATC check in the retrofit system. Only enter a variant name if you want to use a
modified version of this variant.

Change Control Management

Quality Gate Management PUBLIC 573
Configuring SAP S/4HANA Checks for Customizing

1. Implement the SAP Notes 2825417 and 2841592 in the managed development systems. If you have
maintained the parameter ATC_HUB_RFC in transaction DNO_CUST04 of SAP Solution Manager, these
notes must also be implemented in the ATC Hub system.
2. Set up custom SAP S/4HANA retrofit checks.
1. In SAP Solution Manager, use transaction SM30 to edit the table /TMWFLOW/RCONFIG and set the
parameter SCEN_S4CHK to Active.
2. Use transaction SM30 to maintain the table /TMWFLOW/RSCENS4 with the following values:
1. ExtSID: Add the SID of your retrofit target system.
2. Cus. Check: X
3. Update the simplification database. If you have specified an ATC_HUB_RFC in transaction DNO_CUST04,
you must update the simplification database in the ATC Hub system. If you haven’t specified an
ATC_HUB_RFC, you must update the simplification database in the retrofit target system:
1. Follow the steps described in SAP Note 2241080 .
4. (Optional) Maintain the exclude list that can be used to categorize incompatible customizing tables or
views for manual retrofit (red category). This can be necessary for customizing certain third-party add-ons.
For SAP standard objects, this is not necessary in the SAP S/4HANA upgrade scenario.
1. Check which of your third-party add-ons are compatible.
2. Add any incompatible components to the list by using transaction SM30 for SAP Solution Manager and
maintaining the table /TMWFLOW/S4BLACK as follows:
1. PgID: Enter a program ID, for example R3TR.
2. Obj.: Enter a DDIC object type, for example TABL.
3. Object Name: Enter an object name.
4. Software Component: Enter a software component, for example S4CORE.
5. SAP Release: Specify the release with which the incompatible change was introduced, for example
102.
6. SP Level: Specify the SP level with which the incompatible change was introduced.
7. Short Description: Add a description.
5. (Optional) Maintain the include list to allow certain customizing tables and views to be retrofitted by
auto-import (green category) even though they are listed in the simplification database. For SAP standard
objects, this is not necessary in the SAP S/4HANA upgrade scenario.
1. Check which objects are compatible but are listed in the simplification database.
2. Maintain the table /TMWFLOW/S4WHITE in SAP Solution Manager by using transaction SM30.

 Note

The columns are the same as the ones in the exclude list.

Related Information

• Additional Functions in Retrofit [page 343]

• Information for the Integration of the ABAP Test Cockpit (ATC) with Change Request Management in SAP
Note 2590595
• Retrofit to SAP S/4HANA in SAP Note 2652106

Change Control Management

574 PUBLIC Quality Gate Management
5.7 Downgrade Protection
The downgrade protection (DGP) function tracks objects in transport requests, and reports conflicts in five
scenarios when an object that is saved in two or more transport requests is released, reassigned, or imported.

Use

Downgrade protection is available in Change Request Management and in Quality Gate Management. The
function is identical, however, the user interfaces and the related terminology may differ.

Downgrade protection is available for ABAP systems as well as for non-ABAP systems. For non-ABAP systems,
only imminent downgrade and predecessor checks are supported.

For Git-enabled changes (Change Request Management only), cross-system object lock (CSOL), release check,
and reassign check are available.

 Tip

If you use these functions on a regular basis and with a large amount of data, consider using the
housekeeping reports as described in SAP Note 2138047 .

Prerequisites

• You have configured downgrade protection and the cross-system object lock in the SAP Solution Manager
Configuration (transaction SOLMAN_SETUP), in the Change Request Management or the Quality Gate
Management scenario, under Set up Downgrade Protection and Retrofit Configure CSOL and DGP ,
globally, and locally in the development system.

 Note

You can configure the conflict criticality for each check type as well as the systems that have custom
DGP responses.

For more information, see the detailed documentation for the activities in the Configure CSOL and DGP
substep of your scenario in SAP Solution Manager Configuration (transaction SOLMAN_SETUP).

• The SAP Solution Manager system has an up-to-date CTS plug-in version installed.
For more information, see SAP Note 1665940 .
The import check logic depends on the central CTS import check logic for downgrade protection, which is
a part of the CTS plug-in.
• If you want to use the predecessor and the imminent downgrade checks, you have installed and
distributed the CTS service plug-in to the managed systems (including development, quality assurance,
and production systems). For more information, see SAP Note 1665940 .
• Authorization object SM_CM_DGPN has been assigned to your role so that you can explicitly ignore conflicts.
If you don’t have one of the following roles (which are in the standard SAP delivery), the authorization
object must be assigned to your user.

Change Control Management

Quality Gate Management PUBLIC 575
 • SAP_CM_SMAN_CHANGE_MANAGER (Change Manager)
• SAP_CM_SMAN_OPERATOR (IT Operator)
• SAP_CM_SMAN_ADMINISTRATOR (Administrator)
• SAP_CM_SMAN_DEVELOPER (Developer)
• SAP_CM_SMAN_TESTER (Tester)
• SAP_SM_QGM_CM_CHANGE (Change Manager)
• SAP_SM_QGM_CM_TRANSPORT (IT Operator)
• SAP_SM_QGM_CM_ALL (Administrator)

Features

• Integration in the WebClient UI

In Change Request Management, the Transport-Related Checks assignment block is available for change
cycles and change documents. Detected conflicts are displayed in the assignment block.
In Quality Gate Management, information related to downgrade protection is displayed in the Downgrade
Protection dialog box.
• Manual and automatic checks:
• In Change Request Management, you can start downgrade checks from the Transport-Related Checks
assignment block. In Change Request Management, you can also start a downgrade check from a task
list. If a conflict is detected, a popup notifies you, and you can choose to ignore the conflict or to cancel
the operation.
In Quality Gate Management, you can start the check manually with Actions Transport-Related
Checks (in the scenario overview) or Actions Downgrade Protection (in the change overview).
The system analyzes potential release check conflicts for all open transport requests in the
development system, and import check conflicts for all released transport requests in all systems
into which they can be imported. This helps you to handle the conflicts before triggering the transport.
When you do a manual check in the assignment block, the system performs the DGP check. Detected
conflicts are reported as warnings.
• Downgrade checks run automatically when transport requests are released, imported, decoupled, or
assigned. They are also triggered when a change document is reassigned.
If a conflict is detected, you can choose to ignore it and continue the operation. Ignored conflicts are
shown in the assignment block or dialog box.
You can configure the system so that developers and testers can ignore any automatic check. For
more information, see the documentation in the Customizing activities for downgrade protection. You
can customize the DGP check as “Silent” mode: During release and import of transport requests, the
system doesn’t perform the DGP check but skips it directly.

 Note

The automatic check analyzes a smaller number of transport requests: The manual check analyzes
all open transport requests (release check) and all importable transport requests (import check),
including all corresponding target systems. The automatic check analyzes only the transport requests
to be released or imported, and only the relevant target systems.

Change Control Management

576 PUBLIC Quality Gate Management
Downgrade Check Scenarios

The following downgrade checks can be performed:

Cross-System Object Lock

The cross-system object lock (CSOL) ensures that when an object is changed in a managed system, it is locked
in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being
made to this object in any other transport request.

Release Check
When you release a transport request, downgrade protection can detect conflicts for objects in transport
requests. The conflicts are the same as those displayed by the cross-system object lock when saving the
objects to the transport requests.

Reassign Check
The system performs this check when you reassign a change document or assign or decouple transport
requests in a change document.

Predecessor Check
The system can detect conflicting predecessors, that is, preceding transport requests containing conflicts, at
the time of importing transport requests or transports of copies to the production or quality assurance system.

Imminent Check
The system can detect impending (imminent) downgrade conflicts when transport requests are imported. This
kind of conflict would become an actual downgrade if you ignored the conflict.

 Note

Import checks depend on the transport requests being imported. Any conflicts found while importing a
change cycle or urgent change task list are displayed in the Transport-Related Checks assignment block of
the change cycle document. Any conflicts found while importing a change document are displayed in the
Transport-Related Checks assignment block of the change document.

The check for potential downgrades is carried out both when you perform a preliminary import of a change
(normal change or urgent change) and when you import via the task list for the change cycle. The duplicate
check ensures that potential downgrades are identified even if changes belong to the same change cycle.
If you plan to ignore the conflicts, pay attention to the type of import operation you’re performing. If you
perform a preliminary import, the system prompts you to ignore the conflicts at change level. When you
later import the changes at cycle level, the system prompts you to ignore the changes again, but this time
at cycle level. If you import changes only at cycle level, you have to ignore only the cycle-level conflicts.

 Caution

Release check conflicts are sometimes not seen during an import check. This is because the release
check reports conflicts between the same objects in different transport requests to be imported into the
production system. In one particular case, they are not reported as import check conflicts: when the import
order of the transport requests is the same as the release order. For example, if TR1 and TR2 have modified
the same object, they result in release check conflicts. However, if TR1 is released first, TR2 is released

Change Control Management

Quality Gate Management PUBLIC 577
 second, and TR1 is imported first, TR2 is imported second, the system reports no conflicts during the
predecessor check and the imminent check.

Related Information

Cross-System Object Lock [page 363]

Technical Details of the CTS Plug-In [page 383]
Performing Transport-Related Checks [page 150]
Using the Transport-Related Checks Assignment Block [page 165]
Release Check [page 373]
Reassign Check [page 374]
Predecessor Check [page 376]
Imminent Check [page 377]
Using the CTS Plug-In Management Web UI [page 382]

5.7.1 Cross-System Object Lock

Use

The cross-system object lock (CSOL) ensures that when an object is changed in a managed system, it is locked
in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being
made to this object in any other transport request. This applies to all managed systems and clients for which
the cross-system lock is active and prevents version conflicts at an early stage.

Regardless of whether you use a separate development system or share the same system for your projects,
you must avoid different teams working on the same object concurrently if the changes are to be imported
in the same production system. It can lead to inconsistencies. The object must stay locked until it has been
imported in the production system.

Prerequisites

The cross-system object lock has been configured and activated in SAP Solution Manager Configuration
(transaction SOLMAN_SETUP) by completing the activities in the Change Request Management scenario or the
Quality Gate Management scenario in the Configure CSOL and DGP sub-step.

Change Control Management

578 PUBLIC Quality Gate Management
Features

• You can activate or deactivate the cross-system object lock.

When the cross-system object lock is active, the system can detect conflicts between objects in different
transport requests that are part of the same production logical system (system and client) as their
transport target, depending on the type of object that was changed.
• When the cross-system object lock is active, you can activate downgrade protection. Downgrade
protection cannot be activated if the cross-system object lock is inactive.
• You can define your cross-system object lock conflict scenario by choosing between the default mode
and the expert mode. The default conflict analysis scenario is cross-cycle (cycle relation Cross) with
change type relation Urgent Only. In the expert mode, you define customized conflict scenarios for the
cross-system object lock. For more information, see the system documentation of the activity.
• If you want to get notified about the cross-system object lock conflicts, you can select a Warning Only
option. Only a warning message is displayed for all conflicts. You can still save your data. Be aware that
when choosing this option, you might run the risk of possible software downgrades when older transport
requests overwrite more recent transports containing the same objects.

 Caution

Transport requests that are assigned neither to a Change Request Management cycle nor to a quality
gate management cycle are not taken into account during conflict analysis.

• If you are using the Stop at Error check mode for the CSOL check, you can configure that the check reports
only a warning, and not an error, if it detects conflicts for specific Customizing objects and Workbench
objects. for this, you specify these objects in the Administration Cockpit on the Cross-System Object
Lock and Downgrade Protection tab. On the Cross-System Object Lock and Downgrade Protection Settings
subtab, you can configure these settings in the Object-Specific Warning Mode Configuration section .
• Defect corrections: You will not be notified about cross-system object lock conflicts that are detected
during upon-saving checks and release checks, and when the conflicts originate from a defect correction
itself, from a normal change, or a standard change in same cycle.
• You can define your own conflict scenario for the cross-system object lock. You can label the conflict with
message types such as Error or Warning, depending on your scenario. The final conflict message to be
displayed contains the following information:
• Conflict type (error or warning)
• Affected transport requests
• Owners of the transport requests
It depends on the conflict type whether you can continue to change an object.

Extended Features

• The conflict analysis tracks the objects stored in transport requests using lock entries. Within one
transport request and one production logical system, there are records for each object in the transport
request.

 Note

In the central SAP Solution Manager system, the cross-system object lock manager (in the
Administration Cockpit) provides an overview of all current lock entries. The entries are displayed
in table form, and can be selected if you need to delete them, for example.

Change Control Management

Quality Gate Management PUBLIC 579
• You can activate and deactivate the cross-system object lock in each managed system with the
TMW_CONTROL_PROJECT_LOCK report in the managed system. You can also do this on the Landscape
Overview tab in the administration cockpit by setting the CSOL Check checkbox for managed development
systems.

 Caution

To execute the TMW_CONTROL_PROJECT_LOCK report, you require change authorization for the
Transport Management System.

• You might need to update the central object lock information about a transport request. You can do so by
using the TMW_TRKORR_LOCK_UPDATE report. If you are the owner of the transport request, you have the
required authorization. Enter the name of the transport request for which you want to update the object
lock information.

 Note

If SAP Solution Manager is temporarily unavailable but you still want to change objects in the
development system, use the TMW_CONTROL_PROJECT_LOCK report to deactivate the cross-system
object lock temporarily and change the objects. When SAP Solution Manager is available again, you can
activate the cross-system object lock and run the TMW_TRKORR_LOCK_UPDATE report for the transport
request in which you saved objects during the inactive period.

You can also update the lock entries for a batch of transport requests in the cross-system object lock
manager of the SAP Solution Manager system.

• With regard to the cross-system object lock, the Workbench Organizer provides the following features:
• When changing to edit mode for an object, the system displays a warning message and prompts you to
save any changes as soon as possible.
• When you change transport objects manually, that is, you delete, edit, or merge objects, the lock
entries in SAP Solution Manager are updated automatically.

 Note

To use these features, you have to implement the SAP Notes listed in SAP Note 1900560 in the
development systems in your landscape.

More Information

Conflict Analysis Scenarios [page 369]

Change Control Management

580 PUBLIC Quality Gate Management
5.7.1.1 Track-Specific CSOL Configuration

Use the track-specific configuration to specify cross-system object lock (CSOL) configuration for each
managed development system. These settings override the general settings made when you activate CSOL
globally.

Procedure

1. Go to Administration Cockpit Cross-System Object Lock and Downgrade Protection Cross-System

Object Lock and Downgrade Protection Settings . Under Cross-System Object Lock Configuration, open
Track-Specific Conflict Configuration.

 Note

Any settings that you make or change on this tab are active immediately.

2. Add a new entry and specify the scope by the following categories. You can use an asterisk (“*”) as a
wildcard to allow all possible values of the category.
• Landscape
• Branch
• Cycle type
• Managed development system name
• Managed development system type
• Managed development system client

 Example

If you specify landscape “*”, branch “*”, cycle type “*”, managed development system name “DV1”,
type “ABAP”, client “100”, the CSOL configuration applies to all transport requests created from the
specified development system.

If you specify landscape “LANDSCAPE1”, branch “MAINTENANCE”, cycle type “*”, managed
development system name/type/client “*”, the CSOL configuration row applies to all transport
requests that belong to cycles using the specified change control landscape and branch.

3. Select a CSOL check mode:

• Stop at Error: You can define the conditions that categorize conflicts as error, which the end user
cannot ignore. If the conditions are not met, the conflicts are classified as warning, which the end user
can choose to ignore.
• Warning Only: Any conflicts detected between transport requests are classified as warning, which the
end user can ignore.
• Silent: Any conflicts detected between transport requests are categorized as “information”, and are
only logged in database table /TMWFLOW/CSOLILG.
• Off: CSOL check is switched off for transport requests from the specified development system (or
cycles with the specified landscape, branch, and type).

Change Control Management

Quality Gate Management PUBLIC 581
  Caution

For check modes Warning Only, Silent, and Off, be aware of the risk of possible software downgrades
when newer transport requests overwrite older transports requests containing the same objects.

4. For check mode Stop at Error, specify the conditions that categorize a conflict as error with the following
options:
• Same Development System
• Cycle Relationship
• Change Type Relationship
5. Any settings are active immediately. You don't have to save your changes manually.

CSOL Check Options

For check mode Stop at Error, the following options define the conditions for the conflicts that are classified as
Error, which the end user cannot ignore.

Same Development System

• Inactive (default setting): Conflicts between transport requests are categorized as error unless cycle
relation and change type relation specify otherwise.
• Active: Conflicts between transport requests from different managed development systems are
categorized as a warning. Transport requests from the same managed development system are
categorized as error, unless cycle relation and change type relation specify otherwise.

 Note

Activate this option if you work with retrofit in combination with a maintenance landscape and an
implementation landscape and you want to treat conflicts between the two landscapes as warning, not
as an error.

Cycle Relationship

• All Cycles: Conflicts between transport requests are categorized as error, unless the Same Development
System option or the change type relationship specify otherwise.
• Same Cycle: Conflicts between transport requests from the same cycle are categorized as error, unless
the Same Development System option or the change type relationship specify otherwise. Conflicts between
transport requests from different cycles are categorized as a warning.
• Different Cycles: Conflicts between transport requests from different change cycles are categorized as
error, unless the Same Development System option or the change type relationship specify otherwise.
Conflicts between transport requests from the same cycle are categorized as a warning.

Change Type Relationship

• Both Urgent Changes: Conflicts between transport requests that both belong to urgent changes (or QGM
changes) are categorized as error, unless they are categorized as warning by the Same Development
System option or the cycle Relationship. Other conflicts are handled as warning.

Change Control Management

582 PUBLIC Quality Gate Management
• Either of two is Urgent Change: Conflicts between transport requests of which one belongs to an urgent
change are categorized as error, unless they are categorized as warning by the Same Development System
or the cycle relationship. Other conflicts are classified as warning.
• Any Change Type: Conflicts between transport requests of any change type are categorized as error, unless
they are categorized as warning by the Same Development System option or the cycle relationship.

 Note

Select Both Urgent Changes if you want to prevent conflicts between urgent changes while, at the same
time, importing other types of changes on the cycle level to keep them free from downgrades.

Related Information

Cross-System Object Lock [page 363]

Creating Cross-System Object Lock Entries [page 331]
Conflict Analysis Scenarios [page 369]

5.7.1.2 Creating Cross-System Object Lock Entries

You can manage cross-system object lock entries in the administration cockpit.

Procedure

1. In the administration cockpit, go to Cross-System Object Locks Register .

2. Select a development system or choose all systems. You can also use the following options:

• You can restrict the range of transport requests by request number. For external requests, the
transport request number prefix (containing the external system name) can be different from the
real (internal) source system name.
• You can choose to send e-mail notifications if conflicts are detected: Default recipients are the change
managers (and for Change Control Management, also IT operators) of the change documents or QGM
changes that contain the transport requests with conflicts. You can also enter an additional e-mail
address.

 Note

To send a notification to the change manager and IT operator, the e-mail addresses must be
maintained for their business partners.

The system does not send any e-mail notifications to the transport request owners.

• You can specify the execution time (immediate or scheduled).

3. After you have registered the lock entries, to see the progress, monitor the job log.

Change Control Management

Quality Gate Management PUBLIC 583
 a. Call transaction SM36 (Define Background Job) and select Own jobs.
b. Find job CM_CROSS_SYS_OBJ_LOCK_REGISTER, scheduled to run at the time you specified, and open
Job Log.

When the job is finished, the job log refers to the application log. The application log contains detailed
messages, whereas the job log shows only the job progress.

Results

For each system, the application log displays the final processing result. You see warning messages for
transport requests that cannot be processed, and, for example, if the system does not find an e-mail address.

Next Steps

To check the application log, call transaction SLG1 with object /TMWFLOW/CMSCV and subobject
CROSS_SYS_OBJ_LOCK.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Downgrade Protection [page 360]

5.7.1.3 Conflict Analysis Scenarios

The selected scenario specifies which kind of transport conflict is classified as an error, which in turn means
that the object can’t be changed. All other conflicts cause a warning only; you can decide whether to change
the object.

Features

The conflict analysis function is defined by the relationship between the change cycles, and between the
change transaction types:

• Conflicts between transport requests that belong to the same change cycle and conflicts between
transport requests that belong to different change cycles
• Conflicts for urgent changes and conflicts between transactions of another type (for example, between an
urgent change and a normal change, or between normal changes)

You can use this function in Change Request Management and Quality Gate Management.

Change Control Management

584 PUBLIC Quality Gate Management
Scenarios

By default, it's an error when the conflicting transport requests both are in urgent changes, regardless if they
are in the same or different change cycle. You can select other scenarios.

To select a scenario, go to Administration Cockpit Cross-System Object Lock and Downgrade Protection
Cross-System Object Lock and Downgrade Protection Settings .

Cross-System Object Lock Scenarios

Cycle Relation Change Type Relation Conflict Causing an Error

All Cycles Both Urgent Changes This is the default mode:

An object conflict between transport

requests of two urgent changes, both
belonging to the same or two different
change cycles.

Either of two is Urgent Change An object conflict between two trans-

port requests and at least one of them
is contained in an urgent change, both
belonging to the same or two different
change cycles.

Any Change Type An object conflict between two trans-

port requests for any change type, both
belonging to the same or two different
change cycles.

Same Cycle Both Urgent Changes An object conflict between transport re-
quests of two urgent changes, both be-
longing to the same cycle.

Either of two is Urgent Change An object conflict between two trans-

port requests and at least one of them
is contained in an urgent change, both
belonging to the same cycle.

Any Change Type An object conflict between two trans-

port requests for any change type, both
belonging to the same cycle.

Different Cycles Both Urgent Changes An object conflict between transport re-
quests of two urgent changes, both be-
longing to two different cycles.

Either of two is Urgent Change An object conflict between two trans-

port requests and at least one of them
is contained in an urgent change, both
belonging to two different cycles.

Change Control Management

Quality Gate Management PUBLIC 585
Cycle Relation Change Type Relation Conflict Causing an Error

Any Change Type An object conflict between two trans-

port requests for any change type, both
belonging to different cycles.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Change Cycles [page 28]
Processing Urgent Changes [page 81]
Creating Cross-System Object Lock Entries [page 331]

5.7.1.4 Skipping CSOL and DGP Check for PFCG Roles and
Customizing Objects

Context

In Administration Cockpit, you can configure the cross-system object lock and downgrade protection check to
skip the check for PFCG role objects or for all customizing objects. This can improve the performance of the
check if the transports contain large amounts of PFCG role objects or other customizing objects.

Procedure

1. In the Administration Cockpit, navigate to Cross-System Object Lock and Downgrade Protection Cross-
System Object Lock and Downgrade Protection Settings .
2. In the Cross-System Object Lock and Downgrade Protection Settings, under Advanced Configuration, select
the option for the Role and Customizing Object Check:

• On: Check all PFCG role objects and other customizing objects (This is the default setting.)
• Skip Role Objects Check: Skip the check for PFCG role objects
• Skip All Customizing Objects Checks: Skip the check for all customizing objects.

If you choose Skip Role Objects Check or Skip All Customizing Objects Checks, either only PFCG role
objects or all customizing objects will be filtered out of the conflict calculation.

Change Control Management

586 PUBLIC Quality Gate Management
  Note

CSOL lock entries are still generated for all objects to support the retrofit functionality.

DGP tracking data is still generated for all objects in case the customizing is reset.

5.7.2 Downgrade Protection System Configuration

Use the downgrade protection system configuration to configure the downgrade protection (DGP) for each
managed system. These settings override the general settings made when you activate DGP globally.

Procedure

1. Go to Administration Cockpit Cross-System Object Lock and Downgrade Protection Cross-System

Object Lock and Downgrade Protection Settings Downgrade Protection Configuration Downgrade
Protection System Configuration .

 Note

Settings on this tab are active immediately.

2. Add a new entry and specify the scope with the following categories. You can use an asterisk (*) as a
wildcard to allow all possible values of the category:
• Landscape
• Branch
• Cycle type
• Managed system name
• Managed system type
• Managed system client
• Managed system role
3. Select a DGP check mode:
• Stop: You can define the conditions that categorize conflicts as errors, which the end user cannot
ignore. If the conditions are not met, the conflicts are classified as warnings, which the end user can
choose to ignore.
• Warning: Any conflicts detected between transport requests are classified as warnings, which the end
user can choose to ignore.
• Silent: Any conflicts detected between transport requests are categorized as “information” and are
only logged in the backend database table.
• Off: The DGP check is switched off for transport requests from the specified system (or cycles with the
specified landscape, branch, and type).

 Caution

For check modes Warning, Silent, and Off, be aware of the risk of possible software downgrades when
newer transport requests overwrite older transports requests containing the same objects.

Change Control Management

Quality Gate Management PUBLIC 587
4. Select a DGP check type:
• Release Check: Performs a DGP check before releasing a transport request or transport of copy.
• Reassign Check: Performs a DGP check before assigning a transport request to a change document.
• Predecessor Check: Performs a DGP check before importing a transport request or transport of copy
into the target system.
• Imminent Check: Performs a DGP check before importing a transport request or transport of copy into
the target system.
5. All settings are active immediately. You don't have to save your changes manually.

Check Options

For check type Predecessor Check and Imminent Check, the following option defines whether conflicts that
occur between transport requests from different development systems should be reported or not.

Same Development System

• Inactive (default setting): If conflicts are detected between transport requests, the conflicts are always
reported.
• Active: If conflicts are detected between transport requests, and only if these transport requests are from
the same managed development system, the conflicts are reported. If the transport requests are from
different managed development systems, the conflicts are not reported.

 Note

Activate the Same Development System option if you work with the retrofit function in combination with a
maintenance landscape and an implementation landscape, and you don't intend to treat conflicts between
two transport requests across the two landscapes as a real downgrade. In this case, you can select the
Same Development System option to prevent the conflicts from being reported.

5.7.3 Release Check

Use

The system performs this downgrade check when you release a transport request. The system can detect
conflicts for objects in different transport requests. If a transport request that was released first were to
be imported second, the conflict object would be downgraded. The release check prevents this issue from
occurring.

Prerequisites

For a list of prerequisites, see Downgrade Protection [page 360].

Change Control Management

588 PUBLIC Quality Gate Management
Activities

1. You release a transport request.

2. The system performs the downgrade check.
3. If the system detects a conflict, you are prompted to either cancel the release or (depending on your
authorizations) to ignore the conflict and continue with the release.
• If you cancel the release, the conflicts that were detected are logged. The conflict check results are
displayed in the Downgrade Protection assignment block in Change Request Management or in the
Downgrade Protection dialog box in quality gate management.
• If you ignore the conflicts and continue with the release, the conflicts are archived in the system.

Example

1. You modify function module Z_TEST_FUNC1 and save it in transport request DEVK000001 in change NC1.
2. You release DEVK000001 without noticing any conflicts.
3. You modify the function module again and save it to another transport request, DEVK000002, in change
NC2, bypassing the cross-system object lock warning in the managed system.
4. When you try to release DEVK000002, a conflict is shown.
5. To continue with the release, you can ignore these conflicts. Alternatively, you can import DEVK000001
into the production system by importing it into the quality assurance system, and then import it into the
production system. DEVK000002 can then be released without conflicts.

5.7.4 Reassign Check

This check detects conflicts when you reassign a change, or when you assign or decouple transport requests in
a change document.

If the transport requests belong to different change cycles after one of these actions, the transport requests
might be released and imported in a different order. This type of conflict can cause a downgrade.

Before you carry out any of these actions, consider whether assignment, reassignment, or decoupling can be
avoided.

Prerequisites

For a list of prerequisites, see Downgrade Protection [page 360].

Change Control Management

Quality Gate Management PUBLIC 589
Activities

1. You reassign a change, or you assign or decouple a transport request.

2. You get information about potential conflicts of the involved transport requests.
3. You can either cancel the operation, or ignore the warning and continue.

Example

Example 1

1. You modify function module Z_TEST_FUNC1 and save it to transport request DEVK000001. You release
the transport request.
2. You modify the function module again and save it to transport request DEVK000002, ignoring the warning
about the cross-system object lock. DEVK000001 belongs to change NC1, while DEVK000002 belongs to
change NC2.
3. When you try to reassign change NC2 to another change cycle, potential conflicts with NC1 are detected. A
simulation shows the effects of reassignment.
4. If you ignore the conflicts, NC2 is reassigned.

Example 2

You already have two conflicting transport requests, DEVK000001 and DEVK000002, in changes NC1 and
NC2. When you decouple DEVK000002 from NC2, you get information about the existing conflicts on
DEVK000002. You can continue only if you ignore the conflicts.

Example 3

Transport request DEVK000002 was previously decoupled and has conflicts with DEVK000001 in change NC1.
When you try to assign DEVK000002 to normal change NC2, conflicts are detected. A simulation shows what
would happen if you reassigned DEVK000002 to the normal change.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Reassigning Change Transactions [page 141]
Decoupling Transport Requests in Change Request Management [page 134]
Assigning Transport Requests [page 135]

Change Control Management

590 PUBLIC Quality Gate Management
5.7.5 Predecessor Check

When a transport is imported into the production or quality assurance system, this import check detects
whether there are any conflicting older transport requests. Importing a newer transport request before its
predecessor would cause a downgrade.

 Example

A transport request containing object “A” in a new version is to be imported into a system, while an
older transport request containing the same object “A” is also yet to be released into the same system.
If the more recent transport request is imported before the older transport request, the result is an
imminent downgrade. For business reasons, system administrators generally are instructed to import the
older request, but they must be careful to avoid a downgrade. To prevent such downgrade situations, the
predecessor check reports the initial conflict and stops the import.

Import checks depend on the transport requests being imported. Any conflicts found while importing in a
change cycle task list are displayed in the Transport Related-Checks assignment block of the change cycle
document or in the Transport Related-Checks dialog box in Quality Gate Management. Any conflicts found while
importing a change document are displayed in the same assignment block of the change document.

Prerequisites

For a list of prerequisites, see Downgrade Protection [page 360].

Activities

1. You start to import a transport request.

2. The system performs the downgrade check.
3. If there is a conflict, the import is stopped and you get a message.
You can view the logged conflicts in the Transport Related-Checks assignment block in Change Request
Management and in the Transport Related-Checks dialog box in Quality Gate Management.
4. To continue, you can ignore the conflicts and repeat the import.
Ignored conflicts are archived as conflict history.

Related Information

Conditions for Ignoring Transport Conflicts [page 380]

Change Control Management

Quality Gate Management PUBLIC 591
5.7.6 Imminent Check

Use

The system can detect impending (imminent) downgrade conflicts when transport requests are imported. This
kind of conflict would become an actual downgrade if you ignored the conflict.

 Example

Any kind of transport request (workbench request, a customizing request or a transport of copies)
containing, object “A” is imported on top of another transport request containing the same object “A”
but with a more recent export time stamp. It is also referred to as an “overtaker”. This situation is reported
within Downgrade Protection and the import is canceled.

Prerequisites

See Downgrade Protection [page 360].

Activities

1. When a transport request is imported into the production or quality assurance system, a downgrade check
is performed.
2. If the system detects a conflict, it displays an error message and cancels the import.
The conflicts are logged and displayed in the Downgrade Protection assignment block in Change Request
Management and in the Downgrade Protection dialog box in quality gate management.
3. To import the transport requests, you can ignore the conflicts in the assignment block or dialog box and
repeat the import.
If you ignore the conflicts and continue with the import, the conflicts are archived in the system.

 Recommendation

Do not ignore the imminent downgrade conflicts and continue with the import. Import the transport
requests in the correct order, including the newer request and its predecessor (if the newer request is in the
project import).

5.7.7 Delta Downgrade Protection Check

The delta downgrade protection check (delta DGP check) is an incremental check based on a previous
complete downgrade check.

The delta DGP check is an import check (predecessor or imminent check) check, which is triggered
automatically when you import the transport requests of a change cycle or scenario into the follow-on system

Change Control Management

592 PUBLIC Quality Gate Management
(for example the quality assurance system or production system). You can also trigger it with a manual
downgrade check of the change cycle or QGM scenario. The delta DGP check is intended for the following use
case:

Before a go-live phase, you made a complete manual downgrade check of all transport requests in the change
cycle (or QGM scenario) to identify conflicts before transporting the changes to the follow-on system (for
example, the quality assurance or production system). After this complete downgrade check, new transport
requests have been added to the import buffer of the follow-on system. If you then trigger the import of the
transport requests of the cycle (or scenario) to the follow-on system, instead of a new complete downgrade
check, which would check again all transport requests, a delta DGP check is performed to check only the
transport requests that have been added since the last complete check. Since the delta DGP check checks only
the transport requests that have been added since the last complete downgrade check, the delta DGP check is
much faster than a complete check.

Prerequisites

Downgrade protection performs delta DGP checks only if the following prerequisites are met:

• No imports into the production system happened during or since the last complete downgrade check. If
imports, for example, urgent changes, have been made during or since the last check, a new complete DGP
check is required.
• New transport requests have been added to the import buffer of the follow-on system since the last
complete downgrade check..
• If the change cycle is not cCTS-enabled, it depends on whether the new transport requests have been
added at the end of the import buffer or not:
• A delta DGP check is performed only if the transport request are found at the end of the buffer.
• If they are not at the end of the buffer, it is assumed that the buffer has been manipulated and a new
complete downgrade check is required.

Enabling the Delta Downgrade Protection Check

To enable the delta DGP check, do the following:

1. In transaction SM30 (Maintain Table Views) , open table AGS_WORK_CUSTOM (Workcenter Customizing).
2. In the table, for the parameter key AIC_DGP_DELTA_SWITCH, enter the value X.

Change Control Management

Quality Gate Management PUBLIC 593
5.7.8 Import Groups in Downgrade Protection

An import group comprises transport requests that are imported into the same production system in the
sequence in which they were released. If the same object is changed in different transport requests, but the
transport requests belong to the same import group, there is no risk of a downgrade and thus no conflict.

Use

Import groups are used by the following downgrade protection checks when dealing with conflicts:

• Cross-system object lock

• Release check
• Reassign check

Features

Transport requests belong to the same import group under the following conditions:

• Two transport requests in the same normal change, git-enabled change, standard change, or defect
correction that are on the same transport track
• Two transport requests in the same QGM change or QGM urgent change that are on the same transport
track
• Two transport requests in the same urgent change

 Note

Transport requests in the same urgent change are always imported into the same production system
from one development system. There cannot be two transport tracks in an urgent change.

In all other cases, two transport requests belong to different import groups, for example:

• Two transport requests created from the same task list

• Two transport requests in the same normal change that are on different transport tracks. They can be
imported separately into the production system by transport track, using the CTS project ID.
• One transport request in a normal change and another transport request in an urgent change. They can be
imported into the production system independently.
• Two transport requests in different urgent changes because they can be imported into the production
system independently
• Two transport requests in the same QGM change that are on different transport tracks. They can be
imported separately into the production system, by transport track, using the CTS project ID.
• Two transport requests in different QGM changes. They can be imported into the production system
independently.
• One transport request in Change Request Management and another in QGM. They can be imported
independently.

Change Control Management

594 PUBLIC Quality Gate Management
  Note

Two transport requests created from the same task list can be on the same transport track. In this case,
they don't cause a potential downgrade but they are still in different import groups. This allows for conflict
reporting for task list-only use cases.

The import group function does not prevent downgrades caused by selective imports. Use the downgrade
protection import check for this purpose. During the selective import, downgrade protection may report
new conflicts that were not reported when saving or releasing transport objects.

Related Information

Downgrade Protection [page 360]

Import Strategies: Standard, Status-Dependent, and Selective [page 396]

5.7.9 Conditions for Ignoring Transport Conflicts

For Change Request Management and Quality Gate Management, matrixes display the conditions when
transport conflicts can be ignored by specific business roles.

Default Configuration for Conflict Type

To view and change the default and system-specific settings, go to Administration Cockpit Cross-System
Object Lock and Downgrade Protection Cross-System Object Lock and Downgrade Protection Settings
Downgrade Protection Configuration .

You can choose the check mode based on the type of check, and you can choose to use only warning mode or
stop mode for specific systems

Default Matrix for Conflict Type as in Table Downgrade Conflict Type

Check Type Check Mode

Release check, reassign check Warning mode

Import check (predecessor check, imminent check) Stop mode

In general, errors must be solved, while warnings can be ignored. There are exceptions for particular business
roles, which are highlighted in the following matrixes.

Change Control Management

Quality Gate Management PUBLIC 595
Conflict Matrix for Change Request Management

Trans-
Check port Op- Ignoring Conflict in DGP (or Transport-Related Ignoring Conflict in DGP (or Transport-Re-
Mode eration Checks) Popup lated Checks) Assignment Block

DEV TST ITO CM ADM DEV TST ITO CM ADM

Warning Release          
mode
Reassign      N/A
(assign,
decou-
ple)

Stop Selective      N/A

mode import

Nonse-          
lective
import

Conflict Matrix for Quality Gate Management

Trans-
port
Check Opera- Ignoring Conflict in DGP (or Transport-Related Ignoring Conflict in DGP (or Transport-Related
Mode tion Checks) Dynamic Check Popup Checks) Static Check Popup

DEV TST ITO CM ADM DEV TST ITO CM ADM

Warning Release          
mode
Reas-      N/A
sign (as-
sign, de-
couple)

Stop Import          
mode (either
selec-
tive or
nonse-
lective)

Related Information

Downgrade Protection [page 360]

Performing Transport-Related Checks [page 150]
Transport-Related Checks in QGM [page 530]

Change Control Management

596 PUBLIC Quality Gate Management
Release Check [page 373]
Reassign Check [page 374]
Predecessor Check [page 376]
Imminent Check [page 377]
Import Strategies: Standard, Status-Dependent, and Selective [page 396]

5.7.10 Using the CTS Plug-In Management Web UI

If you use Change Request Management without central CTS, you can distribute CTS plug-ins with the CTS
Plug-In Management Web UI.

Prerequisites

 Note

If you use Change Request Management with the central CTS infrastructure, you don’t need the CTS
Plug-In Management Web UI to distribute CTS plug-ins.

Instead, you can use the Central CTS Configuration Web UI, which is also used to configure central CTS.

• The CTS plug-in (software component CTS_PLUG) is installed on your SAP Solution Manager. This is
done automatically as part of the SAP Solution Manager installation. For more information, see SAP Note
1665940 .
• A specific RFC destination is required between the CTS server (SAP Solution Manager) and the managed
systems to which you want to distribute the plug-ins, the import destination. For this, a SAP Solution
Manager destination is reused, which was created during Managed Systems Configuration in SAP Solution
Manager Configuration (transaction SOLMAN_SETUP). If the Change and Transport System - Plug-in
Management Web UI tells you that the import destination is missing, check that the RFC destinations
in your SAP Solution Manager configuration are correctly configured.
• If the managed systems are not part of the SAP Solution Manager transport domain, or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute the
CTS plug-ins.
For more information, see SAP Note 1688276 .
• You have the correct authorizations.

Context

With the Change and Transport System - Plug-in Management Web UI, you can distribute the CTS Service and
CTS Bootstrapper plug-ins from the CTS server to the managed systems in your transport landscape. For
non-ABAP systems, the plug-ins are distributed to the ABAP communication system of the non-ABAP system.

Change Control Management

Quality Gate Management PUBLIC 597
The CTS Service plug-ins contain analysis functions for downgrading and overtaker requests based on object
overlaps. The CTS Bootstrapper plug-in is required for activation.

If a message informs you that the functions of the CTS Service plug-in are needed for downgrade protection
functions in Change Control Management, use the Plug-in Management Web UI to distribute the plug-ins.

Procedure

1. Start the Plug-in Management Web UI in your CTS server (SAP Solution Manager).
2. Select the systems to which you want to distribute the plug-in and validate their status to find out whether
all prerequisites are met.

Under Status, a traffic light icon indicates the overall result. To see a list of status messages, select the link
in the Status column. If you select a status message, you see the associated long text.
3. Distribute the CTS Service and CTS Bootstrapper plug-ins.

If the plug-ins are not up to date, you must distribute them. For ABAP systems, this means importing
transport requests into the managed systems. For non-ABAP systems, this means importing the transport
requests in the ABAP communication system of the non-ABAP system.

Related Information

Plug-In Management Web UI - Layout [page 389]

Central Change and Transport System [page 400]
Technical Details of the CTS Plug-In [page 383]
Plug-In Management Web UI - Authorizations [page 385]
Downgrade Protection [page 360]
Starting the Plug-in Management Web UI [page 387]
Plug-In Management Web UI - Distributing CTS Plug-Ins [page 392]

5.7.10.1 Technical Details of the CTS Plug-In

Use

The CTS plug-in is an add-on that installs the software component CTS_PLUG on SAP systems. This classifies
the SAP system as a CTS server. You can find details on the installation and supported SAP releases in SAP
Note 1665940 .

The CTS plug-in (software component CTS_PLUG) contains the following further plug-ins:

• CTS Service plug-in

Change Control Management

598 PUBLIC Quality Gate Management
 This plug-in contains CTS functions that are required in the managed systems. This includes central CTS
functions as well as functions required for downgrade protection checks in Change Control Management of
SAP Solution Manager.
The CTS Service plug-in is release-dependent. There is one CTS Service plug-in for each SAP NetWeaver
release. For an overview of supported releases, refer to SAP Note 1665940 .
• CTS Bootstrapper plug-in
This plug-in contains functions that are required to activate the CTS Service plug-ins on the managed
systems.
There is one Bootstrapper plug-in for each SAP NetWeaver release, available for the same releases as the
CTS Service plug-ins.

From a technical point of view, the CTS plug-ins are transport requests. When the CTS plug-in (software
component CTS_PLUG) is installed in an SAP system, the CTS Service plug-ins and the CTS Bootstrapper
plug-in are extracted to the transport directory. They can be distributed from the CTS server to the managed
systems. Distributing the plug-in means importing the transport requests in the managed systems.

CTS Service plug-ins are independent of the SAP NetWeaver Support Package level. Therefore, they can always
be installed in a system with a minimum Support Package level of the software component SAP_BASIS. When
the transport request of the CTS Service plug-in is imported in the managed system, the transport request of
the CTS Bootstrapper plug-in is also imported.

These characteristics enable the CTS Service and Bootstrapper plug-ins to be installed at any time, even during
production operation. In particular, no system restart is necessary and there are no constraints concerning
production usage. In this way, you can use the current SAP technology in SAP systems without the need to
update all managed systems to the current Support Package level. You can update the managed systems in the
maintenance cycles that you are used to.

Figure: Distribution of CTS plug-ins to managed systems

Change Control Management

Quality Gate Management PUBLIC 599
The graphic illustrates the plug-in distribution process.

1. The CTS server asks the managed system if the CTS Service and the Bootstrapper plug-ins are available
and in which version.
2. The managed system returns the required information.
3. If the CTS Service or Bootstrapper plug-ins need to be updated, you can trigger the distribution from the
CTS server to the managed system.

 Note

The system compares the versions of the CTS Service and Bootstrapper plug-ins on the managed
systems with the versions available in the transport directory of the CTS server. It does not check for
versions of the CTS plug-in that are available on SAP Support Portal.

If the CTS plug-ins on managed systems are out of date, that means if they have lower version than the
plug-in on the CTS server, you get a warning but you can still perform operations that use central CTS
or downgrade protection.

 Note

If the managed systems are not part of the SAP Solution Manager transport domain or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute
the CTS plug-ins.

For more information, see SAP Note 1688276 .

Updates to the CTS Plug-In

To import updates or corrections to the CTS server (SAP Solution Manager), you must import the relevant SAP
NetWeaver Support Packages, or implement the relevant SAP Note corrections into SAP Solution Manager.

To import corrections that are required on the managed systems, you must import the relevant Support
Packages for the CTS plug-in into SAP Solution Manager and distribute the CTS plug-ins to the managed
systems. For an overview of the Support Packages available for the CTS plug-in, refer to SAP Note 1665940 .

More Information

• Central CTS: Distributing CTS Plug-Ins to the Managed Systems [page 432]
• Plug-In Management Web UI - Distributing CTS Plug-Ins [page 392]

5.7.10.2 Plug-In Management Web UI - Authorizations

Use

To be able to distribute CTS plug-ins using the Plug-In Management Web UI, the logon user must be assigned
specific authorizations.

Change Control Management

600 PUBLIC Quality Gate Management
Authorizations Required on the CTS Server (SAP Solution Manager)

In general, the user must have a copy of the following role assigned:

• SAP_BC_TRANSPORT_ADMINISTRATOR

If you do not want to use the predefined authorization or if the role contains too many authorizations, you
can run an authorization trace to find out which authorizations are required. For more information, refer to the
information provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

Task Authorization

Starting the Plug-In Management Web UI using the transac- The user who starts the UI using the transaction code SZEN-
tion code SZENPLUGIN. PLUGIN needs to be assigned authorization object S_TCODE
with field TCD and value SZENPLUGIN.

This authorization object is part of the roles

SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANS-
PORT_ADMINISTRATOR as of SAP NetWeaver 7.0 Enhance-
ment Package 2, SP13.

Displaying objects on the UI including the following tasks: Display authorization: The user needs to be assigned au-
thorization object S_TRANSPRT with field ACTVT and value
• Searching for systems
03.
• Displaying search help and value help

Distributing CTS plug-ins to the managed systems. On the CTS server, the user needs to be assigned the author-
ization object S_CTS_ADMI with field CTS_ADMFC and value
TABL.

 Note

If the user needs both display and change authorization, assign both authorizations.

Authorizations Required on the Managed System

• User TMSADM must exist on the managed system. It must not be locked and must have the standard
profile assigned (S_A.TMSADM).

• Make sure that the user who performs a validation in the Plug-In Management Web UI also exists in the
managed systems for which he wants to perform the validation. Otherwise, validation will fail.
• To distribute CTS plug-ins, the user who is used for plug-in distribution to the managed system (usually
the user that is logged on to the current system) must have the authorization object S_RFCACL in the
managed system if the import destination uses Trust Relationship. For more information on S_RFCACL and
Trust Relationship, refer to the information provided in the “More Information” section.

In general, the user who is used for plug-in distribution to the managed system must have copies of the
following roles assigned:

• SAP_BC_TRANSPORT_OPERATOR: Required for distributing CTS plug-ins

• SAP_BC_TRANSPORT_ADMINISTRATOR: Required if the managed system is not in the same transport
domain as the CTS server.

Change Control Management

Quality Gate Management PUBLIC 601
If you do not want to use the predefined authorization or if it contains too many authorizations, you can run an
authorization trace to find out which authorizations are required. For more information, refer to the information
provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

• S_TRANSPRT with field ACTVT and value 03

• S_CTS_ADMI with field CTS_ADMFC and value IMPA
• S_DATASET with the values required to access the transport directory. This authorization is required
to read files. If the user does not have this authorization object assigned the error message
OPEN_DATASET_NO_AUTHORITY is displayed.
• S_RFC with the following values:
• field ACTVT and value 16
• field RFC_NAME and values STPA and TMSC
• field RFC_TYPE and value FUGR

More Information

• Maintaining Trust Relationships between SAP Systems

• Authorization Object S_RFCACL
• Using the System Trace to Record Authorization Checks (Transaction STAUTHRACE)
• Authorizations in the CTS
• Transport Operator
• Transport Administrator
• For more information on authorization object S_TCODE, see Authorization Checks.
• For more information on the releases and Support Packages which delivered changes to the
roles SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANSPORT_ADMINISTRATOR, see SAP Note
1748949 .

5.7.10.3 Starting the Plug-in Management Web UI

The Plug-in Management Web UI distributes CTS Service plug-ins to managed systems. You usually use it when
the system asks you to. You can start it with a transaction code, or using your favorites in the SAP Easy Access
user menu.

Prerequisites

• You have activated the services for the Plug-ln Management Web UI. The service is called
CTS_CONFIGURATION_PLUGIN_MGNT.
For more information on ICF services required to run an ABAP Web Dynpro application, see SAP Note
517484 .

Change Control Management

602 PUBLIC Quality Gate Management
 For more information on activating ICF services, see Activating and Deactivating ICF Services.
• To start the UI using a transaction code, you have the required authorization.

Context

 Note

To start the Plug-in Management Web UI with a Transaction Code, log on to your CTS server with the user
and password that you use to perform imports and call transaction SZENPLUGIN.

To start the Plug-in Management Web UI using the SAP Easy Access user menu, you must first create it as a
favorite:

Procedure

1. Log on to your CTS server with the user and password that you use to perform imports.

2. In SAP Easy Access user menu, choose Favorites Add Other Objects Web Dynpro Application .

The Web Dynpro Application dialog box is displayed.

3. In the Web Dynpro Application field, enter CTS_CONFIGURATION_PLUGIN_MGNT.
4. Specify a description of the favorite, for example CTS Plug-in Management Web UI.
5. Choose Enter.

The Plug-in Management Web UI has been added to your SAP Easy Access user menu.
6. To start the UI, double-click the entry.

Results

CTS Plug-in Management Web UI starts in a web browser.

Related Information

Plug-In Management Web UI - Authorizations [page 385]

Change Control Management

Quality Gate Management PUBLIC 603
5.7.10.3.1 Plug-In Management Web UI - Layout

Context

The Change and Transport System - Plug-In Management Web UI provides an overview of all systems that
belong to your transport landscape. You can use this UI to validate the status of the systems with respect to the
distribution of the CTS service plug-in.

For some screen elements, quick help is available. Quick help provides additional explanation of the screen
elements, mainly for inexperienced users. A green line below the text indicates that quick help is available. To
enable quick help, right-click anywhere on the screen and choose Display Quick Help.

Layout

The Plug-In Management Web UI is divided into a Search Area in the top half of the screen and a Search Result
and Work Area in the lower half.

The Search Area allows you to search for systems according to specific criteria. This enables you to reduce the
number of systems that is displayed in the Work Area. The Search Area is hidden by default.

For more information, see Plug-In Management Web UI - Searching and Refreshing Data [page 390].

At the left side of the Work Area, a small black triangle is displayed. Clicking on the triangle opens a small box
that contains Related Links to related functions. Clicking on a link in the box opens the corresponding function
using SAP NetWeaver Business Client (NWBC) for HTML.

Details on Work Area

The Work Area displays all systems of your transport landscape that have been found according to the search
criteria you specified in the Search Area.

The Work Area allows you to perform the actual tasks that are required for the distribution of CTS plug-ins.
Validating the systems in your transport landscape is the starting-point in the CTS Plug-In Management Web
UI. The validation evaluates whether the CTS Service and CTS Bootstrapper plug-ins need to be updated on the
managed systems. The results of the validation are displayed using traffic light icons in the Status column and
using a link in the Plug-In Distribution column. If the plug-in needs to be updated, the link takes you to a dialog
box that lets you distribute the plug-ins.

The following functions are available:

Function Description More information

Validate Starts a validation for the selected sys-

tems.

Distribute Plug-in Imports the current version of the CTS Plug-In Management Web UI - Distribut-
Service and CTS Bootstrapper plug-ins ing CTS Plug-Ins [page 392]
into the managed system.

Change Control Management

604 PUBLIC Quality Gate Management
Function Description More information

Filter Allows you to filter the elements dis- Plug-in Management Web UI - Filtering
played in the work area according to [page 391]
different criteria.

Refresh Refreshes the data of all elements dis- Plug-in Management Web UI - Search-
played in the work area. ing and Refreshing Data [page 390]

Personalize Allows you to personalize the layout of

the work area according to your needs.
This includes setting the number of visi-
ble rows and changing the sequence of
the columns in the table as well as hid-
ing columns that you do not need.

The following traffic light icons are available:

Status Quick Info Description

Green light Plug-in distribution is up-to-date The CTS Service and the CTS Boot-
strapper plug-ins are up-to-date in the
managed system.

Red light See details - Validation completed with The CTS Bootstrapper plug-in or the
errors CTS Service plug-in or both are not up-
to-date. Moreover, it is possible that the
import destination required to update
the plug-ins has not been configured.

Grey light Not Yet Validated The system has not yet been validated
since you have started the Plug-In Man-
agement Web UI.

5.7.10.3.2 Plug-In Management Web UI - Searching and

Refreshing Data

Use

When the Plug-in Management Web UI is called, the system initially searches for all systems in the transport
landscape.

You can use the search function to perform a search according to specific criteria. By default, the search
criteria are hidden. You can display them using Display Search Criteria. The results of the search are displayed
in the work area.

Change Control Management

Quality Gate Management PUBLIC 605
The Refresh function is available in the work area. It refreshes the data for the systems that are displayed in
the work area. Note that the refresh function does not perform a new search. It just refreshes the data for all
systems that have been found during the current session.

Procedure

Performing a Search

1. To enable the search, choose Display Search Criteria.

2. Enter your search criteria or select them from the value help. You can specify a range or use the asterisk
(*).
3. To start the search, choose Search or Search and Hide Search Criteria as required.
The systems that are found are displayed in the work area. The search criteria are either displayed or
hidden depending on the option that you selected.
If you select Search and Hide Search Criteria and no systems are found, the search criteria are still
displayed.
4. Reset Search Criteria resets the search criteria to the values with which the Plug-in Management Web UI
was started.

Performing a Refresh

To refresh the data in the work area, choose Refresh.

5.7.10.3.3 Plug-in Management Web UI - Filtering

Use

You can use the filter function in the Plug-in Management Web UI to reduce the number of elements in your
work area or to display only specific systems that match your filter criteria.

Procedure

1. To enable the filter function, choose Filter.

A filter row appears.
2. Depending on the elements that are displayed in the column, either enter text or select filter criteria from
the dropdown list.
You can enter any character or character strings including asterisks. You can combine different filter
criteria in multiple text fields. Icons are filtered using their tooltip text. For icons, you select the filter criteria
from a dropdown list.
3. If you have selected a filter criterion from a dropdown list, the filtering result is immediately displayed.
4. If you have entered text, choose Enter to display the filter result.

Additional Notes on the Filter Function

Change Control Management

606 PUBLIC Quality Gate Management
• To disable the filter function, choose Filter again. This discards the filter and displays all systems and
clusters according to the search criteria.
• The value help of the filter criteria is generated dynamically from the visible elements in the work area.

5.7.10.4 Plug-In Management Web UI - Distributing CTS Plug-

Ins

Prerequisites

• You have performed a validation in the CTS Plug-In Management Web UI and the system tells you that there
are CTS plug-ins (CTS Bootstrapper or CTS Service plug-in) that need to be updated.
• All prerequisites are fulfilled that are described in Using the CTS Plug-In Management Web UI [page 382].
• The managed systems to which you want to distribute the CTS plug-ins have the required version of the
transport tools tp and R3trans. For more information, see SAP Note 1665940 .
• The user who is used for plug-in distribution exists in the managed system, and, if the import destination
uses Trust Relationship, the user has the authorization object S_RFCACL in the managed system.

Procedure

1. In the CTS Plug-In Management Web UI, choose the link in the Plug-In Distribution column.

Dialog boxes inform you about the distribution of CTS plug-ins and the detailed results of the validation.
2. Confirm that you want to distribute the plug-in to the managed system.
3. If the plug-ins can be distributed, choose Distribute Plug-Ins.

If the plug-ins cannot be distributed, a message informs you about the reasons.

The CTS plug-ins that must be updated are distributed to the managed system. If the managed system
is a non-ABAP system, the plug-ins are distributed to the ABAP communication system of the non-ABAP
system.

Results

The transport requests for the updated CTS plug-ins are imported in the managed system. The CTS server can
use the functions of the CTS Service plug-in in the managed system.

Change Control Management

Quality Gate Management PUBLIC 607
5.8 Managing Changes for Non-ABAP Systems

The Enhanced Change and Transport System (CTS+) enables you to transport Java objects and SAP-related
non-ABAP applications in your system landscape, alongside ABAP objects. You can also administer non-ABAP
systems in a CTS transport domain in SAP NetWeaver Application Server ABAP.

Use

Moving developments and changes across a system landscape requires the management of transport. In
response to this need, SAP offers the Change and Transport System (CTS) for ABAP transports and the
Enhanced CTS (CTS+) for non-ABAP as well as non-SAP applications.

CTS helps you to transport software changes between the systems in your transport landscape. It assures that
every change that has been performed in the development system is first imported into the test system before
it can be imported into the production system.

The Enhanced CTS synchronizes changes for ABAP- and non-ABAP-based SAP system landscapes. It
consolidates the changes independent of whether they’re based on ABAP or non-ABAP or even non-SAP.
CTS+ provides a unified transport tool and makes the work of administrators easier when executing imports.
You only need access to one tool to execute imports for different backend systems. The deployment tools are
called automatically.

CTS together with CTS+ enables the management of ABAP and non-ABAP objects, including combined
transports for mixed objects like ABAP and JAVA.

Integration

CTS and CTS+ are fully compatible with SAP Solution Manager, and can be used in Quality Gate Management
and Change Request Management.

The enhanced CTS is an additional option to manage changes for non-ABAP content. Its integration into SAP
Solution Manager makes it easier to control of different types of changes within SAP system landscapes that
are based, for example, on AS Java.

For information how to set up CTS+, see Configuring CTS+ in SAP Solution Manager 7.1 and 7.2 .

Related Information

Change Control Management Using Central CTS [page 399]

Enhanced Change and Transport System

Change Control Management

608 PUBLIC Quality Gate Management
5.9 Change Control Management Using Central CTS

The central Change and Transport System (central CTS) provides a technical infrastructure for the enhanced
flexibility functions in Change Control Management.

Use

You can use central CTS with Change Request Management and Quality Gate Management. Central CTS is the
transport foundation; Change Request Management and Quality Gate Management (QGM) manage the change
control process and provide the user interfaces.

For each new change cycle, you can decide whether you want to use CTS or central CTS.

If you activate central CTS for your change cycle, several functions in Change Request Management and Quality
Gate Management have enhanced features. These are described in the documentation of each function.

Prerequisites

• You are using a SAP Solution Manager version that supports central CTS. Central CTS is delivered as the
CTS Plug-In add-on, which is part of the SAP Solution Manager 7.1 stack, as of Support Package 05.
• Your system landscape is set up accordingly. For central CTS, you need the SAP Solution Manager system,
and managed systems that are connected to the central CTS server and that can be controlled by it.

Features

After activating central CTS for your change cycle, you can use the following functions:

• Flexible assignment of transport requests, even after their release

• Synchronous control and monitoring of parallel transport routes
• Prevention of conflicts between central transport control and local transport administration (local
Transport Management System — STMS)
• Combine individual systems (different applications) to reflect semantic dependencies
• Synchronize transports requests if the resolution of an issue involves different applications
• Bundle transports if more than one transport request is to be imported to complete the issue (for example,
initial change and corrections)
• Ensure that only the most recent version of an object is imported and that no objects are overwritten
(downgrade protection)
• Enhanced unification of ABAP and non-ABAP transports

Change Control Management

Quality Gate Management PUBLIC 609
Related Information

Central Change and Transport System [page 400]

Configuring Central Change and Transport System - Overview [page 407]
Change Request Management [page 21]
Quality Gate Management [page 478]
Setting Up Quality Gates and Assigning Phases [page 487]
Enhanced Transport Functions with Central CTS [page 448]
SAP Note 1665940
https://archive.sap.com/documents/docs/DOC-49155

5.9.1 Central Change and Transport System

Use

Central Change and Transport System (central CTS) enhances the classic CTS with functions for complex
heterogeneous system landscapes, which allow you to control transports within a transport landscape
centrally. This means you can combine multiple systems of your transport landscape into system clusters.
You can bundle transports between these clusters using transport collections. A transport collection is a
combination of the transports from the different systems of a cluster.

SAP Solution Manager represents the central CTS server that is responsible for the central management of the
transport landscape. You can control transports into the managed systems from the central CTS server.

 Note

Before using central CTS on SAP Solution Manager, read SAP Note 2231041 Collective Note: central CTS
with SAP Solution Manager 7.2.

Implementation Considerations

The functions of central CTS on SAP Solution Manager are provided as part of SAP NetWeaver. In addition,
the CTS plug-in (software component CTS_PLUG) is installed in SAP Solution Manager. This classifies SAP
Solution Manager as a central CTS server and makes the functions of central CTS available for distribution to
the managed systems.

Managed systems can have the following releases:

• ABAP systems: For more information on the releases of the managed systems that are supported by
central CTS as well as on the required tp and R3trans versions, refer to SAP Note 1665940 .
• Non-ABAP systems: The enhanced CTS must be configured for the non-ABAP system and SAP Solution
Manager must be used as the domain controller and communication system.

Usage of central CTS is optional. You can use it to exploit the enhanced flexibility functions in Change Request
Management and Quality Gate Management (QGM). Before you implement central CTS for your transports,

Change Control Management

610 PUBLIC Quality Gate Management
check whether it is suitable for your situation. You can also continue to use classic CTS, TMS, or classic Change
Request Management and QGM.

If you want to test whether the functions of central CTS are suitable for your requirements, you can initially use
central CTS for just part of your landscape or projects, or just for a test project.

Integration

Central CTS enhances the existing Change and Transport System. You can only use central CTS in connection
with the existing CTS. Depending on the configuration of central CTS, some functions of the existing CTS might
be disabled. For example, if the central control of transports is activated, then the local execution of transports
in the systems might be deactivated. Central CTS is integrated into Change Request Management and QGM of
SAP Solution Manager. It is required if you want to use the enhanced flexibility functions.

Features

Combine individual systems with content dependencies into system clusters

• All systems in your transport landscape that you want to supply with transports at the same time can
be grouped into clusters. You can combine Business Suite development systems and Portal development
systems to form a single cluster. You can also combine the relevant consolidation, test, and production
systems into clusters of their own. This means, you create system clusters for systems that have the same
role (for example, DEV, QAS, and PRD).
• You can combine ABAP and non-ABAP systems into a system cluster.
• System clusters are defined centrally for your transport landscapes in the central CTS server.

Combine transports into transport collections

• You create transport collections to combine transports from different systems. In this way you can, for
example, transport ABAP developments together with non-ABAP developments.
• After exporting a transport collection you can add further transport requests to the transport collection.
You can then import the transport collection again but only the changed transport requests will be
reimported. This means, for example, that you can collect all related transport requests in a collection
which contains both a new version of an application as well as the necessary corrections for that
application.

 Note

You create transport collections in Change Request Management or QGM.

More Information

• Concepts for Central CTS [page 402]

• Configuring Central Change and Transport System - Overview [page 407]

Change Control Management

Quality Gate Management PUBLIC 611
• Using Central Change and Transport System [page 436]
• Change Control Management Using Central CTS [page 399]
• Central CTS on SAP Community Network: https://scn.sap.com/docs/DOC-7643#centralCTS

5.9.1.1 Concepts for Central CTS

Use

For central CTS, new entities are required to combine systems and the transports within the systems. The
entity which combines systems is called system cluster. The entity which combines transport requests is called
transport collection.

More Information

• System Cluster [page 403]

• Transport Collection [page 404]
• Technical Details of the CTS Plug-In [page 383]

5.9.1.1.1 System Cluster

Use

Those systems in your transport landscape that you want to supply with transports at the same time can be
grouped into system clusters. You create a system cluster for systems that have the same role (for example,
DEV, TST, and PRD). In this way you can, for example, combine a Process Integration (PI) development system
together with a Business Suite development system and a Portal development system into a single cluster. You
can also combine the relevant test, and production systems into one cluster.

You can combine ABAP and non-ABAP systems into a system cluster.

You configure system clusters centrally in the central CTS server using the Central CTS Configuration Web
UI. System clusters are represented in Transport Management System (TMS) by a three-character system
identifier (SID), like any other system. However, they are not real systems that you have to install. The cluster
SID has to be unique in your transport landscape.

You can configure your system clusters in such a way that the central CTS server takes over the control of your
transports. This means the local CTS can be deactivated.

Change Control Management

612 PUBLIC Quality Gate Management
 Figure: Example of a system cluster track for PI, Portal, and Business Suite developments consisting of development, test,
and production clusters.

The graphic shows a sample three-cluster track. There is one development cluster, one test cluster, and one
production cluster. Each cluster contains a PI, a Portal, and a Business Suite system with the respective role
(development, test, and production).

 Note

When creating a cluster track, for example, consisting of a development, a test, a pre-production, and a
production cluster, it is possible to set up a so-called “uneven” cluster track. “Uneven” means that not all
system clusters in the cluster track contain the same number of systems with the same roles. For example,
if the PI track does not have a pre-production system, but all other tracks have one, you can create a
pre-production cluster for the other applications and omit PI from the pre-production cluster.

More Information

• Transport Collection [page 404]

5.9.1.1.2 Transport Collection

Use

After combining systems as system clusters, you can combine transport requests within the system clusters.
The entity which combines transport requests is called a transport collection.

Change Control Management

Quality Gate Management PUBLIC 613
Transport requests that are part of a transport collection are released separately. The released transport
requests are transported when the transport collection is released. They are then imported into the
corresponding test or production systems contained in the follow-on system cluster.

Figure: Example of a transport collection that contains transport requests from Process Integration (PI), Enterprise Portal,
and Business Suite systems.

The graphic shows a transport collection that contains multiple transport requests from the development
systems that are part of the system cluster. The transport collection contains transport requests from the
development systems: one transport request from the Business Suite system (BSD), two transport requests
from the Portal system (EPD), and one transport request from the Process Integration system (PID).

More Information

System Cluster [page 403]

5.9.1.1.3 Technical Details of the CTS Plug-In

Use

The CTS plug-in is an add-on that installs the software component CTS_PLUG on SAP systems. This classifies
the SAP system as a CTS server. You can find details on the installation and supported SAP releases in SAP
Note 1665940 .

Change Control Management

614 PUBLIC Quality Gate Management
The CTS plug-in (software component CTS_PLUG) contains the following further plug-ins:

• CTS Service plug-in

This plug-in contains CTS functions that are required in the managed systems. This includes central CTS
functions as well as functions required for downgrade protection checks in Change Control Management of
SAP Solution Manager.
The CTS Service plug-in is release-dependent. There is one CTS Service plug-in for each SAP NetWeaver
release. For an overview of supported releases, refer to SAP Note 1665940 .
• CTS Bootstrapper plug-in
This plug-in contains functions that are required to activate the CTS Service plug-ins on the managed
systems.
There is one Bootstrapper plug-in for each SAP NetWeaver release, available for the same releases as the
CTS Service plug-ins.

From a technical point of view, the CTS plug-ins are transport requests. When the CTS plug-in (software
component CTS_PLUG) is installed in an SAP system, the CTS Service plug-ins and the CTS Bootstrapper
plug-in are extracted to the transport directory. They can be distributed from the CTS server to the managed
systems. Distributing the plug-in means importing the transport requests in the managed systems.

CTS Service plug-ins are independent of the SAP NetWeaver Support Package level. Therefore, they can always
be installed in a system with a minimum Support Package level of the software component SAP_BASIS. When
the transport request of the CTS Service plug-in is imported in the managed system, the transport request of
the CTS Bootstrapper plug-in is also imported.

These characteristics enable the CTS Service and Bootstrapper plug-ins to be installed at any time, even during
production operation. In particular, no system restart is necessary and there are no constraints concerning
production usage. In this way, you can use the current SAP technology in SAP systems without the need to
update all managed systems to the current Support Package level. You can update the managed systems in the
maintenance cycles that you are used to.

Change Control Management

Quality Gate Management PUBLIC 615
 Figure: Distribution of CTS plug-ins to managed systems

The graphic illustrates the plug-in distribution process.

1. The CTS server asks the managed system if the CTS Service and the Bootstrapper plug-ins are available
and in which version.
2. The managed system returns the required information.
3. If the CTS Service or Bootstrapper plug-ins need to be updated, you can trigger the distribution from the
CTS server to the managed system.

 Note

The system compares the versions of the CTS Service and Bootstrapper plug-ins on the managed
systems with the versions available in the transport directory of the CTS server. It does not check for
versions of the CTS plug-in that are available on SAP Support Portal.

If the CTS plug-ins on managed systems are out of date, that means if they have lower version than the
plug-in on the CTS server, you get a warning but you can still perform operations that use central CTS
or downgrade protection.

 Note

If the managed systems are not part of the SAP Solution Manager transport domain or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute
the CTS plug-ins.

For more information, see SAP Note 1688276 .

Change Control Management

616 PUBLIC Quality Gate Management
Updates to the CTS Plug-In

To import updates or corrections to the CTS server (SAP Solution Manager), you must import the relevant SAP
NetWeaver Support Packages, or implement the relevant SAP Note corrections into SAP Solution Manager.

To import corrections that are required on the managed systems, you must import the relevant Support
Packages for the CTS plug-in into SAP Solution Manager and distribute the CTS plug-ins to the managed
systems. For an overview of the Support Packages available for the CTS plug-in, refer to SAP Note 1665940 .

More Information

• Central CTS: Distributing CTS Plug-Ins to the Managed Systems [page 432]
• Plug-In Management Web UI - Distributing CTS Plug-Ins [page 392]

5.9.1.2 Configuring Central Change and Transport System -

Overview

Use

Before you can use the central Change and Transport System (central CTS), you must prepare the systems
involved.

The starting point for the configuration is the Central CTS Configuration Web UI. This UI shows an overview of
all systems of your transport landscape. You can check whether the systems can be used for central CTS and
perform all configuration tasks required for setting up your systems for central CTS.

 Note

You can also find all configuration steps including screenshots and examples in the How-
To-Guide How To... Set Up cCTS for ChaRM and QGM at https://www.sap.com/documents/
2016/08/2cd565a1-847c-0010-82c7-eda71af511fa.html .

Procedure

The following table lists the tasks that are required to configure central CTS. To navigate directly to a specific
topic use the links in the More Information section.

Make sure that the systems that you want to use with There are specific prerequisites concerning the availability of
central CTS meet the requirements. central CTS software, and required authorizations, for exam-
ple.

Change Control Management

Quality Gate Management PUBLIC 617
Start the Central CTS Configuration Web UI in your cen- Your central CTS server is your SAP Solution Manager sys-
tral CTS server. tem. Start the Central CTS Configuration Web UI there to
perform all configuration tasks.

Select the systems that you want to configure for central Before you can begin to configure your systems for central
CTS and validate their statuses. CTS, you need to find out if the systems meet the require-
ments. To do this, select the systems that you want to use
with central CTS and choose Validate.

The system checks which configuration tasks have already

been performed. Depending on the result, the system shows
you the tasks you still need to perform.

Perform the missing configuration tasks. An overall status is displayed for each system that has been
validated. If all configuration tasks have been performed, a
green traffic light icon appears. If there are configuration
tasks missing or if the system could not calculate a result, a
red traffic light icon is displayed. To view the results, choose
See Details in the Status column. The dialog box displays a
list of status messages. If you select a status message in the
upper area of the dialog box, the long text of the message is
displayed in the lower area of the dialog box. If a column con-
tains a link with an error message, selecting the link either
lets you perform the configuration task or provides more
information about the required task.

This can include the following tasks:

• Creating system clusters

• Creating RFC connections to the managed systems
• Setting TMS parameters that are required for using cen-
tral CTS
• Distributing plug-ins to the managed systems

Depending on the task you performed and on your personal

settings, the system may automatically trigger validation
(when assigning systems to clusters, for example). If this
is not the case, choose Validate after performing the task to
retrieve the current configuration status.

Repeat the configuration steps for all systems that you If all traffic lights are green for all systems that you want to
want to configure for central CTS. use with central CTS, you must still perform the following
steps.

Connect the system clusters. To enable transports between clusters, you need to define
transport routes between the clusters. You do this in the
same way as for systems in Transport Management System
in your central CTS server.

Change Control Management

618 PUBLIC Quality Gate Management
Connect the individual systems that are contained in the After you have configured the transport routes at cluster
clusters. level, define the transport process of the individual systems.
You do this by determing the import targets for all target
systems that belong to a cluster.

Distribute the TMS configuration to all systems in the Perform this task once you have completed the configura-
transport domain. tion steps for all the systems that you want to use with
central CTS. To distribute the configuration to all systems
in the transport domain, choose Distribute Configuration in
the central CTS Configuration Web UI.

 Note
It is sufficient to perform this configuration step once af-
ter you have performed all steps for all systems that you
want to use with central CTS. The configuration will then
be distributed to all systems of the transport domain.

If systems from foreign domains (with or without do-

main links) are part of your system clusters, you must
perform the configuration distribution on the domain
controller(s) of these systems.

Result

You can use the systems for central CTS.

More Information

• Prerequisites for Configuring Central CTS [page 411]

• Central CTS Configuration Web UI - Layout [page 414]
• Starting the Central CTS Configuration Web UI [page 416]
• Creating or Changing System Clusters [page 421]
• Configuring RFC Destinations for Cenral CTS [page 428]
• Setting TMS Parameters for Central CTS [page 424]
• Distributing CTS Plug-ins to the Managed Systems [page 432]
• Configuring Transport Routes (link to classic Transport Management System documentation)
• Defining Import Targets [page 434]

Change Control Management

Quality Gate Management PUBLIC 619
5.9.1.2.1 Prerequisites for Configuring Central CTS

Use

To configure central Change and Transport System (CTS) make sure that the following prerequisites are met:

• The SAP Solution Manager system and the systems that you want to manage centrally have a release that
is supported by central CTS. The CTS plug-in is installed in SAP Solution Manager. For further information
on the CTS plug-in and an overview of the supported releases for managed systems, see SAP Note
1665940 .
• You have activated the ICF service for the central Change and Transport System Configuration UI. The
service is called CTS_CONFIGURATION.
• You have a basic understanding of working with the existing Change and Transport System and with the
Transport Management System, particularly its configuration.
• Transport Management System is configured for the managed systems.
• The managed ABAP systems and the communication systems of the non-ABAP systems have a trust
relationship with the central CTS Server (SAP Solution Manager). For this, you have performed the
Managed Systems Configuration in SAP Solution Manager.
• If the managed systems are not part of the SAP Solution Manager transport domain or if they are
not linked to the SAP Solution Manager domain with a domain link, you must initially import the CTS
Bootstrapper plug-in manually in the managed systems. Afterwards, you can automatically distribute the
CTS plug-ins.
For more information, see SAP Note 1688276 .
• You have the relevant authorizations for configuring central CTS.

More Information

• Links to CTS and TMS documentation:

• Change and Transport System - Overview (BC-CTS)
• Transport Management System (BC-CTS-TMS)
• Links to ICF documentation:
• Activating and Deactivating ICF Services
• For more information on ICF services required to run an ABAP Web Dynpro application, see SAP Note
517484 .
• SICF authorizations: Authorizations
• Maintaining Trust Relationships between SAP Systems
• Authorizations for Configuring Central CTS [page 412]

Change Control Management

620 PUBLIC Quality Gate Management
5.9.1.2.2 Authorizations for Configuring Central CTS

Use

Authorizations Required on the CTS Server (SAP Solution Manager)

In general, the user must have a copy of the following role assigned:

• SAP_BC_TRANSPORT_ADMINISTRATOR

If you do not want to use the predefined authorization or if the role contains too many authorizations, you
can run an authorization trace to find out which authorizations are required. For more information, refer to the
information provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

Task Authorization

Starting the Central CTS Configuration Web UI using the The user who wants to start the UI using the transaction
transaction code SZENCONFIG. code SZENCONFIG needs to be assigned authorization ob-
ject S_TCODE with field TCD and value SZENCONFIG.

This authorization object is part of the roles

SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANS-
PORT_ADMINISTRATOR as of SAP NetWeaver 7.0 Enhance-
ment Package 2, SP13.

Displaying objects on the UI including the following tasks: Display authorization: The user needs to be assigned au-
thorization object S_TRANSPRT with field ACTVT and value
• Searching for systems or system clusters
03.
• Displaying clusters
• Displaying search help and value help

Changing objects including the following tasks: Change authorization: The user needs to be assigned the au-
thorization object S_CTS_ADMI with field CTS_ADMFC and
• Creating, changing, or deleting system clusters
value TABL.
• Changing TMS parameters
• Distributing the TMS configuration

Distributing CTS plug-ins to the managed systems On the CTS server, the user needs to be assigned
change authorization (see above) and authorization object
S_TRANSPRT with field ACTVT and value 03.

 Note

If the user needs both display and change authorization, assign both authorizations.

Authorizations Required on the Managed System

• User TMSADM must exist on the managed system. It must not be locked and must have the standard
profile assigned (S_A.TMSADM).

Change Control Management

Quality Gate Management PUBLIC 621
• Make sure that the user who performs a validation in the Central CTS Configuration Web UI (logon user)
also exists in the managed systems for which he wants to perform the validation. Otherwise, validatation
will fail.
• To distribute CTS plug-ins, the user who is used for plug-in distribution to the managed system (usually
the user that is logged on to the current system) must have the authorization object S_RFCACL in the
managed system if the import destination uses Trust Relationship. For more information on S_RFCACL and
Trust Relationship, refer to the information provided in the “More Information” section.

In general, the user who is used for plug-in distribution to the managed system must have copies of the
following roles assigned:

• SAP_BC_TRANSPORT_OPERATOR: Required for distributing CTS plug-ins

• SAP_BC_TRANSPORT_ADMINISTRATOR: Required if the managed system is not in the same transport
domain as the CTS server.

If you do not want to use the predefined authorization or if it contains too many authorizations, you can run an
authorization trace to find out which authorizations are required. For more information, refer to the information
provided in the “More Information” section.

Alternatively, you can restrict authorizations by assigning the following authorization objects individually:

• S_TRANSPRT with field ACTVT and value 03

• S_CTS_ADMI with field CTS_ADMFC and value IMPA
• S_DATASET with the values required to access the transport directory. This authorization is required
to read files. If the user does not have this authorization object assigned the error message
OPEN_DATASET_NO_AUTHORITY is displayed.
• S_RFC with the following values:
• field ACTVT and value 16
• field RFC_NAME and values STPA and TMSC
• field RFC_TYPE and value FUGR

More Information

• Maintaining Trust Relationships between SAP Systems

• Authorization Object S_RFCACL
• Using the System Trace to Record Authorization Checks (Transaction STAUTHRACE)
• Authorizations in the CTS
• Transport Operator
• Transport Administrator
• For more information on authorization object S_TCODE, see Authorization Checks.
• For more information on the releases and Support Packages which delivered changes to the
roles SAP_BC_TRANSPORT_OPERATOR and SAP_BC_TRANSPORT_ADMINISTRATOR, see SAP Note
1748949 .

Change Control Management

622 PUBLIC Quality Gate Management
5.9.1.2.3 Central CTS Configuration Web UI - Layout

Concept

The Central Change and Transport System (central CTS) Configuration Web UI provides an overview of all
systems and system clusters that belong to your transport landscape. It displays the configuration status of
systems and clusters with respect to central CTS.

You can use the Central CTS Configuration Web UI to perform all tasks that are necessary for configuring the
systems for central CTS.

For some screen elements, quick help is available. Quick help provides additional explanation of the screen
elements, mainly for inexperienced users. A green line below the text indicates that quick help is available. To
enable quick help, right-click anywhere on the screen and choose Display Quick Help.

Features

Layout

The Central CTS Configuration Web UI is divided into a Search Criteria area in the top half of the screen and a
Search Result and Work Area (Work Area) in the lower half.

The search area allows you to search for system clusters or systems according to specific criteria. This enables
you to reduce the number of systems displayed in the work area. The search area is hidden by default.

At the left side of the Work Area, a small black triangle is displayed. Clicking on the triangle opens a small box
that contains Related Links to important functions that you may need to configure central CTS, such as RFC
Destination Maintenance. Clicking on a link in the box opens the corresponding function using SAP NetWeaver
Business Client (NWBC) for HTML.

Work Area

The work area displays all systems and system clusters of your transport landscape that have been found
according to the search criteria you specified in the search area. The work area allows you to perform the actual
tasks that are required for configuring the systems for central CTS.

Validating the systems is the starting point in the Central CTS Configuration Web UI. The validation evaluates
whether the systems can be configured for use with central CTS. The results of the validation are displayed
using traffic light icons in the Status column and by using text messages. If actions need to be performed,
the text is displayed as a link that either leads to additional explanation or allows you to perform the required
action.

The Status column gives an overall status of the results of the validation for the system or cluster.

Change Control Management

Quality Gate Management PUBLIC 623
The following functions are available in the toolbar:

Function Description More information

Validate Starts a validation for the selected sys- Configuring Systems for Central
tems and system clusters Change and Transport System [page
407]

Cluster Create Cluster /Display/ Allows you to create system clusters Creating or Changing System Clusters

Change Cluster/Delete Cluster and/or assign systems to existing clus- [page 421]
ters, as well as delete existing clusters

Distribute Configuration Allows you to distribute the TMS config- Configuring Systems for Central
uration to all systems in the transport Change and Transport System [page
domain 407]

Display as: Allows you to switch the layout of the Central CTS Configuration Web UI - Per-
work area between Hierarchical List and sonalization [page 419]
Flat List.

Filter Allows you to filter the elements dis- Central CTS Configuration Web UI - Fil-
played in the work area according to tering [page 417]
different criteria.

Refresh Refreshes the data of all elements dis- Central CTS Configuration Web UI -
played in the work area. Searching and Refreshing Data [page
418]

Personalize Allows you to personalize the layout of Central CTS Configuration Web UI - Per-
the work area according to your needs. sonalization [page 419]
This includes setting the number of visi-
ble rows and changing the order of the
columns in the table as well as hiding
columns that you do not need.

The following traffic light icons exist:

Status Tooltip Text Description

Green light Configuration is up-to-date The system has been configured for central CTS. It
can be used with central CTS.

Red light See details - Validation com- Some configuration steps are missing for the system
pleted with errors to be used with central CTS or the system cannot
be used at all with central CTS. For example, if the
release or Support Package level of the system is not
supported, it cannot be used with central CTS.

Yellow light Cannot be validated This status is for clusters that do not contain any sys-
tems.

Change Control Management

624 PUBLIC Quality Gate Management
Status Tooltip Text Description

Grey light Not yet validated The system has not yet been validated since you have
started the Central CTS Configuration Web UI.

The following tasks have to be performed on request if the system displays a related error message:

Task Description More information

Setting TMS To be able to use central CTS, the system requires Setting TMS Parameters [page 424]
parameters specific TMS parameters. If these are not set cor-
rectly, you must set them. A detailed description is
provided on how to set them.

Creating RFC To be able to communicate with the managed sys- Configuring RFC Destinations [page 428]
connections tems, specific RFC connections between the central
CTS server and the managed systems are required.
If the RFC connections have not been created, you
must do this. A detailed description is provided on
how to create them.

Updating plug- To be able to use the up-to-date functions of central Distributing CTS Service Plug-Ins to the Managed
ins CTS in the managed systems, the current version Systems [page 432]
of the CTS Service and CTS Bootstrapper plug-ins
must exist there. You can update them by clicking
on the corresponding link.

5.9.1.2.3.1 Starting the Central CTS Configuration Web UI

Use

You can start the UI using a transaction code if you have sufficient authorization to do so, or using your
favorites in the SAP Easy Access user menu.

Prerequisites

• You have activated the ICF service for the Central CTS Configuration Web UI.
• To start the UI using a transaction code, you have the required authorization.

Change Control Management

Quality Gate Management PUBLIC 625
Procedure

Starting Central Change and Transport System Configuration Web UI

To start the UI using a transaction code, log on to your SAP Solution Manager system and call transaction
SZENCONFIG.

Optional: Adding the Central CTS Configuration Web UI to your favorites in the SAP Easy Access user
menu

This allows you to call the Central CTS Configuration Web UI from the SAP Easy Access user menu.

1. In SAP Easy Access user menu, choose Favorites Add Other Objects Web Dynpro Application .
The Web Dynpro Application dialog box is displayed.
2. Enter CTS_CONFIGURATION in the Web Dynpro Application field.
3. Specify a description of the favorite, for example cCTS Config UI.

You can now start the Central CTS Configuration Web UI from your Easy Access user menu.

More Information

• Prerequisites for Configuring Central CTS [page 411]

• Authorizations for Configuring Central CTS [page 412]

5.9.1.2.3.2 Central CTS Configuration Web UI - Filtering

Context

You can use the filter function in the central Change and Transport System Configuration Web UI to reduce
the number of elements in your work area or to display only specific systems or clusters that match your filter
criteria.

Procedure

1. To enable the filter function, choose Filter.

A filter row appears.

2. Depending on the elements that are displayed in the column, either enter text or select filter criteria from
the dropdown list.

Change Control Management

626 PUBLIC Quality Gate Management
 You can enter any character or character strings. The system will search for any text that contains the
character or character string. You can combine different filter criteria in multiple text fields. Icons are
filtered using their tooltip text. For icons, you select the filter criterion from a dropdown list.

If you have selected a filter criterion from a dropdown list, the filtering result is immediately displayed.
3. If you have entered text, choose Enter to display the filter result.

5.9.1.2.3.3 Central CTS Configuration Web UI - Searching and

Refreshing Data

Use

When the Central CTS Configuration Web UI is called, the system performs an initial search. The search criteria
for the initial search may vary depending on the application that starts the Central CTS Configuration Web UI.
If you start the UI directly, the system initially searches for all systems and system clusters in the transport
landscape.

You can use the search function to perform a search according to specific criteria. By default, the search
criteria are hidden. You can display them using Display Search Criteria. The results of the search are displayed
in the work area.

The Refresh function is available in the work area. It refreshes the data for the systems and clusters that are
displayed in the work area. Note that the refresh function does not perform a new search. It just refreshes the
data for all systems that have been found using the search and for all clusters that have been created during
the current session.

Procedure

Performing a Search

1. To enable the search, choose Display Search Criteria.

2. Enter your search criteria or select them from the value help. You can specify a range or use the asterisk
(*).
3. Optional: Select or deselect the options under Further Settings.
4. To start the search, choose Search or Search and Hide Search Criteria as required.
The systems and clusters that are found are displayed in the work area. The search criteria are either
displayed or hidden depending on the option that you selected. If you select Search and Hide Search
Criteria and no systems and clusters are found, the search criteria are still displayed.
5. Reset Search Criteria resets the search criteria to the values with which the Central CTS Configuration Web
UI was started.

Performing a Refresh

1. To refresh the data in the work area, choose Refresh.

Change Control Management

Quality Gate Management PUBLIC 627
Example

You want to display all clusters that start with an A. You enter A* in the Cluster ID field. Cluster AB1 is displayed.

Afterwards, you create cluster CD2. Cluster CD2 is also displayed in the work area. Then, another user adds
systems to cluster CD2.

If you use the Refresh function, the data for both clusters AB1 and CD2 is refreshed in the work area. The
systems that the other user has added are now displayed.

The other user then creates cluster AB3 in another session. If you use the Refresh function now, cluster AB3
will not be displayed because the refresh function only refreshes data in the work area. It does not perform a
new search. To display cluster AB3, you need to perform a new search.

5.9.1.2.3.4 Central CTS Configuration Web UI -

Personalization

Use

Web Dynpro provides a framework for personalizing applications. Since the Central CTS Configuration Web UI
is a Web Dynpro application, it offers the default options for personalizing general settings. In addition, it offers
other options for adjusting the layout in the work area to your requirements.

Procedure

1. Choose Personalize....
2. A dialog box opens with the following tabs:
• General Settings
• Other Settings
3. Make your changes on the tab pages as desired. For more information on the options you have on the tab
pages, refer to the sections below.
4. To confirm your settings, choose Save.

Personalizing General Settings

On this tab you can add columns to and remove columns from the list as well as change the sequence of the
columns. You can also reset to the default settings.

 Note

The first column is a key column. You cannot move it.

 Note

If you move columns in Central CTS Web UI using drag & drop this will be reflected in the list here.

Change Control Management

628 PUBLIC Quality Gate Management
Personalizing Other Settings

• Number of Visible Rows

You can change the number of visible rows in the Work Area. Up to 99 rows are allowed. Reset resets the
number of visible rows to the default value of 20.
• Display as ...
You can set the display of the work area as a flat list or a hierarchical list.
The hierarchical list displays clusters and their systems in one column, and is therefore able to group
certain information. This reduces the number of columns displayed and provides a better overview. The flat
list displays clusters and systems and their descriptions in individual columns. This option provides more
filter options.

 Note

You can also set the type of list display by selecting it from the dropdown list in the work area.

• Display Systems not yet assigned to a Cluster in ...

You can specify where systems are displayed which are not yet assigned to a cluster. They are either
displayed in the main view in the work area or in a separate tab (separate view). If main view is selected,
systems without cluster assignment are grouped in a “dummy”cluster called N.A. (not applicable) only for
display reasons. You cannot display or edit the N.A. cluster.
• Automatic Validation
You can specify whether the system automatically starts a validation after you have made an important
change to the configuration. Important changes are creating or deleting a cluster, or making changes to a
cluster, for example.
• Distribution of Configuration
You can specify if the TMS configuration is to be distributed by default after you have made an important
change to the configuration. You can override the default setting on the individual dialog boxes.

More Information

For more information on how to personalize Web Dynpro ABAP applications, see .

5.9.1.2.4 Tasks for Configuring Central CTS

Use

To be able to use central CTS you need to create system clusters and assign the systems in your transport
landscape to these clusters. To be able to work with the clusters, you have to make additional settings. This
includes setting TMS parameters to classify systems as managed systems, configuring RFC destinations for
communication between the CTS server and the managed system, and distributing CTS plug-ins which contain
the CTS functions required on the managed systems. The system tells you which tasks you must perform when
you validate a system in the Central CTS Configuration Web UI.

Change Control Management

Quality Gate Management PUBLIC 629
  Note

You do not have to perform the tasks in a specific sequence. However, some tasks depend on each other.
For example, the import destination is required to distribute CTS plug-ins.

In addition, you must ensure that the transports created in the systems that belong to system clusters reach
the correct systems. Therefore, you need to connect the system clusters as well as define import targets for
the systems that belong to the clusters. You do this in the classic Transport Management System. The Central
CTS Configuration Web UI cannot validate whether you have performed these tasks.

Procedure

Tasks in the Central CTS Configuration UI

• Creating or Changing System Clusters [page 421]

• Setting TMS Parameters for Central CTS [page 424]
• Configuring RFC Destinations for Central CTS [page 428]
• Distributing CTS Plug-Ins to the Managed Systems [page 432]

Additional Tasks

• Connecting System Clusters [page 433]

• Defining Import Targets [page 434]

5.9.1.2.4.1 Creating or Changing System Clusters

Use

You create system clusters to group different systems with the same role. You do this in the Central CTS
Configuration Web UI.

From a technical point of view, this means creating a virtual system with a system ID as a system cluster, and
assigning systems that are to be contained in the cluster.

Prerequisites

• The systems fulfill the basic requirements to be included in system clusters (Release and Support Package
level).
• You are in the Central CTS Configuration Web UI.

Change Control Management

630 PUBLIC Quality Gate Management
Procedure

Creating a New Cluster

1. To create a new cluster and add systems to it, choose Cluster Create Cluster .
2. In the dialog box, enter the required information, such as Cluster ID and Description. The Cluster ID must
consist of three characters and must be unique within the transport domain.
3. If you are configuring a source cluster, that is if you want to group development (source) systems in one
cluster, select the Source cluster check box.
For source clusters, you must select a client. The client is required to create transport collections.
Therefore, you must select the client in which you want to use Transport Organizer and in which you want
to create transport collections. Since the cluster is a virtual system, you must use the client of the ABAP
communication system of the cluster. The correct client is usually the production client of the system to
which you are currently logged on.
4. Optional: If you want to add systems to the system cluster, select the systems from the list.

 Note

If you want to add a system to the cluster that is not contained in the list, check that the configuration
of the Landscape Management Database (LMDB) is consistent. You can do this in LMDB on the tab
page Transport Domains.

For source systems, also select the client where you want to use Transport Organizer and in which you want
to create transport requests.
• For ABAP and dual-stack systems: All clients that exist in the ABAP system are displayed. Select the
client in which development takes place. If you want to develop in multiple clients of an ABAP system
you can add the system more than once using different clients.
• For non-ABAP systems: The client that has been defined as TMS parameter NON_ABAP_WBO_CLIENT
for this system is pre-selected. You cannot edit the client here.
• For virtual or external systems: You must enter a client only if extended transport control is active in
the system. You can either select one of the clients that exist in the system (or in the communication
system) or enter any other client. This option is useful if you want to prepare the cluster assignment
for systems or clients which do not yet exist.
For target systems, it depends on your transport strategy whether you must select a client or not.
• For target ABAP and dual-stack systems: You must select a client only if extended transport control is
active in the system. All clients that exist in the system can be selected. If extended transport control is
not active, no client can be selected.
• For target non-ABAP systems: No client can be selected.
• For virtual or external systems: You must enter a client only if extended transport control is active in
the system. You can either select one of the clients that exist in the system (or in the communication
system) or enter any other client. This option is useful if you want to prepare the cluster assignment
for systems or clients which do not yet exist.
5. If you want to distribute the TMS configuration to all systems in the transport landscape after the cluster
has been created, select the corresponding checkbox.
6. Choose Check to check your entries for completeness and consistency without closing the dialog box.
7. If the check does not display any errors create the cluster.

Change Control Management

Quality Gate Management PUBLIC 631
  Note

The cluster can only be created if the client is valid.

Changing an Existing Cluster

1. To change an existing cluster, select the link with the cluster ID.
2. Choose Display <-> Change.
Except for the cluster ID, you can change any data of the cluster.
3. Optional: To add systems to the cluster, choose Add Row and select the system that you want to add to the
cluster. If a client is required, proceed as described under Creating a New Cluster.
4. Optional: To remove systems from the cluster, choose Delete Row for the corresponding system.

 Note

Before you remove a system from a cluster make sure that there are no modifiable transport requests
of this system that are part of modifiable transport collections of the cluster. Otherwise, you will get an
inconsistent system state.

If you have defined an import target for the removed system you must delete the entry for this system
after removing the system from the cluster.

5. Repeat the previous steps for all systems that you want to add to the cluster or delete from it.
6. If you want to distribute the TMS configuration to all systems in the transport landscape after the cluster
has been changed, select the corresponding checkbox.
7. Choose Check to check your entries for completeness and consistency without closing the dialog box.
8. If the check does not display any errors save your changes.

Result

The cluster has been created in the transport domain of the system to which you are logged on or changes
have been made to an existing cluster of this transport domain.

More Information

• System Cluster [page 403]

• For more information on clients, see Clients and Their Roles.
• TMS Parameters for Central CTS [page 426]
• Deleting a System Cluster [page 435]
• Defining Import Targets [page 434]

Change Control Management

632 PUBLIC Quality Gate Management
5.9.1.2.4.2 Setting TMS Parameters for Central CTS

Use

To be able to use central CTS, you must set specific parameters in the Transport Management System
(TMS) configuration. Depending on whether the managed system belongs to the same transport domain
as the central CTS server or not, you can use the Central CTS Configuration Web UI to set the missing TMS
parameters or you must set them in TMS.

The following TMS parameters are relevant for central CTS:

• MANAGED_SYSTEM: Classifying the system of a cluster as a managed system.

• OPERATION_MODE: Specifying the operating mode of a managed system to define the level of control that
the central CTS server has over this system and influence the import sequence of the transport requests in
the transport collection, if required.
• NON_ABAP_WBO_CLIENT: Specifying the logon client of Transport Organizer in all non-ABAP source
systems and source clusters to make sure that transport requests are created in the correct client.

 Note

The TMS parameter NON_ABAP_WBO_CLIENT is used when you configure non-ABAP systems for CTS
transports. You can set this parameter only in TMS. In the Central CTS Configuration Web UI, it is only
displayed.

Prerequisites

You have executed a validation in the Central CTS Configuration Web UI and the system tells you that TMS
parameters are invalid.

Procedure

Setting TMS Parameters for Systems in the Same Transport Domain

If the managed system belongs to the same transport domain as the central CTS server you can use the central
CTS Configuration Web UI to set the missing TMS parameters.

To do this, proceed as follows:

1. In the central CTS Configuration Web UI, choose the TMS Parameters invalid link.
2. Choose Display <-> Change.
3. The invalid TMS parameters have a red traffic light icon next to their value.
4. Select correct values for the invalid TMS parameters. If the value for NON_ABAP_WBO_CLIENT is invalid,
proceed as described under Setting TMS Parameters for Systems in a Foreign Transport Domain.
5. If you set the value for OPERATION_MODE to QUEUED or QUEUED_DYNAMIC, a job needs to be scheduled for
the program SCTS_QUEUE_IMPORT_CONTROL which is used for importing the transport requests in the
managed system. Choose Create to create this job in the managed system.

Change Control Management

Quality Gate Management PUBLIC 633
6. To check the values for completeness and consistency, choose Check.
7. If no errors are displayed, save your changes.

Setting TMS Parameters for Systems in a Foreign Transport Domain

If the managed system is not part of the transport domain of the central CTS server or of a linked domain,
you can only display the TMS parameters in the Central CTS Configuration Web UI. You cannot change them
there. In addition, if the system is not part of a linked transport domain, you must have performed the Managed
Systems Configuration in SAP Solution Manager Configuration (transaction SOLMAN_SETUP) to be able to
display them.

To set the TMS parameters, you must start TMS in the transport domain controller of the managed system.

To do this proceed as follows:

1. In the central CTS Configuration Web UI, choose See details for the managed system that has invalid TMS
parameters.
2. The dialog box displays a specific message for each invalid or missing TMS parameter. To set the invalid
or missing TMS parameters, follow the instructions described in the specific messages. The general
procedure is as follows:
1. Log on to the transport domain controller of the system that you want to classify as a managed
system.
2. Call transaction STMS.
3. Choose System Overview.
4. Select the required system by double-clicking it.
The screen Display TMS Configuration: System <SID> appears.
5. Choose the tab page Transport Tool and switch to change mode.
6. Add the parameters for the invalid or missing parameters and assign the appropriate values as
described under TMS Parameters for Central CTS [page 426].
7. Save the settings and distribute the configuration.
8. Repeat the previous steps for all managed systems that have invalid TMS parameters.

Schedule a Job for Operation Mode QUEUED or QUEUED_DYNAMIC for Systems in a Foreign
Transport Domain
If the managed system is not part of the transport domain of the central CTS server or of a linked domain, you
cannot use the central CTS Configuration Web UI to schedule a job on the managed system if you use one of
the operation modes QUEUED or QUEUED_DYNAMIC. Proceed as follows:

1. Log on to the managed system for which the operation mode is set, and use transaction SA38 to execute
program SCTS_SCHEDULE_IMPORT4QUEUED.
You can leave the default options unchanged. These are:

Program Options

Job Class C: Regular Priority

Delete existing jobs Selected

Schedule a job Selected

2. Execute the program.

If you left the default options unchanged, all existing jobs are deleted and a new job is scheduled called
SAP_CCTS_&<system name>&_QUEUED_IMPORT.

Change Control Management

634 PUBLIC Quality Gate Management
 Schedule exactly one job for every managed system with QUEUED or QUEUED_DYNAMIC.

Result

You have set the TMS parameters required to configure central CTS. By doing this, you have done the following:

• You have converted the systems involved into managed systems.

• You have defined the level of control that central CTS has for these managed systems.
• If you have set different operation modes for different systems, you have influenced the import sequence of
the transport requests in the system cluster.

5.9.1.2.4.2.1 TMS Parameters for Central CTS

Use

The following TMS parameters are required to work with central CTS.

MANAGED_SYSTEM

This parameter classifies the system as managed.

The following values are available:

Value Description

TRUE The system is managed by central CTS.

PARTLY The system is managed partially by central CTS.

You can control imports both using the central CTS server and using the local Transport
Management System. Transport requests that were created using central CTS are controlled by
central CTS. Transport requests that were created locally in the SAP system can be imported
using the local Transport Management System.

You can use this value if you want to introduce central CTS step-by-step or for test purposes.

 Note

To use Change Request Management or Quality Gate Management with central CTS, you must set this
parameter to PARTLY.

OPERATION_MODE

This parameter specifies the operating mode of the system. It defines the extent of import control that
the central CTS has for the managed systems. You can also use this parameter to define the extent of
parallelization of the import.

It must always be set in connection with the TMS parameter MANAGED_SYSTEM.

Change Control Management

Quality Gate Management PUBLIC 635
The following values are available:

 Note

The following description of the parameters is valid for all transport requests that were created using
central CTS if the TMS parameter MANAGED_SYSTEM is set to TRUE or PARTLY. However, it does not apply
to transport requests that were created locally in the system if MANAGED_SYSTEM is set to PARTLY.

Value Description

CONTROLLED The central CTS server controls the transports in the managed systems. Imports can no longer
be executed locally in the managed systems. The transport requests of the systems of a
system cluster for which the operation mode is set are imported into the target systems in
sequential order, one after another.

QUEUED The central CTS server controls the transports in the managed systems. Imports can no longer
be executed locally in the managed systems. The transport requests of all systems of a system
cluster for which the operation mode is set are imported into the target systems in parallel. All
imports are started at the same time.

This operation mode enables the parallel import of transport requests to all systems of a
system cluster for which this operation mode is set. This can reduce the overall import time
when importing into large clusters.

For this operation mode, you must schedule a job for the import of transport requests in the
managed system. For more information, see Setting TMS Parameters for Central CTS [page
424].

PROPOSED The central CTS server suggests imports for the managed systems by placing transports in the
import queue. Imports must be started locally in the system. We recommend that you schedule
regular import jobs.

MONITORED The central CTS server only has a monitoring function. Transports must be started locally in the
systems.

<value for The addition _DYNAMIC is used if process tools on top of central CTS, such as Change Request
OPERATION_MODE>_DY- Management, define the degree of control for the managed systems.
NAMIC

 Note

To use Change Request Management or Quality Gate Management with central CTS, you must set this
parameter to CONTROLLED_DYNAMIC, or QUEUED_DYNAMIC.

 Note

If a cluster contains systems where the operation mode is set to CONTROLLED_DYNAMIC as well
as QUEUED_DYNAMIC, the imports are processed (in sequential order) in systems with operation
mode CONTROLLED_DYNAMIC first. The imports in systems with operation mode QUEUED_DYNAMIC are
processed afterwards (in parallel). This means that you can use the parameter to define an import
sequence in your systems.

Change Control Management

636 PUBLIC Quality Gate Management
NON_ABAP_WBO_CLIENT

This parameter specifies the logon client of Transport Organizer. It is used for communication with the source
system. It is required for all non-ABAP source systems and for system clusters. If you have performed the
configuration steps for non-ABAP transports, this parameter already exists in your source systems.

 Note

You can only set this parameter in TMS. You cannot set it in the Central CTS Configuration Web UI.

The following values are available:

Value Description

000-999 Value of the logon client in Transport Organizer. This is the client in which your TMS was
configured and in which you are developing.

More Information

• Setting TMS Parameters for Central CTS [page 424]

• Parameters for Non-ABAP Transports

5.9.1.2.4.3 Configuring RFC Destinations for Central CTS

Use

To enable communication of the central CTS server with its managed systems RFC connections must exist
from the central CTS server to the managed systems. For managed non-ABAP systems, the RFC connection
must exist from the central CTS server to the ABAP communication system of the managed system.

This includes the following RFC destinations:

• Transport Organizer destination: Required for working with transport requests (creating, deleting,
changing transport requests). This destination is required for source systems only.
• Import destination: Required for importing the CTS plug-ins to the managed systems
• Deploy destination: The import process of a transport collection needs this destination to be able to
import transport requests that are assigned to a transport collection.

Prerequisites

• You have performed a validation in the Central CTS Configuration Web UI and the system tells you that RFC
connections are missing.

Change Control Management

Quality Gate Management PUBLIC 637
• You use Trusted System to log on to the managed system.
• You use Secure Network Connection (SNC) for RFC communication with managed systems.
• For the deploy destination, you need a technical user with specific authorizations in all managed systems.

Procedure

The Transport Organizer and import destinations can be re-used from existing SAP Solution Manager
destinations. These were created when performing Managed Systems Configuration in SAP Solution Manager
Configuration (transaction SOLMAN_SETUP). If the system tells you that either the Transport Organizer or the
Import destination is missing, check the SAP Solution Manager Configuration.

The following procedure applies if you want to configure the Deploy destination:

1. Log on to the central CTS server (SAP Solution Manager system) and call the RFC destination maintenance
using transaction code SM59.
2. Navigate to ABAP connections and create new ABAP R/3 Connections (Type 3).
3. Enter the data as described in Deploy Destination [page 430].
4. To create the destination, choose Save.
5. To make sure that the destination has been configured correctly, perform the tests available in transaction
SM59.

 Note

To perform the authorization test, the user that performs the test (logon user) must have the
authorizations as described for the individual RFC destinations. Otherwise, the test can fail even
though the RFC destination was correctly configured.

Result

You have configured an RFC connection to a managed system. Afterwards, validate the system again.

More Information

• For more information on configuring RFC destinations, see Displaying, Maintaining, and Testing
Destinations.
• For more information on Trusted System, see Maintaining Trust Relationships between SAP Systems.
• For more information on Secure Network Connection (SNC), see Secure Network Communications (SNC).
• For more information on how to create a user for the deploy destination, see Deploy Destination [page
430].

Change Control Management

638 PUBLIC Quality Gate Management
5.9.1.2.4.3.1 Deploy Destination

Use

The import process of a transport collection needs this destination to be able to import transport requests
that are assigned to a transport collection. This destination is required for all communication systems of target
clusters. It points from the communication system of the cluster (central CTS server) to a managed ABAP
system or to the communication system of a managed non-ABAP system.

Enter the following data:

• Name according to the following naming convention: TMSDPL@<SID>.<Domain_Name>

 Note

All entries are case-sensitive.

• Technical Settings tab: Target Host:

• For ABAP systems: Use the actual managed system as the Target Host for the destination.
• For non-ABAP systems: Use the communication system of the managed system as the Target Host for
the destination.
• Logon & Security tab: We strongly recommend that you use Trusted system with the technical user
described in the Prerequisites section.
• Language: Enter a language that is installed both in the central CTS Server and in the managed system.
We recommend that you use English (EN).
• Client: Enter the client of the managed system in which you have created the technical user.
• User: Enter the technical user that you created in the managed system.
• Trust Relationship: Select Yes.
In addition, to encrypt communication data, we recommend that you use Secure Network Connection
(SNC) for RFC communication with managed target systems.

Using this setup, you make sure that only user DDIC in client 000 is allowed to communicate using the deploy
destination.

 Example

The non-ABAP system NAT is configured as target system and uses system ABC as the communication
system in domain DOMAIN_ABC. System ABC is also the central CTS server. In this case you must create a
deploy destination [email protected]_ABC.

Prerequisites

For the deploy destination, you need a technical user with specific authorizations and roles assigned in all
managed systems. This user is used for communication between the central CTS server and the managed
system. You must create this user in the managed system. For non-ABAP systems, you must create it in the
communication system of the managed system.

Change Control Management

Quality Gate Management PUBLIC 639
To create this technical user including the necessary roles, proceed as follows:

1. Log on to the managed system for which you need the Deploy destination in any client.

 Note

Remember in which client you created the technical user since you must later enter this data for the
Deploy destination.

2. Create a copy of the role SAP_BC_TRANSPORT_OPERATOR, for example Z_BC_TRANSP_OP. We recommend

that you always assign copies of roles.
3. Create a new role, for example Z_TRANS_RFC_ACL. The new role must contain the authorization object
S_RFCACL. Use the following field values for the authorization object S_RFCACL:

Field Technical Name Value

Activity ACTVT Execute (16)

RFC client or domain RFC_CLIENT 000 (required for import process)

RFC same user ID RFC_EQUSER Call by the same user is not possible
(No)

RFC information RFC_INFO *

System ID (for SAP and External) RFC_SYSID <communication system of the clus-
ter>

RFC transaction code RFC_TCODE *

RFC User (SAP or External) RFC_USER DDIC

4. Create a technical user of type System, for example CCTSTRANS.

5. Assign the roles that you created before to this user.

More Information

Authorization Object S_RFCACL.

Change Control Management

640 PUBLIC Quality Gate Management
5.9.1.2.4.4 Distributing CTS Plug-Ins to the Managed
Systems

Prerequisites

• You have performed a validation in the central CTS Configuration Web UI and the system tells you that the
CTS plug-ins (CTS Service or CTS Bootstrapper plug-ins) in the managed system are not up-to-date.
• All prerequisites are fulfilled as described in Prerequisites for Configuring Central CTS. [page 411]
• The import destination exists for the distribution of CTS Service plug-ins.
• The managed system has the required version of the transport tools tp and R3trans.
For more information, see SAP Note 1665940 .

Context

Using the Central CTS Configuration Web UI you can distribute the CTS Service and CTS Bootstrapper plug-ins
from the central CTS server to the managed systems.

Procedure

1. In the Central Change and Transport System Configuration Web UI, choose the link Plug-In not up-to-date.
2. A dialog box opens where you must confirm that you want to distribute the plug-in to the relevant system.

On this dialog box, you can navigate to the validation details on the plug-in distribution status. This
provides an overview of the installed plug-in versions and the versions that are available for installation as
well as the import destination and transport tools functions.
3. Choose Distribute Plug-ins.

The CTS plug-ins which must be updated are distributed to the managed system.

Next Steps

• Technical Details on the CTS Plug-In [page 383]

• Central CTS Configuration Web UI - Configuring RFC Destinations [page 428]

Change Control Management

Quality Gate Management PUBLIC 641
5.9.1.2.4.5 Connecting System Clusters

Context

To enable transports between system clusters you need to define transport routes between the clusters. This is
done in the same way as for systems.

Procedure

1. To connect clusters, start Transport Management System (transaction STMS) in your central CTS server.

2. In the menu choose Overview Transport Routes .

3. Configure the transport routes for the system cluster just as you would for individual systems. That is,
define a consolidation transport route from the development cluster to the quality cluster and a delivery
transport route from the quality cluster to the production cluster.

 Caution

When you create the consolidation route, make sure that the standard transport layer is added.

Results

These transport routes determine the transport process of transport collections.

To define the transport process for transport requests of the individual systems, you must also define the
import targets of the individual systems.

Next Steps

Configuring the Transport Routes

Change Control Management

642 PUBLIC Quality Gate Management
5.9.1.2.4.6 Defining Import Targets

Prerequisites

You have defined the transport routes for the individual systems that belong to the cluster.

Context

After you have configured transport routes for the system clusters, you must define how the individual
transport requests are to be transported along these transport routes. To do this you must define the import
targets for the transport requests.

Procedure

1. Start Transport Management System (transaction STMS) in the central CTS server.
2. Choose Transport Routes.
3. Switch to change mode using Display <-> Change.
4. Double-click to select the target cluster for which you want to define import targets.
5. Choose the Import Targets tab.
6. In the Request Source column, enter the system from which the transport requests are to be exported
(source system for transport requests). This is always the development system, also if you have a three-
system track (DEV, TST, PRD) and you are defining import targets for the production cluster.
7. In the Source Client column, only enter a client if you use extended transport control and if you want to
make sure that the developments of a specific client in the source system reach a specific client in the
target system. In all other situations, especially for non-ABAP systems, do not enter any client. Leave the
field empty.
8. In the Target System column, enter the system into which the transport requests are to be imported (target
system for transport requests).
9. In the Target Client column, only enter a client if you use extended transport control and if you want to
make sure that the developments of a specific client in the source system reach a specific client in the
target system. In all other situations, especially for non-ABAP systems, do not enter any client. Leave the
field empty.
10. Choose Continue.

Ensure that the transport route for the import target runs along a cluster transport route that is already
defined. The system does not check your entries.
11. Repeat these steps for all systems that belong to target clusters in your system landscape. If you develop
in multiple clients of an ABAP system, repeat these steps for all clients in which you want to execute
transports.

Change Control Management

Quality Gate Management PUBLIC 643
Results

You have defined the import targets for the systems that are contained in clusters. If you have performed
all configuration steps for central CTS you can use it with Change Request Management or Quality Gate
Management.

Next Steps

Configuring Transport Routes

5.9.1.2.4.7 Deleting System Clusters

Prerequisites

• You are in the Central CTS Configuration Web UI.

• The cluster that you want to delete does not contain any open transport collections that must still be
transported through the system landscape. Otherwise, you will get an inconsistent system state.

Context

After you performed an initial configuration of central CTS, your systems are ready for work with central CTS.
After some time, you may want to make changes to this initial configuration. For example, you may want to
delete a system cluster because development of a project has ended.

 Caution

Delete system clusters only in the Central CTS Configuration Web UI. Do not delete any system clusters in
Transport Management System. Otherwise, you will get an inconsistent system state.

Procedure

1. To delete an existing cluster, select the cluster and choose Cluster Delete Cluster .
2. To confirm the deletion, choose Delete.

Change Control Management

644 PUBLIC Quality Gate Management
Results

You have deleted a system cluster.

If the system cluster was connected to other system clusters using transport routes, you must delete the
transport routes.

If you have defined import targets for the systems that are part of your cluster, you should delete these as well.

Next Steps

Deleting Transport Routes

5.9.1.3 Using Central Change and Transport System

Context

Central Change and Transport System (central CTS) is used as the technical infrastructure for the enhanced
flexibility functions for Change Request Management and Quality Gate Management (QGM). Usually, you do
not use central CTS directly. However, for special tasks, you may want or need to use central CTS functions
directly:

• Displaying information related to central CTS

• Displaying Transport Collections on the Central CTS Server
On the central CTS server, you can use CTS Transport Manager Web UI to display transport collections
including all transport requests, and objects, as well as assigned changes and project cycles that
belong to them.
• Displaying Assignments to Transport Collections in Managed Systems
In managed systems, you can display the transport collections to which a transport request is
assigned.
• Performing Imports into System Clusters
In specific situations, you can import transport collections in system clusters using Import Queue Web UI.
• Activating and Displaying the Application Log for Central CTS
You can activate an application log for actions triggered by central CTS.

See also:

• CTS Transport Manager Web UI - Layout [page 438]

• Displaying Transport Collections on the Central CTS Server [page 440]
• Displaying Assignments to Transport Collections in Managed Systems [page 441]
• Performing Imports into System Clusters [page 442]
• Activating and Displaying the Application Log for Central CTS [page 447]

Change Control Management

Quality Gate Management PUBLIC 645
5.9.1.3.1 Activating Services for CTS Transport Manager
Web UI

Prerequisites

• You have authorization for transaction SICF.

• All ICF services required to run an ABAP Web Dynpro application are activated.
For more information, see SAP Note 517484 .

Procedure

Activating Services for CTS Transport Organizer Web UI

1. Call transaction SICF. This transaction is a cross-client transaction.

2. Enter Service in the Hierarchy Type field and CTS_ZENUI_MANAGER in the Service Name field.
3. Choose Execute.
4. Select the CTS_ZENUI_MANAGER service on the Maintain Services screen.
5. Activate the service by opening the context menu (secondary mouse button) and choosing Activate
Service.
A dialog box for Activating ICF Services is displayed.
6. Choose Yes (with tree icon).

 Note

If you want to test the service, open the context menu (secondary mouse button) and choose Test
Service.

When you test the services for CTS Transport Manager Web UI, you can find its URL in the address bar
of the test system.

7. Repeat the previous steps for each of the following services:

• 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
• CTS_ORGANIZER_OBJECTLIST

Change Control Management

646 PUBLIC Quality Gate Management
5.9.1.3.2 CTS Transport Manager Web UI - Layout

Use

You can use CTS Transport Manager Web UI to display information related to central CTS, such as system
clusters, and transport collections including the transport requests that belong to them.

You do not use CTS Transport Manager Web UI to trigger actions related to central CTS. All actions related to
central CTS are usually triggered by Change Request Management or Quality Gate Management (QGM).

Prerequisites

You have activated the ICF Services for CTS Transport Manager Web UI.

Structure

Layout of CTS Transport Manager Web UI

The interface of CTS Transport Manager Web UI is divided into the following areas:

View Selection

Here you can select the view that you require, depending on the information you want to display.

You hide or display the view selection using the double arrow to get a larger detailed display of the views.

Below the view selection there are further selection options, such as Useful Links to Transport Organizer Web UI
and Transport Log Viewer.

Change Control Management

Quality Gate Management PUBLIC 647
Detailed Display of Views

The following views are available:

• Organize
In this view you can display transport collections for source clusters including assigned transport requests
and object lists. For systems that use Change Request Management or QGM, the assigned change and
project cycle are also displayed.
You can display the transport logs for transport collections.
In the Landscape area in the lower part of the screen, you see the system clusters of your transport
landscape in a graphical or list format, depending on your selection.
• Transport
In this view you can display import queues for target clusters. This view corresponds to the Import Queue
Web UI and the import overview of the Transport Management System (STMS) in the local systems. For
systems that use Change Request Management or QGM, the assigned change and project cycle are also
displayed.
In the Landscape area in the lower part of the screen, you see the system clusters of your transport
landscape in a graphical or list format, depending on your selection.
• Configuration
This view offers various functions on different tab pages:
• Systems and Landscape
This tab page displays clusters that you have configured using the Central CTS Configuration Web UI.
In the Landscape area in the lower part of the screen, you see the system clusters of your transport
landscape in a graphical format.
• Projects
When transport collections are created in Change Request Management or QGM, they are usually
assigned to a project cycle. Here you can display all changes and project cycles known in central CTS.
When you select a registered project type, all projects that belong to it are displayed including their IDs
and descriptions.
• Transport Locks
This tab page displays all active transport locks set for clusters by Change Request Management or
QGM.
• Application Log
The application log records all actions triggered in the central CTS area. On this tab page, you can
enable application logging and specify the logging detail level.

More Information

• Activating Services for CTS Transport Manager Web UI [page 437]

• Configuring Central Change and Transport System - Overview [page 407].
• For more information on Import Queue Web UI, see .
• Activating and Displaying the Application Log for Central CTS [page 447]

Change Control Management

648 PUBLIC Quality Gate Management
5.9.1.3.3 Displaying Transport Collections on the Central
CTS Server

Use

On the central CTS server (SAP Solution Manager), you can use CTS Transport Manager Web UI to display
transport collections together with their transport requests and further attributes, such as description, owner,
and return code. If the transport collection was created using Change Request Management or Quality Gate
Management, the assigned change and project cycles are also displayed.

Procedure

1. Start CTS Transport Manager Web UI using transaction code SZENTMS.

The Organize view is displayed by default.
2. Enter a source cluster for which you want to display transport collections.
3. To display transport collections for a specific user enter the user name as Owner. If you want to display all
transport collections of a selected cluster, enter an asterisk (*).
4. Optional: You can restrict the displayed transport collections to a specific status (Modifiable, or Exporting,
for example). To do this, select the respective option by clicking the small black arrow next to the Owner
input field.
This starts the search.
5. If the search is not started, choose Refresh to start the search.
The system displays all transport collections in a list that correspond to the search criteria.
6. You have the following options:
• You can expand the node for the transport collection to display the transport requests that belong to
the transport collection. Expanding the node further displays the objects contained in the transport
requests.
• You can navigate to the transport logs of the collection. To do this, select the transport collection and
choose Logs.
Transport Log Viewer opens in a new browser window.

More Information

CTS Transport Manager Web UI [page 438]

Change Control Management

Quality Gate Management PUBLIC 649
5.9.1.3.4 Displaying Assignments to Transport Collections
in Managed Systems

In the Transport Organizer Web UI, you see information about transport collection assignments of transport
requests in the systems managed by central CTS. You use this function if you have a transport request in the
managed system and want to know to which transport collection it belongs.

Prerequisites

The managed system or the communication system of the managed non-ABAP system is configured as
managed by central CTS. This means that in the managed system or in the communication system, the TMS
parameter MANAGED_SYSTEM is set to TRUE or PARTLY.

Context

Different versions of Transport Organizer Web UI are available depending on whether or not the CTS plug-in is
installed in the managed systems (or in the communication systems of the managed non-ABAP systems).

• In systems in which the CTS plug-in is not installed, the Web Dynpro ABAP applicationCTS_BROWSER is
available.
• In systems in which the CTS plug-in is installed, the Web Dynpro ABAP application CTS_ORGANIZER is
available (for SAP Solution Manager systems as of 7.1 and SAP NetWeaver systems as of 7.3 Enhancement
Package 1).

 Note

If you have distributed the CTS Service plug-in to the managed system, this does not mean that the CTS
plug-in is installed in this system. The CTS plug-in is installed as part of the initial installation of SAP
Solution Manager, or using SAP Add-On Installation Tool, or Software Update Manager.

Procedure

1. Start Transport Organizer Web UI on your managed development system or communication system of the
managed non-ABAP development system.
2. Depending on the Web Dynpro application you use, this is how you display the assignment to transport
collections:

• CTS_BROWSER
Select the link under Transport Collection to see the IDs of the corresponding transport collections and
further information.
If the transport request is part of exactly one transport collection, the link is the ID of this collection. If
the transport request is part of multiple collections, the link is labeled Multiple Collections and opens
the IDs of the corresponding transport collections.

Change Control Management

650 PUBLIC Quality Gate Management
 • CTS_ORGANIZER
1. To display an additional column, the Transport Collection column, personalize the Transport
Organizer Web UI.
The link under Transport Collection provides more information.
If the transport request is part of exactly one transport collection, the link is the ID of the
collection. If the transport request is part of multiple collections, the link is labeled Multiple (See
Details).
2. In the Details area of the transport request, open the Transport Collections tab page.
You see the IDs of the transport collections. If the transport collection is assigned to a project, you
can view more information about the project. If a URL has been assigned to the project, you can
select the link for more information.
3. To display the entire collection, select collection ID.

This opens CTS Transport Manager Web UI on the central CTS server, which displays the entire content of
the collection and its attributes, including projects, if the transport collection is assigned to a project.

Related Information

Setting TMS Parameters for Central CTS [page 424]

TMS Parameters for Central CTS [page 426]
Displaying Transport Collections on the Central CTS Server [page 440]

5.9.1.3.5 Performing Imports in System Clusters

Use

Usually, you import transport collections into system clusters using Change Request Management or Quality
Gate Management (QGM) and not using Import Queue Web UI. You use Import Queue Web UI only to display
import queues of system clusters.

However, in specific situations, you may also need to use Import Queue Web UI on SAP Solution Manager to
import transport collections into system clusters:

• In emergency situations, if functions of Change Request Management or QGM do not work.

• For transports into additional systems of your transport landscape where transports are not or not yet
controlled by Change Request Management or by QGM.
This applies to additional test, training, or sandbox systems, for example, for which process compliance is
not as important as for production systems.
These systems can be bundled as separate system clusters, and imports into these systems can be
performed in the central CTS server (SAP Solution Manager) using Import Queue Web UI.
• If you want to add new systems to an existing system landscape and you must therefore add a new cluster
to the related cluster landscape.
In this case, you must set up an initial import queue for the new system cluster using Import Queue Web UI.

If you are in such a situation, or if SAP support asks you to do so, you can activate Import Queue Web UI for
system clusters.

Change Control Management

Quality Gate Management PUBLIC 651
  Note

If SAP Solution Manager is not working at all, proceed as described under Performing Imports if SAP
Solution Manager is Not Working [page 445].

More Information

• Activating Import Queue Web UI for System Clusters [page 443]

• Importing Transport Collections into System Clusters [page 444]

5.9.1.3.5.1 Activating Import Queue Web UI for System

Clusters

Prerequisites

You are in one of the situations described in Performing Imports in System Clusters [page 442].

Context

If you use Change Request Management or QGM for transports, and if you need to perform imports into
clusters that are usually controlled by Change Request Management or QGM, you must switch off the import
locks for the target cluster that were set by Change Request Management or QGM before you can use Import
Queue Web UI.

Procedure

1. On the central CTS server (SAP Solution Manager), start Transport Management System using transaction
STMS.
2. Choose the target cluster from the System Overview.
3. On the TMS Configuration screen, choose the Transport Tools tab and add the parameter
watch_importlocks with the value false.
4. Save your entries.

Change Control Management

652 PUBLIC Quality Gate Management
Results

You can now use Import Queue Web UI on the central CTS server to perform imports of transport collections
into system clusters.

To de-activate Import Queue Web UI for imports into system clusters later on, delete parameter
watch_importlocks from the TMS configuration.

Next Steps

Importing Transport Collections into System Clusters [page 444]

5.9.1.3.5.2 Importing Transport Collections into System

Clusters

Use

The import of transport collections into system clusters works similar to the import of transport requests.

Prerequisites

You have activated Import Queue Web UI on your central CTS server (SAP Solution Manager) for the import of
transport collections using Import Queue Web UI.

Procedure

 Note

The following is an overview procedure of the steps involved in the import process. For detailed information
on how to perform imports using Import Queue Web UI, see the documentation reference in the More
Information section below.

1. On the central CTS server, start Import Queue Web UI using transaction code STMS_IMP.
2. Display the import queue of the required target cluster.
3. You have the following options:
• If you want to import all transport collections of the import queue, choose Import All and select the
required options for the import.
• If you want to import one or more transport collections, select the ones that you want to import.

Change Control Management

Quality Gate Management PUBLIC 653
 1. Optional: If you do not want to import all transport collections in the import queue, run the
dependency analysis.
To do this, choose Dependencies.
2. Optional: If the results of the dependency analysis show that you need to include more transport
collections in the import, select these as well.
3. Choose Import.
4. Select the required options for the import.
4. Choose Import.

Result

The imports are started or scheduled in the target cluster. This means that the transport requests belonging to
the transport collection are imported or scheduled in the respective target systems of the cluster. The relevant
status is displayed in Import Queue Web UI.

As long as the transport collection is in the import queue you can click the return code to open Transport Log
Viewer where you can see return codes and detailed logs of completed transport steps. After the transport
collection has disappeared from the queue you can display this information using Import History Web UI.

More Information

• Activating Import Queue Web UI for System Clusters [page 443]

5.9.1.3.6 Performing Imports if SAP Solution Manager is

Not Working

Context

In the following situation you may need to perform imports using the local Transport Management System
(TMS):

• You are using Change Request Management or Quality Gate Management (QGM).
• Your SAP Solution Manager (central CTS server) is currently not working.
• You urgently need to perform an import into a managed system.

In this case, you can temporarily switch on the local TMS to perform emergency imports.

This procedure is valid for ABAP transports only. It cannot be used for non-ABAP transports since SAP Solution
Manager is the communication system for managed non-ABAP systems.

Change Control Management

654 PUBLIC Quality Gate Management
Procedure

1. If your SAP Solution Manager system is configured as the domain controller for the managed system:
Activate the backup domain controller as the domain controller. The backup domain controller must have
the CTS plug-in (software component CTS_PLUG) installed. For more information on the CTS Plug-In, see
SAP Note 1665940 .
2. In the (new) domain controller, change the TMS parameter OPERATION_MODE to the value MONITORED for
the managed system into which you want to import the transport request. For more information, see the
link to Setting TMS Parameters for Central CTS in the More Information section below.

Distribute the configuration afterwards.

3. If the domain controller cannot be used or if you cannot install the CTS plug-in in the (backup) domain
controller you can change the TMS parameter directly by editing the transport profile in the managed
system.

 Caution

Only use this option if you are an expert user. If you edit the transport profile you do not have
to activate the backup domain controller. However, be aware of the fact that your changes to the
transport profile will be overwritten when the domain controller works again and the TMS configuration
is distributed. In addition, changes to the transport profile are not logged.

4. Start the import queue for the managed system and choose Refresh.

The transport requests that you want to import are still in status Inactive.

5. Select the transport requests that you want to import one after another and choose Extras Activate
Inactive Requests .
6. Select the transport requests that you want to import one after another and choose Import request.

The transport requests will be imported into the managed system.

7. After checking that your imports were successful, you can reset the configuration changes. To do this,
proceed as follows:
• Reset the TMS parameter OPERATION_MODE to the previous value (usually CONTROLLED_DYNAMIC).
• If you have moved the domain controller, re-activate SAP Solution Manager as the domain controller if
possible.
8. When SAP Solution Manager is available again we recommend that you change the status of the related
change document in Change Request Management or QGM so that it is consistent with the actual software
distribution status. The change tracking function will identify that the related imports were already
performed and will change the status without re-importing the request. Afterwards, Change Request
Management or QGM is consistent with the import status in the local systems.

Next Steps

• Activating the Backup Domain Controller

• Setting TMS Parameters for Central CTS [page 424]
• Transport Profile

Change Control Management

Quality Gate Management PUBLIC 655
• Change Request Management [page 21]

5.9.1.3.7 Activating and Displaying the Application Log for

Central CTS

Use

Central CTS comes with an application log that logs all actions triggered in the central CTS area. This also
includes any actions triggered in CTS. Unlike the transport log, the application log does not log the export or
import process itself, but all actions that lead to these processes including time stamps, users, and related
errors, such as authorization errors.

Procedure

Activating the Application Log for central CTS

To activate the application log for central CTS, proceed as follows:

1. Start CTS Transport Manager UI using transaction SZENTMS.

2. Select the Configuration view.
3. Choose the Application Log tab page.
4. Select the Enable application logging for CTS actions check box.
5. Select the logging detail level by choosing one of the radio buttons.

You have activated the application log for central CTS.

Displaying the Application Log for central CTS

When you have activated the application log for central CTS, you can display it as follows:

1. Start the analysis of application logs using transaction SLG1.

2. Enter CTS in the Object field.
3. Enter an asterisk (*) in the Subobject field.
4. The default time interval is the current day. You can change this interval.
5. Choose F8 .

The application log for central CTS displays the log information depending on the level of detail that you have
selected before.

More Information

CTS Transport Manager Web UI - Layout [page 438]

Change Control Management

656 PUBLIC Quality Gate Management
5.10 Enhanced Transport Functions with Central CTS

When you use the central Change and Transport System (central CTS) for Change Request Management or
QGM, some functions have enhanced features and specific prerequisites apply when working with them.

Prerequisites

You have activated central CTS for your change cycles. For more information, see Configuring Change Request
Management [page 473] and Setting Up Quality Gates and Assigning Phases [page 487].

Features

If you’re using central CTS for your scenario, the following functions work differently compared to standard
Change Request Management or QGM projects:

Change Request Management

• Decoupling a Transport Request [page 134]
• Assign Transport Requests [page 135]
• Reassigning Changes to Other Projects [page 141]
• Importing Transport Requests [page 127]
• Site-Specific Rollout of Changes [page 139]

Quality Gate Management

• Decoupling a Transport Request [page 525]
• Assigning a Transport Request [page 513]
• Importing Changes [page 514]

Change Control Management

Quality Gate Management PUBLIC 657
6 System Recommendations

With the System Recommendations app, you can manage the SAP Notes and support package patches that
are not yet implemented and installed on your managed systems. You can start the app from the SAP Solution
Manager launchpad.

For more information, see System Recommendations at http://help.sap.com/solman_fiori .

Change Control Management

658 PUBLIC System Recommendations
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Change Control Management

Important Disclaimers and Legal Information PUBLIC 659
www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN