Use SAP Security to Manage Your Project Scope

  • by D. Russell Sloan, Implementation and Governance Specialist — SAP Solution Manager, IBM Global Business Services
  • May 10, 2010
Manager/Project Management
Finding the right balance between allowing teams to get work done and managing the business process scope can be daunting early in a project. Learn how to leverage the SAP security model in SAP Solution Manager to automate governance during the blueprint and configuration phases. See how to activate the change control, how to set up user access to the Business Process Hierarchy structure nodes, and the effects these activities have on the behavior of blueprint and configuration transactions in SAP Solution Manager.
Key Concept
SAP Solution Manager uses the full capabilities of SAP security. With SAP security, you can control who can change your project scope, who can add or remove transactions, configuration, and documentation to your project, and how you automate change governance.

In the last 18 months alone, I’ve worked with projects ranging in size from 30 to nearly 500 team members implementing SAP solutions. One thing that all of these projects have in common is a need to manage project scope. Fortunately, SAP Solution Manager has some tools to help with this. In addition to the Business Process Hierarchy (BPH) found in transaction SOLAR01 (which is used to define the project scope), utilities contained in transaction SOLAR_EVAL evaluation reports can also help you see what has changed over time.

You might be wondering: What if you don’t want to take the “audit” or reactive approach to managing your scope? What if you would like to implement and systematically enforce change control for your project scope? If you use the techniques I describe in this article in conjunction with those I described in “Improve Document Management by Securing Attributes,” you can take charge of the changes taking place in your project scope.

The initial setup to allow you to take control of the changes in the BPH is not very complex and gives you a level of control over changes to the project scope that was not practical prior to the deployment of SAP Solution Manager. Before it was introduced, project scope was managed via spreadsheets and documentation was stored all over the place. Now you have a structured way to manage scope and store solution documentation for your projects with SAP Solution Manager.  

D. Russell Sloan

D. Russell Sloan is a specialist in project and program governance for IBM. He focuses on the use of SAP Solution Manager for global rollout projects for IBM’s largest customers, having worked with SAP software since 1996. Russell has degrees in accounting and information systems and has been a team and project leader for SAP projects for more than 14 years. He has been developing and deploying software systems for over 30 years.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.