1 Reply Latest reply on Jul 10, 2012 5:02 PM by David Stanton

    Survey: Frequency of Support Pack/Stack Application

      How frequently do you apply Support Packs/Stacks/EhPs to your systems?

       

      We are on ECC6.05 and have separate instances for

      ERP

      HR

      APO

      CRM

      SRM

       

      In the HR space, we follow SAP's instructions and apply a synchronization stack annually (June/July) followed by Country Legal Changes for the U.S. in December.

       

      In other instances of our SAP landscape, we are attempting to determine the best practice and understand how other companies operate. I would appreciate anyone's feedback!

       

        • 1. Re: Survey: Frequency of Support Pack/Stack Application
          David Stanton

          Our practice over the past 3-4 years has been to apply support packs annually in December for the HR legal changes, and to catch up on the other components at the same time.

           

          We have a single ECC landscape supporting multiple components, e.g., HR, FI, CO, etc (which complicates the pre- and co-requisites somewhat; but this single-landscape strategy was decided over ten years ago, and cannot readily be changed). We also have SRM, BW, and EP landscapes, which are usually updated at the same time. We arrived at this annual cycle for our major systems in large part because of the testing effort involved.

           

          We are trying to shift to a strategy of applying support packs two-three times each year, with December reservered (as much as possible) for HR legal changes, and the other times to keep the other components updated, reducing the number of changes taking place during the limitted time frame at the end of the year.

           

          We do try to apply EhP in anticipation of needed functionality, then activate the functionality as needed as part of projects.

           

          To address the testing effort, we recently acquired a third-party tool that compares the changes in an updated with an un-updated system, along with application usage statistics (ST03). This tool generates reports that help guide testing to areas where it will be most effective.

           

          We have other landscapes, e.g., SolMan, PI, that are updated on their own schedules, since they have less impact on critical business processes or require less testing effort.