Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

New SU53, wow!

jurjen_heeck
Active Contributor
0 Kudos

Recently I installed a new SAP Netweaver trial because I couldn't renew the licenses for my old one anymore. The new one has component version SAP EHP 2 for SAP NetWeaver 7.0. Nice to be up to date again with my sandbox.

I just ran SU53 in this new system and almost fell off my chair with amazement!!!!

It has history!

It updates without the end-user having to trigger anything!

I knew the changes were coming but hadn't seen the results yet and kinda forgot about it. Wow! We have all been waiting so long for this much more usable tool. Thank you SAP and all involved in requesting this change!

Thank you! Thank you! Thank you!

Jurjen

2 REPLIES 2

former_member202471
Participant
0 Kudos

Hello Jurjen,

We're glad to hear that you've enjoyed new SU53.

FYI: this has been announced in SCN back in March 2013:

http://scn.sap.com/thread/3209446

Hopefully this improved feature will smooth your work in a daily basis.

With warm regards,

Felipe Fonseca

Former Member
0 Kudos

You might want to add a "watch" on the security functionality watchlist: http://wiki.sdn.sap.com/wiki/display/Security/Security+Functionality+Wishlist-Topics

This one was: http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=85000831

Actually the real origin was an even earlier discussion about the ability to perform licensing measurement optimized via correct authorizations (starting S_ALR_Blabla costs more if you have SAP_ALL than if you have a display info user role) without having to use the St01 trace, but the webservices and webdynpros and RFCs and external programs and batch processing got in the way because no context is available and classification can only be tied to tcodes to a limited extent.

The ability to monitor several checks in time intervals and also see the (extended) reason codes is for me the biggest improvement. That is very valuable information.

The old SU53 combined with inaccurate SU22 data is responsible for most security flops IMO! (second only to "value role" concepts) because the project team thought they are passing just a small problem on to the help desk....

Cheers,

Julius