Restriction in Background-jobs for end-users

[Former Member]

Currently our end-users do not have the ability to run for example their reports via background-jobs. We are currently looking for possiblities in authorizations which allow end-users to run their reports via background-jobs, but we want to restrict them from planning/scheduling these reports as background-jobs.

So the requirement is that end-users may use the background-jobs, but only direct and NOT via scheduling.

Does anyone know if SAP Authorizations can help to meet these requirements?

In other words, can I restrict the scheduling of background-jobs, but allow the direct execution of background-jobs via Authorizations in SAP?

Thanks in advance.

Mark

[Former Member]

The below objects should help you.

S_BTCH_ADM

S_BTCH_JOB

S_BTCH_NAM

S_CTS_ADMI

Regards,

CP

[jurjen_heeck]

> S_CTS_ADMI

How is managing the transport system of help in creating background jobs? I'd skip this one.

[Former Member]

Yes. agreed. thats not relevant at all.

[Former Member]

Please use the below value.

S_BTCH_ADM with value BTCADMIN=Y

Also please let us know how it matters or the problem if the user schedules a job.

Thanks,

Gowrinadh

Edited by: Gowrinadh Challagundla on Mar 12, 2009 11:33 AM

[jens_hoetger]

Hello,

> Please use the below value.

> S_BTCH_ADM with value BTCADMIN=Y

IMHO not a good idea. With this authorization a user can do nearly everything with all jobs of all users in all clients.

I would forward to S_BTCH_JOB with activities DELE, RELE, PROT, LIST.

Nevertheless, enabling an end user for scheduling jobs is a risk (but often given). A user might overload the system with lots of longrunning jobs and cause disturbances in the operation. Unfortunately there is AFAIK no good solution for this. Just an advice: the end user normally schedules his jobs with job class C, therefore productive and regular jobs should be scheduled with job class B for giving them priority.

HTH and kind regards

Jens Hoetger

[Former Member]

Hi,

This auth on S_BTCH_JOB is always not allowed to run the jobs in background. For example, check in transaction F150. No where this object checked in.

If you say users can schedule and overload the system, then how is the business going to run. There should be clear guidlines for the users on how should they schedule. As per my knowledge only BW or BI jobs which takes long time. Also we are not allowing users to go to SM36 and schedule a job, hence they can only schedule type C.

I agree with you that S_BTCH_ADM is a critical object.

Regards,

Gowrinadh

[ep_murali]

Hi,
I would like to limit the number of background jobs for each user since don't want one of the users to use up all background job queues.
How can I do it?