SAPTechno

Note 394616 - Release strategy for SAP Solution Manager

Version : 112 / 2014-03-19


Symptom

  • You are planning the installation, upgrade, and maintenance of SAP Solution Manager for the following releases:
                      Product release                                                Add-On Release         Add-On Release   
SAP Solution Manager 7.1 on HANA ST 712 ST-BCO 712
SAP Solution Manager 7.1 ST 710 ST-BCO 710
SAP Solution Manager 7.0 EhP 1 ST 400 ST-BCO 400
SAP Solution Manager 7.0 ST 400
SAP Solution Manager 3.2 ST 320
SAP Solution Manager 3.1 ST 310
SAP Solution Manager 2.2 ST 220
SAP Solution Manager 2.1 ST 210

Other Terms

  • Solution Manager Tool, Solution Tools
  • ST712, ST710, ST400, ST320, ST310, ST220, ST210
  • ST-BCO712, ST-BCO710, ST-BCO400

Solution

 

Contents

      0. Last changes
I. General information
II. Overview
III. Installations
IV. Upgrades
V. Combination with other add-ons
VI. Maintenance

 

0. Last changes

      Date                          Section         Short description                                                                                           
December 2013 III and VI Stack parts (in general)
December 2013 V Combination of ST and ST-BCO, ST-TST, ST-TAO, and ST-RDS
December 2013 VI Dependencies of ST in combination with ST-BCO und ST-PI
December 2013 VI Deletion of parts of final ABAP stacks belonging to ST 320 and ST 310
December 2013 II, III, VI further additions related to ST-BCO
December 2013 all Layout changes

 

I. General information

  • The SAP Solution Manager is the platform for carrying out the activities that are required for introducing, operating and maintaining an SAP solution throughout its entire life.

  • For further information about SAP Solution Manager, refer to SAP Service Marketplace at https://service.sap.com/solutionmanager. The Product Availability Matrix offering further detailed information about the SAP Solution Manager product is provided at   https://service.sap.com/pam (search term "SAP Solution Manager").

  • As of May 1st, 2008, SAP Solution Manager 4.0 was officially renamed as SAP Solution Manager 7.0. This pure name change does not affect the release strategy of SAP Solution Manager. The add-on ST therefore remains the same. SAP Note 1161294 provides details about this renaming.

 

II. Overview

  • This SAP Note deals with the release strategy of SAP Solution Manager (software components ST and ST_BCO) based on SAP Basis Release 6.20 and higher.

                      SAP Solution Manager 7.1 on HANA
ST Release: ST 712
NetWeaver Release: NW 7.4
CRM Release: CRM 7.0 EhP 2
Availability: 13.08.2013 (ramp-up version, ST 712 Support Package 1, ST-BCO 712 Support Package 1)
Maintenance end: December 31, 2015 (ST 712, ST-BCO 712)
 
SAP Solution Manager 7.1
ST Release: ST 710
NetWeaver Release: NW 7.0 EhP 2
CRM Release: CRM 7.0 EhP 1
Availability: May 16, 2011 (ramp-up version, ST 710 Support Package 1)
July 20, 2011 (ramp-up version, ST-BCO 710)
August 15, 2011 (default release, ST 710 Support Package 2, ST-BCO 710)
Maintenance end: December 31, 2017 (ST 710, ST-BCO 710)
SAP Solution Manager 7.0 EhP 1
ST Release: ST 400
NetWeaver Release: NW 7.0 EhP 1
CRM Release: CRM 5.0
Availability: December 15, 2008 (default release, ST 400 Support Package 18)
June 20, 2011 (default release, ST-BCO 400)
Maintenance end: December 31, 2013 (ST 400, ST-BCO 400)
SAP Solution Manager 7.0
ST Release: ST 400
NetWeaver Release: NW 7.0
CRM Release: CRM 5.0
Availability: December 16, 2005 (ramp-up version, ST 400)
March 31, 2006 (default release, ST 400)
Maintenance end: December 31, 2013 (ST 400)
 
