Skip to Content
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/925b02f9-0b01-0010-bbbf-c68268bb3c41″ width=”235″/> http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/7ec202f9-0b01-0010-589e-a51bcd596fed” width=”235″/> This solution allows customers to centralize the implementation, operation, monitoring, support and maintenance of all NetWeaver components. SAP® Solution Manager has positive technical as well as business impacts, because it improves the interconnection between processes and the underlying IT infrastructure in a centralized or decentralized environment. The result is concrete: easy and effective communications between the IT department and the business units of your organization; crucial for the success of your company business.

Brief description of characteristics and opportunities:

Solutions Monitoring: It allows real time monitoring of systems, business processes, interfaces and even system interdependencies, reducing the administration efforts. Proactive monitoring helps you prevent critical situations, while automatic notifications allow you to respond rapidly. NetWeaver Implementations: Using Solution Manager in the configuration of information and process orientation, configuration and final preparation will accelerate the system implementations. Solution Manager allows the efficient administration of projects and centralized control of cross-components. Synchronization of customized preferences: Solution Manager will allow you to keep a consistent IT environment. This solution favors the administration of the parameters you are willing to customize. Therefore, the expense of unnecessary inconsistency test and even the risk of making mistakes are not faced. Solution Manager reduces the manual synchronization efforts automatically distributing its preferences to multiple systems, in a simultaneous and centralized fashion. Testing: It provides a single access point to the system and it allows centralized storage of materials and results of each test, which will be useful as support of other test processes in the future. IT and applications support: The Support Desk included in Solution Manager helps you handle incidents more efficiently, and it also favors the support cost estimation. The support messages centralized administration makes all the organization much more efficient. Global Development: The homogenous methodology and functionality of this tool helps the standardization and harmonization of processes in global companies or with multiple sites or branches. Thus, the implementation in each site will be simple because the total configuration of facilities in each one will not be necessary. Service Level Reporting and Management: This solution favors the simple definition of service levels and provides automatic reports. The information regarding the service level comprehends all the solution systems and provides a consolidated report that contains all the information that you need to make strategic decisions in the IT environment of your company. Service Recommendations: Solution Manager puts forward adequate recommendations about additional support services needed to obtain the highest performance of your IT operations.

Here are five key benefits:

  • Trustworthy IT solutions:
  • Minimizing the risk during configuration and operation.
  • Implementation and improvement cost reduction:
  • The tools that make up this solution make your projects more efficient.
  • Fast ROI:
  • Accelerating the implementation and continuous IT infrastructure, improving the business.
  • Lower operating costs:
  • Through a unique administration point for multiple component environments.
  • More from your investments:
  • As it is an open solution it integrates to environments of applications SAP® and non SAP®. The above shown descriptions indicate basically how Solution Manager can help you (in your work). Nowadays, several companies make the following questions before implementing this powerful tool: 1. Why should I need to implement Solution Manager in my landscape? 2. Can I wait until next release upgrade of the R3 system, ie: ECC 500? 3. Should I wait for the next Solution Manager release version or can I implement the current version? 4. Will this tool increase my administrative efforts since I need to maintain an additional SAP instance? 5. Is there any additional fee associated with Solution Manager? These are the 5 top questions that currently every customer asks me when they come to evaluate the possibility of implementing a Solution Manager in their SAP landscape or they ask me if they should wait. The answer to these questions is that you will be benefited as soon as you implement a Solution Manager without having to wait for the next Solution Manager release or your next R3 release upgrade. Moreover, in order to avoid unnecessary delays with the implementation or upgrade of your current NetWeaver components, I suggest starting the Solution Manager implementation planning beforehand. Take enough time to learn the key functionalities of this tool, and then put them into practice to enhance your new project. Solution Manager is included into your maintenance contract so there will be nothing that can stop you from immediately implementing a Solution Manager. Those companies that have already implemented a Solution Manager understand that it is unnecessary to have a resource completely assigned to the administration of Solution Manager itself; it is just a matter of having the proper hardware sizing and a correct installation; then we can assure Solution Manager is self-administered. Those smart customers who have been using Solution Manager for many years are happy to know that for the next release upgrade and/or implementation, Solution Manager will be a key part of the project; and not only from the implementation point of view, but also from business processing, change management, monitoring and alerting perspective.

