How to find out which jobs are connected to the user

[former_member614652]

Hello, i have a question, but i was unable to find the answer. The problem is that our internal consultant left the company, and there are certain jobs that run under his account. We want now to switch this jobs to other accounts. The problem we are facing is how to find out what jobs, or job steps are connected with his account, so we can safely demote his account, so that no other jobs will be run under his account. Thank you very much

Sincerely,

Luka Prijic

[former_member188883]

Hi,

Go to tcode SM37. Put down the username you looking for.

Select options scheduled and Released

Select event based option as *

Execute.

This will list down all the jobs scheduled and released under the user you looking for.

You can select each of these jobs and change the username for each of these jobs.

Hope this answers your query.

Regards,

Deepak Kori

[former_member614652]

Thank you deepakkori, but I have another question. What if the job is scheduled or released under different user, but some of the job steps need consultat account to finish? Will your procedure display all jobs (with job steps that use our consultant acc), or will display just scheduled and released jobs under his account.

What about table TBTCP - Background Job Step Overview, does this table contain enough information to see which job step is connected with his account?

Thank you very much for help!

Sincerely,

Luka Prijic

[former_member614652]

Actually can you give us hints or ideas we need to perform to safely lock consultant account (consultant that customized our system, backups, statistics, rfc connections, BI loading, Solman etc...), so the system can work normally without any errors? If there is a SAP document that explains the procedures in this situation (consultant lef the company), please be kind to post the information or link to the information here.

Thank you.

[Former Member]

the only reliable way to do this is by scanning table TBTCP using the person's userID in field AUTHCKNAM and filtering by job statuses: scheduled, released, ready and active (sorry I can't remember the code#'s off top of my head, something like P=scheduled, S=scheduled...you have to look it up). When you search SM37 it only permits you to scan by the userID who created the job, but it won't tell you if a different userID is defined in a job step. That's why you need to scan TBTCP. Don't forget that you should also check for a user's open Workflow items before deletion.

I noticed some posts in this forum that suggest a userID should never be deleted, only locked, added to a special user group, and all role assignments removed. However I've never worked somewhere that does this.

[Former Member]

Luka,

This note includes a report to check for jobs with deleted or locked users: 1533612. I guess you probably are looking for a preventive action to avoid problems before lock or delete the user, but this new report maybe helps you to figure out the issue.

Anyway, I think it´s always advisable to create a special user (without logon) to run periodic background jobs.

Regards,

Diego.

[Former Member]

Anyway, I think it´s always advisable to create a special user (without logon) to run periodic background jobs.

Exactly, people should not immortalize themselves in the system..

For future periodic recuring jobs with non-System users in the steps I am also only aware of browsing TSTCP or creating a query / program to select it correctly (as SE16 selection screen is not very user friendly for this, and also to join on the user type or other user ID attributes such as user group).

Cheers,

Julius