SAP Solution Manager 3.2
ST Release: ST 320
WebAS Release: WAS 6.20
CRM Release: CRM 3.1
Availability: October 22, 2004 (ramp-up version, ST 320)
March 31, 2005 (default release, ST 320)
Maintenance end: March 31, 2009 (ST 320)
 
SAP Solution Manager 3.1
ST Release: ST 310
WebAS Release: WAS 6.20
CRM Release: CRM 3.1
Availability: May 5, 2003 (ramp-up version, ST 310)
October 22, 2003 (default release, ST 310)
Maintenance end: December 31, 2006 (ST 310)
Stop Support Package download: December 31, 2007 (ST 310)
  • SAP Note 402806 contains information about Add-On ST based on SAP Basis 4.6C and 4.6D.

 

III. Installing the SAP Solution Manager

  • The SAP Solution Manager is available as a complete installation in the latest release. The software components ST and ST-BCO are already part of this installation (see SAP Note 781448). Reinstalling an older release, or upgrading to an older release is not intended, instead we recommend that you reinstall or upgrade to the latest release.

  • You can find purchase order information and installation guides on SAP Service Marketplace at https://service.sap.com/solutionmanager. Add-on installations can only be installed on specific releases of the basis components. Add-On ST can therefore only be used on the CRM and NetWeaver Releases listed in section II.

  • Consider the following restrictions regarding upgrade and maintenance for your SAP system:

    • It is possible to uninstall software components (ST and ST-BCO in this case).

    • You can upgrade only to SAP releases that are supported for this software component (in this case, ST). For an overview of the upgrades supported for ST, refer to section IV.

    • There are technical restrictions for specific SAP Solution Manager stack parts that prevent you from implementing Support Packages for these stack parts independently of other stack parts. You can find an overview of these stack parts in section VI.

 

IV. Upgrading the SAP Solution Manager

  • Upgrade ST 712 for SAP Solution Manager 7.1 on HANA:

    • No upgrade, no migration.

  • Upgrade ST 710 for SAP Solution Manager 7.1:

    • SAP Note 1462137. (For additional information about the procedure, see SAP Note 1577909.)

    • The following equivalencies for the leading software component ST are defined for the upgrade from Release 7.0 Enhancement Package 1 (ST 400) to Release 7.1 (ST 710):

                      Support Package Stack of ST 400         Support Package Stack of ST 710   
31 (09/2013) 10 (10/2013)
30 (12/2012) 08 (02/2013)
29 (07/2012) 06 (08/2012)
28 (11/2011) 04 (12/2011)
27 (06/2011) 02 (07/2011)
26 (03/2011) 01 (04/2011)
25 (10/2010) 01 (04/2011)
24 (06/2010) Release
23 (04/2010) Release

Starting from a specific Support Package for ST 400, you can carry out the upgrade only when you include the equivalent Support Package for ST 710. The table above lists the equivalent Support Package of the higher Release ST 710, which is the minimum Support Package that must be included in the upgrade. You cannot upgrade the source release to a Support Package that is lower than this equivalent Support Package for the target release.

  • Upgrade ST 400 for SAP Solution Manager 7.0 Enhancement Package 1:

  • Upgrade ST 400 for SAP Solution Manager 7.0:

  • Upgrade ST 320 for SAP Solution Manager 3.2:

  • Migration ST 310 for Solution Manager 3.1:

    • You cannot upgrade from ST 210 or ST 220 to ST 310. However, since Q4/2003, you have had the option to migrate data from these releases to 3.1. For further information, refer to SAP Notes 644123 (implementation) and 492051 (operation).

 

