SE38 and SA38

[Former Member]

Hi,

How to prevent the users from accessing SE38 and at the same time giving them the access of

SA38? In fact, is there is any particular reason why SAP recommends SA38 instead of SE38

to users.

Thanks in advance

[former_member239282]

SA38 provides the same ability to run programs, but not some of the other abilities of SE38.

[Former Member]

Hi Rama,

Even if you run at both Tcodes; you will understand the difference.

In SA38 you can only execute a program ( either in dialog mode or in background )

While in SE38 you can create / change or display the source code/ program. which users are not supposed to do.

Hence we provide authorization for SA38 and not SE38

Please confirm if solved.

Cheers.

--Shamish

[Former Member]

Hi,

I understood the difference. But How to prevent them. Please post me the procedure for preventing

users to access SE38, but at the same time giving permission to SA38.

Thanks

[Former Member]

Rama,

Assign transaction code SA38 to the role of the particular user. and delete any entry of SE38 in the menu as wel as from the bject s_tcode.

Remove any activity other than SUBMIT from the object s_program.

Thus the user will not be able to execute SE38.

Please confirm if solved.

Cheers

--Shamish

[Former Member]

HI Rama,

Is your problem solved?

If yes, then please confirm it.

---Shamish

[former_member222850]

Thanks for clean explanation Shamish

Regards,

Saravana Kumar V S.

[Former Member]

Hi Rama,

Through SE38 you create/change/run a report program. This is generally assigned to ABAPers. Instead you can give access to SA38 which will allow to display/execute a program. You can restrict SE38 with th following object:

S_PROGRAM, it has the following fileds:

<b>Authorization group ABAP program</b>: Name of the program group that the user is authorized to work with.

Programs that are not assigned to a program group can be started and maintained by any user. The function does not support generic names.

<b>User action ABAP program</b>: Permitted activities.

Possible values:

SUBMIT: Start the program

BTCSUBMIT: Schedule the program to run as a background job

VARIANT: Maintain variants (The SUBMIT authorization is necessary here as well, since programs are executed during variant maintenance).

Hope it helps.

Please award points if it is useful.

Thanks & Regards,

Santosh

[manohar_kappala2]

Hi Rama Krishna,

The main difference between SE38 and SA38 is that the former (SE38 is used for development activities including coding, compiling and execution of the programs.

But the SA38 is mainly for execution of the programs mainly report type programs (the programs which have a execute button at the top).

Now coming to the ways of controlling them

Both would require access to S_PROGRAM, if you dont give access to S_PROGRAM having access to SA38 wouldnt make much sense.

So you can have Submit, Submit with a Variant and Submit as background can be given to this field.

However coming to the development activities its controlled mainly by S_DEVELOP so here u make sure to not include this object or give only display activity at the max.

So this way you can give access to SA38 activities without giving access to development activities of SE38

Hope it helps

Manohar