cancel
Showing results for 
Search instead for 
Did you mean: 

Creating new Roadmaps

Former Member
0 Kudos

Hi.

We have our own methodology and want to create our own roadmaps and use the Solution Manager for managing projects. I'm interested in any experiences with creating customer roadmaps and use of Solution Manager as a project managment tool.

Best Regards

Morten

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Morten,

In answer to your question, yes you can create your own Roadmap - by building it from scratch or by 'adapting' one of the standard Roadmaps and building furthermore.

Please use RMDEF & RMAUTH transactions.

On how exactly to use these, you can find enough information from http://service.sap.com/rkt-solman Tutor files

(1) [This|https://websmp103.sap-ag.de/~sapidb/011000358700004942292004E.sim] provides you a good overview

(2) [This|https://websmp103.sap-ag.de/~sapidb/011000358700000687242006E.sim] file is about Roadmap Authoring - Construction

(3) [This |https://websmp103.sap-ag.de/~sapidb/011000358700000687212006E.sim]is about Roadmap Modification

As regards use of SolMan as a Project Management tool, my personal view is (others may contest) - please use only if yours is a modest size implementation and not run as multi-stream, multi-geography, multi-phased programme.

It will never be as nimble and user friendly for such heavily customised projects.

More later.

Regards,

Srini

Former Member
0 Kudos

Thank you!! Alot of good sim's.

Still I miss some experiences from other users on our approach. Anyone created and maintained their own roadmaps and experienced any ups-and-downs??

Former Member
0 Kudos

Hi Morten,

Award of commensurate points will be a good motivator to write such elaborate replies.

There are no specific downs that I can see. You get what the functionality allows for. May be the following can be an issue:

(1) Frequent changes to Roadmap not possible; will never be as flexible as a simple MS Project Plan can be

(2) Building Aesthetics not feasible, it will only look and feel as good as a standard Roadmap of SolMan

(3) Not everyone can do this; as you can see, specific transactions and specific activities are involved; only a trained hand should do. Again, this is something where a typical tool like MS Project may seem more intuitive for a larger team (that of course makes it vulnerable).

Ups:

(1) Another reason why Project team does not have to look elsewhere and come back to SolMan itself - if the Roadmap doesnt have to be modified quite often, it's good to keep all in one place (viz. SolMan)

(2) Ability to add Accelerators (Templates)

Regards,

Srini

Former Member
0 Kudos

Thank you Srini for the complementary reply.

You have pinpointed many issues that we also have discussed and are worried about. It will be matter of pro's and con's and the degree of control you wish to gain.

Our main goal is to manage the project with focus on the projects goals, the project deliverables (WBS structure) and control of documents - configuration management.

Normally, many run the project with use of MS Project and the filestructure in Windows Explorer. This has also been our apporach in some cases, but this is also a very anarchist way of managing the project. The filestructure seems to live it's own life, the MS Project only display the activities on name level.

So, in the end you may have a situation where you not are sure where the latest version of the document is. The teamleaders don't remember the content of the WBS description and only focus on solving problems etc.

Conclusion:

Solution manager is not a very flexible tool, you need good planning and establish a solid structure from day one.

It will give you a better overview of the activites and documents in the project. It is more transparent than a filestructure, and will provide better control for the project management regarding version control of important documents.

Another possibillity, which I have thought of is to create our own template - based on our methodology. Then re-use this in each implementation project. Looks that this could work, need some more investigation.

Best regards

Morten

Former Member
0 Kudos

Hello Srini. How are you?

I have an issue with the roadmap configuration. After this creation, inside of the transaction RMMAIN, in any structure selection, I have the error messenger u201C000000000000Enhancement /KWCUST/ (Release 610) does not existu201D appearing in the right-side screen. Any idea of this?

Sorry for my bad English.

Best Regards,

FS

Former Member
0 Kudos

Hi Fabio,

I am sorry, didn't face that error before and it seems like the issue is with the 'context' of the Knowledge Warehouse (KW) in use. I would have imagined the context to be 620 and thus system warning you that 610 does not exist.

Can you please find out where you can change the pointer to 620 and see if the error disappears.

Best regards,

Srini

Former Member
0 Kudos

HI Srini,

Thanks for your comments. I already fix the problem, applying the SAP note 924068.

Regards,

FS

Former Member
0 Kudos

Hi Fabio,

Thanks for sharing the solution here. It's always good to know such fixes. Very valuable.

Best regards,

Srini

Answers (0)