Debug in smartforms and jobs


Debugging smartforms can be quite simple, you can just enter your smartform in SMARTFORMS transaction and go to "Environment"->"Function Module Name" . Get the FM name, as an example /1BCDWB/SF00012345 and access that by SE37.In SE37 you should look for your debugging code  in the Master Program:






You can also debug jobs, by accessing your selected job in SM37, after that you must select your job and execute =JDBG transaction. This command will automatically set the debugging mode active on the programmed job. but note that this will not get that you on the exact spot that you want, so you must press "F7" command until you get to the main program.


Comentários

Enviar um comentário

Mensagens populares deste blogue

Count on internal tables - in new abap 7.4

Imagem
  Requirement Getting count of rows agains a key combination in ABAP 7.4. Here is a simple example of code where you can get the count of a key combination on an internal table table in new abap 7.4, as the following syntax shows:   Here is quite more complex requirement in SD Module, where i prevent the deletion of invoiced outbound deliveries (with no partial credits), but for this I need to count both invoices and credit notes, as my following code shows:    
Ler mais

CLASS MAINTENANCE BY CLMM

Imagem
  This topic will be about class maintenance, for instance when you have an object or multiple objects assigned to a class, we can do the mass maintenance of that object or multiple objects by running the CLMM transaction: The first option “Copy values assigned to a object” allows you to copy all the characteristic values to another object or multiple objects: Just insert the values on the characteristics that you want to insert and then click on the "copy characteristics value" button and the values will be memorized, on the second tab you may put the destination objects : Right above you will get two options: test mass change or actual mass change: As you can see if you make these changes on test mode you will get the simulation of the values change, but if you press the other option obviously you will get the effective changes: Anyway I advise you to be careful when you try ovewrite values, just check carefully all the data before you execute the effetive change in order t...
Ler mais

CALL TRANSACTION MIGO

Imagem
  One useful tip for ABAP/MM consultants, when you make a "call transaction" statement that can be tricky when you do it for MIGO, because you as you may know  for MIGO we have several modes: A01 is for good receipts -> BES ID parameter A04 is for displaying material documents->MBN ID parameter So if you want to make that hotspot for the MIGO transaction in display mode in one of your reports, you can use the standard "MIGO DIALOG" MF with the following import parameters values: I_ACTION  =  'A04' I_REFDOC  =  'R02' Here is an example of my code for this purpose, and in this case I will always select the year of my document on the MSEG table because I don't want to have trouble if I'm accessing consecutive document from different years (MJA is the parameter for the year value):   ELSEIF  rs_selfield - sel_tab_field  =  'XXXX'          AND NOT  rs_selfield - value...
Ler mais