cancel
Showing results for 
Search instead for 
Did you mean: 

'Created by' column in SM37 contains inactive users - audit issue?

Former Member
0 Kudos

Hi,

Most of the jobs in sm37 in our systems have been created by staff who had already left. So under the 'created by' column in SM37 we can see jobs running under users who have been locked/deleted. But it's only the 'created by' column. All the 'steps' run under a system user called 'BATCHUSER', that's why the jobs run fine.

Is it a problem to have inactive users under the 'created by' column in SM37? Is it an audit issue? I've thought that as long as the steps run as a system user then it shouldn't be an audit issue but having discussing about it in my team.

Any comments will be very welcome!

Thank you

Marcia

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

The best practice would be to not allow periodic jobs to run from individual IDs. You may create functional IDs for jobs realted to specific module and run the periodic jobs with these IDs. This way anytime any employee leaves, you do not need to copy these jobs and it would also go fine with the audits.

Cheers!!

Javed

JPReyes
Active Contributor
0 Kudos

Is it a problem to have inactive users under the 'created by' column in SM37? Is it an audit issue?

Certainly it doesn't compromise the funtionality, but from the Audit point of view I guess you need ownership and accountability so I think your best shot is simply to copy the jobs under the new user and remove the ones created by old users as mentioned before.

Regards

Juan

Former Member
0 Kudos

Yes,

This is purely depends on your org understandness, As in system there won't be any issue as long as the jobs run.

In SAP there is no such way to change the owner (Created by) of background job, we only can change the step owner.

If you feel that there will be an issue, my suggestion is to copy the jobs to BATCHUSER and delete all old jobs created by inactive users.

Regards,

Nick Loy