SM37 Background job failing surprisingly

[Former Member]

Hi Experts,

There are two user IDs- A functional consultant ID(FCID) and a user id(UID) for SAP APO system login.

There is a job in SM36 which is created by the functional consultant ID(FCID) and saved(not released).

Following behavior is experienced while using different IDs-

Functional consultant(FCID)-In SM37, job>repeat scheduling>immediate-->save.- the job is cancelled with an error as "No authorization for ATP area DB and SAP liveCache Reorganization and activity Execute(SAP msg number- /SAPAPO/ATP151)"

User ID(UID)

In SM37, job>repeat scheduling>immediate-->save.- the job is cancelled with an error as "No authorization for ATP area DB and SAP liveCache Reorganization and activity Execute(SAP msg number- /SAPAPO/ATP151)"

The same job is set up as a process chain and being executed successfully. Workaround is to change the 'user' in each step for the background job and make it as (BTCPROCESSOR), which is the user id that we get if we run the process chain. But it is a tedious work as there are multiple jobs like this with multiple steps in each of the jobs.

Even the FCID is working fine in another SAP APO system for the same job in SM37.

Any pointer for the reason of failure and the possible solution would be highly appreciated.

Regards

Manotosh

[Former Member]

Hi All,

I got the answer.

FCID had a universal access along with all Z access also in the DEV system. Hence the jobs created by FCID in DEV worked fine even with other users. This access was limited in the current system(Test system), where FCID didnt have the universal access. Even if SAP_ALL in test system is granted to FCID, there were still basis accesses which were missing. This caused the jobs created by FCID to fail.

BTCPROCESSOR is the user ID created for background jobs. This access has SAP_ALL and other basis authorisations.

Few of the basis authorisations needed and the options are- S_BTCH_ADM = Y, S_BTCH_JOB with DELE(for deleting other user's jobs), LIST(to display spool request), PLAN(to copy other user's job), SHOW(Display job details) etc. If these authorisations are granted to an ID, we will get the results accordingly.

Hence, as a normal practice, we use a user ID which has universal access while creating batch jobs, like BTCPROCESSOR.

Cheers

Manotosh