topic Re: Restricting SM35 by Program Name in Application Development and Automation Discussions

Restricting SM35 by Program Name

Former Member — Fri, 13 Nov 2015 12:13:53 GMT

Dear All,

Does anybody know a way to restrict what programs can be released/executed from transaction SM35.

When I run a trace I find the below:

User	Program Name	Check	Result	Object	Field 1	Value 1	Field 2	Value 2
user01	SAPMSBDC_CC	0	S_BDC_MONI	BDCAKTI	ABTC	BDCGROUPID	POSITION
user01	SAPMSBDC_CC	0	S_BDC_MONI	BDCAKTI	ABTC	BDCGROUPID	POSITION
user01	SAPLBTCH	0	S_BTCH_ADM	BTCADMIN	Y
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLSPOR	user11	0	S_SPO_DEV	SPODEVICE	LOCL
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_ADM	BTCADMIN	Y
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_NAM	BTCUNAME	UK05195
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '
user01	SAPLBTCH	0	S_BTCH_JOB	JOBACTION	RELE	JOBGROUP	' '

Re: Restricting SM35 by Program Name

justin_dauby1 — Fri, 13 Nov 2015 14:14:55 GMT

I restrict SM35 by session name. The users who get the role access are limited by session name.

Re: Restricting SM35 by Program Name

abhishek_sehgal — Mon, 16 Nov 2015 07:22:23 GMT

That can be controlled at transnational level by S_PROGRAM for auth object for restricting tcode to be executed and thus restricting it to be run as a batch

Re: Restricting SM35 by Program Name

Former Member — Mon, 16 Nov 2015 11:50:49 GMT

Check the table USOBT_C, under the object S_Program

Look for Look for field name "P_ACTION" and value

In the name field you can see "Program, transaction or function module name"

So you can restrict by "Authorization group ABAP/4 program" and not giving value "BTCSUBMIT" under field "User action ABAP/4 program"

Here "Authorization group ABAP/4" is the value in "P_ACTION" in the table USOBT_C.

Please let me know if you need more info

Cheers

Pavan M

Re: Restricting SM35 by Program Name

michael_kozlowski — Mon, 16 Nov 2015 12:00:48 GMT

Use authorization object 'S_BDC_MONI'. Check Docu in trx SU21 for further details.

Re: Restricting SM35 by Program Name

Former Member — Mon, 16 Nov 2015 13:38:33 GMT

Hi Pavan,

I'm not sure I follow.

Are you suggesting I add object S_PROGRAM to the role?

Re: Restricting SM35 by Program Name

Former Member — Mon, 16 Nov 2015 13:41:04 GMT

Hi Michael,

how does this restrict which programs can be run?

Re: Restricting SM35 by Program Name

michael_kozlowski — Mon, 16 Nov 2015 14:03:13 GMT

Authorization for trx SM35 can be restricted with authorization object S_BDC_MONI as below:

1. The name of the session

User can only processing the sessions start with names authorized for.

2. The activity in a session (program name doesn't matter)

ABTC: Pass on sessions to background processing

ANAL: Analyze sessions and logs

AONL: Process sessions in dialog mode

DELE: Delete sessions

EXPO: Export sessions

FREE: Release sessions

IMPO: Import sessions

LOCK: Lock and release sessions

REOG: Reorganize sessions and logs

Re: Restricting SM35 by Program Name

Former Member — Mon, 16 Nov 2015 20:51:57 GMT

Luckily Pavan's answers are far enough off the mark that it is clear not to spend much to "try it and see if it works". So I will not reject them as they document his fall progress.

The trick with this is that programs can generate the sessions, so they can control the session names in S_BDC_MONI if you have a convention for them. That is the good news.

Down sides are that if you did not have a convention from the beginning, then it is hard to retro fit. Also the authorization fields follow the ASCII character set from left to right so you need to decide between module first or org. unit first in some cases. Some standard programs are hardcoded but you can SU24 them "out of sight" but others generate numbers even or use a date....

However possibly you meant restricting the program which generates the batch input file which is processed in SM35. That is IMO more critical and object S_DATASET is your weapon here (it has a field for the program name - restrict to it's capability via the code and the auths for the program name) and then use tcode FILE to create logical file paths. These checks are in the SAP kernel of the ABAP commands so you do not even need to code them yourself necessarily. Go for the program name in this case as a first resort (in that sense Pavan is almost correct and pinned the tail just left of the where the kernel checks the program name).

Cheers,

Julius

Re: Restricting SM35 by Program Name

Former Member — Tue, 17 Nov 2015 10:12:01 GMT

yes please

Re: Restricting SM35 by Program Name

Former Member — Mon, 07 Dec 2015 13:45:29 GMT

thanks for your help Julius.