Skip to Content

Get Ready for Enhancement Packages (4) – Equivalent support packages and how they are related with Enhancement Packages

  Editions of this series: Get ready for Enhancement Packages (1)Get Ready for SAP Enhancement Packages (2): The differences between enhancement packages and release upgrades – Get Ready for SAP Enhancement Packages for SAP ERP (3): Include EHP 3 in your SAP ERP 6.0 Installation / Upgrade ! – 4


Enhancement Packages base on a dedicated Support Package

SAP Enhancement Packages for SAP ERP are pieces of software that are installed on top of an existing SAP ERP 6.0 system. The development of an enhancement package starts on a defined state of the underlying software – this dedicated stated is described not only by the release (SAP ERP 6.0), but also by the support level. For example, enhancement package 2 is built on top of SAP ERP 6.0 Support Package Stack 08 (SPS 08).

For Enhancement Package 2 (EHP2), this means that SPS 08 (and all former stacks) have to be installed before Enhancement Package 2 is installed. ‘Before” means, if we look at a queue of installation packages, SPS 08 comes before EHP2. So the SPS and the EHP can in fact be installed in one installation queue, in one step, in one downtime. (The identification of the relevant installation packages as well as building the installation queue takes place automatically by the SAP Solution Manager Maintenance Optimizer.)



Enhancement Packages include corrections

In a timely manner, EHP2 was built in parallel to SPS 09 and SPS 10. All corrections on traditional (SAP ERP 6.0) functionality are available in both software deliveries:

  1. The corresponding Support Package (for SAP ERP 6.0) and
  2. The enhancement package

In other words: an enhancement package does not only include new functions (which are of course ‘hidden behind switches), but it includes also corrections (which are not hidden, as usual). Corrections that are delivered in an enhancement package have the same impact on your solution as corrections delivered in a Support Package.

This is one reason why the installation of enhancement packages – even before activating any business functions – requires thorough regression testing. In order to not face an extra iteration of regression testing, EHPs have to be implemented along with the maintenance cycles – unless they are installed in an upgrade or a new installation.

The installation of EHP2 also brings the corrections of SPS 09 and SPS 10 to your system. This is also the case if you had SPS 08 or SPS 09 installed before installing the EHP. The corrections ‘cannot be left out’ during the EHP installation. This is valid for all software components that are part of the selected technical usage(s) of your EHP. Other software components – those that are not part of the technical usage and that are supposed to remain in their old version – will be touched (neither by enhancements nor by corrections) if you do not change their correction level.


Due to the short release cycles, Enhancement Package 3 was built in parallel to Enhancement Package 2 and shipped in parallel to SPS 11. As a consequence, EHP3 also bases on SPS 08, as EHP2 does. All corrections of SPS 09, SPS 10 and SPS 11 are part of EHP3 and are always installed during an EHP3 installation.

The later an Enhancement Package is implemented, the more occurrences you will face that corrections enter your system again – even though these corrections were already implemented in the system. Should you have any modifications in these corrected objects, these would have to be adjusted again.


Equivalent Support Packages

After the initial delivery of an enhancement package, all further support levels of this enhancement packages are in synch with the support packages of SAP ERP 6.0. Once an enhancement package is installed, you only need to have the support level of your enhancement package in mind, and corrections for software components on lower versions will be automatically (again by the Maintenance Optimizer) included in your  installation queue.

All SP Stacks that SAP delivers for each EHP are time-synchronized with SP Stacks for SAP ERP 6.0 . These time-synchronized SP Stacks are called ‘equivalent support package stacks”.


Enhancement Packages are cumulative

The installation routine for enhancement packages ensures that an EHP cannot be installed without the former installation of all former EHPs. For example, EHP3 requires EHP2 – as a result, EHP3 also includes all functionality that was originally delivered with EHP2.

You cannot install EHP4 without receiving all business functions that were originally provided with EHP2 or EHP3.


Enhancement Package 3 includes SAP Enhancement Package 2 for SAP ERP 6.0

The delivery of EHP 03 technically differs from the delivery of EHP4:

  • An EHP3 shipment includes all objects that were changed with EHP2 and EHP3.
    The installation of EHP 2 brings a number of enhanced objects to your system. If then, EHP3 is installed, these same objects enter your system again, even if these have not been changed again with EHP3. Therefore, if you have the choice to implement either EHP2 or EHP3, you should directly go with EHP3.
  • An EHP4 shipment will include only objects that were changed with EHP4.
    If EHP3 was already installed, only objects changed with EHP4 are installed.
    if EHP2 was already installed, an EHP4 installation would trigger the installation of the required sublayer: EHP3 (with EHP2 included).


