Professional Documents
Culture Documents
08
uuu
h t t p : / / w w w. l i n ke d i n . c o m / i n / s o l u t i o n m a n a g e r
We nce sl ao L aca ze
Change Request Management – Urgent Correction Lifecycle Management
Table of Contents
Author Bio..................................................................................................................3
Landscape Preparation:.............................................................................................4
Users Preparation:.....................................................................................................4
Project Preparation....................................................................................................4
Cycle overview..........................................................................................................5
Create the Change Request...................................................................................5
Aprove the Change Request...................................................................................7
Start the corrections...............................................................................................8
Release the modifictation to test.........................................................................11
Start the Testing Phase.........................................................................................12
Release to Production...........................................................................................13
Confirm the Correction ........................................................................................14
Complete the Cycle..............................................................................................15
See the log...........................................................................................................17
3439018.doc Page 2 of 17
Change Request Management – Urgent Correction Lifecycle Management
Author Bio
My name is Wenceslao Lacaze and I’ve been working as a SAP
basis Administrator and Solution Manager Consultant for the last 8
years.
I’m a Techno-Functional SAP Solution Manager Subject Matter
Expert (SME), I Design, Build and Implement the product using “Run
Sap” Methodology.
I have developed a very extended experience with medium and
large scaled SAP installations in several (multi)national
environments.
3439018.doc Page 3 of 17
Change Request Management – Urgent Correction Lifecycle Management
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
Project Preparation
We create a project and 1 Maintenace cycle
3439018.doc Page 4 of 17
Change Request Management – Urgent Correction Lifecycle Management
Cycle overview
Click in the Button “Urgent Correction”, if you don’t have add manually in “Extra
Settings Specific Push Button 1 = SDHF
3439018.doc Page 5 of 17
Change Request Management – Urgent Correction Lifecycle Management
• Description of Change
• Reason of Change
Then Save
3439018.doc Page 6 of 17
Change Request Management – Urgent Correction Lifecycle Management
The system show all the Transaction open, The Change Manager (CHM) double
click over the transacion 80000163.
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.
3439018.doc Page 7 of 17
Change Request Management – Urgent Correction Lifecycle Management
3439018.doc Page 8 of 17
Change Request Management – Urgent Correction Lifecycle Management
Inside the Development system(SMR-801) , the developer make some change and
Save.
Make a Change
The Developer select the request SM4K900047 Created for CHMANAGER with the
TASK SMK4900048 for DEVELOPER
3439018.doc Page 9 of 17
Change Request Management – Urgent Correction Lifecycle Management
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 the Tester
3439018.doc Page 10 of 17
Change Request Management – Urgent Correction Lifecycle Management
The system show the Transport request for select the releated. (1 for Customizing
and 1 for Workbench)
The Change Manager Select “Pass Correction to Test to move the Urgent Correction
to QA
3439018.doc Page 11 of 17
Change Request Management – Urgent Correction Lifecycle Management
3439018.doc Page 12 of 17
Change Request Management – Urgent Correction Lifecycle Management
The Tester return to Solution Manager and write the Test Report, then in the
TASKLIST select “Confirm Successful Test”
Release to Production
The Change Manager logon in Solution Manager and in the TASKLIST select
“Released for Production”
3439018.doc Page 13 of 17
Change Request Management – Urgent Correction Lifecycle Management
The IT Operator logon to Solution Manager and in the TASKLIST select “Import
Correction to Production System”.
3439018.doc Page 14 of 17
Change Request Management – Urgent Correction Lifecycle Management
The Requester return to Solution Manager and select “Confirm Correction” in the
TASKLIST
3439018.doc Page 15 of 17
Change Request Management – Urgent Correction Lifecycle Management
3439018.doc Page 16 of 17
Change Request Management – Urgent Correction Lifecycle Management
Full Text
General Note REQUESTER 04.11.2007 15:34:19
Task list created in SAP Change Manager
Task list H000000022 created in SAP Change Manager
Description of Change REQUESTER 04.11.2007 15:42:15
Update T005A
Reason for Change REQUESTER 04.11.2007 15:47:57
Update the information in Table T005A for TAX
Effect on System(s) REQUESTER 04.11.2007 15:52:39
Work with old information
General Note CHMANAGER 04.11.2007 15:57:23
The status was set to the value 'In Development'
General Note CHMANAGER 04.11.2007 16:10:15
Requests SM4K900045 SM4K900047 created
Test Instruction DEVELOPER 04.11.2007 16:22:56
Logon and Check the Table T005A
General Note DEVELOPER 04.11.2007 16:25:38
Imported into subsequent system started
The status was set to the value 'To Be Tested'
Test Instruction DEVELOPER 04.11.2007 16:32:00
See the content of T005A with SM30
Test Report TESTER 04.11.2007 16:32:00
The test was OK
General Note TESTER 04.11.2007 16:32:00
The status was set to the value 'Successfully Tested'
General Note CCHMANAGER 04.11.2007 16:38:03
The status was set to the value 'Authorized for Import'
General Note ITOPERATOR 04.11.2007 16:40:47
Import into production system started
The status was set to the value 'Production'
General Note REQUESTER 04.11.2007 16:45:21
The status was set to the value 'Confirmed'
General Note CHMANAGER 04.11.2007 16:48:22
Task list H000000022 in the SAP Change Manager Completed
3439018.doc Page 17 of 17