Show TOC

Process documentationDependency Analysis in Upgrade Planning Locate this document in the navigation structure


In the dependency analysis, you check and evaluate the effects of a target product version planned for an upgrade on product instances that are currently connected to each other. You select the target product version so that, if possible, no critical dependencies are created for you between the connected product instances.


  1. As the project leader, you want to pan the requirements for upcoming upgrade activities. To do this, you create a new analysis project.

  2. You select an existing project or solution landscape and adjust it to your requirements for the planned upgrade.

    You can extend product systems with corresponding product instances that you have previously only planned, if you are interested in dependency statements for product instances that already exist. To do this, add the planned product system and the product instances with the associated logical components that have already been created.

    If you want to plan the installation of enhancement packages that are modeled as add-on products (such as SAP ERP, SAP CRM, SAP SCM, and SAP SRM), you first need to assign the enhancement package to the associated product system as the starting product version. You then need to explicitly select the appropriate logical component.

    Note Note

    These settings are used for planning purposes only and are not copied to the Solution Manager System Landscape.

    End of the note.
  3. For each product of a product system for which you want to perform an upgrade, you select the planned target product version.

    In the case of Enhancement Packages that are modeled as Add-On products, you need to select the product version of the Enhancement Package again as the target product version.

  4. You can select product systems individually and display the connections between product instances. Once you have added additional product systems, define additional manual connections for planning purposes, so that you can calculate dependency statements for these.

    The status of the connections is initial.

  5. Analyze the dependencies by checking the connections between the product instances.

    The connections between the product instances are indicated by interfaces between the associated logical components. The SAP Solution Manager system checks whether current cross-system functions of the connected product instances will be reduced by the planned target product version. The calculation of a dependency statement is based on the possible starting statuses of the product instances.

    The status of the connections is determined. The list contains the dependency statements and, if there are any, upgrade-related SAP Notes.

  6. You analyze the dependency statements and can evaluate their effect on the planned upgrade yourself. Your evaluation overrides the status determined for the connections.

    The dependency analysis considers cross-system functions implemented at the start time and checks possible effects that a planned upgrade could have on these features. Changed or newly-developed processes are not taken into account in a target product version.

    The basis of calculation for a dependency statement includes all of the product instances that can be installed on a technical system. In some cases, a dependency statement might actually relate to a product instance of the technical system that you do not use. If so, it might be possible to assign a different valuation to a critical dependency statement to the one specified. Therefore, check the dependency statement (for example, with a yellow valuation) and analyze your business processes and product instances using the scenario and process component list on the SAP Service Marketplace at, too.

    The system uses the status of the connections to aggregate the planning status for the respective product system, the product version, and the associated product instances, and uses these to aggregate the overall status of the analysis project. The worst status takes precedence here.

  7. If an upgrade option indicates critical dependencies for you, search for a target product version with which these dependencies do not exist.

    To document the planning process, you can add comments or additional documents as attachments. You can show the progress of your analysis project using the analysis phase. You can also print your analysis project data as a PDF.

  8. (optional) You can display messages indicating technical dependencies between product instances on the same technical systems by choosing Check Upgrades.

    For example, an error message is displayed if an add-on product does not match the selected target version of the main product. In such cases, you usually have to select a suitable target version of the add-on product. However, it may not be possible to then carry out the selected upgrade.

    Note Note

    Also refer to the Upgrade and Installation Guides for SAP applications for which you have installed product instances on the technical system. For more information, see SAP Service Marketplace at   SAP Components   SAP Solution Manager <current release>  .

    End of the note.


If the overall status of your analysis project is not critical in your view, you can implement the planned upgrade activities.