Roadmap And Project Structure

What is the difference between roadmap structure & project structure?

In RMMAIN/ RMAUTH I am creating roadmap structure, mentioning ASAP methodology phases (Project preparation, Blueprinting, Realization, Final prep & Golive).

In each phases of a roadmap, I am assigning project team member & status.

The same (team members & Status) I am maintaining for projects also (In SOLAR_PROJECT_ADMIN).

In SOLAR01, I am assigning team member to specific nodes also.
 

What is the difference between maintaining all those details in RMMAIN & SOLAR_PROJECT_ADMIN, SOALR01?

The assignment of people and status values has different purposes:

Roadmap (RMMAIN) - assigning the people to each task in the plan (roadmap)

Project administration (SOLAR_PROJECT_ADMIN) - assigning the people which shall contribute in the project. When distributing tasks you can select between people added here.

Business Blueprint (SOLAR01) - assigning people to the elements in the Business Process Model for the Business Blueprint Phase.

Config (SOLAR02) - assigning people to the elements in the Business Process Model for the Configuration Phase.

(1) RMMAIN (Roadmap) is to be used by you only if your project is committed to that methodology or the newly authored methodology - this is not a mandatory transaction and in most projects that I have worked on, people don't really care about this apart from just downloading standard Accelerators that SAP has provided as part of the content it delivers. 

This transaction, the documents and team members you assign here are helpful for 'running' and 'monitoring' the project itself and has nothing to do with the business solution itself that's delivered.

(2) Blueprint transaction (SOLAR01), Admin Tab is the place where, you make people assignments reflecting ownership of the solution - in other words, if you assign Mr.ABC against a Business Scenario called Procure to Pay, it means that person is responsible for designing that solution and also, in all likelihood, responsible for storing documents against that node. You can 'cascade' that same person's name to all nodes below the Scenario (to all layers below) in one step too.

(3) Configuration transaction (SOLAR02) Admin Tab is where you make fresh assignment(s) of people responsible for Build/Test activity against the respective node, on the structure.

In my view, please consult your Project Manager if he/she intends following Roadmap diligently and use that as the primary place of Project Management definition and tracking. Chances are that, the answer will be a resounding No ! If so, I would recommend not spending too much time on it and straightaway focus on SOLAR01.

In most projects, PMs find it easy to deal with myriad versions of MS Project Plans and Excel sheets and not keen to log on to SolMan to edit or update status values.

The MS Project download functionality provided by SolMan is just a one way tool (you can't upload values back from MS Project to SolMan) and therefore of very ornamental value alone!

SAP PS Tips

Read Also
Whether To Activate Project Cash Management

Get help for your SAP PS problems
SAP PS Forum - Do you have a SAP PS Question?

SAP Project System Books
SAP PS Books - Certification, Interview Questions and Configuration

SAP Project System Tips
SAP PS Tips and Project System Discussion Forum

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.