CHARM uses best practice (methodlogies) to manage changes effectively (using Solution Manager), on other hand you use transaction PFCG to create/manage roles (authorization).
Whatever you do using CHARM can also be done independetly in respective systems as well (i.e. creating transport etc) but doing it centrally and then distributing create more systematic approach and all changes are recorded in one place.
Disclaimer: I am no expert on CHARM and just know very basics of it so I would advice you to visit right forum on SCN: or use search.
If you use ChaRM you should not use local development anymore, and in fact that is what you are doing.
With ChaRM you (automatically) close the ability to create your own Transport Requests from SE09 for example.
BUT, and this is really important, this is project related, so if the team from Authorizations create their own project (in CTS) and this is not connected/related to any ChaRM project, they can do whatever they want. Create, release, transport requests.
This should be a big issue, because if another project does use the ChaRM functionallity and the authorizations team not, you could run into integration problems because the CTS without ChaRM, is not held back by the phase of the ChaRM project.
So everybody thinks they are doing OK in the integration test (phase) and all the time the authorizations are changed.
I think it should be determined "company wide" which road to follow, WITH (of course) or without ChaRM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.