topic Re: Background Administration Setup - End Users in Application Development and Automation Discussions

Background Administration Setup - End Users

Former Member — Tue, 30 Oct 2007 10:07:28 GMT

Hello

We want to put in some restrictions from Transaction SM37 to our end-users

We only want end-users to have access to display , delete , release their OWN Jobs and not have access to the other users’ from SM37

From the Roles in PFCG that have access to SM37 I have done the following:

•Deactivated S_BTCH_ADM (I don’t want them to have access to Manage Background Administration)

•Deactivated S_BTCH_NAM (I only want the user to view himself and not other users with entry “ *” or username )

•S_BTCH_JOB (Gave the values RELE , DEL , List , Prot ) – I excluded Show as for reason not to have access to display others jobs

With the above done I can still view the other end users’ background jobs.

Any idea on how I can setup correct security measures for SM37?

Thanks & Regards

Marlon

Former Member — Tue, 30 Oct 2007 10:34:41 GMT

They should be able to do this stuff via SMX

Former Member — Fri, 02 Nov 2007 09:31:10 GMT

Thanks for reply but is this the only answer?

Is there no way to restrict SM37 from users to display other's background jobs and to resubmit it?

The users are used to SM37 and to enforce SMX is gonna be quite some pain.

Regards

Former Member — Fri, 02 Nov 2007 10:02:34 GMT

As far as I am aware, unless you want to modify SM37 then you should use SMX to restrict users to displaying (and managing) only their jobs.

If you leave S_BTCH_ADM, S_BTCH_JOB & S_BTCH_NAM blank, users will still be able to see all the batch jobs but only manage their own.

The screens are very similar between SM37 & SMX so your users shouldn't have too much trouble (though nothing would surprise me.......)

Former Member — Wed, 05 Nov 2008 06:40:12 GMT

Thanks