Change Control Management

This document provides information about new, changed, and deleted functions in the change control management in SAP Solution Manager 7.2 SPS 1.

Change Control Management

Function	Type of Change	Description	More Information
Administration cockpit	New	As a central entry point to the administrative activities for Change Control Management, it replaces functions that were previously available in SAP GUI, for example, task list management, definition of critical transport objects, and tracking changes.	Administration Cockpit
SAP Solution Manager Configuration	Changed	Change Control Management is available as a scenario, with the following subscenarios: Change Request Management Quality Gate Management Managed System Setup	SAP Solution Manager Configuration work center
CTS Plug-In	Enhanced	Central CTS: Domain links from the central CTS server to the managed systems are no longer necessary. Improved handling of erroneous customer transports that have the return code 8. The transport log now issues a warning in the deployment step if a target system is not defined for a transport request that belongs to a transport collection. Improved readability of transport logs. Improved search capabilities in CTS Transport Manager Web UI. The import of a transport collection no longer fails if one system in the system cluster is down.	Central Change and Transport System
“Missing transports” risk type	Enhanced	When you release a transport request, missing transport risks are now displayed only if the transport request is in the queue of the target system. For example, if your system landscape comprises systems ABC, DEF, and XYZ and you release a transport request in system ABC, the missing transport risk is shown only for system DEF. The risk is not shown for system XYZ because the transport request is not yet in the queue for this system.	For Change Request Management, see Landscape Assignment Block. For Quality Gate Management, see Risks.
Downgrade protection	Enhanced	In the Customizing activity Configure Downgrade Protection, the Switch off and Cancel at options have been replaced by the new Check Mode dropdown list, which also contains a “warning” option. By setting a combination of the conflict type and the check mode, you can gain a greater degree of control over how the system responds in the event that a downgrade conflict is detected. Any action that results in a transport request being released or imported triggers a conflicts popup in which the user can cancel the release or import, or ignore any conflicts and continue with the release or import. This applies if the warning mode has been configured.	Downgrade Protection
Cross-system object lock	Changed	The cross-system object lock monitor (transaction /TMWFLOW/LOCKMON) has been replaced by the cross-system object lock manager in the administration cockpit. It now supports the registering of cross-system object lock entries for multiple transport requests in a batch run.	Creating Cross-System Object Lock Entries
Transport management	New	Apply the SAP Notes 1977240 and 2148577 to your managed systems in order to have transport management system data automatically transferred to the system landscape directory (SLD) and from there to the landscape management database (LMDB). If you do not apply these SAP Notes, the data is not transferred.	SAP Solution Manager Configuration Change Control Management Managed System Setup Configure LMDB

Change Request Management

Function	Type of Change	Description	More Information
Change Request Management configuration	Changed	If you want to use Change Request Management, you have to set it up by following the steps described in SAP Solution Manager Configuration and SAP Solution Manager Customizing. SAP Solution Manager project administration (transaction SOLAR_PROJECT_ADMIN) is not used any longer.	Configuring Change Request Management
Release planning	New	You can use release management to plan, manage, and coordinate your release activities.	Release Planning
Change cycles	New	The following change cycles are available: SMRE: Release cycle SMAI: Continual cycle (was: Maintenance cycle, SMMM) SMIM: Phase cycle (was: Implementation cycle, SMDV and SMMN)	Change Cycle
Change cycles	Enhanced	You can use change cycles with or without managing software changes. This means you can use change cycles with or without task lists.	Using Change Cycles Without a Task List
Task lists	New	You can create task lists in the WebClient UI, using a guided procedure.	Creating Task Lists
Task lists	Enhanced	You can redefine your system landscape and then recreate the task list structure based on the new landscape.	Redefining a Landscape
Change transactions	Removed	The following transaction types are no longer delivered with the standard Customizing settings: SDCR: Request for change SDHF: Urgent change SDMI, SDMJ: Normal change SDAD: Administrative change SDCD: Job request change document SDMM: Maintenance cycle SDMN: Maintenance cycle SDMV: Implementation cycle Any documents with transaction types that have been copied from standard SD transaction types must be closed before you upgrade to Release 7.2. In the WebClient UI, use the transaction types that are delivered with standard SAP Customizing for Change Request Management.
Change transactions	Changed	The content of the Details assignment block has changed. It contains data for the change cycle, branch, and change control landscape.	Functions in Change Transactions
Approvals	Enhanced	You can now use approval procedures for change documents.	Approval Procedures
Partner functions	Changed	The partner function “Support Team” has been renamed to “Development Team” .
Solution Documentation assignment block	New	The Solution Documentation assignment block contains the elements that are assigned to the change transaction. It shows how the change transaction is integrated in the solution	Solution Documentation Assignment Block
Documents and Projects and Solutions assignment blocks	Changed	The Documents and Projects and Solutions assignment blocks can only be displayed in the WebClient UI.	Documents Assignment Block and Projects and Solutions Assignment Block
Processing normal changes	Enhanced	In order to import changes immediately into the test system, without having to wait for the next import job, the COPY_ALL_ENH Change Request Management action is available. You can assign it to your normal change, replacing the COPY_ALL action.	Processing Normal Changes
Change documents	Enhanced	You can create follow-up transactions for change documents. By default, you can create the following transactions: Task Knowledge article Problem Defect correction E-Mail	Follow-Up Transactions
Transports into the sandbox system	New	You can now create transports to the sandbox system for urgent changes and defect corrections. New action definitions are available. You can use the enhanced Change Request Management action COPY_ALL_ENH to create and release transports of copies in the development system and import them into the target system.	Transports into the Sandbox System
Uneven cluster tracks	New	“Uneven” cluster tracks mean that not all system clusters in a cluster track contain the same number of systems with the same roles. Uneven landscapes are fully supported in the central CTS scenarios, that is, in the preliminary import of normal changes and the automatic import of urgent changes.	System Cluster
Reassigning change transactions	Changed, enhanced	You can reassign change transactions to change cycles with or without task lists, depending on specific conditions. You can now reassign requests for change to other change cycles.	Reassigning Change Transactions to Other Change Cycles
Change Request Management actions	Deleted	The following Change Request Management actions have been removed: APPRV_CO_WEB ASSIGN_TRA CALL_SE09 CREATE_REQ CREATE_TASK DECOUPLE_TRA NAVIGATE_SYS NAVI_SYS_WEB NAV_TEST_PLA
Change Request Management actions	New	The following new Change Request Management actions are available: COPY_ALL_ENH CREATE_REQ_W CR_TASKLIST RELEASE_COPY SET_CYC_CMPL SET_DATE_DY SET_STA_TASK SET_SUCCDOC SOL_DOC_ACT SOL_DOC_CREA	Customizing under SAP Solution Manager Capabilities Change Control Management Change Request Management Framework Actions in Change Request Management Define Actions .
Change Request Management consistency checks	Deleted	The consistency check S_USER_CHECK (S user existence check) has been removed.
Change Request Management consistency checks	New	The following new consistency checks are available: BO_LINK_REVERSE CHECKLIST_DONE CHECK_PPM_STATUS_SET CHECK_PROCESSOR CROSSING_ROUTES CYCLE_COMPLETE_CHECK DISTRIBUTOR FATHER_IS_PRODUCTIVE IB_CMP_OK MAINT_CAT NO_SCOPE_OR_REJECTED REL_PHASE_TEST_CHECK SOL_DOC_ACT_CHECK SOL_DOC_ACT_PRECHECK TR_REQ_EXIST TR_REQ_OPEN TSKL_CAN_BE_CLOSED	Customizing under SAP Solution Manager Capabilities Change Control Management Change Request Management Framework Consistency Checks Define Consistency Checks .
Retrofit	Enhanced	You can perform retrofits for systems that are on different support package, enhancement package, or release levels. The system performs various checks to ensure that no downgrade occurs. You can use the retrofit functions without using Change Request Management. You can start the retrofit directly from the Transport Management assignment block using a pushbutton.	Dual Landscape Synchronization (Retrofit)
Critical objects	Changed	The UI for defining critical object checks has been changed. In order to uniquely identify a system, the system type is displayed, for example, ABAP. The field displaying the date when the data was updated has been removed, as data is now permanently retrieved from the LMDB. You can now use the checkbox in the Cross-System Object Lock field to specify whether the setting is active.	Critical Transport Object Checks
Automatic import of urgent changes in parallel systems	Removed, changed	The following reports are not available anymore. You can now synchronize urgent changes directly from the task list. /TMWFLOW/SCMA_BTCH_SYNC_UC /TMWFLOW/SCMA_BTCH_SYNC_TEST	Administration Cockpit Synchronizing Urgent Changes in Parallel Systems
Integration with Requirements Management	New	You can create change documents or requests for change based on an IT requirement. Alternatively, you can handle the requested change as part of a project in PPMS.	Requirements Management
Reports in Change Request Management	Removed, changed	The transactions /TMWFLOW/REPORTINGN and SOLAR_EVAL are not supported anymore. You can now use the search function in the administration cockpit.	Change Request Management Reporting
Tracking changes for a project	Removed, changed	Transaction /TMWFLOW/TRMO is replaced by the transport analysis function in the administration cockpit.	Transport Analysis
Project logistics	Removed	Transaction /TMWFLOW/PROJ is replaced by functions in the administration cockpit, on the Task Lists, Landscape Overview, and Transport Analysis tab pages.	Administration Cockpit
Schedule imports	Removed	The report /TMWFLOW/SCHEDULE_IMPORT is no longer available. You can now schedule imports for a specific date or for random periods (for example, every 15 minutes, hourly, daily) directly from the task list, in the administration cockpit.	Starting an Import: Scheduling
Scheduling tool	Removed	Transaction /TMWFLOW/MAINTINST has been replaced by the Task Lists tab page in the administration cockpit.	Administration Cockpit
Configuration check	Changed	You can call up the configuration check for a change cycle now in the WebClient UI, under More Actions and in the administration cockpit, on the Task Lists tab page. The report /TMWFLOW/CHARMCHK is no longer available.	Configuration Check
Product maintenance monitor	Removed	Transaction /TMWFLOW/MAINTENANCE has been replaced by the search function in the administration cockpit.
System change options, critical objects	Removed	Report /TMWFLOW/CMSCONF has been replaced by the Landscape Overview and the Critical Objects tab pages in the administration cockpit.	Administration Cockpit

