Skip to Content
Author's profile photo Tom Cenens

#sapadmin checking SAP packages for specific corrections

While working on a log file monitor through CCMS I noticed that my CCMS autoreaction method fails to execute automatically. Only when triggered manually, the method succeeds.

Searching SAP Service Marketplace I stumbled on SAP Note 1736161 – Alert generated but no autoreaction executed- https://service.sap.com/sap/support/notes/1736161.

The note describes how alerts are being generated but no autoreaction method is executed. It’s not a fix for sure but since the kernel of our SAP Solution Manager isn’t brand new either, I suspect this SAP note can be the solution to the problem I’m encountering.

The proposed solution is updating the SAP kernel and in the lower part of the SAP note, there is a SP Patch Level table which shows in which SP Patch Levels the bug fix has been implemented.

/wp-content/uploads/2012/11/sppatchlevel_154284.jpg

Now, my customer is running a SAP Solution Manager 7.1 on a 720 EXT 64-BIT UC which is not mentioned in the SP Patch Level list. At first sight you would think no patch is available for 720 EXT 64-BIT UC and an update to 721 EXT 64-BIT UC is required to solve the issue.

So how can you check if there is no patch available for the level your customer is on? You can check which corrections are in a particular package in the swdc area of SAP Service Marketplace.

Navigate to https://service.sap.com/swdc and call up the relevant kernel package folder:

/wp-content/uploads/2012/11/dw_154285.jpg

Next to the packages there is a Info link. When you click on the Info link you will get the list of SAP notes which are parts of the package.

/wp-content/uploads/2012/11/correction_154298.jpg

When I perform a search on 1736161 (the relevant SAP note number) I end up on (0.316) which means the correction is part of the dw package 7.20 EXT 64-BIT UC level 316 and higher.

This also means I’m not forced to update the kernel to 721, instead, the updated dw package can be implemented to solve the problem.

Assigned Tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      I think you can use information about patch level for SAP Kernel 7.20 64-bit Unicode equally for SAP Kernel 7.20 and 7.20 EXT. But method you described is very useful. Thanks.

      Author's profile photo Tom Cenens
      Tom Cenens
      Blog Post Author

      Hi Roman

      Thanks for your comment.

      That's not exactly the case, there is a difference between non EXT and EXT and the package releases are not aligned. If you check service marketplace you will notice newer full packages (SAPEXE, SAPEXEDB) are available for the non 720 EXT kernel compared to the 720 EXT kernel.

      Best regards

      Tom