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: 

Problem with an id used by a background job.

Former Member
0 Kudos

Hi All,

I've scheduled a backround job with a system id.

For some reasons, the job is failing SM21 logs says "Failed to activate authorization check for user BATCHER-ID".

SM37 joblog shows that "Logon of user BATCHER-ID in client 100 failed when starting a step"

For some reason i am unable to relate the 2 errors.

Has anyone such kind of problem?

Appreciate any help on this.

8 REPLIES 8

manohar_kappala2
Contributor
0 Kudos

Hi,

Verify if you have the right to create job and release with that particular ID.

For this you would require access to

S_BTCH_NAM with that particular ID with which you are trying to run the job.

You can also give access by using the object

S_BTCH_ADM with value Y

But it would give far more wide access so better not to use it.

Hope this helps

Let me know if this is the cause of problem

Manohar

0 Kudos

Hi,

the second Message seems that the User does not exist or is locked in the client.

Gruß

Toni

0 Kudos

Hi,

You can check in transaction SM20 what kind of user error this is.

But the main question is if this have worked earlier?

best regards,

Karl

Former Member
0 Kudos

Well the id does exist & it is not locked.

This was working before.

SM20 didnt show anything.

0 Kudos

Also, the person who released did have all the access to S_BTCH_ADM

0 Kudos

One more checking. Check the user id valid to date under the "Logon Data" tab, and check the roles valid to date to. Also click on the "profiles" tab, drill down the profile to see it the Auth Object and value is there. We have a profile that has transport error, the role look fine, by the transport generated profile was missing the value.

Hope this help.

Lye

0 Kudos

the id is perfectly fine..roles are generated..absolutely fine.

0 Kudos

The error messages sound like an id problem to me instead of Authorization. I seen this error messages before, just cannot recalled the root cause. You said it was working before, in this case, can you run SUIM -> Change Document -> for User to see if there are any changes to this uid recently.