Change Request Management scenario: Working exampl...

DoloresCorrea · ‎07-23-2009

Change Request Management scenario: Working examples Final Points and Appendix

This blog is the last part of the working case initiated in SDN blog : Change Request Management scenario: Working examples.

Here you will find also the possible actions and statuses of normal and urgent corrections, change documents and test messages.

Final points to remember

Never leave the SDMN document in edit mode you can get action errors in the associated corrections like "No link to maintenance cycle". Put the SDMN document in display mode and recheck the correction to fix the error.

You can move the MC phase to previous phases and move up again.

In TEST phase don't work at all with your SDMJ corrections, only with SDHF corrections and with SDTM test messages.

In EMERGENCY CORRECTION phase don't work at all with your SDMJ and SDHF corrections because you only are allow to create a TR and released it by using the task list directly.

Usually customers are most of the time in Development with Release phase.

Every time you move the phase up check the warning to see the corrections that are not in the correct status for this phase and contact the responsible to see how to work with these corrections.

When you schedule task "Import Transport Request (Background)" check that if you are running this job from an urgent correction the command is: tp IMPORT SMMK900688 SMM clires200 U0, and this TR remains in the import buffer until you don´t execute the job "Import Transport Request (Background)" from the M* task list. This job will run a tp IMPORT ALL SMM clires200 proj=0001,SMM_P00044

Last point, manual deletion of CRM documents in Charm may lead to serious problems such as database inconsistencies, please see note 902973 "Unrestricted deletion of change transactions"

Note that I am always working with same user and not with the correct users, change manager, developer, tester, IT user, etc. In the appendix you will see the person in charge of each action in each MC phase.

Appendix A. Interesting transactions to know

- solar_project_admin: to manage the project

- crmd_order or crm_dno_monitor: to find your documents

- /tmwflow/maintinst: to see your SDHF document and see to which project are assigned and to see the project task list directly

- /tmwflow/proj: to see the CTS status Switches and in Project Structure tab the TRs assigned to each correction, see below.

- /tmwflow/cmsconf: System Change Options

- /tmwflow/trmo: Tracking

Appendix B. Change request SDCR possible actions per status

*Step*	*Who- Where*	*User Status*	*Action*	*Final User Status*	*Details*
1	Change Manager - Solman	To be Approved	Authorize Change Request	Authorized
1	Change Manager - Solman	To be Approved	Reject ECR

Appendix C. Normal correction possible actions per status

*Step*	*Who- Where*	*Initial User Status*	*Action*	*Final User Status*
1	Change Manager- Solman	Created
2	Developer- Solman	Created	Set to "In Development"	In Development
2	Developer- Solman	Created	Cancel Procedure	Withdrawn
3	Developer - Solman	In Development	Logon to System	In Development
			Complete Development	To be Tested
			Cancel Procedure	Withdrawn
			Create Transport Request	In Development
			Create Task	In Development
			Critical Transport Objects	In Development
			Test Transports	In Development
			Transport into Sandbox System	In Development
			Go to the Task Plan	In Development
4	Tester- Solman	To be Tested	Logon to System	To be Tested
			Confirm Successful Test	Consolidated
			Reset Status to "in Development"	In Development
			Go to the Task Plan	To be Tested
5	Change Manager- Solman	Consolidated	Logon to System	Consolidated
			Set Production Status	Production
			Start Retrofit	Consolidated
			Go to the Task Plan	Consolidated

Appendix D. Urgent correction possible actions per status

*Step*	*Who- Where*	*Initial User Status*	*Action*	*Final User Status*
1	Change Manager- Solman	Created
2	Developer- Solman	Created	Set to "In Development"	In Development
2	Developer- Solman	Created	Withdraw Correction	Withdrawn
3	Developer - Solman	In Development	Logon to System	In Development
			Release Transport Request
			Pass Correction to Test	To be Tested
			Withdraw Correction	Withdrawn
			Create New Transport Request	In Development
			Create Task	In Development
			Critical Transport Objects
			Transport into Sandbox System
			Go to the Task Plan	In Development
4	Tester- Solman	To be Tested	Logon to System	To be Tested
			Confirm Successful Test	Successfully Tested
			Reset Status to "In Development"	In Development
			Go to Task Plan	To be Tested
5	Change Manager- Solman	Successfully tested	Logon to System	Successfully tested
			Released for Production	Authorized for Import
			Reset Status to "In Development"	In Development
			Go to Task Plan	Successfully tested
6	IT- Solman	Authorized for Import	Logon to System	Authorized for Import
			Import Correction to Production System	Production
			Reset Status to "In Development"	In Development
			Start Retrofit
			Go to Task Plan	Authorized for Import
7	Change Manager - Solman	Production	Logon to System	Production
			Confirm Correction	Confirmed
			Reset Status to "In Development"	In Development
			Go to Task Plan	Production
8	Change Manager - Solman	Confirmed	Logon to System	Confirmed
			Complete Correction	Completed
			Reset Status to "In Development"	In Development
			Go to Task Plan	Confirmed

Appendix E. Test Messages possible actions per status

*Step*	*Who- Where*	*Initial User Status*	*Action*	*Final User Status*
1	Tester- Solman	Created	Take "in Process"	In Process
2	Developer- Solman	Created	Take "in Process"	In Process
3	Developer- Solman	In Process	Logon to System	In Process
			Pass to "Retest"	To be Retested
			Create Transport Request	In Process
			Release Transport Request	In Process
			Create Task	In Process
			Go to Task Plan	In Process
4	Tester- Solman	To be Retested	Logon to System	To be Retested
			Confirm Correction	Confirmed
			Reset "in process"	In Process
			Go to Task Plan	To be Retested