Patch Level (ABAP not equal Java)

[Former Member]

Hi!

We would like to implement ChaRM, Service Desk and Implementation in our SOLMAN.

The ABAP stack is patched to SPS 13. Should the Java side also be patced to SPS 13 or does it make any difference, if we do not use some Java functionality such as Diagnostics?

With other words: should always ABAP stack SPS be equal to SPS of Java stack within SAP Solution Manager?

Thank you very much!

regards

Thom

[former_member185954]

Hello Thom,

I do not know the internals of SAP, however the logic looks like for every DUAL stack system, the JAVA and ABAP patch levels are made as a 'couple' (that's the best way to put it).

So keeping your ABAP and JAVA at different stack levels in a DUAL stack might invite uncessary demons in your dreams

Regards,

Siddhesh

[Former Member]

Hi

It is not mandatory to apply the JAVA and ABAP support packages at the equivalent level.

There are some factors that influence the SPS application:

Some infomation from SAP

The specific customer situation (projects, productive status)

The product (technical conditions, legal changes)

The advantages, especially when it comes to support, of already running on the current Support Package or patch level

The customeru2019s estimation of the risk of operating with known errors (hence incurring unnecessary costs or having to react at short notice)

The anticipated costs of planned maintenance

It is impossible to devise a general rule for calculating the optimal time and frequency of planned maintenance. Customers have to decide for themselves what is best in the given circumstances. However SAP recommends that even without arising problems, there should be a planned maintenance at least once, better two to four times per year, in order to avoid the aforementioned risks becoming too great. SAP assumes, that during the planned maintenance the up to date available SP Stacks are implemented and that the SP stacks used are not older than one year. If problems do occur, SAP can still oblige customers to apply Support Packages or patches that are newer than those specified in the SP Stack.

Irrespective of planned maintenance, problems do sometimes occur unexpectedly and need to be solved as quickly as possible and with minimum effort. Different mechanisms are available for situations such as these, which depend on the technology of the affected component and the type of problem, for example, correction instructions for ABAP-based tracks (which can resolve problems relatively locally and specifically), or kernel patches (which for technical reasons mostly include solutions to several problems and are less specific).

For further information: please go through and navigate for http://service.sap.com/sp-stacks