Strategy for support pack strategy

[Former Member]

Hi,

We are working on SAP R/3 4.6C. We have the strategy to apply support packs which is one less than the latest one. For instance if the latest support pack is 51, we apply 50. Is this a good strategy? Or should we apply the latest one. How can we know the pros and cons? How should we do my analysis to arrive at the best decision?

Also we have heard that SAP is going to support SAP R/3 only upto Dec 006; in that light is the assumption correct that there would be no more Support packs released by SAP after Dec 2006?

[former_member184494]

No reply for 8 months - assumed answered

Arun

[Former Member]

Prerna,

Not knowing what your landscape looks like, it is kind of difficult to answer this question. However, one other approach to consider is using Support Package Stacks. By checking the "Product Availability Matrix," you can see when each stack is scheduled for release. I think the basic software for 4.6C is released twice each year. You could plan on downloading the support package stack (all support packages pertinent to that stack plus kernel programs) perhaps a month after its release date. This would give the software a chance to "shake down" any problems. Then, check Note 173814 (OCS - Known Problems with 4.6 Support Packages) periodically as you apply the support package stack to your Sandbox, Development, Quality Assurance, and definitely just before applying to Production.

If you happen to use Industry Solution add-ons, then you will need to seek out those support packages on an individual basis (adding those support packages to the ones that you have downloaded from the SPS [support package stack]).

Unfortunately, if you use HR/Payroll, the scheduled release dates of the SPSs are not very realistic with the amount of time that the application folks need to get ready for year-end. So, you could start with a SPS, and then piecemeal add things to it.

This is ultimately a business decision. Have fun!

[Former Member]

It means that 4.6c goes into a period of extended maintenance following the 5-1-2 rule that SAP launched a while ago. In simple terms you will pay additional maintenance charges to guarantee continued support packs & (legal change packs for HR) . The first year is an additional 2% on your normal maintenance charge, the following two years thereafter its an additional 4%.

Once you reach the end of the eighth year (512) its customer specific maintenance, there is no guarantee that SAP will support you although they normally do as the have the right to negotiate a specific fee for doing this. Can I suggest that you talk to your customer account exec from SAP, in the meantime here is the link to the SAP service marketplace

https://websmp204.sap-ag.de/maintenance

[former_member184494]

Prerna,

Welcome to SDN...

Getting support packs installed unto n-1 is the usually followed strategy , where n is the latest support pack level.

In some cases Support packs are deployed quarterly and every quarter they bring up the level to n-1.

Some Pros and Cons I can think of...

Pros : Regularly updated , not much notes to search for

Support is easy with OSS

Cons: Frequent installation of support packs is a pain especially so if the number of servers is large and the upgrade process takes a very long time.

By the product going off support , it would mean that in case you have any issue that has to be resolved , OSS will ask you to upgrade to the supported version.

The pain in SAP Support packs was that , each component was on a different support pack , now with the netweaver integrated support packs coming , it would become better.

Arun

Message was edited by: Arun Varadarajan