Quality Gate Management

Function	Type of Change	Description	More Information
User interface	Changed	The user interface for quality gate management has been streamlined to improve usability. The most significant changes include the following: Projects have been replaced by QGM scenarios. The tab pages containing project data have been consolidated into an Actions... dropdown list. The guided procedure for creating a scenario (formerly a project) has been restructured. Quality gate management now consists of two main interfaces: one for the scenario and one for the changes and transport requests. Links are provided on each of the UIs to access information such as task lists, downgrade protection, and risks.	Quality Gate Management Overview
Calendar View and Landscape View	Changed	These views are now based on SAP UI5 technology, which provides powerful functions that can you use to manage your data. Load times have been significantly improved as a result of this change.	Calendar View Landscape View
Integration with Change Request Management	Changed	Quality Gate Management is no longer integrated with Change Request Management.	–
Transports into a sandbox system	New	You can now create and release transports of copies to a sandbox system.	Transporting to a Sandbox System
Dialog box for quality gate details	Deleted	We have removed the issues tab from the dialog box containing the details of the quality gates.	Quality Gates
Business partners for quality manager and quality advisory board	Changed	You can now enter the business partner number of an organizational unit so that any member of the unit can pass a quality gate. You can also define a substitute for your business partner (individual only) by setting the relationship Replaces in business partner maintenance.	Assigning Groups of Business Partners
Release and import of transport requests	Changed	When you release a change from the Changes table or from the Scenario Transport button, you can select which transports you want to release. When you import the transport requests, you must import all of the transport requests belonging to the associated change.	Creating and Releasing Transport Requests Importing Changes