Related Solution Manager configuration guides on SDN

System Monitoring configuration guide for Dummies

Service Desk configuration guide for dummies.

SDCC – Service Data Control Center configuration guide for Dummies.

CCMS Rule Based Monitors configuration guide for Dummies

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Christopher Solomon
    We began the project I am currently a part of with Solution Manager set to be a big part of the overall solution. As mentioned above, it seemed like the perfect solution to all of our problems of managing a complex solution. We are upgrading from a simple R/3 4.6c system to a complex, environment of NetWeaver Portal, XI, CRM , ECC 5.0 and more (various non-SAP components). Solution Manger was initially set-up to be the “hub” to manage everything as mentioned above in the blog…..configuration, business process, testing, etc. However, we learned some hard lessons that made us pull back and utilize Solution Manager much less now. First off, we kept hitting odd “bugs” and such that had to be hunted down and corrected. These were related to the operation of Solution Manager itself. As a fairly new product, it can be expected, but it still took time to address. Secondly, since Solution Manager was so new to most everyone on the project team, there was a lot of time spent just figuring out exactly “what” it is , “why” we need it” and “how” do we use it in our immediate project tasks. In the end, we were spending much more time on Solution Manger than actually moving the project forward. We pulled back from our grand visions of all that Solution Manger was going to be, and at this time are doing little more than tracking configuration and related documentation with it. Not to say that it will not be utilized much more later or does not have the potential to actually meet all the marketing mumbo-jumbo mentioned in the blog above, but we just do not have the time to get the project team up to speed with all the details of Solution Manager while also trying to complete our project with the allotted time and budget. I would just advise folks to carefully consider the time necessary for Solution Manager set-up and training when evaluating it for their own projects.
    (0) 
    1. Federico Babelis Post author
      Hi Christopher:

      For some of those reasons you mention is why I suggest starting Solution Manager implementation beforehand, the people involved in the project needs to take some time to learn the functionality and also needs to understand what SolMan can do in their project. Keep in mind this products is almost requirement when installing some NetWeaver components as you are required to get the installation key, so the earliest you work whit Solution Manager, the better.

      Thanks for taking the time to read the blog!

      Best Regards,
      Federico

      (0) 
      1. Rodney Benjamin
        Hi Federico
        We have implemented and upgraded our Solman to 4.1. We have only configured the system for basic System Administration/EW and the apps people will be sitting down with the BP. I will be configuring the CCMS-Alerts shortly. One thing we would like to do and which I cannot get info on is this:
        In the task list you can check(manually) a backup on a remote system(DB12) – what I would like is that these types of tasks can be run automatically to report on a series of tasks on a remote system instead of me doing it manually. I would then have these tasks run automatically which will report on a remote system i.e DB16, DB12 (Time of last backup etc) – I can then pull the report without having to check each and every system (in our case 18+ SAP systems).
        Is this possible?
        Regards Rodney Benjamin
        (0) 
  2. Axel Reif
    Hi,

    the ideas behind Solution Manager are good, but the implentation is simply… hmmm, how do i say it in a nice way… catastrophic!

    Do not get me wrong, i have been for over 13 years in the SAP Consulting Business now, SAP Basis to be exact, and i know and like most of SAP’s Products. But Solution Manager is a prime example for a good idea totally screwd up.

    To me SolMan looks like the concept has been invented by a professor in university, tossed into a room with 50 Programmers, everybody coding a single transaction and none of them talking to each other. The result is a complicated (and i mean complicated, not complex!) grab bag of single functions without any red line tying them together. You need a masters degree either in nuclear physics oder brain surgery to customize it. To make things worse, it is still is full of bugs and only a few really meaningfull error messages.

    Many customers of mine have played with the thought of using SolMan as THE central system for managing their SAP Landscape, but all of them have stood back from this idea after evaluating the product when they realized that they are spending almost double the time with using and understandig SolMan than implementing their Project.

    I would love to the concept of SolMan implemented in a really usable software but until then i can only warn of SolMan! Use it for MOPZ and EWA, maybe monitoring, everthing else is simply not worth the time and effort.

    Best Regards,
    Axel Reif

    (0) 

Leave a Reply