You can use SAP GUI Property Collector to identify the UI elements in an SAP GUI transaction (a dynpro screen) and their properties that are to be extracted and passed to the side panel.
In NWBC for Desktop, start SAP GUI Property Collector by pressing CTRL and simultaneously choosing.
To use the tool with standalone SAP GUI, log on to your system using SAP Logon. Then start SAP GUI Property Collector from one of the following installation folders:
C:\Program Files (x86)\SAP\NWBC35\NwbcPropertyCollector.exe
Each SAP GUI main window is a session. Sessions with disabled scripting are shown in the dropdown menu with a comment.
You can use long IDs or short IDs . Short IDs are the last unique fragment of long IDs. If you do not select the Long ID checkbox, short IDs are added to the collection.
You have multiple G/L accounts that have identical short IDs but different long IDs. If you want to extract a specific G/L account, use long IDs since only long IDs are unique in this case.
You have two transactions AS23 (transaction does not exist) and AS03 (transaction does not exist), which are identical from a coding point of view. Long IDs for fields used in these transactions are:
Fixed asset: lid:/wnd/usr/subKOPF:SAPLAIST:0099/ctxtANLA-ANLN1.Text
Group asset: lid:/wnd/usr/subKOPF:SAPLAIST:0097/ctxtANLA-ANLN1.Text.
Technically, fixed asset and group asset are the same, therefore you can only use the short ID: sid:ctxtANLA-ANLN1.Text.
Short IDs are not unique since they might appear multiple times on the screen in different subscreens. In this case, the first short ID found wins.
Short IDs do not work for elements like titles, since they do not have technical names.
Short IDs work in the active window only. For example, when a dynpro dialog box is opened, the fields on the screen are found only when using long IDs. Long IDs contain Wnd and therefore also allow you to read field values below dialog boxes. This works only if the dialog box and the dynpro below are in the same program.
We recommend that you use short IDs; use long IDs only where necessary.
If you have multiple fields that are similar and that have identical short IDs on different subscreens, you should use long IDs. You should use short IDs if you have screens that are slightly different depending on the transaction context. It is possible that long IDs are slightly different for the same field and this is not obvious at first glance. In this case, you have to use the short ID because the tag is a key field in the tag table and you cannot have two entries with the same tag name that differ only in the property (short/long ID).
The data context stays available as long as the current transaction is running in NWBC.
The data context stays available as long as you do not leave the main screen.
The colors in the Value column have the following meaning:
The fields are alive in the data context but not on the current screen.
The black properties are not alive in the data context.
The green properties are all currently read from the screen or they are constants (value: prefix in ID). They are alive in the data context.