on 06-27-2012 9:46 AM
Hi,
here I'd like to ask some questions about the usage of CHARM in Business Blueprinting phase.
The Requirements from customer side change very fast in this phase. So the related documents like PDD, FSD or test case docs should be changed accordingly. Our goal is to go through a process for monitoring, approving and implementing this kind of changes.
The thought is to mirror one Change Request to one Requirement change, in this Requirement change, it should be checked, which document should be changed, and if one doc is done, we set a flag.
What is in your opinion the best way to handle this with CHARM? Which transaction type should we use? Is it possible to use multiple Change Documents within one Change Request? How should we handle the flag?
Thanks a lot!
Regards,
Kris
Hi Kris,
Charm itself following its own process flow. It has all the Phases(scope, design,test, , with allign to its term as
Dev without release
Dev with releese
testing
...
..
Golive.
Thease in term of charm called as Project cycle phases, and maintenance cycle phases.
http://help.sap.com/saphelp_sm71_sp01/helpdata/en/4c/315d1fdcdd4ff695f350fc984b0647/content.htm
By default, means standard charm flow itself has approval of change request by change manager and change advisory board, I dont think so you require anything additional settings and customisation on trasaction types.
Please follow standard charm implementation, you could get lots of documents in Google.
and demo under service.sap.com/rkt-solman.
and yes, you can create multiple change document in one CR.
Thanks,
Jansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jansi,
thanks firstly for your reply.
But I might not have quite expressed myself, the original scenario is:
If a customer Requirement has been changed, the related documents like Process Design Documents (PDD), Functional Spec Documents (FSD) and so on in the business processes should also be adjusted. At the beginning, it should be specified, which docs are to be adjusted. After the adjustment of one doc, it should be noted and marked as "finished".
Question is: how to build a CHARM transaction to reflect this process? I suppose I should define a new transaction type, right? Can this transaction type be related to a template project?
I can imagine to use a CR for a Requirement change, several ChangeDocs for the to-be-changed docs. But is this the best way?
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.