Sap Sol Man

8/2/2019 Sap Sol Man

1/18

uuu

Change Request ManagementUsing Urgent Correction with Change Request Management

SAP Solution Manager

h t t p : / / w w w . l i n k e d i n . c o m / i n / s o l u t i o n m a n a g e r

W e n c e s l a o L a c a z e


2/18

Change Request Management Urgent Correction Lifecycle Management

SAP-SOLMAN-CHARM-UrgentCorrection-v2.0.doc Page 2 of 18

Table of Contents

Author Bio Versioning ......................................................... ............................................................ ..................................3Author Bio ............................................................ ............................................................ ...................................................... 3Landscape Preparation:....................................................................................................................................................4Users Preparation: ...................................................... ............................................................ ............................................ 4Project Preparation.............................................................................................................................................................4Cycle overview......................................................................................................................................................................5

Create the Change Request ..................................................... ............................................................ ........................5Aprove the Change Request........................................................................................................................................7Start the corrections......................................................................................................................................................8Release the modifictation to test .................................................... ............................................................ ........... 11Start the Testing Phase............................................................. ............................................................ ..................... 12Release to Production..................................................... ............................................................ ............................... 14

Confirm the Correction........................................ ............................................................ .......................................... 15Complete the Cycle................... ............................................................. ........................................................ .............. 16See the log...... ............................................................ ............................................................ ......................................... 17


3/18



Author Bio VersioningVersion Change Date

1.0 Original 10/06/2008

2.0 Webpage Link. 23/06/2008

Author BioMy name is Wenceslao Lacaze and Ive been working as a SAP basis

Administrator and Solution Manager Consultant for the last 8 years.

Im a Techno-Functional SAP Solution Manager Subject Matter Expert (SME), IDesign, Build and Implement the product using Run Sap Methodology.

I have developed a very extended experience with medium and large scaledSAP installations in several (multi)national environments.

I am based in Argentina, but work all around the World.I work directly for clients or via an agency.

I do speak Spanish, Italian and English fluently.You can contact me at:

Email: [email protected]

http://www.linkedin.com/in/solutionmanager

You can found more papers at :

http://wlacaze.googlepages.com/home


4/18



Landscape Preparation:For this Demo we use 3 client inside Solution Manager

801 Development

802 Quality

803 Productive

Users Preparation:We create 5 diferent users and profiles

Creates and confirm the Change Request

Categorizes, Approve and monitors Change Request.

Implements a change, and hands it over to the Tester

Test changes and ajust the Change Document Status

Manages and coordinates software logistics

Project PreparationWe create a project and 1 Maintenace cycle


5/18



Cycle overview

Create the Change Request

The Requester logon to SM and run the transaction CRMD_ORDER.

Click in the Button Urgent Correction, if you dont have add manually in Extra Settings

Specific Push Button 1 = SDHF


6/18



This is the Main Change Request Window.

For create a Urgent Correction you need to identify some information:

Description Change Manager It Operator Current Processor Ibase/Component

Description of Change

Reason of Change

Effect on the System

Then Save


7/18



Aprove the Change Request

The Change Manager logon to the system and run the transaction CRM_DNO_MONITOR

The system show all the Transaction open, The Change Manager (CHM) double click over thetransacion 80000163.

The system show this warning.

The CHANGE MANAGER read the Urgent correction document and select if Approve or Withdraw

the document, in this sample we aprove putting the document in In Development the task.


8/18



When the CHANGE MANAGERsave, the system create 2 transport in the development system, 1

for Customizing, 1 for Workbench, SOLUTION MANAGER ask for the Request Owner, Shortdescription and the Task Employee,(Ussualy the developer)

When we save, the document status change to In Development.

Start the corrections

Tthe Developer logon to SOLUTION MANAGER and open the Urgent Correction 8000000163.Inside the Tasklist select Logon to System

Inside the Development system(SMR-801) , the developer make some change and Save.


9/18



Make a Change

The Satellite System (SM4-801) ask for a request,


10/18



The Developer select the request SM4K900047 Created for CHMANAGER with the TASK

SMK4900048 for DEVELOPER

Then the Developer release his Task SM4K900048 , You can see that the TASK is for user

Developer and the Transport if for user Chmanager.

Then the Developer return to Solution Manager and in Test Instruction put the task for theTester


11/18



Release the modifictation to test

Then the Change Manager go to the TASKLIST and set Release Transport Requests.

The system show the Transport request for select the releated. (1 for Customizing and 1 for

Workbench)


12/18



The Change Manager Select Pass Correction to Test to move the Urgent Correction to QA

Solution Manager in automatic way start the import in QA

Start the Testing Phase

The Tester logon to Solution Manager and open the Urgent Correction 800000163 and Read the

Test Instrucction , then use the TASKLIST for connect to the TEST system.


13/18



In the TEST System check the value modificated before.

The Tester return to Solution Manager and write the Test Report, then in the TASKLIST select

Confirm Successful Test


14/18



Release to Production

The Change Manager logon in Solution Manager and in the TASKLIST select Released forProduction

The IT Operator logon to Solution Manager and in the TASKLIST select Import Correction to

Production System.

The System start the import


15/18



Confirm the Correction

The REQUESTER logon in SOLUTION MANAGER and in the TASKLIST Select Logon to System tologon in the productive enviroment for check the modification.

In the Productive enviroment check the values.

The Requester return to Solution Manager and select Confirm Correction in the TASKLIST


16/18



Complete the Cycle

The CHANGE MANAGERselect in the TASKLIST Complete Correction

SOLUTION MANAGER Show a warning for complete the Urgent Correction

SOLUTION MANAGER show the check of all the Task List.


17/18



Now the Urgent Correction is in Status Completed.

See the log

Solution Manager create a log for all the task during the change management cycle.

Full TextGeneral Note REQUESTER 04.11.2007 15:34:19Task list created in SAP Change ManagerTask list H000000022 created in SAP Change ManagerDescription of Change REQUESTER 04.11.2007 15:42:15Update T005AReason for Change REQUESTER 04.11.2007 15:47:57Update the information in Table T005A for TAXEffect on System(s) REQUESTER 04.11.2007 15:52:39Work with old informationGeneral Note CHMANAGER 04.11.2007 15:57:23The status was set to the value 'In Development'General Note CHMANAGER 04.11.2007 16:10:15Requests SM4K900045 SM4K900047 createdTest Instruction DEVELOPER 04.11.2007 16:22:56Logon and Check the Table T005AGeneral Note DEVELOPER 04.11.2007 16:25:38Imported into subsequent system startedThe status was set to the value 'To Be Tested'Test Instruction DEVELOPER 04.11.2007 16:32:00See the content of T005A with SM30Test Report TESTER 04.11.2007 16:32:00

The test was OKGeneral Note TESTER 04.11.2007 16:32:00The status was set to the value 'Successfully Tested'


18/18


General Note CCHMANAGER 04.11.2007 16:38:03The status was set to the value 'Authorized for Import'General Note ITOPERATOR 04.11.2007 16:40:47Import into production system startedThe status was set to the value 'Production'General Note REQUESTER 04.11.2007 16:45:21The status was set to the value 'Confirmed'

General Note CHMANAGER 04.11.2007 16:48:22Task list H000000022 in the SAP Change Manager Completed

Documents

Sap Sol Man