‎2005 Sep 27 12:55 PM
‎2005 Sep 27 12:59 PM
Hi
Insert a break-point in the beginning of user-exit and run the program.
Max
Message was edited by: max bianchi
‎2005 Sep 27 12:59 PM
Hi
Insert a break-point in the beginning of user-exit and run the program.
Max
Message was edited by: max bianchi
‎2005 Sep 27 1:00 PM
place a break-point in the code in user exit.
run the transaction and depending on the event the user exit is in it will get triggered when you run that part of the transaction.
Regards
Raja
‎2005 Sep 27 1:01 PM
hi,
insert the break point in the user-exit include or use
break <username>
cheers,
sasi
‎2005 Sep 27 1:29 PM
Hi Thank you for your reply.
If it is in development sysytem its ok..
If it goes to testing system? Every time it will go to the debugging screen.
Will it create any problem in Testing system?
Regards,
TOM..
‎2005 Sep 27 1:39 PM
Hi Tom,
It is not good to put a hard coded break point in the user exit and transport to other systems. Instead you can have the soft break point. Check the 'Stop' button on the application toolbar.
It seems you are using the command 'break <username>'. For this the break point will be activated only for the username given.
Cheers
Vinod
‎2005 Sep 27 1:51 PM
Hi
Tom you haven't to set (write) a break point in the code of program, but:
goto se38 or se37 or se19 (depend on the type of user-exit), enter in program of your user-exit, place the cursor at the beginning of user-exit and push the ICON BREAK-POINT (red icon with STOP sign).
After run your program, it'll stop where you have setted the breakpoint.
Max
Message was edited by: max bianchi
‎2005 Sep 27 1:59 PM
hi,
we should remove the break statement before release the transport. very few cases only we use for break statement.
cheers,
sasi
‎2005 Sep 27 9:58 PM
You can check for your sy-sysid
if sy-sysid = 'TESTSYSTEM'.
break <username>
endif.
Biut I would use a soft-break in se38 also.
Matthias Kabel