sap solution manager - charm - normal correction v0 1

7/23/2019 Sap Solution Manager - CHARM - Normal correction v0 1

http://slidepdf.com/reader/full/sap-solution-manager-charm-normal-correction-v0-1 1/19

Change Request ManagementNormal Correction with Change Request Management

08Fall

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 rW e n c e s l a o L a c a z e



Change Request Management – Normal Correction Lifecycle

Table of ContentsAuthor Bio ..................................................................................................................3

Landscape Preparation: .............................................................................................4Users Preparation: .....................................................................................................4Project Preparation ....................................................................................................4Cycle overview ..........................................................................................................5Start the Maintenance Cycle .....................................................................................5

Create the Change Request ...................................................................................5Aprove the Change Request ......................................................................................7

Authorize change ...................................................................................................7Create the Transports .............................................................................................8Start the corrections ...............................................................................................9

The Maintenance Cycle ........................................................................................... 11Release the Transports .........................................................................................11Import in QA .........................................................................................................12

Start the Testing Phase ............................................................................................14Import in Production ................................................................................................16

Start the import in Production ..............................................................................16Close the Change Document ...................................................................................18

3439024.doc of 19




Author BioMy name is Wenceslao Lacaze and I’ve been working as a SAPbasis Administrator and Solution Manager Consultant for the last 8

years.I’m a Techno-Functional SAP Solution Manager Subject MatterExpert (SME), I Design, Build and Implement the product using “RunSap” Methodology.I have developed a very extended experience with medium andlarge scaled SAP installations in several (multi)nationalenvironments.

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]://www.linkedin.com/in/solutionmanager

3439024.doc of 19

mailto:[email protected]

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

mailto:[email protected]

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




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.

Is the Steering Committee in the Change Management

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

3439024.doc of 19




Cycle overview

Start the Maintenance Cycle The Change Manager set the Maintenance Cycle in “Development with ReleasePhase”

Create the Change Request

The Requester logon to SM and run the transaction CRMD_ORDER.

3439024.doc of 19




Click in the Button “Normal Correction”, if you don’t have add manually in “Extra

Settings Specific Push Button 1 = SDCR

This is the Main Change Request Window.For create a Normal Correction you need to identify some information:

• Description

• SoldTo Party

• Requestor

• Change Manager

• Change Advisory Board

• Ibase/Component

•Description of the Change

Then Save.

3439024.doc of 19




Aprove the Change Request The Change Advisory Board decide wich kind of change document are necessaryfor this change.document , in this case select Normal Correction(Maintenace) and save.

Authorize change

The Change Manager recive the notification and then select “Authorize ChangeRequest”

When the Change Manager approve the Change Document, Solution Managerchange the document to Authorized and Create a new Normal CorrectionDocument.

3439024.doc of 19




The Change Manager open the Normal Correcion 800000170 and select “InDevelopment” in the TaskList

Create the Transports

Now the Normal Correction is in Status “In Development”. The Project Leader ,Change Manager or Developer inside Solution Manager createthe New Transport Request.

Solution Manager ask for the Request Owner, Short Descriotion and the developer

who make the tasks, the system create 2 transport in the development system, 1for Customizing, 1 for Workbench,

3439024.doc of 19




Start the corrections Tthe Developer logon to Solution Manager and and open the Normal Correction8000000170. Inside the Tasklist select “Logon to System”

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

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

3439024.doc of 19




The Developer select the request SM4K900051 Created for AOMEADM with the TASK SMK4900052 for DEVELOPER

Then the Developer release his Task SM4K900052 ,

The Developer return to SOLUTION MANAGER and in “Test Instruction” put theinstruction to the Tester, then move the Normal Correction to “CompleteDevelopment”

3439024.doc of 19




The Maintenance Cycle

Release the Transports

At this point the Change Manager release the transport Request manually usingthe transacction SCMA and then execute the task “Release transport Request”

Right Click over “Release Transport Request” and select “Schedule”

3439024.doc of 19




The Change Manager select the Execution Data and then run

The System show the Transport Request ready for release

Import in QA

The Change import the transport in QA Environment

3439024.doc of 19




Solution Manager show the Execution Data

Change Manager select the Import parameters and then start the process

3439024.doc of 19




Start the Testing Phase The Change Manager move the Phase of the Maintenance Cycle to Test to makethe integration test

The Tester logon to solution Manager and open the Normal Correction, Read the Test Instrucction , then use the TASKLIST for connect to the TEST system.

3439024.doc of 19




In the TEST System check the value

The TESTER return to SOLUTION MANAGER and write the Test Report, then in the TASKLIST select “Confirm Successful Test”

At this point the Normal correction is in Status Consolidated

3439024.doc of 19




Import in Production The Change Manager move the Phase to Go-Live to start the imports in theProductive enviroment

Start the import in Production

The change Manager run the “Import Transport Request”

3439024.doc of 19




Select the import execution and run the transaction

The Requester logon to the Production for check the import, if is correct changethe Normal Correction to “Production Status”.

3439024.doc of 19




The Normal correction is in Production status.

When the Normal Correction change the status to “Production”, the Changedocument change automatic to “Implemented” the status

Close the Change Document The Change Manager control all the documentation and then move the ChangeRequest to “Confirms Realization”.

3439024.doc of 19




The Change Request in Status “Confirmed” closing the cycle for this maintenace.

sap solution manager - charm - normal correction v0 1

Documents