Blogs

Kathrin Winkmann

Announcement – New SAP Enhancement Package Installer available
Kathrin Winkmann SAP Employee Active Contributor Silver: 500-1,499 points
Business Card
Company: SAP AG
Posted on Nov. 24, 2009 12:06 AM in ABAP, Application Server, SAP Business Suite, Enhancement Packages, ERP, SAP NetWeaver Platform

Subscribe.Subscribe
Print. Print
Permalink Permalink
Share
Introduction

This is an announcement for the newest version of the SAP Enhancement Package Installer. This new version will be available for Download via SAP Service Marketplace on 25th November 2009. Read more and check out which new features and improvements this new tool provides you.

Starting with SAP enhancement package 4 for SAP ERP 6.0 and SAP enhancement package 1 for SAP NetWeaver 7.0 the SAP Enhancement Package Installer (SAPehpi) is the standard tool which is used for the SAP enhancement package implementation.  
Implementation ScenarioImplementation Scenario

Mid of May 2009 we announced a Pilot Program SAP enhancement package installer for SAP Support Packages for customers planning to install SAP Support Packages –only with a downtime minimized and risk mitigation approach. After a successful pilot phase we are glad to announce the general availability of this tool.

Of course this SAPehpi can also be use for SAP enhancement package implementation and by the way we also added a lot of new and improved features to this shipment.

New features and Improvements

All the features below are also described in the Installation Guide for SAP enhancement package installations:

  • Using SAPehpi to apply Support Package Stacks on ABAP-only systems: You can use SAPehpi to apply Support Package Stacks to your ABAP-only system, even if you do not install an enhancement package. Using SAPehpi for Support Package Stacks-only you can benefit significantly unsing the SAPehpi System Switch Technology for a larger number of Support Packages. With the new procedure you can benefit from a downtime and risk mitigation approach compared to Support Package Stack implementation via Transaction SPAM (Support Package Manager).
    Note: This scenario is currently only released for ABAP-only systems.
  • Improved system cloning: With an improved system cloning procedure the overall runtime of an SAP enhancement package installation via SAPehpi is reduced. The system cloning is now accomplished faster and with less free space needed. The parallelization of the system cloning was completely revised to improve performance and can now be easily controlled. If possible, only client 000 is copied to the shadow table. This option significantly reduces the amount of data to be copied and thus the runtime of the cloning and additional space requirements on the database.
  • Health Check Test of Source System: During the SAP enhancement package installation we build up the shadow system by cloning the existing repository (productive system). Implementing SAP enhancement package is a customer individual approach, therefore it becomes necessary to apply patches to the original system to avoid problems and errors during the installation procedure. SAPehpi now displays a list of SAP Notes (these SAP Notes are part of the General Installation Note – 1245473) that you have to implement to avoid problems and errors resulting from you source system during the installation.

 Health Check

  • Logon to installation GUI is password protected: To avoid unauthorized access to the enhancement package installation process, the logon to the installation GUI is password protected. You are asked for the initial password during the starting procedure of the SAPehpi in the command prompt.

Password 

  • TroubleTicket: The enhancement installation program creates a trouble ticket and a log archive in the case of an error.
  • Modification adjustments transports: The enhancement package installation program offers to choose between different adjustment transports or to enter your own transport request.

Modifications Adjustments Transports 

  • Optimized preconfiguration modes: The preconfiguration modes – standard resource use and high resource use – have been optimized regarding the use of available system resources. After you have choosen the preconfiguration mode which you will use to run the SAP enhancement package installation SAPehpi provides you with an overview of the tool configuration.

Preconfiguration Modes 

  • Accessibility mode: The enhancement package installation can run in accessibility mode.

 

