SAPTechno

Note 394616 - Release strategy for SAP Solution Manager

Header
Version / Date 105 / 2013-02-08
Priority Recommendations/additional info
Category Release planning information
Primary Component SV-SMG SAP Solution Manager
Secondary Components BC-UPG-ADDON Upgrade Add-On Components (IS)

Summary
Symptom

You are planning the installation and upgrade of SAP Solution Manager for the following releases:

Solution Manager Release Add-On Release
SAP Solution Manager 7.1 ST 710
SAP Solution Manager 7.0 EhP 1 ST 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, ST210, ST220, ST310, ST320, ST400, ST710

Solution

Contents

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

0. Last change

Date Section Short description
February 2012 V Add-On ST-LV
February 2012 VI Stack parts

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.
  • You can find further information about SAP Solution Manager on SAP Service Marketplace under the quick link "solutionmanager". Under the quick link "pam", you can find the Product Availability Matrix with more information about the product "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. Note 1161294 provides details about this renaming.

II. Overview
  • This note deals with the release strategy of SAP Solution Manager (software component ST) based on SAP Basis Release 6.20 and higher.

  • SAP Solution Manager 7.1
    ST Release ST 710
    NW Release NW 7.0 EHP 2
    CRM Release CRM 7.0 EHP 1
    Availability ST 710 SP 1
    MAY/16/2011 (ramp-up version)
    Maintenance end December 31, 2017 (ST 710)
    SAP Solution Manager 7.0 EHP 1
    ST Release ST 400
    NW Release NW 7.0 EHP 1
    CRM Release CRM 5.0
    Availability ST 400 SP 18
    DEC/15/2008 (default release)
    Maintenance end DEC/31/2013 (ST 400)
    SAP Solution Manager 7.0
    ST Release ST 400
    NW Release NW 7.0
    CRM Release CRM 5.0
    Availability ST 400
    DEC/16/2005 (ramp-up version)
    MAR/31/2006 (default release)
    Maintenance end DEC/31/2013 (ST 400)
    SAP Solution Manager 3.2
    ST Release ST 320
    WebAS Release WAS 6.20
    CRM Release CRM 3.1
    Availability ST 320
    OCT/22/2004 (ramp-up version)
    MAR/31/2005 (default release)
    Maintenance end MAR/31/2009 (ST 320)
    SAP Solution Manager 3.1
    ST Release ST 310
    WebAS Release WAS 6.20
    CRM Release CRM 3.1
    Availability ST 310
    MAY/05/2003 (ramp-up version)
    OCT/22/2003 (default release)
    Maintenance end DEC/31/2006 (ST 310)
    Stop SP download DEC/31/2007

  • 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 component ST is already part of this installation. 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 an installation guide on SAP Service Marketplace at http://service.sap.com/solutionmanager.  Add-On ST can therefore only be used on the CRM and WebAS releases listed in section II.
  • Consider the following restrictions regarding updates and maintenance for your SAP system.
    • You cannot uninstall software components (in this case, ST) once they are installed.
    • 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.

IV. Upgrading the SAP Solution Manager
  • Upgrade ST 710 for SAP Solution Manager 7.1
    • Note 1462137 (for additional information about the procedure, see 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):

    • ST 400 (SP Stack) ST 710 (SP Stack)
      SP 30 (12/2012) SP 08 (scheduled, not yet available)
      SP 29 (07/2012) SP 06 (08/2012)
      SP 28 (11/2011) SP 04 (12/2011)
      SP 27 (06/2011) SP 02 (07/2011)
      SP 26 (03/2011) SP 01 (04/2011)
      SP 25 (10/2010) SP 01 (04/2011)
      SP 24 (06/2010) "SP 0" (no SP Stack)
      SP 23 (04/2010) "SP 0" (no SP Stack)

                    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
    • Note 1169247
  • After the end of maintenance for SAP Solution Manager 3.1 on December 31, 2006, we recommend that you upgrade this release to SAP Solution Manager 7.0.
  • Upgrade ST 400 for SAP Solution Manager 7.0
    • Note 892412
  • Upgrade ST 320 for SAP Solution Manager 3.2
    • Note 770200
  • 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 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 Implementation Content (ST-ICO): For information, refer to Note 631042
    • SAP Solution Manager Support Desk (ST-SUP): For information, see Note 619054. This add-on was integrated into the software component ST 400 as of Release 7.0.
    • SAP Solution Manager Services (ST-SER): For information, refer to Note 569116
    • SAP Solution Manager Change Management (TMWFLOW): The add-on TMWFLOW was integrated into the software component ST 400 as of SAP Solution Manager 7.0.
    • SAP Solution Tools Plug-In (ST-PI): For information, refer to Note 539977
    • Service tools for applications: ST-A/PI For information, refer to Note 69455
    • cProject Suite (CPROJECTS): For more information about this, see Note 427216. As of Release 7.0, this add-on is replaced with the component CPRXRPM.
    • cProject Suite (CPRXRPM): For more information about this, see Note 427216. Only Version 400 is released. Version 450_700 is NOT released for the Solution Manager.
  • Additional software components for SAP Solution Manager:
    • ST-SEP, ST-QCA, ST-PSM, ST-ETP, ST-SPA): See SAP Note 1109650.
    • ST-LV: See SAP Note 1468604. This add-on is integrated in 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:
    • ESMCRM 7.0 (ESM CRM 7.0): See Note 1263312.
    • ESMEWM 700 (ESM EWM 7.0): See Note 1263311.
    • ESMSCEM 700 (ESM SCEMSRV 7.0): See Note 1263310.
    • ESMSCM 700 (ESM SCM 7.0): See Note 1263308.
    • ESMSCMTM 700 (ESM SCMTM 7.0): See Note 1263208.
    • ESMSNC 700 (ESM SNC 7.0): See Note 1263204.
    • ESMAI 700 (ESM AUTO-ID 7.0): See Note 1263114.
    • ESMSRM 700 (ESM SRM 700): See Note 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 component ST

  • For the software component ST, maintenance is carried out using Support Packages. You can find information about individual errors and how to fix them in SAP Notes.
  • There is no extended maintenance for SAP Solution Manager. You can find information about the maintenance strategy in the SAP Service Marketplace under the quick link "pam" (search term "SAP Solution Manager").
  • Support Packages for ST are available in the Software Distribution Center on SAP Service Marketplace: http://service.sap.com/patches -> Entry by Application Group -> SAP Technology Components -> SAP SOLUTION MANAGER
  • You can check the availability of the Support Packages on SAP Service Marketplace at: http://service.sap.com/ocs-schedules -> SAP Solution Manager
  • 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: http://service.sap.com/sp-stacks -> SAP Solution Manager. Not every Support Package for the software component ST had its own stack for SAP Solution Manager 7.0 and lower.
  • 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.
  • Note 1595736 provides an overview of current Release Information Notes for the SAP Solution Manager.


Dependencies between Support Packages

  • In general, Support Packages of the ST software component require certain SAP_BASIS and SAP_ABA or BBPCRM Support Packages.
  • 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 complete Support Package Stacks.

  • ST 710 SAP_BASIS 702 BBPCRM 701
    "SP 0" SP 04 (SAPKB70204) SP 01 (SAPKU70101)
    SP 1 (SAPKITL701) SP 06 (SAPKB70206) SP 03 (SAPKU70103)
    SP 2 (SAPKITL702) SP 07 (SAPKB70207) SP 04 (SAPKU70104)
    SP 3 (SAPKITL703) SP 08 (SAPKB70208) SP 05 (SAPKU70105)
    SP 4 (SAPKITL704) SP 09 (SAPKB70209) SP 06 (SAPKU70106)
    SP 5 (SAPKITL705) SP 10 (SAPKB70210) SP 07 (SAPKU70107)
    SP 6 (SAPKITL706) SP 11 (SAPKB70211) SP 08 (SAPKU70108)
    SP 7 (SAPKITL707) SP 11 (SAPKB70211) SP 08 (SAPKU70108)

           (Examples: You cannot import Support Package 05 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 complete Support Package Stacks.

  • ST 400 SAP_BASIS 701 BBPCRM 500
    SP 18 (SAPKITL428) SP 02 (SAPKB70102) SP 12 (SAPKU50012)
    SP 19 (SAPKITL429) SP 03 (SAPKB70103) SP 13 (SAPKU50013)
    SP 20 (SAPKITL430) SP 04 (SAPKB70104) SP 14 (SAPKU50014)
    SP 21 (SAPKITL431) SP 04 (SAPKB70104) SP 15 (SAPKU50015)
    SP 22 (SAPKITL432) SP 05 (SAPKB70105) SP 15 (SAPKU50015)
    SP 23 (SAPKITL433) SP 06 (SAPKB70106) SP 15 (SAPKU50015)
    SP 24 (SAPKITL434) SP 06 (SAPKB70106) SP 16 (SAPKU50016)
    SP 25 (SAPKITL435) SP 07 (SAPKB70107) SP 16 (SAPKU50016)
    SP 26 (SAPKITL436) SP 07 (SAPKB70107) SP 17 (SAPKU50017)
    SP 27 (SAPKITL437) SP 08 (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)

           (For example: 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.)

           In addition to these recurring dependencies, specific Support Packages may have further dependencies.

  • 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 complete Support Package Stacks.

           

           Each column of the following table contains the technical names of the previous 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 09 (SAPKU50009)
SP 13 (SAPKITL423) SP 13 (SAPKB70013) SP 09 (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)

           (For example: You cannot import Support Package 14 from SAP_BASIS 700 without importing Support Package 15 from ST 400 at the same time.)

           In addition to these recurring dependencies, specific Support Packages may have further dependencies.

  • 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 Note 619054).
  • SAP Solution Manager 3.2 and below: You can import Support Packages for SAP_BASIS and SAP_ABA without the corresponding ST Support Packages. Nonetheless, we recommend that you only import the Support Packages from a stack or a Support Package collection at once.


The following is a list of the current Support Packages for all software components from the ABAP stack of the various releases of the SAP Solution Manager, for your reference.

  • SAP Solution Manager 7.0 Enhancement Package 1

           This information is provided in the stack definitions for SAP Solution Manager 7.0 Enhancement Package 1, which are available on SAP Service Marketplace at http://service.sap.com/sp-stacks (under "SP Stack Information").

  • SAP Solution Manager 7.0

  • Software Component Support Package Technical Name
    SAP_BASIS 700 SP 16 SAPKB70016
    SAP_ABA 700 SP 16 SAPKA70016
    SAP_BW 700 SP 18 SAPKW70018
    SAP_AP 700 SP 12 SAPKNA7012
    PI_BASIS 2005_1_700 SP 16 SAPKIPYJ7G
    ST-PI 2005_1_700 SP 06 SAPKITLQI6
    BBPCRM 500 SP 12 SAPKU50012
    CPRXRPM 400 SP 13 SAPK-40013INCPRXRPM
    ST 400 SP 17 SAPKITL427
    ST-SER 700_2008_1 SP 04 SAPKITLOO4
    ST-ICO 150_700 SP 15 SAPK-1507FINSTPL
    ST-A/PI 01K_CRM560 - SAPKITAC4C

Optional:
BI CONT 7.03 SP 08 SAPKIBIIP8
PI_BASIS 2006_1_700 SP 06 SAPKIPYM06

  • SAP Solution Manager 3.2

  • Software Component Support Package Technical Name
    SAP_BASIS 620 SP 65 SAPKB62065
    SAP_ABA 620 SP 65 SAPKA62065
    PI_BASIS 2004_1_620 SP 07 SAPKIPYI57
    ST-PI 2005_1_620 SP 08 SAPKITLQG8
    BBPCRM 310 SP 14 SAPKU31014
    CPROJECTS 310_620 SP 04 SAPK-31204INCPROJECT
    ST 320 SP 19 SAPKITL329
    ST-SUP 320 SP 19 SAPKITLC59
    TMWFLOW 320 SP 19 SAPK-32019INTMWFLOW
    ST-SER 620_2006_2 SP 08 SAPKITLOJ8
    ST-ICO 150_620 SP 10 SAPK-1506AINSTPL
    ST-A/PI 01J_CRM315 - SAPKITAC2B

Similarly, in SAP Note 781448, the level of the Support Package that is included in the new installation if the SAP Solution Manager is specified. This level changes for different service releases.

The following releases are no longer maintained, the specifications refer to the closing status when maintenance ended:

  • SAP Solution Manager 3.1

  • Software Component Support Package Technical Name
    SAP_BASIS 620 SP 61 SAPKB62061
    SAP_ABA 620 SP 61 SAPKA62061
    PI_BASIS 2004_1_620 SP 07 SAPKIPYI57
    ST-PI 2005_1_620 SP 05 SAPKITLQG5
    BBPCRM 310 SP 14 SAPKU31014
    ST 310 SP 31 SAPKITL2A1
    ST-SUP 310 SP 14 SAPKITLC24
    ST-SER 620_2005_2 SP 12 SAPKITLOBC
    ST-ICO 150_620 SP 07 SAPK-15067INSTPL
    ST-A/PI 01F_CRM315 - SAPKITAC27

Affected Releases
Software Component Release From Release To Release And subsequent
ST610210210
ST620220320
ST700400400
ST702710710

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