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: 

Protecting a background job...

Former Member
0 Kudos

Hello!

This question may seem ridiculous, but I actually have an application for it. Does anyone know if I can protect a released background job from being deleted (accidentally or intentionally), and if I can protect it from being cancelled while it is running?

Thanks!

John

1 ACCEPTED SOLUTION

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

Other than removing the authorization for SM37. I don't think that you can.

Regards,

Rich Heilman

2 REPLIES 2

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

Other than removing the authorization for SM37. I don't think that you can.

Regards,

Rich Heilman

0 Kudos

Hi Rich;

Unfortunately, that is not an option in these cases. We are running an event-driven job to track any instances of super-user log-ons in the system. The job checks to see if the super user has logged off, then it sends an e-mail of the transactions they executed to the big wigs. Since the super users have SAP_ALL, and they would need SM37 for other reasons, that probably will not work.

It is a ridiculous question, and I can't imagine SAP would offer a solution but I thought I would try...

Thanks!

John