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: 

Transaction SM35 Authorizations

Former Member
0 Kudos

Please don't grill me for posting this question here. Not quite sure where else.

How can we ensure that the user can only see her/his own jobs? Or is there an alternate transaction that has this built in?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

For restrcting this, you need to properly maintain the auth object: S_BDC_MONI in field value: Session name (BDCGROUPID).

Before this there should be a proper session naming convention within the oraninzation... Users have to create the session name as per the authorization given to the user in object: S_BDC_MONI.

Regards,

Sandip.

11 REPLIES 11

Former Member
0 Kudos

SM37 is used to display only.

Regds,

Anil

Former Member
0 Kudos

Hi,

There may by ways of achieving this with authorisation objects, but if you assign authorisation for transaction SMX instead of SM37 this will limit the user to their own jobs.

Regards,

Nick

Former Member
0 Kudos

please use SM37 and don't change the default username.

0 Kudos

create a tcode of type transaction code with variant.

pass tcode : se37.

check the skip the first page.

in the button provide the options what ever you want.

try this,

0 Kudos

> create a tcode of type transaction code with variant.

>

> pass tcode : se37.

> check the skip the first page.

>

> in the button provide the options what ever you want.

That won't work.

raymond_giuseppi
Active Contributor
0 Kudos

Did you ask for

- SM35 and batch input sessions (look at authorization object S_BDC_MONI) - look at [Protecting the Batch Input Sessions|http://help.sap.com/saphelp_nw04/helpdata/en/8c/95ef39dcf9de7fe10000000a11402f/frameset.htm]

- SM37 and batch jobs (look at authorization objects S_BTCH_JOB and S_BTCH_ADM) - Look at [Roles and Authorizations Used in Background Processing|http://help.sap.com/saphelp_nw70/helpdata/en/86/f7f3393bef4604e10000000a11402f/content.htm]

Regards,

Raymond

Former Member
0 Kudos

Moved to security and duplicate deleted.

Please read the forum rules (and try a search).

Former Member
0 Kudos

Hi,

For restrcting this, you need to properly maintain the auth object: S_BDC_MONI in field value: Session name (BDCGROUPID).

Before this there should be a proper session naming convention within the oraninzation... Users have to create the session name as per the authorization given to the user in object: S_BDC_MONI.

Regards,

Sandip.

0 Kudos

It looks like the best possible workaround revolves around restrictions on session name.

This works well if the session names all follow a particular convention.

Former Member
0 Kudos

Go to sm37 and give the name of the user and execute. you can see only the jobs of the user.

0 Kudos

>

> Go to sm37 and give the name of the user and execute. you can see only the jobs of the user.

This is no solution for the problem posted. Please read threads more carefully before answering.