Skip to Content
author's profile photo Former Member
Former Member

SAPGui-Windows Transaction iview

Happy New Year SDN forum,

I developed a SAPGui-Windows Transaction(SMEN) iview, I'm passing the client(100) as parameter. When appending the (tested and hardcoded) userid and password to the parameters field (as client=100&user=baba&password=zolo), I'm getting "wrong user id or password" in the SAPGui. Yet when typing the user and password, then I logon to the SAPGui successfully.

1- What is the correct parameters syntax for user and password?

2- With Both EP6 and the SAP R3 back-end system set for SSO, can I user MappedUser and MappedPassword as a valid parameter, to pass?

3- How does the R3 receives the EP6 user credentials?

4- with SSO, Shall I use parameters or not?

Regards,

AAAttar

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 26, 2004 at 11:03 PM

    Aater,

    If I understand correctly, you want to create an R/3 transaction iView which logs all users on to R/3 using one signle hard-coded ID? If so, then you should use the portal's integrated user mapping functionality and set you iview to "uidpw" authentication. In the R/3 system object, set user mapping type to "admin". Now, assign that single R/3 user/password combination to all users that shall access the iView. The best way to do so is to assign these credentials not to individual users but to a group or role (say: group "authenticated users" if all users shall be able to access the iView).

    Regarding your questions, the approach given above should answer 1 and 2. For 3, the user credentials will be encoded and finally placed in the R/3 "launcher snippet" (being either a SAP shortcut file or a web page that loads sapgui as either Java applet or ActiveX control - depending on the iView's configuration).

    For question 4, I assume you are speaking of the SAP Logon Ticket mechanismn as "SSO". What are you reffering to as "parameters"? As the SAP logon ticket already contains a user Id, you won't be able to give an alternate ID. Of course, it is still possible (and required) to specify a client number and tcode as parameters.

    Regards,

    Dominik

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks Dominik,

      You are right, there is no need for UI/Pwd as parameters for SSO since the EP and SAP are configured correctly. After detailed investigation, we found out the users did not have access to the intended SAP system! others did not install the SAPgui in the stadard file path, and others use different passwords (with the same UID) the access multi-SAP system. This a prime candidate solution for user mapping.

      One question, with SSO set and using default authentication iviews, we were accessing many SAP/BW systems with same user ID but regardless the password!

      Have a happy new year,

      AAAttar

  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2004 at 12:13 AM

    Hi,

    I am facing some what similar problem.

    We are running EP 60 SP7 and SSO to R/3. Could anyone please help me on the following problems:

    1. I created WinGui iView, when i clicked on "PREVIEW" button, its throwing an error "Unknown Service".

    2. Also i created JavaGui iView, when i clicked on "PREVIEW" button, its showing CROSS symbol in the browser body and "Applet not initiated". I placed installation files in the Web server and configured Transaction_Configuration service. And also i have JRE 1.4.2 installated on the client machine.

    Your help is really appreciated.

    Thanks

    Vijay

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.