This space is for those bits of information that can save you a lot of time and

trouble and usually are hard to find in the documentation.

1.

Problems with username/passwords while setting JCO's?... try with the

password in UPPERCASE.

2.

Going home in a hurry?, use transaction /nex to close all your sessions
at the same time in specific application server you are logged-in.

3.

In an R/3 screen, use %pc to download any TCode full page in any
format you want.(.htm, .txt etc). Also use TCode /nSO21 to specify the
default download location (this is very useful as saving all files to the
sapworkdir can be little annoying at times)

4.

Show Work Process usage over time by running SM50 -> List -> CPU.
This shows CPU usage in minutes since startup. If all of your DIA WP's show
time, then consider adding more.

5.

If you want to select text on your SAP screen and if you are not able to
do it. use Ctrl+Y and then you can select text.

6.

To acces history of Tcodes used, click on the Tcode command field and
use UP and DOWN arrow keys.

7.

To display the checked object when not authorized call transaction

SU53. It reports the last objects verified and also the respective values.
Incase missing authorization through pop-up then close it (click cross
mark) instead of continue it. Then run SU53 immediately either in same
session (/nSU53) or in new session (/oSU53).

8.

Use ctrl+? to go to the tcode command field on SAP screen.

9.

Enter /i on tcode field to delete the current session.

10.

Enter /nend to cancel all SAP sessions and log off.

11.
Use ALT+F+W and ALT+F+U in SAP Easy Access Screen to download
and upload the user favourites within/across systems.
12.
Check the child page added to this page for a handy way to open sap
notes from SAP OSS Portal.
13.
To send a SAP messge to an other person use Function Module
TH_POPUP from transactino SE37.

14.

Ctrl & + to open new SAP session

15.

ctrl+shift+F8 System Administration information.

16.

ctrl+shift+F8 Manul entery of Transation Code.

17.

ctrl+shift+F5 Create folder in Favorite list.

18.

ctrl+shift+F7 Add additional object

19.

ctrl+shift+F12 Direct go to Role maintenance

20.
Change application server in SM51 by double clicking on application
server you want to get in.
21.
Note 757964 - Additional information in the SAP GUI window title a
must, if you have several systems open at the same time
22.
Note 205487 - Own text on SAPGui logon screen very usefull for
messages like "(at)1D(at) Do not login, ..." or "Last clientcopy was on ..."
Substitute (at) with "at"-char
23.
ALT + F12
layout

Calls the menu pop up for Customizing of local

24.
CTRL + Shift + P Makes a Hard copy which shows no menu pop up
and can also contain status texts and modal pop ups
25.

CTRL + /

Cursor jumps directly to the OK-Code field

26.

CTRL + I

Cursor jumps to the first focusable field or control

27.

CTRL + ;

Creates Sap shortcut

28.
To change transport job class to "A": Run report RDDNEWPP from
transaction SE38 in the client 000.
29.

multiple logons on AS ABAP system are stored in table: USR41_MLD

This Wiki article explains Backing and Restoring SAP Logon entries and
History from one system to another system during workstation migration.
This trick is currently tested for
clients running Windows Operating System.

This trick can be used for replicate the data on the WTS system from client
running Windows Operating System.
SAP Logon entries refers to the SAP System added in SAP Logon Pad and
History refers to Dropdown Values which are shown during a User-Input in
SAP GUI.
Warning: All the SAP Logon entries and History will be deleted and will be
replaced with the corresponding data from the source system.
It is highly recommended to take backup of any file which is getting replaced
or overwritten.
1. Backing SAP Logon Pad entries and History from Source System
Follow the steps mentioned below in the Source System for Backing process:
Step 1.1: Close the SAP Logon Pad from the System Tray:
Exit all the SAP system(s) opened on the system and right-click on the
SAPLogon Icon.Click Close SAP Logon that will end the SAP Logon Process
(saplogon.exe).
Make Sure SAP Logon Process (saplogon.exe) is not running: Open Windows
Task Manager by right-clicking the taskbar, and then clicking Start Task
Manager. You can also open Task Manager by pressing Ctrl+Shift+Esc. In the
Processes tab, make sure that SAP Logon Process (saplogon.exe) is not
running.
Step 1.2: Know the Location of SAP Logon Pad entries and History
Open the SAP GUI Configuration by launching sapfewcp.exe which is located
in the folder %ProgramFiles%\..\Program Files (x86)\SAP\FrontEnd\SAPgui\.

Location of History file

In the Folder Node Local Data go to History Node and note the Path for
Directory of Input History as shown below:

Location of SAP Logon entries files

In the Folder Node SAP Logon Options go to Local Configuration Files Node
and Note the Path of Local Configuration Files as shown below:

Step 1.3: Copying Files from Source System

From the Location of History file noted in Step 1.2, copy the .mdb file
into your custom backup folder.

From the Location of SAP Logon entries files noted in Step 1.2, copy all
the files into your custom backup folder.
2. Restoring SAP Logon Pad entries and History in Target System
Follow the steps mentioned below in the Target System for Restoring process:
Step 2.1: Close the SAP Logon Pad from the System Tray:
Perform Steps 1.1 in the Target System.
Step 2.2: Know the Location of SAP Logon Pad entries and History
Perform Steps 1.2 in the Target System.
Step 2.3 Copying Files in Target System

In the Location of History file noted in Step 2.2, copy the .mdb file from
your custom backup folder which was retrieved in Step 1.3. Backup and
delete any existing file before copying.

In the Location of SAP Logon entries files noted in Step 2.2, copy all the
files from your custom backup folder which was retrieved in Step 1.3.
Backup and delete any existing file before copying.