Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
This documents covers how to manage the Charm , the change management tool in SolMan.
Process to create Charm, combine the changes in charm and move the changes to Production. Login to SOLMAN Production system. Enter the below Tcode solman_workcenter
Enter values as mentioned in below screen. Enter Description and Ext. Reference no. as per the request raised rest of the details will be same Also Enter Requester business partner whosoever will be working on this request.
Click on Transaction Data tab, and add Remedy attachment as per below also enter rest of the values as per the below screen. Enter Requestor id as the person whosoever is working on the request and Target Completion date as per the request.
Click on save button Thus it will go to Change Manager to Approve and once he approves status of the Charm will change to Authorize
This will create sub-request on which individual person will be working. Click on below button on main request page
Click on sub request no. and it will show the request as below.
Click on
Click on save button. As soon as we click on In Development it will prompt for Development system, select HRDCLNT220. Save.
Then in below screen it will prompt for Transport request type for the same always select Customizing request
Prepare the required changes in Transport request and copy them in the transport request created in sub request. This will prompt as per below screen.
Click on Own Request , Then click on Subtask as below. Thus changes will be combined in below transport request.
Click on Display
Double click the subtask, you need to update the documentation in subtask as below then click on button to release the sub task.
Once release. Click on Pass Correction to Test. This will move the changes to QA system and its status will change to To be Tested
Send the mail to Functional Team/ Owner to check the changes in QA- 400. Once confirmation received change the status of Charm to Successfully Tested and attach documents as per below.
UT Evidence and UAT Signoff Mail, this will confirm that Business/Functional team has to confirm the changes in QA.
Change Manager has to update his comments in below area confirming changes are fine to move to production.
Further to this QA team will check all the documents are in place with respect to the changes in Charm then he will change the status to Authorized for Import Then Basis will move the changes to Production, once done Basis will confirm to respective person that changes are move to production.