Process of Table checking in SAP

This HOWTO will give the steps you need to find where the data is stored in SAP when you want to create an ABAP query or ABAP report using fields that you can find on transaction screens.

[edit]

Steps

1.    The first step is always to find out the table and field name of the screen field. With the cursor in the field you want, press F1 or click on the "?".

2.    The initial help screen will give you descriptions and information about the field.

3.    From there press F9 or click on [Technical info].

4.    Here you can get names of the table, field and the data element.

5.    If you are lucky the system gives you a transparent table name. If you're not lucky you'll get a structure name.

6.    Doubleclick on the data element and search via the where used of the dictionary.

7.     Failing above you can set up the TCODE or a portion of it just before screen where the field exists and then switch on SQL Trace, run the screen, turn off SQL trace and then list the Trace Log following which tables/views were hit. Obviously it is best to turn on and off the trace in the smallest time-window possible to lessen the number of Trace Log entries you have to look through.

8.     Another thing to try is : run program RSSDOCTB. This gives you a list with info about the table such as fields, check tables ....

9.     Or try Transaction SE84 (Repository Info System)- Select in the tree ABAP Dictionary -> Fields -> Table Fields - Insert in the Select-Option "Field name" the name of the files (E.g. CARRID and CONNID) and execute it - now you will get a list of all tables which have one or both of this fields - it's easy to identify the tables which contain both fields in the list.

10.   Or start an sql trace and look at the tables that are read

11.   Last resort, find the program name (click on the triangle icon at botton right to expand information and click on the icon right of client number) and look the ABAP code with TCODE SE38

Which is usefull to check the Run time error in sap

  Tcode for Run Time Error : se30

12.   Run SE30 against your transaction. When you've done what you needed to do and returned, Hit analyze. Click the hits list. You get all of the modules, tables, forms, FMs,... that were called. Look for interesting names. (EG. Read_structure_name [BEARBEITEN means "Work on", ERMITTELN means "determine", PRUEFEN means "examine or check", AUFBAUEN means "CONSTRUCT", LESEN means "Vintages" but (aren't we germans sneaky, just kidding) GELESEN means "read" so we'll use LESEN instead of GELESEN... and http://babelfish.altavista.com/ does a passable job of translating])