2015 Mar 31 9:42 AM
Hello everyone,
is there a way in the ABAP layer (PAI) to start a logon screen of another SAP system without using RFC?
And returning to the PAI after doing some work and logging out from the remote system.
Thank you in advance,
Marcus
2015 Mar 31 9:48 AM
Hi Marcus
Do you want a user to have visibility into the other SAP System, or just a process to perform a function on that other system?
Regards
Arden
2015 Mar 31 10:02 AM
2015 Mar 31 9:52 AM
Hi Marcus,
you can send a POPUP screen or dialogue screen (CALL SCREEN ... ) with a text like
"Please logon to system xxx and continue with Ok button after that"
and the user uses SAPLOGON screen to connect to the other SAP system and does his work. After finishing and leaving the other system he can press the OK button to proceed.
Regards,
Klaus
2015 Mar 31 10:11 AM
Thank you for your answer, Klaus. This is the way it can look like, but what's under the hood, connecting a value "system xxx" (e.g. RFC-Destination) and invoking the SAPLOGON of the destination?
2015 Mar 31 10:34 AM
Hi Marcus,
for SAPLOGIN.INI may be different in user customizing for each frontend server, this may be difficult.
Regards,
Klaus
2015 Mar 31 10:25 AM
Is there any relation of data between two systems or you just want to switch from current system to work on other system and come back to current system?
you can think to call sapgui.exe from pai of current system...
or
you need to bypass sapgui and direct call shortcut to call login screen.
or may be some other... I am just applying fuzzy logic , not worked on such kind of stuff.
one place where I saw this thing while comparing program using se39 , you can login other system from current system to compare programs.
there must be some FM or logic behind this (its based on RFC).
-Avirat
2015 Mar 31 10:36 AM
Yes Avirat, it is about switching from current system to work on other system and come back to current system.
And its about calling the login screen directly.
It basically shall look like a visible RFC-call, but there's no RFC, just login.
A workaround seemed to call a dummy remote function module with statement CALL TRANSACTION 'SESSION_MANAGER' (which is SAP's main screen), but that dumped to ST22 after the Logon. I guess, it was LUW issues.
Regards,
Marcus
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |