Support Package Stack Components

Details on components of SAP Support Package Stacks

All information on this page is valid for both, SAP applications and SAP enhancement packages.

Starting with a ‘leading' application component, each Support Package stack (SP stack) describes a combination of prescribed or recommended Support Package levels for all single components included in a product version. Dependencies are defined step-by-step, from top to bottom (see example below).

For some components (e.g. SAP GUI) a status is specified for each possible release. Other components may be optional, which means that the corresponding Support Package or patch level only has to be fulfilled if you use the components productively (e.g. an R/3 Enterprise Extension).

The same rule applies to SAP Industry Solutions: The SP stack definition of an Industry Solution contains support packages of many different Industry Solutions. But: You only need to implement those SPs that are

  • used in the activated Industry Solutions in your system (if any).
  • needed as preparation in order to activate an Industry Solution after the implementation of the SPs.
  • required due to a technical dependency (very rarely).  

In principle, the specified level of all components must at least be fulfilled in order to apply a support package of the leading component. Additionally, for most components it is only recommended to have a higher SP level in case there are problems for which no workaround or local corrections are available (for example, correction instructions).

Example what an SP stack could contain:

  • A support package level of the leading application component (e.g. for SAP APPL 6.00), which identifies the SP stack.
  • A support package level of the Application Basis (e.g. SAP ABA 7.00), which is a prerequisite for the application support package above.
  • A support package level of the Basis component (e.g. SAP BASIS 7.00), which is a prerequisite for the above-mentioned SAP ABA support package.
  • A recommended kernel patch level (e.g. SAP KERNEL 7.00).
    The kernel patch level that is used productively can be higher than the one that has to be used for an upgrade to the corresponding release (in this case, the instructions in the upgrade documentation or the corresponding SAP Notes have to be followed).
  • A minimum patch level for each possible SAP GUI release (for example, 4.6D/6.20 for Windows, 6.20/6.30 for Java), whereby the releases are initially seen as alternatives, and each specified patch level represents a minimum requirement that can be exceeded at any time. The minimum requirement within an SP stack will only be increased in exceptional cases. Since the SAP GUI is a part of nearly all SAP products, it must meet the requirements of all SP stacks for the different products used in parallel. This means that you need to use the maximum required SAP GUI with the maximum required patch level. Additional conditions may occur in the context of product-specific GUI add-ons.
  • In some cases, a minimum patch level for each possible SAP ITS release (for example, 4.6D, 6.10, 6.20), whereby like the SAP GUI, the different releases are seen as alternatives.
  • In some cases, additional optional components, which only have to have the specified status for productive use of the components.

 As long as no problems occur, there is usually no need to exceed this level until the next SP Stack implementation.

Normally, there should be no need to exceed this level until the next SP Stack implementation (as far as no problems occur).