V. Combination with other SAP add-ons

  • The SAP Solution Manager is developed in the form of add-on components. The software component ST is also specified as the leading software component.

  • The individual Releases of SAP Solution Manager group together various software components. A complete installation already contains all other required software components.

  • The software component ST is released only in conjunction with these other software components for SAP Solution Manager.

    • SAP Solution Manager BW content (software component ST-BCO): The release is valid as of SAP Solution Manager 7.1 Support Package Stack 02 or SAP Solution Manager 7.0 Enhancement Package 1 Support Package Stack 27 (see SAP Note 1578583).

    • SAP Solution Manager Implementation Content (software component ST-ICO): For information, refer to SAP Note 631042.

    • SAP Solution Manager Services (software component ST-SER): For information, refer to SAP Note 569116.

    • SAP Solution Tools Plug-In (software component ST-PI): For information, refer to SAP Note 539977.

    • Service tools for applications (software component ST-A/PI): For information, refer to SAP Note 69455.

    • cProject Suite (software component CPRXRPM): For information, refer to SAP Note 427216. Version 450_700 is not released for SAP Solution Manager.

    • cProject Suite (software component CPROJECTS): For information, refer to SAP Note 427216. This add-on is replaced by the component CPRXRPM as of Release 7.0.

    • SAP Solution Manager Service Desk (software component ST-SUP): This add-on is integrated into software component ST 400 as of Release 7.0.

    • SAP Solution Manager Change Management (software component TMWFLOW): The add-on TMWFLOW was integrated into the software component ST 400 as of SAP Solution Manager 7.0.

  • Additional software components for SAP Solution Manager:

    • Software components ST-SEP, ST-QCA, ST-ETP, ST-PSM, and ST-SPA): For information, refer to SAP Note 1109650.

    • Software components ST-TST and ST-TAO: For information, refer to SAP Note 1733109.

    • SAP Rapid Deployment solutions (software component ST-RDS): For information, refer to SAP Note 1686668.

    • Landscape Verification (software component ST-LV): For information, refer to SAP Note 1468604. This add-on is integrated into software component ST 710 as of Release 7.1.

  • ESM documentation: The following software components are released and can be installed in ST 400 only:

                      Software component                                    SAP Note    
ESMCRM 7.0 (ESM CRM 7.0) 1263312
ESMEWM 700 (ESM EWM 7.0) 1263311
ESMSCEM 700 (ESM SCEMSRV 7.0) 1263310
ESMSCM 700 (ESM SCM 7.0) 1263308
ESMSCMTM 700 (ESM SCMTM 7.0) 1263208
ESMSNC 700 (ESM SNC 7.0) 1263204
ESMAI 700 (ESM AUTO-ID 7.0) 1263114
ESMSRM 700 (ESM SRM 700) 1263111
  • A combination of other SAP add-ons with ST has been released in general, if the same system requirements are met.

 

VI. Maintenance

  • Corrections for software components ST and ST-BCO:

    • For the software components ST ad ST-BCO, maintenance is carried out using Support Packages. You can find information about individual errors and how to fix them in SAP Notes.

    • The Support Packages for individual components were combined into Support Package Stacks for the SAP Solution Manager, and you can find these on SAP Service Marketplace at https://service.sap.com/sp-stacks -> SAP Solution Manager.

      • The general recommendations of SAP for importing SP stacks also applies to SAP Solution Manager. We strongly recommend that you import SP stacks at least once a year. This recommendation is given at https://service.sap.com/sp-stacks.

      • With regard to the Support Packages, we recommend assigning Support Packages from one Support Package Stack to the following stack, and importing all Support Packages that belong to a Support Package Stack at the same time. The individual stack parts are provided in the stack definitions for SAP Solution Manager, which you can find on SAP Service Marketplace at: http://service.sap.com/sp-stacks -> SAP Solution Manager -> <Select your Support Package Stack> -> Show SP Stack Content.

      • SAP Note 1595736 provides an overview of release information about individual Support Package Stacks of SAP Solution Manager. There you can find announcements of important corrections, necessary working procedure steps and also information about the use of Software Update Manager (SUM).

      • You can check the availability of the Support Package Stacks on SAP Service Marketplace at: https://service.sap.com/sp-stacks -> SP Stack maintenance schedule -> SAP Solution Manager.

      • For SAP Solution Manager 7.0 and earlier releases, SAP did not provide a dedicated Support Package Stack for every Support Package of software component ST. You can find the Support Packages for component ST on SAP Service Marketplace at: https://service.sap.com/swdc -> SAP Software Download Center -> Support Packages and Patches -> Browse Our Download Catalog -> SAP Technology Components -> SAP Solution Manager.

    • There is no extended maintenance for SAP Solution Manager. You can find information about the maintenance strategy on SAP Service Marketplace at https://service.sap.com/pam (search term "SAP Solution Manager").

  • Dependencies between Support Packages:

    • Support Packages of software component ST require in general specific Support Packages for SAP_BASIS and SAP-ABA or BBPCRM (see below for product specific details). In addition to these recurring dependencies, some software components have further dependencies or special characteristics:

      • Software component ST-BCO:

In SAP Solution Manager, the software components ST and ST-BCO are very closely linked functionally. A Support Package of one software component may be used only together with the Support Package of the other software component if the latter one is defined in the corresponding Support Package Stack. The Support Package Stacks of SAP Solution Manager contain the respectively valid combinations of these two software components.

The software component ST-BCO is an add-on to the software component BI_CONT. The Support Package Stacks of the SAP Solution Manager each list a valid combination of the software packages for ST-BCO and BI_CONT. SAP does not recommend for SAP Solution Manager a separate implementation of software packages for BI_CONT that are not listed in the corresponding stack definition.

      • Software component ST-PI:

SAP provides Support Packages for this software component not only for SAP Solution Manager but also for systems that are managed using this tool.

In SAP Solution Manager itself, you may implement only the software package for ST-PI that is used in the Support Package Stack for ST-PI. Futhermore, you must not implement any newer Support Package or release for ST-PI individually. You may only implement a newer Support Package or release in combination with a newer and entire Support Package Stack for SAP Solution Manager.

The implementation of software packages in managed systems is dependent on the SAP product and its stack definition installed on the respective managed system. Depending on the Support Package Stack (or, alternatively, the general release strategy for the product), it may be necessary to implement additionally individual software packages for the software component ST-PI. In the particular case, you can view the relevant stack definition at: http://service.sap.com/sp-stack -> <Select you SAP product> -> <Select your Support Package Stack> -> Show SP Stack Content. For this, the title of the column is relevant where you can find the technical name of the ST-PI software package.

    • SAP Solution Manager 7.1 on HANA:

Support Packages for the software components SAP_BASIS 740 and BBPCRM 712 can only be imported together with a Support Package for ST 712, which then displays a Conflict Resolution Transport (CRT). This means that you can import only Support Packages for these software components (SAP_BASIS, BBPCRM) that have already been released if a suitable Support Package for ST 712 has been released. There is a gap between the releases of the individual Support Packages. This problem does not affect you if you import entire Support Package Stacks.

Each row of the following table contains the technical names of the above mentioned Support Packages. The import conditions of these Support Packages must be met by importing all of these or by all of these existing in the system:

                      ST 712                               SAP_BASIS 740                   BBPCRM 712                 
SP 1 (SAPKITL801) SP 3 (SAPKB74003) SP 3 (SAPKU71203)

Example:

      • You cannot import Support Package 3 of SAP_BASIS 740 without importing Support Package 1 of ST, and Support Package 3 of BBPCRM at the same time.

    • SAP Solution Manager 7.1:

Support Packages for the software components SAP_BASIS 702 and BBPCRM 701 can only be imported together with a Support Package for ST 710, which then represents a Conflict Resolution Transport (CRT). This means that Support Packages that have already been released for these software components (SAP_BASIS, BBPCRM) can be imported only if a suitable Support Package for ST 710 has been released. There is a gap between the releases of the individual Support Packages. This problem does not affect you if you import entire Support Package Stacks.

Each row of the following table contains the technical names of the above mentioned Support Packages. The import conditions of these Support Packages must be met by importing all of these or by all of these existing in the system:

                      ST 710                               SAP_BASIS 702                   BBPCRM 701                 
Release SP 4 (SAPKB70204) SP 1 (SAPKU70101)
SP 1 (SAPKITL701) SP 6 (SAPKB70206) SP 3 (SAPKU70103)
SP 2 (SAPKITL702) SP 7 (SAPKB70207) SP 4 (SAPKU70104)
SP 3 (SAPKITL703) SP 8 (SAPKB70208) SP 5 (SAPKU70105)
SP 4 (SAPKITL704) SP 9 (SAPKB70209) SP 6 (SAPKU70106)
SP 5 (SAPKITL705) SP 10 (SAPKB70210) SP 7 (SAPKU70107)
SP 6 (SAPKITL706) SP 11 (SAPKB70211) SP 8 (SAPKU70108)
SP 7 (SAPKITL707) SP 11 (SAPKB70211) SP 8 (SAPKU70108)
SP 8 (SAPKITL708) SP 12 (SAPKB70212) SP 9 (SAPKU70109)
SP 10 (SAPKITL710) SP 13 (SAPKB70213) SP 10 (SAPKU70110)
SP 11 (SAPKITL711) SP 14 (SAPKB70214) SP 11 (SAPKU70111)

Examples:

      • You cannot import Support Package 5 of SAP_BASIS 702 without importing Support Package 6 of SAP_BASIS, Support Package 1 of ST, and Support Package 3 of BBPCRM at the same time.

      • You cannot import Support Package 7 of SAP_BASIS 702 without importing Support Package 2 of ST, and Support Package 4 of BBPCRM at the same time.

    • SAP Solution Manager 7.0 Enhancement Package 1:

Support Packages for the software components SAP_BASIS 701 and BBPCRM 500 can only be imported together with a Support Package for ST 400, which then represents a Conflict Resolution Transport (CRT). This means that you can import only Support Packages for these software components (SAP_BASIS, BBPCRM) that have already been released if a suitable Support Package for ST 400 has been released. There is a gap between the releases of the individual Support Packages. This problem does not affect you if you import entire Support Package Stacks.

Each row of the following table contains the technical names of the above mentioned Support Packages. The import conditions of these Support Packages must be met by importing all of these or by all of these existing in the system:

                      ST 400                               SAP_BASIS 701                   BBPCRM 500                 
SP 18 (SAPKITL428) SP 2 (SAPKB70102) SP 12 (SAPKU50012)
SP 19 (SAPKITL429) SP 3 (SAPKB70103) SP 13 (SAPKU50013)
SP 20 (SAPKITL430) SP 4 (SAPKB70104) SP 14 (SAPKU50014)
SP 21 (SAPKITL431) SP 4 (SAPKB70104) SP 15 (SAPKU50015)
SP 22 (SAPKITL432) SP 5 (SAPKB70105) SP 15 (SAPKU50015)
SP 23 (SAPKITL433) SP 6 (SAPKB70106) SP 15 (SAPKU50015)
SP 24 (SAPKITL434) SP 6 (SAPKB70106) SP 16 (SAPKU50016)
SP 25 (SAPKITL435) SP 7 (SAPKB70107) SP 16 (SAPKU50016)
SP 26 (SAPKITL436) SP 7 (SAPKB70107) SP 17 (SAPKU50017)
SP 27 (SAPKITL437) SP 8 (SAPKB70108) SP 18 (SAPKU50018)
SP 28 (SAPKITL438) SP 10 (SAPKB70110) SP 19 (SAPKU50019)
SP 29 (SAPKITL439) SP 11 (SAPKB70111) SP 20 (SAPKU50020)
SP 30 (SAPKITL440) SP 12 (SAPKB70112) SP 21 (SAPKU50021)
SP 31 (SAPKITL441) SP 13 (SAPKB70113) SP 22 (SAPKU50022)

Examples:

      • You cannot import Support Package 9 of SAP_BASIS 701 without importing Support Package 10 of SAP_BASIS, Support Package 28 of ST, and Support Package 19 of BBPCRM at the same time.

      • You cannot import Support Package 8 of SAP_BASIS 701 without importing Support Package 27 of ST, and Support Package 18 of BBPCRM at the same time.

    • SAP Solution Manager 7.0:

Support Packages for the software components SAP_BASIS 700 and BBPCRM 500 can only be imported together with a Support Package for ST 400, which then displays a Conflict Resolution Transport (CRT). This means that you can import only Support Packages for these software components (SAP_BASIS, BBPCRM) that have already been released if a suitable Support Package for ST 400 has been released. There is a gap between the releases of the individual Support Packages. This problem does not affect you if you import entire Support Package Stacks.

Each row of the following table contains the technical names of the above mentioned Support Packages. The import conditions of these Support Packages must be met by importing all of these or by all of these existing in the system:

                      ST 400                               SAP_BASIS 700                   BBPCRM 500                 
SP 12 (SAPKITL422) SP 12 (SAPKB70012) SP 9 (SAPKU50009)
SP 13 (SAPKITL423) SP 13 (SAPKB70013) SP 9 (SAPKU50009)
SP 14 (SAPKITL424) SP 13 (SAPKB70013) SP 10 (SAPKU50010)
SP 15 (SAPKITL425) SP 14 (SAPKB70014) SP 11 (SAPKU50011)
SP 16 (SAPKITL426) SP 15 (SAPKB70015) SP 11 (SAPKU50011)
SP 17 (SAPKITL427) SP 16 (SAPKB70016) SP 12 (SAPKU50012)

Example:

      • You cannot import Support Package 14 of SAP_BASIS 700 without importing Support Package 15 of ST, and Support Package 11 of BBPCRM at the same time.

    • SAP Solution Manager 3.2 and 3.1:

Support Packages for BBPCRM 310 can only be imported with a Support Package for ST-SUP 320 or ST-SUP 310 (CRT, see also SAP Note 619054).

    • SAP Solution Manager 3.2 and below:

In general, you can import Support Packages for SAP_BASIS and SAP_ABA without the corresponding ST Support Packages. Nonetheless, SAP recommends that you only import the Support Packages from a stack or a Support Package collection at the same time.



Header Data

Released On 19.03.2014 15:01:59
Release Status Released for Customer
Component SV-SMG-INS Installation, Configuration and Upgrade of Solution Manager
Other Components
BC-UPG-ADDON Upgrade Add-On Components (IS)
Priority Recommendations / Additional Info
Category Release planning information

Validity

Software Component
From Rel.
To Rel.
And Subsequent
ST
210
210
 
220
320
 
400
400
 
710
710
 

References

This document refers to:

SAP Notes
1244713   Configuration of Custom Development Management Cockpit
1170668   The role of SAP Solution Manager in Remote Service Delivery
1161294   Name chg, SAP Solution Manager 4.0 to Solution Manager 7.0
1149742   SAP (CQC) Going Live Support
1109650   SAP Solution Manager 7.x Extension Add-Ons
1077981   SAP Upgrade Assessment Preparation Note
631042   Release strategy for Implementation Content (ST-ICO)
569116   Release strategy for Solution Manager Service Tools (ST-SER)
539977   Release strategy for add-on ST-PI

This document is referenced by:

SAP Notes (21)
1170668   The role of SAP Solution Manager in Remote Service Delivery
619054   Release strategy for Solution Manager Service Desk (ST-SUP)
1612514   Solution Manager 7.1 SP Stack 03: recommended corrections
1736166   Solution Manager 7.1 SP Stack 06: recommended corrections
631042   Release strategy for Implementation Content (ST-ICO)
1882217   Solution Manager 7.1 on HANA Stack 01 recommended corrections
1752273   Solution Manager 7.1 SP Stack 07: recommended corrections
1109650   SAP Solution Manager 7.x Extension Add-Ons
1801078   Solution Manager 7.1 SP Stack 08: recommended corrections
1953075   Solution Manager 7.1 SP Stack 11: recommended corrections
539977   Release strategy for add-on ST-PI
569116   Release strategy for Solution Manager Service Tools (ST-SER)
1567091   Solution Manager 7.1 SP Stack 01: recommended corrections
1585777   Solution Manager 7.1 SP Stack 02: recommended corrections
1149742   SAP (CQC) Going Live Support
1843689   Solution Manager 7.1 SP Stack 10: recommended corrections
1077981   SAP Upgrade Assessment Preparation Note
1639266   Solution Manager 7.1 SP Stack 04: recommended corrections
1244713   Configuration of Custom Development Management Cockpit
1161294   Name chg, SAP Solution Manager 4.0 to Solution Manager 7.0
1686689   Solution Manager 7.1 SP Stack 05: recommended corrections