Page tree
Skip to end of metadata
Go to start of metadata


With SAP Solution Manager 7.2 the solution can cope with requirements of all lifecycle phases in one unified model. No matter whether a process is in design, build, or run phase, the same solution manages the content. The solution becomes a single source of truth.



Solution is the sum of a company’s systems, applications and processes. It acts as a container for versions of solution documentation, one of which is the production version..

To benefit form the solution, you need to understand the following fundamental concepts:

  • Solution documentation content as a result of the process design and modeling activities
    The term solution documentation content denotes all artifacts, documents, diagrams, test cases, and other materials that you created to describe one or more aspects of your software solution. SAP Solution Manager 7.2 allows you to structure and organize the solution documentation in as many process levels as required by your organization. It also allows you to manage these elements along the complete lifecycle.  
  • Standards for documents as a possibility to centralize document management in SAP Solution Manager 
    You can use document templates in the solution and their configuration as sources for your own definitions. You can define the design of the templates, define their status, and determine the place where they shall occur.
  • Views facilitate a focus on relevant information
    Views allow you to define of areas of interest, focusing on a subset of solution documentation. Views also enable you to define reporting and scope areas. 
  • Branches separate different versions of solution documentation content to establish a proper lifecycle management
    Branches are the linchpin of the SAP Solution Manager content lifecycle concept. They control the visibility and changeability of solution documentation content. By default, when you create a solution, there will be a production and a maintenance branch. While the production branch only contains productive documentation, the maintenance branch offers a version of solution documentation content in a staging area to further maintain customer solution documentation without interference with productive content. 
  • The system landscape represented by the logical system architecture that you use to execute processes
    Solution documentation content provides most value to customers if it is fully synchronous with the technical reality of the actual systems. SAP Solution Manager 7.2 is the only tool in the IT industry that firmly links documentation and system reality along the complete lifecycle. To do so, you need to document your system landscape precisely. SAP Solution Manager introduces logical component groups to facilitate this process. Logical component groups allow you to document all abstraction levels required for the individual user types. 
  • Change control landscape bundles Logical Component Groups which should follow the same release
    Release management can focus on the entire solution landscape, including all logical component groups documented in the solution, or relate to a change control landscape which defines a sub landscape. In such a sub landscape, just these Logical Component Groups will be defined, which follow the same release cycles.
  • Site concept as possibility to reflect complex 1:n landscapes
    In case the system landscape consists of one central development system and many productive systems, the definition of the Logical Component Group would require a site concept. Please read more about the site concept.

In SAP Solution Manager 7.1, many customers created multiple solutions for various reasons. In SAP Solution Manager 7.2, the solution concept was simplified significantly. Hence, there is no need to create individual solutions for specific use cases for the majority of customers because SAP Solution Manager 7.2 provides simpler means to achieve the same result.


SAP recommends to use only one solution to reflect the entire system landscape and its documentation also for large and interconnected companies. An exception of this recommendation can be a service provider who manages several independent customers. In that case, each customer can be defined as a separate solution.


Integration aspects

By the design and use of a solution, the Process Management is centrally integrated to many other SAP Solution Manager functionalities. The picture below show possible integrations.

  • The content provided in the Process Management can be used for monitoring of processes and interfaces (Business Process and Interface Monitoring). The monitoring will inform you once a system, process or interface will not behave as you expected.
  • In case the content shall be changed, it can interact with Project Management by creating a project.
  • The project can be part of a release in Release Management. Release and Project can be used with a close interaction to Change Management which itself has a deep integration to Transport Management and Process Management by controlling also changes on documentation.
  • Changed documentation can influence the way how the processes shall be tested. This will have an impact on test preparation in Test Management.
  • During test execution defects can be created within the ITSM module, these defects can be converted into a correction in Change Management.
  • After successful adjustments and re-test, the transport management can release appropriate transport requests into the productive landscape while all relevant documentation will be released to the production branch.



  • No labels