Skip to Content
0

ChaRM Approval Process

May 01, 2017 at 08:01 PM

55

avatar image

We are considering the use of ChaRM for our change management process, and I would like to be sure I've accurately captured the process. I would be grateful if those using ChaRM would validate that I have the steps correct below. If not, I'd love your feedback on what I'm not understanding.

(1) Create Request for Change and populate requirement, expected change details, etc.

(2) Requestor or Systems Analyst modifies status to "Release for Approval"

(3) Manager reviews change details, and if approved, modifies status to "Release for Development"

(4) Systems Analyst or Developer generates transport within ChaRM, then makes necessary configuration or ABAP changes, and assigns them to the transport

(5) Following unit testing in the development environment, Systems Analyst or Developer modifies status to "Awaiting Approval"

(6) Manager reviews unit test documentation against original requirement, and if approved, modifies status to "Pass Change to Test"

(7) Basis team imports transport to QA

(8) Requestor performs integration testing in QA

(9) If tests fail, go back to step 4, else Systems Analyst or Developer modifies status to "Awaiting Approval"

(10) Manager reviews integration test documentation against original requirement and validates requestor sign-off, and if approved, modifies status to "Pass Change to Production"

(11) Basis team imports transport to Production

(12) Systems Analyst / Requestor validate change in Production

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers