Documents

abapdebuggingfrombasictoadvance-140214043218-phpapp01

Description
Starting abap debugging 1. Putting /H in command box and hitting execute button 2. Setting breakpoint in program. Diference among F5 , F6 ,F7 and F8 F5: debug in single step (line b line! F : Skips Subroutines/F# $hene%er a control encounters a subroutine or F# debug them unlike F5 F&: controls return to main program 'rom Subroutines ( F# F): executes program until next break point. Breakpoint Types 1. Debugger breakpoint: $hen ou set a breakpoint in the *ebugger+ it is created as a d
Categories
Published
of 10
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  Starting abap debugging 1. Putting /H in command box and hitting execute button 2. Setting breakpoint in program. Diference among F5 , F6 ,F7 and F8 F5: debug in single step (line b line!F : Skips Subroutines/F# $hene%er a control encounters a subroutine or F# debug them unlike F5F&: controls return to main program 'rom Subroutines  F#F): executes program until next break point. Breakpoint Types   1. Debugger breakpoint :$hen ou set a breakpoint in the *ebugger+ it is created as a debugger breakpoint  b de'ault. , debugger breakpoint is onl %alid -hile the *ebugger instance+ in -hich it -as set+ is acti%e. $hen the *ebugger is closed+ all debugger breakpoints set in it are deleted. 2. Session breakpoint: ' ou set a breakpoint in the ,,P 0ditor+ 'or example+ this breakpoint is a session breakpoint . Session breakpoints remain acti%e independentl o' the existence o' a *ebugger and are %alid 'or all external sessions o' a logon. $ithin the *ebugger+ ou can con%ert a debugger breakpoint into a session breakpoint and %ice %ersa.' the setting Session Breakpoints Active Immediately   is checked (%ia Utilities   →  Settings   →    ABAP    Editor    →  Debugging   in the ,,P 0ditor or bect 3a%igator!+ ou can set a session breakpoint in an external session o' a logon to 'orce a running program into the *ebugger that runs in the same logon ('or example+ in an external session! and -ill process the point at -hich the session breakpoint -as set. 4.  User breakpoints:User breakpoints (pre%iousl kno-n as external breakpoints! are %alid 'or all user logons on the current ser%er o' the current sstem. ser breakpoints are speci'icall re6uired -hen debugging SP or $eb *npro applications. n these cases+ ou do not log on using the S,P 7 but %ia a bro-ser+ 'or example.8here'ore+ an breakpoints must be set be'ore logging on.ser breakpoints are onl %alid 'or a period o' 2 hours. ,s o' 9elease &.+ user breakpoints set 'or SP or $eb *npro applications are also %alid 'or S,P 7 logons.  $ithin the *ebugger+ ou can con%ert debugger or session breakpoints into user breakpoints and %ice %ersa. $e can create maximum 4 breakpoints onl. System Debugging ' ou set this option+ the *ebugger is also acti%ated 'or sstem programs (programs -ith status S  in their program attributes!. $hen ou sa%e breakpoints+ the System Debugging   setting is also sa%ed. Update Debugging pdate 'unction modules do not run in the same user session as the program that is currentl running in the ,,P *ebugger. 8hese 'unction modules are there'ore not included in debugging. nl i' ou select the Update Debugging   option ou can displa and debug them a'ter the ;##8 $9<.   Remote abap debugging1. pen the Function module/ Prox class and set an external break=point. 0xecute the transaction code>S9*07? (3ote: this tcode is a%ailable onl in 0;; . sstem on-ards! ;lick on the button ,cti%ate *ebugging. , pop=up screen -ill be opened. Fill the ser=* -ith -hich break=point has been set. (8he same user=id should be used as authentication data in the @ -hile creating 9F; communication channel!. Select the radio buttons >all ,ppl. Ser%ers? and >0xternal breakpoints alread set?. ;lick on <.     ,nother pop=up -ill be opened -ith a message >0nd debuggingA? Bea%e the pop=up as it is. (*onCt close the transaction!. When you run transaction in source system debugger will start in target system where SRDEBUG transaction is set
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks