Calling Remote function tool leads always to a logon screen

[Former Member]

Hello,

I run an remote function tool in system A. In System B I run a report calling this function module.

Each time, I execute the report, a remote logon screen appears. It looks the same like the one you logon the system. You have to specifiy client, user and password.

I know one possibilty to avoid this logon screen appeaering.

System B (holding the function module) must declare System A as a trusted system. Thus, the user does not need to logon system B, each time calling the func. module. I processed this in correspondence with the help data, but the screen still appears.

Is there any other possibilty to avoid appearing the logon screen or does anybody know wheter I did something wring??

thanks, holger

[Former Member]

Hello,

I run an remote function tool in system A. In System B I run a report calling this function module.

Each time, I execute the report, a remote logon screen appears. It looks the same like the one you logon the system. You have to specifiy client, user and password.

I know one possibilty to avoid this logon screen appeaering.

System B (holding the function module) must declare System A as a trusted system. Thus, the user does not need to logon system B, each time calling the func. module. I processed this in correspondence with the help data, but the screen still appears.

Is there any other possibilty to avoid appearing the logon screen or does anybody know wheter I did something wring??

thanks, holger

[Former Member]

Hi Holger,

Check in the interface parameters of the RFC, if fields for the login details can also be passed along with the data.

Regards,

Ravi

[Former Member]

soory but where can i adjust these settings in the function builder?

thanks,

holger

[Former Member]

Hi Holger,

1. This has to do with tcode SM59 (Maintain RFC Connections)

[

THE CALLING SYSTEM HAS NOT DEFINED

USER ID / PASSWORD TO LOGON TO THE TARGET SYSTEM.

HENCE, IT SHOWS BLANK LOGIN SCREEN

]

2. Under the node RFC Destinations ---> R/3 Connections,

various systems are defined for RFC Purpose.

3. Lets say ur system(which u want to connect) is PRD.

4. Double Click PRD and go the the details.

5. There are 3 Tabs. Goto LOGON/SECURITY TAB.

6. In the logon information , enter the

USERID and password and client.

7. Save.

Then try your program.

Hope this helps.

Regards,

Amit Mittal.

[Former Member]

thanks, but the function module should be called in many systems from more than a hundred users.

If a user is logged on system A and calls the function module in system B remotely he should not need to type in his username and password for system B. System A is defined as A trusted system for system B. So user check will not be done.

[athavanraja]

in such a case you have to go for setting trust relations.

for more info on this check the following link.

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/frameset.htm">Trusted System: Trust Relationships Between SAP Systems</a>

Regards

Raja

[Former Member]

Hi again,

1. What i understand is this :

In System B, thru sm59

System A has been defined as a TRUSTED SYSTEM.

2. One possibility might be :

In the same tcode SM59,

same tab Logon/Security

There is on checkbox for LOGON SCREEN. (Right to the radio buttons of trusted system N Y )

If that checkbox is ticked, then also

such thing can happen.

If it is checked, just remove the check

and try once more.

Hope this helps.

Regards,

Amit M

[Former Member]

What we do is:

Create a user (say RFCUSER) in system A (the called system) and give it only the authorizations needed to run the FM there.

In system B, in SM59, create a new destination (say DESTA). Enter the userid and password.

When calling the FM from system B, use the new destination.

Looking back at the other responses to this thread, I think this is what Ravi is saying.

Rob

Message was edited by: Rob Burbank

[Former Member]

thanks,

but I can only specify a destination in the system where I run the report, calling the func mod.

Do you mean, I can also define a destination for the func. mod. in system B.

I did not find anywhere a possibility to define a destination for the function module in system B!?

[Former Member]

Whatever system the calling program resides in has the definition of the destination of the system in which the remote enabled FM will run. The calling program specifies that destination in the call to the FM.

Rob

[Former Member]

yes.

you use CALL FUNCTION 'func' DESTINATION 'dest' in system A to execute the function module 'func' in system B. The destination is defined by: hostname_systemname_systemmumber.

That's all.

In System B, you just define the system A as a trusted system.

That's all.

I do not understand your second answer. I am a little bit confused. Can you please suggest me.

Thanks a lot, Holger

[Former Member]

I don't know if you have to define system A as trusted in System B. I was just trying to say that in system A, using SM59, you can pass the userid and password when you define the destination for system B. That should keep the password screen from appearing.

Rob

[Former Member]

Hi Holger - did any of this help? If you're finished, please close the post. If not, do you have any more questions?

Rob