Remote function call raise a log on screen!

[Former Member]

I call function 'RSSM_EVENT_RAISE' included in an ABAP4 program in a job on R3 system to trigger an event on BW system. It is successfully run on our Development box, but on the Test box, the job gets cancelled and job log was titled as "ABAP/4 processor: CALL_FUNCTION_REMOTE_ERROR", if opening the job log, find the error just occrred at the call of this function 'RSSM_EVENT_RAISE'. When I debug this trigger program on the Test box, find when it calls this function, a log on box pops up promoting me to input a user name (with my user name as default) and password, maybe that's the reason why background job cancelled. If I debug this trigger program on Development box, there is no such log on box popping up and the background job runs successfully to trigger BW event from R3. Is there a way on Test box that the log on box can be got rid off so that the background job can be executed smoothly?

Thank you all!

Message was edited by: Kevin Smith

Message was edited by: Kevin Smith

[RichHeilman]

I think you will have to check the RFC config in SM59. Make the connection in your TST system look exactly like it is in your DEV system.

Regards,

Rich Heilman

[Former Member]

I compared the two systems, find in our Test box, under the Logon/Security tab, the user ALEREMOTE missing which exists in Development box. I can input the user ALEREMOTE, but i remember some of my coworker used to say that it's better to use user called "system", which one is better?

Thanks

[RichHeilman]

Not sure that it matters, but the users should have the same authority.

Regards,

Rich Heilman

[Former Member]

it hardly matters which user you are using.

only what matters is a remote connection can be establised.

so use any user which exist in Test box

regards

[Former Member]

Check for the user logon data provided in SM59 for the RFC destination. Try to logon to that system using remote logon. If it throws a logon sreen then reasons are -

User password on target system and that maintained in your RFC destination is different.

Or.

"Logon Screen" checkbox is checked in Logon Security section of SM59.

( Put in the correct password and it should work. )

Cheers.

[Former Member]

recreate RFC connection in SM59 in test box

thanks

surjit