Skip to Content
Author's profile photo Gregor Wolf

How to setup R/3 Reference system for User Mapping

I think it is a common problem that usernames in R/3 are different from the Portal username. This especially occurs when the Portal authentication is done to a LDAP Directory like Active Directory. We had this problem and here is a how to guide to setup a R/3 Reference system in the Portal to solve this problem.

A detailed description how the Usermapping works can be found in this /thread/15552 [original link is broken].


  • SAP R/3 System
  • SAP Enterprise Portal 6.0 SP 7

Create Reference system in the System Landscape

Logon to the Portal as an Administrator and open System Administration, System Configuration, System Landscape.

  • Open the Folder with your Systems or create a new one if you have not Folder for the systems.
  • Create a new System
  • Select the appropriate Template. For testing it is best to use „Dedicated Application Server for R/3 System” and click Next.
  • Enter System Name, System ID and System ID Prefix and click next
  • Confirm the Summary with Finish
  • As the next step choose “Open the object for editing” and click OK
  • Switch to the Property Category “Connector” enter at least this Fields:

Parameter Setting
Application Host                    
Gateway Host  
Gateway Service  
SAP Client  
SAP System ID (SID)  
SAP System Number  
Server Port  

Important: If you enter a Gateway Service by name e. G. sapgw00 then you have to maintain also the file services in C:WINNTsystem32driversetcservices. For the R/3 Reference System the Gateway Host and Service must be maintained.

  • Switch now to the Property Category “User Management” and choose “SAPLOGONTICKET” as Logon Method and User Mapping Type “User”
  • Switch to display “System Aliases”
  • Enter a Alias for this system and mark it as default.
  • Save the configuration changes and close the system.

Configure User Management to use the R/3 Reference System

  • Open System Administration, System Configuration,UM Configuration in the Portal.
  • Switch to the tab security settings
  • Choose the SAP Reference System from the Dropdown list.
  • Save your settings
  • Restart the J2EE Server of the Portal

Maintain Usermapping

  • Logon to the Portal
  • Click on “Personalize”
  • Choose “User Mapping”
  • Select the System that was defined as R/3 Reference System
  • Enter User and Password and click Save
  • If you entered a valid Username and Password you will get the message “Logon data saved”

Test the Usermapping

To test the Usermapping you can install the Portal Application coming with SAP Note 701205. It provides a IView to display the SSO Cookie Information. After you have installed the PAR in your portal you can access the URL http://portal.server:port/irj/servlet/prt/portal/prtroot/SSOSupport.default and click on “Send” then it will show you the MYSAPSSO2 Cookies for the R/3 User and Portal User.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kazutaka Kikuchi
      Kazutaka Kikuchi
      Hello Gregor,

      Thank you for your useful information!!
      Could I ask one question about this topic?

      We face the following situation,
      The usernames in EP and BW are same.
      But only R/3 usernames are different from them.

      In this case I guess we must setup 2 Reference systems(1 for R/3,1 for BW) if we want to use
      SAPLOGONTICKET as Logon Method.
      And our customer want to use it by security reason.

      Then I would like to ask whether 2 reference systems are possible??
      (It seems only one reference system can be registered with a default screen.)

      Best Regard,
      Kazutaka Kikuchi

      Author's profile photo Gregor Wolf
      Gregor Wolf
      Blog Post Author
      Hello Kazutaka,

      sorry for the delay of my response. AFAIK it is not possible to have more than one reference system. But you will not need it. Define the R/3 as the reference system and do a Usermapping from the Portal to the R/3 Usernames. So in the SAPLogonTicket both Usernames are avaliable. The Portal Username which then is used in Portal and BW and the R/3 Username to SSO to R/3.


      Author's profile photo Kazutaka Kikuchi
      Kazutaka Kikuchi
      Hello Gregor

      Thank you for your response.
      I have tested the way you suggested.
      And I face following situation now...

      Portal UID : test1
      R/3 UID : test2
      BW UID : test1

      1) defined R/3 as the reference system
      2) did usermapping from Portal(test1) to R/3(test2).

      After that, "test2" is also used for BW logon automatically.
      Is any setting necessary in order to continue using "test1" as BW UserID??

      Many thanks for your help
      Kazutaka Kikuchi

      Author's profile photo Gregor Wolf
      Gregor Wolf
      Blog Post Author

      unfortenately I don't know an answer. I would suggest that you start a new Forum Topic in one of the EP Forums here in SDN and post the link to it. So it get's recognized more.


      Author's profile photo Kazutaka Kikuchi
      Kazutaka Kikuchi
      OK! I'll confirm it.
      Thanks a lot, anyway.

      Kazutaka Kikuchi

      Author's profile photo Former Member
      Former Member
      I have a few doubts if you can help me.

      I have a portal user Test1 and an R/3 user TestR31.
      Instead of doing user mapping, I wish to set up reference system using logon tickets. Then I proceeed to set up R/3 reference sytem. Next I go for user mapping.

      Now in my case I only wnat administrator to do user mapping. So when he does user mapping he will map Test1 to TestR31, But What If He Does not Know the Password?