EHPs still better than an Upgrade?

This is a question that you might ask yourself after reading this.

Yes it is, for the following reasons:

  • Delta shipment: EHPs deliver only changed objects, whereas in a release upgrade, all objects of all software components are replaced. Since the number of objects can be very big, it is important to use the ‘EHP Installer’ tool in order to minimize your technical system downtime.
  • Partial installation: option to install only selected parts of the EHP, so you can e.g. keep HR components stable while updating your Financials processes
  • No delta customizing
  • No table conversions
  • No new functional developments are visible to the end-user before a business functions is consciousely ‘switched on”.

The scope of your regression test after installing an EHP should be as big as for your SP Stack update. The effort for installing and implementing an EHP (without switching on new features) is similar to a SP Stack implementation. It might be a bit bigger, because you have to deal with the enhancement package concept, which might still be new to you. You may want to decide which technical usages to install etc. And finally, the number of changed objects is larger than in a pure SP Stack update project.

I hope this brings some more light to your understanding of enhancement packages. Any thoughts on this? Questions or other comments?

Best regards, Doris.

You must be Logged on to comment or reply to a post.
  • I have been reading some of your web blogs on SDN and found them very interesting.

    I have one question around the ERP EHP 4.  In a Note 1143022

    – The installation of SAP ERP 6.0 EHP4 requires at least SAP NW
    7.01 Support Package stack 2 (Support Package stack 2 of EHP1
    of SAP Netweaver components).

    Does this mean we need to install the SAP Netweaver EHP 1 on our ECC 6 first or does it mean we would require our EP 7 portal system to have SAP Netweaver EHP 1 if we are to install ERP EHP4 on our ECC 6 system.

    • Hi,

      The underlying NW should be updated to EhP1 of NW for ERP EhP4 to be applied on an ERP system.It is mandatory.But if you are using Portal as frontend and ECC system as the backend system then you need not have to mandatorily update your portal to NW EhP1 while you update ECC to EhP4.If you have to get the new features of EhP1 of NW in portal then you would want to update the portal also to EhP1 of NW.

  • Must appreciate the simple but valuable content in your blog for a relatively new topic for all Basis.

    I have a question:We are upgrading from ECC 6.0 SP11 to EHP4.As i understand,the installer will automatically trigger EH1-EHP3 and then install EHP 4 on top of it ?
    But for my Portal system which is on NW7.0 SP17,i dont want EHP1 but still would like to deploy some BPs and XSS available for EHP4.Is this also progressive,meaning do i need to deploy BP ESS 1.31 before BP ESS 1.41 ?

    • Hi Azalina,

      The Solution Manager – Maintenance Optimizer (Mopz) will automatically identify and download all required SPs and EHPs, based on the selected “Technical Usage”. The EHP Installer will then consume the Stack XML (which the Mopz also created) to install/update all required components.
      In case the Technical Usage only contains packages for the ECC Server everything will be updated according to the Mopz definition (based on NW 7.01).
      In case you select a Technical Usage which also contains Portal content (e.g. the one for ESS) you can choose between two product versions: “EHP4” and “EHP4/NW 7.01). So you are not forced to update the portal to 7.01 in order to use the latest ERP EHP4 functionality (just use the product version “EHP4” in that case in the Maintenance Optimizer).

      In case you have further questions, please let me know.

      Best regards,

  • A simple but important question: Where would I find equivalence between ERP 6.0 SP Stack and ERP 6.0 EhP4 SP Stack?
    From the blog I can understand that ERP 6.0 SP Stack 14 is equivalent to ERP 6.0 EhP4 SP01.
    But I need to know where I can find this information being it a continuous process I need to know equivalence for each latest EhP4 SP Stack releasing.
    • I have the same question. This can resolve another question that I have. What is the “Technical Usage” that I should choice for an ERP 6.0 IDES System (we use only the BC-Application Hierarchy including SAP_ABA, SAP_BASIS, SAP_BW, PI_BASIS, CPRXRPM …) so that with an EhP4 Installation/Update scenario I’m sure I have an equivalent of an ERP SP13 or SP14.

      Best regards,