Essentials You need To Know about
…the SAP Enhancement Package Installer Tool

  • Uses a new and improved version of the System Switch Technology (proven since SAP basis 6.10 as ABAP upgrade technology). We clone the existing repository while the overall runtime remains equal.
  • Follows an intuitive guided procedure.
  • Is characterized by a streamlined installation process. 
  • SAPehpi 

     

    …your Benefits
    • You can use your system in productive mode until the point where the Enhancement Package Installer switches between your original repository and your shadow repository. That means a long uptime processing plus significantly shorter downtime.
    • You have the possibility to reset the installation procedure at any point in time before the Downtime Roadmap Step is reach. This is the phase where the repository switch takes place.
    • The "point of no return" of the installation procedure via SAPehpi is reached significantly later than via transaction SPAM/SAINT.
    …regarding the preparation of the necessary prerequisites  
    • Make yourself familiar with the SAP enhancement package concept and strategy, see Must Know document.
    • Prepare yourself and your system, that means learn more about the End-To-End Process, about how to setup correct and consistent maintained system landscape data via SLD and transaction SMSY and cover some insights into related tools like SAP Solution Manager, Maintenance Optimizer and SAP enhancement package installer, see How To Install SAP enhancement package 4 Guide and SAP enhancement package installer (SAPehpi) guide.
    • Download the newest SAPehpi executable, see Software Delivery Center -->Download --> Support Packages and Patches --> Support Packages and Patches - Entry by Application Group --> Additional Components --> Upgrade Tools --> SAP EHP INSTALLER 7.00

    Kathrin Winkmann  Active Contributor Silver: 500-1,499 points Technology & Innovation Platform Product Management Lifecycle Management


    Comment on this article
    Comment on this weblog
    Showing messages 1 through 7 of 7.

    Titles Only Main Topics Oldest First

    • backwards compatible?
      2010-02-24 11:53:50 Edward Klemm Business Card [Reply]

      i see an installer for 7.00, 7.02, 7.10..


      can i use 7.10 to apply abap patches for a 700 system???

      • backwards compatible?
        2010-02-25 00:44:14 Kathrin Winkmann SAP Employee Business Card [Reply]

        Hi Sandeep,


        as described in the blog please use SAP EHP INSTALLER 7.0


        7.1 can not be use to apply SP's for ABAP only systems.


        Hope this helps.


        Best regards,
        Kathrin

    • Questions
      2010-01-22 13:41:04 Gopal Palanivel Business Card [Reply]

      1. Can the SAPehpi be used for dual stack ? i.e : ABAP+Java in single system/DB
      2. If Ans is "Yes" for above , Will the SAPehpi tool will intall Java SPs also in downtime phase like in EHP Install?
      3. Does this takes care of the kernel install as well?
      4. What is the xml to be used? . Can the XML generated for SPs download from MOPZ be used?
      • Questions
        2010-01-25 07:51:59 Kathrin Winkmann SAP Employee Business Card [Reply]

        Hi Gopal,


        let me split your questions in 1.SAP enhancement package installation and 2.Support Package Update.


        For 1. SAP enhancement package installation all questions can be answered with YES.


        For 2. Support Package Update the SAPehpi can only be used for ABAP-only systems (Qestion 1.), that means the answer for question 2 is NO. Java Support Packages have to be updated via Java Support Package Manager (JSPM).
        The Kernel can always be updated via SAPehpi and of course the SAPehpi needs always an stack configuration file (XML file) generated via SAP Maintenance Optimizer.


        Hopes this helps.
        If you have further questions feel free to contact me.


        Best Regards,
        Kathrin

    • Very nice ...but is there a way to eliminate downtime
      2010-01-17 02:26:13 Shirish Joshi Business Card [Reply]

      Hi Everyone,
      This is very nice. it is the same thing as the old repository switch approach. it has of course been fine tuned.
      However i hear SAP also now has a Near Zero Downtime Approach. What is basically done is that an entire system is cloned and given to end users. All transactions on this system are recorded by some means (oracle or other tool). The other primary system is now upgraded or migrated. After everything is over , the recorded transactions on the copied system are applied to the primary system. In the event that any of the tables to which these transactions belong have been changed during the upgrade, there is a conflict resolution to fix this issue.


      Regards
      Shirish Joshi

    • does it mean SPAM/SAINT no more used
      2009-11-27 02:23:39 Samrat Dangeti Business Card [Reply]

      with new ehp installer we only need spam/saint tcode to update SPAM/SAINT reset it taken care by ehp installer?
      • does it mean SPAM/SAINT no more used
        2009-11-27 02:43:11 Kathrin Winkmann SAP Employee Business Card [Reply]

        Hi Samrat,


        sorry but I didn't get your question?
        SAPehpi for SP's (ABAP-only) is an additional option to install Support Package Stacks. Applying SP Stacks via SAPehpi is a downtime and risk mitigation approach. If you do not have the need the reduce the downtime for SP Stack installation you can also use SPAM to do it.


        Hope this helps.


        Many Thanks and Best Regards,
        Kathrin


    Showing messages 1 through 7 of 7.