|Sample code, images||Restrictions, R/3 Release, Sapgui version, GuiXT version|
|4 Displaying additional information You need to display in an R/3 screen additional information that is not contained in the standard R/3 transaction. It would not be a problem for you to read this information directly from the database, using a Call Statement in your GuiXT Script and a 1-line select statement in ABAP. But you don’t know the name of the table in which the information is stored.
Solution You probably know a standard transaction in R/3 where you can display the field. Put the cursor on the field; press F1 and then select “Technical information”. In most cases R/3 now shows the right database table name and the field name you are looking for.. Use transaction SE17 (General table display) to verify that you have found the right table. In some cases R/3 will give you only an intermediate program table, but not the database table name that you need for your select Statement. Now you have a little bit more work. Go to transaction ST05 and activate the SQL trace with the button “Trace on for user”. Perform the R/3 transaction again until you see your field. Display the SQL trace (transaction ST05) and try to find the right table. Since all key data are shown in the trace, you have a good chance to find the table name. Verify that it is the right one using SE17. In addition, we suggest that you make sure that the Select statement in your function call does not lead to a full table scan, which can be pretty fast in your test system and pretty slow in production. Use the tools of the ABAP workbench: SE11 to show the secondary indices of the table, ST05 to explain an SQL request.
|Last update: August 18, 2001||InputAssistant needed for Call statement|