Patching Cycles

[Former Member]

Hi Folks,

We've been having a debate with SAP about the frequency of update required to maintain support. There has been an OSS note issued regarding this which is:

http://service.sap.com/sap/support/notes/2051068

It basically states that code corrections will only be released on the latest support package:

"Therefore, prerequisite for a patch to successfully resolve a customer issue is that the IdM installation has been updated to the latest delivered SP of Identity Management 7.2."

As the updates by SAP are produced twice a year, this forces customers to patch twice a year to maintain support. Not only that, but you must patch quickly after each patch is released. As a customer, we thought we were doing a good job patching once a year, but now, depending on our patching cycles we can be out of date within weeks of us finishing our patching. This problem will ease when 7.2 becomes a second class citizen in terms of patching once IdM 8 is released, but for the moment, this is causing us pain.

How is anyone else coping with this, and do you have any thoughts?

Cheers,

Ian

[Brindavan_M]

Hi Lan,

For patching once a year or twice a year its doesn't make matter. SAP will suggest for any patch update based of their new functionality or pervious bug fixing. It is good to update the patch if SAP recommended.

This is what I'm understand.

Thanks,

Brindavan