cancel
Showing results for 
Search instead for 
Did you mean: 

Error in user mapping between ABAP and Java

Private_Member_82764
Active Participant
0 Kudos

Dear all,

I just installed BW 7.40 with ABAP + JAVA. I ran the BI initial ABAP setup wizard and BI Java wizard.  After I finished all the configuration steps, I ran the Diagnostics & support desktop too and I am getting the following errors Web ABAP Setting

Reverse user mapping test by RSWR_RFC_SERVICE_TEST failed J2EE user 'Administrator' was mapped to ABAP user 'XXXX' which was mapped back to J2EE user 'XXXX' called

Check user mapping in the user administration. Ensure that by a roundtrip Java -> ABAP -> Java. the java user does not change.

I just wonder how can I change the J2EE user Administrator to 'XXXX' so the error won't happen again. Thanks all.

Accepted Solutions (1)

Accepted Solutions (1)

RamanKorrapati
Active Contributor
0 Kudos

Please check with your basis team or post at below basis forum.

manumohandas82
Active Contributor
0 Kudos

Hi

Please read the following Note and check   step 13 . whether the User the 'Administrator'/J2EE_ADMIN user is mapped to DDIC.

2113395 - Supportdesk Tool RED signal checking trouble shooting guide


If it is then map it to any other user in the ABAP user Store .

A basis Admin will be able to help you with this if you cannot help yourself by checking the same note under

"Error 'Name or password is incorrect (repeat logon)' while connecting to BI Mastersystem via RFC"


Thanks ,

Manu

Answers (2)

Answers (2)

Private_Member_82764
Active Participant
0 Kudos

Thanks all.

After I put in the ABAP user for mapping in portal under Administrator account , the error goes away. Thanks.

sapna_jgurudutt
Active Contributor
0 Kudos

Hi,

Please check whether the following explanation helps you with regard
to this error message:
This error means that your weren´t using a unique BW user, when
executing the Support Desk Tool (SDT) checks. Please note that every
BW ABAP <-> BW Java user needs to be a unique pair.
In particular case you were using portal user ID "XXXX", which also
exists in ABAP stack. As there is no explicit user mapping maintained
in user administration on J2EE side, this implicit user mapping is used.
This means, user "XXXX" executes programs in ABAP stack as user "XXXX"
too.
But additionally to that you also mapped portal user "XXXX called" to
ABAP user "XXXX". So when doing the check callback from ABAP -> Java
the user ID suddenly changes as the ABAP stack detects this explicit
mapping. This is not allowed. You can either use same user IDs or
unique user mapping.

  > Remove the mapping of user "XXXX called" in portal user
    administration and rerun Support Desk Tool afterwards. Click button "Reload
    configuration" and check whether issue persists.

Please check whether this helps you.

Thanks & Regards,

Sapna