Scheduling Infopackage - System uses user ALEREMOTE instead of my USERID

[Former Member]

Hi,

I am running extractor for datasource 0BBP_TD_CONTR_2. But, when I run schedule the infopackage for a run - it

results in an error showing ",,You do not have authorization to extract

from DataSource 0BBP_TD_CONTR_2 "

Upon further check, I find that the RFC connection uses the user name

ALEREMOTE and this particular user does not have the authorizations to

run the transaction RSA3 in the source system.

But, on investigating the same issue in other source systems - I find

the same datasource uses my user JKI to log into the source system.

Here, my UserID is used to run the transaction RSA3 in other source systems. Can

you tell me what is the reason this is happening ?? Is there some

setting I need to do ?

Cheers

Kiran

[Former Member · Accepted solution]

Hi Kiran,

Actually, all these parameters are set when creating the RFC Connection.

But be careful, it is not a necessity to have SAP_ALL and SAP_NEW, there are standard roles to allow extractions, and for security reasons it prevent other actions.

You can go and check in SM59 transaction, you will see on your BW system which user is set to dialog with the R/3, in "Logon/Security".

The password is set there too.

I hope it helps your understanding !

[Former Member]

Having the same issue when running doing extractions, aleremote has full authorizations in source system, sm59 connections look and test ok

any other ideas

[Former Member]

Thanks both of you.

[Former Member]

Hi Arun,

Thanks for the response. I have requested for the authorizations.

But, my question is in system X the background user is my own USERID, whereas in system Y the background user being used in ALEREMOTE.

I find it surprising that they behave very differently.

Any reasons?

Cheers

Kiran

[former_member184494]

Kiran,

Data loads / background data loading should always be done through the backend user.

This background user should havd SAP_ALL and SAp_NEW as the authorizations. This is standard procedure.

This is because data loads will happen only via background users and hence the background user should have full authhorizations.

Also the ID ALEREMOTE should be a system user / communication user so that logon using this ID is not possible.

The solution to your issue will be to give full authorizations for ALEREMOTE in the source system and make it a communication user / system user.

Arun