How do I use Solution Manager effectively, for implementations?

[Former Member]

I have recently become more involved in SAP projects.  We have several rollouts planned over the next few years, but we are not maximizing our use of Solution Manager.  What functionality/features and work centers do I need (in addition to Implementation/Upgrade) in order to use Solution Manager effectively for SAP rollouts?

I know that I can't just start using the Implementation/Upgrade work center and expect to have everything there.  I am trying to understand the dependencies between the parts and pieces that will help lead to an effective solution.  For example, if I need to have roadmaps and blueprints in place to use the Implementation/Upgrade work center effectively, what to I need to have in place, or do, to use roadmaps and blueprints?  I would like to follow the trail back to the beginning (Initial Preparation), then work my way forward through using ASAP and Solution Manager so that I can present a case to my leadership for the changes we need to make to improve our processes.  Hopefully this makes sense.

Thank you for your input.

Aaron

[GiulioV]

Hi Aaron

Usually to answer your question requires a project: it is the blueprint of your Solution Manager. Nevertheless I will try to give you some guidelines you can refer to make your decisions.

1) Define which part of your architecture you want to manage with Solution Manager (it is not mandatory to include all systems in your architecture in the SM scope).

2) Document the solution in your scope: you can create a template project and document your solution with the support of Solution Documentation Assistant functionalities. At this stage you should decide which contents should be moved out of the documents and managed using SM functionalities (i.e. transactions, keywords and classification, developments, test cases...): the more contents you will be able to manage in the SM the more functionalities you will be able to use to optimimize your solution management activities (pay attention to don't overingeneer your IT processes). At this stage you should also decide how to implement in the Solution Manager your "template strategy": that is how to use your "well documented" solution during your roll-out projects. There are many functionalities that can support you in the solution template management.

3) Every time you launch a new roll-out project according to your template strategy you might be required to create a new project, during this activity you have to select template solutions in the scope and then you are ready to start your roll-out.

4) How to use SM during the project can  be influenced by a lot of factors: based on my experience is quite unusual to use roadmaps during the project life even if can be very helpfull to have them available to be consulted.

Last but not least it is crucial the way you define the three levels business process structure, I cannot say that there is a single way to shape it but the golden rule is to agree the structure with the business, it will become the common dictionary you will use to speak each other.

I hope it can help

Regards

Giulio