Professional Documents
Culture Documents
Table of Contents
(/viewer/8b923a2175be4939816f0981b7
US/505ac239943d4733b925caa15c49391 Use Aa
Change Management Work Center
You can use this process to make urgent changes in your production system. The urgent change is mainly
(/viewer/8b923a2175be4939816f0981b7
US/d1ab2bc8-df8f-4f7e-ab53-9fd7a1d3a5 used for fast implementation, for example, if you want to x an error in existing functionality. The change
is transported into the production system faster than a normal change.
Processes in Change Request Managem
(/viewer/8b923a2175be4939816f0981b7
US/e48ac25411d76474e10000000a44538 Note
Request for Change
Test transports are not used in urgent changes. If an urgent change fails during testing, because the
(/viewer/8b923a2175be4939816f098 transport request was already released, a new transport request needs to be created. Then, the
US/4c315d1fdcdd4ff695f350fc984b06
developer can continue with the implementation of the required changes.
Change Document
(/viewer/8b923a2175be4939816f098 For central CTS-enabled cycles, the preliminary import function supports “uneven” cluster tracks,
US/71a7f315d1a344b6abf73e481db1 that is, not all system clusters in the cluster track contain the same number of systems with the same
Processing Normal Changes roles. For more information, see System Cluster
(/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-
(/viewer/8b923a2175be4939816f0
US/48db938dceba518de1000000 US/b9f89d5197eb5905e10000000a44538d.html).
Processing Standard Changes
(/viewer/8b923a2175be4939816f0
US/b94c1c6855094ab5a6cfdc86a3 Caution
Processing Urgent Changes As transport requests created outside of Change Request Management cannot be identi ed by the
same application as belonging to a scenario, users must not be permitted to create, maintain, or
(/viewer/8b923a2175be4939816f
US/48db8900a73b04e7e1000000 release transport requests or tasks directly in the Transport Organizer.
Using the Code Inspector in U
(/viewer/8b923a2175be49398
US/0ae9da51ebcb3e57e10000 Prerequisites
Distributing Urgent Changes
(/ i /8b923 2175b 49398
A request for change has been created and approved, and a change document of the category
Urgent Change has been generated by the system. The request for change has been released for
development.
The request for change is linked to a continual cycle Urgent changes can only be used in continual
https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-US/48db8900a73b04e7e10000000a42189c.html 1/6
11/03/2019 Processing Urgent Changes - SAP Help Portal
The request for change is linked to a continual cycle. Urgent changes can only be used in continual
Table of Contents cycles.
Change Request Management in the We
If you have been using SAP Solution Manager before, you have con gured the dialog window to
(/viewer/8b923a2175be4939816f0981b7 create transport requests. For more information, see Con guring the Dialog Window for Creating
US/505ac239943d4733b925caa15c49391 Transport Requests in Urgent Changes (/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en- Aa
Change Management Work Center US/5b9e8ac73cb74c95adf104a109dc5a22.html).
(/viewer/8b923a2175be4939816f0981b7
US/d1ab2bc8-df8f-4f7e-ab53-9fd7a1d3a5
Change Document
(/viewer/8b923a2175be4939816f098
US/71a7f315d1a344b6abf73e481db1
https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-US/48db8900a73b04e7e10000000a42189c.html 2/6
11/03/2019 Processing Urgent Changes - SAP Help Portal
Table of Contents
Change Request Management in the We
(/viewer/8b923a2175be4939816f0981b7
US/505ac239943d4733b925caa15c49391
Aa
Change Management Work Center
(/viewer/8b923a2175be4939816f0981b7
US/d1ab2bc8-df8f-4f7e-ab53-9fd7a1d3a5
Change Document
(/viewer/8b923a2175be4939816f098
US/71a7f315d1a344b6abf73e481db1
Distributing Urgent Changes Various options are available in this dialog box:
Table of Contents
Change Request Management in the We 3. The developer logs on to the development system via the Landscape assignment block. He
(/viewer/8b923a2175be4939816f0981b7 implements the requested features in the development system and saves his work to the tasks
US/505ac239943d4733b925caa15c49391 assigned to him by the lead developer.
Aa
Change Management Work Center
4. The developer releases the transport request manually in the Transport Management assignment
(/viewer/8b923a2175be4939816f0981b7 block. The original transport is exported from the development system.
US/d1ab2bc8-df8f-4f7e-ab53-9fd7a1d3a5
Processes in Change Request Managem When releasing the transport request, a code inspector check is run. For more information, see
Using the Code Inspector in Urgent Changes
(/viewer/8b923a2175be4939816f0981b7
US/e48ac25411d76474e10000000a44538 (/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-
US/0ae9da51ebcb3e57e10000000a441470.html).
Request for Change
(/viewer/8b923a2175be4939816f098 5. The developer forwards the urgent change to testing, by choosing Actions Pass Urgent Change
US/4c315d1fdcdd4ff695f350fc984b06
To Test . He then saves the change document.
Change Document
6. The change document is now in status To be Tested and the original transport is imported into the
(/viewer/8b923a2175be4939816f098
US/71a7f315d1a344b6abf73e481db1 test system.
Processing Normal Changes 7. The IT operator calls up the document. He assigns the document to a tester, who can see it in his
(/viewer/8b923a2175be4939816f0 worklist.
US/48db938dceba518de1000000
Table of Contents The change manager can now change the status of the urgent change to “Authorized for
Production”.
Change Request Management in the We
(/viewer/8b923a2175be4939816f0981b7 9. The change manager approves the urgent change for import into the production system, by
US/505ac239943d4733b925caa15c49391 choosing Action Authorize Urgent Change for Production , and forwards the change document
Aa
Change Management Work Center to an IT operator.
(/viewer/8b923a2175be4939816f0981b7
10. The IT operator calls up the document. He triggers the import of the urgent change into the
US/d1ab2bc8-df8f-4f7e-ab53-9fd7a1d3a5
production system, by choosing Action Import Urgent Change into Production System . The
Processes in Change Request Managem
status of the urgent change is now Imported into Production.
(/viewer/8b923a2175be4939816f0981b7
US/e48ac25411d76474e10000000a44538 11. The change manager con rms that the change has been made by choosing Action Con rm
Request for Change Urgent Change . The status changes to “Con rmed”.
(/viewer/8b923a2175be4939816f098
The system updates the status of the request for change to Implemented. This is only true if all
US/4c315d1fdcdd4ff695f350fc984b06
follow-on change documents related to the request for change are in nal status. The last change
Change Document
document related to a request for change that has the status Completed updates the request for
(/viewer/8b923a2175be4939816f098 change status.
US/71a7f315d1a344b6abf73e481db1
Processing Normal Changes 12. The Change Manager chooses Action Complete Urgent Change which sets the document in the
nal status Completed. The change document is now locked for editing.
(/viewer/8b923a2175be4939816f0
US/48db938dceba518de1000000
Using the Code Inspector in U After the transport request of the urgent change document is imported into the QA and production
(/viewer/8b923a2175be49398 systems, the transport request remains in the import buffer, so that the changes are not overwritten
US/0ae9da51ebcb3e57e10000 by other transport requests in the normal change cycle.
Distributing Urgent Changes
(/ i /8b923 2175b 49398
Note
If you want to set multiple change documents to the next status (from Approved for Import to
Productive, for example), execute the batch job CRM_SOCM_SERVICE_REPORT. You can also
https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-US/48db8900a73b04e7e10000000a42189c.html 5/6
11/03/2019 Processing Urgent Changes - SAP Help Portal
use this report to import all changes at a scheduled time, into the follow-on systems.
Table of Contents
Caution: Using this report for a batch import of multiple documents may lead to issues:
Change Request Management in the We
(/viewer/8b923a2175be4939816f0981b7 a. The dependencies of different change documents are not foreseeable. As a result, the
US/505ac239943d4733b925caa15c49391 system cannot process the import order automatically. Aa
Change Management Work Center
b. If multiple imports are triggered simultaneously, the tp program might be impacted due
(/viewer/8b923a2175be4939816f0981b7
to interferences.
US/d1ab2bc8-df8f-4f7e-ab53-9fd7a1d3a5
Change Document
More information on Change Request Management-related roles and pro les: SAP Note 834534
(/viewer/8b923a2175be4939816f098 (http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/834534) and
US/71a7f315d1a344b6abf73e481db1
Security Guide SAP Solution Manager at http://service.sap.com/securityguide
Processing Normal Changes (http://help.sap.com/disclaimer?site=http://service.sap.com/securityguide) SAP
(/viewer/8b923a2175be4939816f0 Components SAP Solution Manager <current release> Security Guide SAP Solution
US/48db938dceba518de1000000 Manager .
Processing Standard Changes
(/viewer/8b923a2175be4939816f0 Previous (/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-US/b94c1c6855094ab5a6cfdc86a3cb055b.html) Next
US/b94c1c6855094ab5a6cfdc86a3
https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.05/en-US/48db8900a73b04e7e10000000a42189c.html 6/6