Skip to Content

Hello colleagues,

I would like to share my experience of SP23 update. If think about updating on this SP level, please think twice. Here is the reasons why.

I assume that SP23 for GRC 10.0 and SP12 for GRC 10.1 are equal, so my descriptions of the problems we faced in SP23 might exist in SP12.

The first issue we faced was spam messages for Mit.Control assignment. The same problem is here.

The interesting thing is that we don’t have active MC assignment process and we didn’t have such a problem before update.

No 1062 entry.

To stop spamming we activated profile parameter 1035 (set it to NO) as Alessandro recommended.

The next issue we experience is password notification for New Account request type.

Before SP update

After SP update

The the last problem discussed here

Our problem is exactly the same and we created the message for SAP. The last advice (that didn’t help) from support was to apply note 2288396.

I hope that we will not face with other problems after update, but I would recommend you to wait for at least SP24 (SP13 for GRC 10.1)


Regards,

Artem

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Harinam SanKirtan

    Rule of thumb, don’t upgrade the SP patch level unless all the notes are required to fix a issue. I tend to recommend customers to go on a certain stable patch level and then only implement the required notes. Try to follow the N-1 rule. i.e. stay on SP22, not on SP23 and implement the necessary notes.

    If, in some cases, a whole SP level update is required to make the solution work (which is sometimes forced upon as a solution by SAP Support), then do it, but even then I would try to be careful 🙂

    “Don’t fix it if it ain’t broken” 😉

    (0) 

Leave a Reply