How to Debug code written in Include RMCSUZ10?

In our Sales extractor 2LIS_11_VAITM we need to get information from custom Partner Functions whichwere added by the R/3 team.
To do this we have used the SAP provided include:RMCSUZ10
I have changed the Structure: MCPARTNER to include new fields PKUYZ, PKUYX, PNA1YZ.
The Code in the include is as follows:
WHEN 'YZ' .
    MOVE UPE_VBPA-ADRNR TO UPE_PARTNER-PKUYZ.
    MOVE UPE_VBPA-NAME1 TO UPE_PARTNER-PNA1YZ.
    WHEN 'YX' .
    MOVE UPE_VBPA-ADRNR TO UPE_PARTNER-PKUYX.
    MOVE UPE_VBPA-NAME1 TO UPE_PARTNER-PNA1YZ.
These additional fields are available in the LO Pool now and I have pulled them into the extractor.
Strangely though, this code only works in the Delta extraction mode. If we do a setup in R3 and pull the data, the fields remain blank. Does anyone have a similar experience with using this exit?
Also I am able to debug this code only while doing setup in R3.
Is there any other way to debug this code and how can we make it work in Full mode too?
Thanks in advance.
AG

Hi AG.
Regarding the debugging, you could do it the hard and dirty way and write an endless loop at the beginning of your logic and then enter debug mode from the process monitor (in development only of course and remember to delete it again!).
Regards
Jacob
Edited by: Jacob Jansen on Dec 29, 2011 10:26 PM

Similar Messages

Debugging code written in assembly with Xcode

I have a program written in C calling a function written in assembly. When I run the debugger, I can step through the C code just fine, but then when it reaches the function, it won't step through the assembly code. It'll just go on to the next statement. In the assembly viewer I see:
call 0x1eda <isgreater>
and then the rest of the main function after that. How do I view the function isgreater and step through it?
My professor uses the Eclipse IDE and it can do it just fine. I'd rather use the Xcode IDE as Eclipse is very buggy.
Thanks!
Kyle.

Hi Kyle,
not sure if you've solved this already, but if you set this:
Run > Debugger Display > Disassembly Only
then it works... it doesn't work if you have 'Source and Disassembly' set for some strange reason.
-chris

How to execute code written in java before javascript?

Hello,
is there any way to call the action or actionlistener method of a commandbutton (for instance, or any other component), before javascript is executed? (jsf 1.2_09, glassfish v2.1)
Eg: I want to open a new window with javascript for the details/editing of a row in a data table. To do so I use a request scoped backing bean for the new window, and in its constructor I pass the rowdata through the session map where I put the object beforehand using an actionlistener/action.
But this won't work, because the script happens before I can put the variable in the session map...
Is there an other way?
thanks
david

only thing I can come up with is to submit the data using Ajax. So do an Ajax call (for example using JQuery) to submit an asynchronous request to some servlet that will put the data in the session bean, then when the Ajax call finishes open the window.

How to debug ABAP code

Hi Gurus,
Can anyone please tell me how to debug code written in EXIT for extractions.
If possible please provide me a step by step approach.
Thanks
Regards,
aarthi
[email protected]

Hi Dinesh,
Thanks for your prompt reply.
That is where, I am facing the problem. I know how to set break point. But, how to check the required field value, which key to press to reach the break point directly, etc. I need to know these kind of this.
Can you please provide details about those things.
Thanks
Regards,
aarthi
[email protected]

Internal error - how to debug and fix

Hi Gurus
I am trying to enter data for a business partner using transaction BP. I am able to create the BP (person) however when I attempt to enter communication information, such as telephone number, I receive the following error message:
Internal error - access to IT_ADR2_L
Can anyone tell me how to debug this? Please include individual steps, as I am not a developer.
Any help greatly appreciated.
Thanks
Harrrry

Dear Harry
I think there are any permission issue better to talk basis team, because i has work in my side.

Examples of code ritten in includes in user exits

Can anyone send some examples on code written in includes of user exits.
                                   Thanks in advance

               U S E R   E X I T   F O R   P A 0 0 0 8               *
IF innnn-infty = '0008' AND
( ipsyst-ioper = 'INS' OR
   ipsyst-ioper = 'COP' ).
             G L O B A L   D E C L A R A T I O N S                   *
DATA:
      g_lga         TYPE lgart,      " Wagetype
      g_count(2)    TYPE n,
      g_cnt_blank(2) TYPE n,          " Record position for hrly WT
      g_cnt_hrly(2) TYPE n,          " Record position for hrly WT
      g_cnt_inc(2) TYPE n,          " Record position for inc WT
      g_cnt_lng(2) TYPE n,          " Record position for lng WT
      g_cnt_ret(2) TYPE n,          " Record position for ret WT
      g_wtype(11)   TYPE c,          " Wage type
      g_wrate(11)   TYPE c,          " Wage rate
      g_ht510_rate TYPE betrg,      " Default rate for WT0011 from T510
      g_maxrate_inc TYPE betrg,      " Maximum Incumbency Rate
      g_maxrate_lng TYPE betrg,      " Maximum Longevity Rate
      g_maxrate_ret TYPE betrg.      " Maximum Retention Rate
                  D A T A   D E C L A R A T I O N                    *
DATA:
      it_9006       TYPE TABLE OF pa9006,
      st_9006       TYPE pa9006,
      i0008         TYPE p0008,
      st_grdcode    TYPE zthhr_grdcode.
                  F I E L D    S Y M B O L S                         *
FIELD-SYMBOLS: <fs_wtype> TYPE ANY, " Used for Wage Type
                 <fs_wrate> TYPE ANY. " Used for Amount
                  C O N S T A N T S                                  *
CONSTANTS:
    c_molga_10   type molga value '10',    " Country grp for US
    c_hlgar_0011 TYPE lgart VALUE '0011', " Hourly Wage Type
    c_ilgar_0012 TYPE lgart VALUE '0012', " Incumbent Wage Type
    c_llgar_0147 TYPE lgart VALUE '0147', " Longevity Wage Type
    c_rlgar_01e0 TYPE lgart VALUE '01E0', " Retention Wage Type
    c_subty_inc TYPE subty VALUE '1',     " Subtype for Incumbency
    c_subty_lng TYPE subty VALUE '4',     " Subtype for Longevity
    c_subty_ret TYPE subty VALUE '5'.     " Subtype for Retention
                  P R O C E S S I N G                                *
Typecast PRELP to PNNNN structure
CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
    EXPORTING
      prelp = innnn
    IMPORTING
      pnnnn = i0008.
Refresh & Clear Process variables.
CLEAR: g_lga, g_count, g_cnt_blank, g_cnt_hrly, g_cnt_inc,
          g_cnt_lng, g_cnt_ret, g_wtype, g_wrate, g_maxrate_inc,
          g_maxrate_lng, g_maxrate_ret.
Populate all unexpired & applicable records of IT9006 of subtype:
Incumbency, Longevity and Retention
REFRESH: it_9006.
SELECT * FROM pa9006 INTO TABLE it_9006
          WHERE pernr EQ i0008-pernr
            AND begda LE i0008-begda
            AND endda GE i0008-begda
            AND ( subty EQ c_subty_inc
            OR    subty EQ c_subty_lng
            OR    subty EQ c_subty_ret )
            AND zapplflg EQ 'X'.
Sort IT9006 Table descending based on Amount
SORT it_9006 BY zwage zaddamt DESCENDING.
Check for validity of Pay Scale Group & Level
SELECT * FROM zthhr_grdcode UP TO 1 ROWS
                  INTO st_grdcode
                 WHERE trfgr = i0008-trfgr
                   AND trfst = i0008-trfst.
ENDSELECT.
IF sy-subrc EQ 0.
If valid, read the Maximum Incumbency Rate
    READ TABLE it_9006 INTO st_9006
                       WITH KEY zwage = c_ilgar_0012
                                zgrdcode = st_grdcode-grdcode
                       TRANSPORTING zaddamt.
    IF sy-subrc EQ 0.
      g_maxrate_inc = st_9006-zaddamt.
    ENDIF.
ENDIF.
Get Max Longevity rate
READ TABLE it_9006 INTO st_9006 WITH KEY zwage = c_llgar_0147
                     TRANSPORTING zaddamt. " to g_maxrate_inc.
IF sy-subrc EQ 0.
    g_maxrate_lng = st_9006-zaddamt.
ENDIF.
Get Max Retention rate
READ TABLE it_9006 INTO st_9006 WITH KEY zwage = c_rlgar_01e0
                     TRANSPORTING zaddamt. " to g_maxrate_inc.
IF sy-subrc EQ 0.
    g_maxrate_ret = st_9006-zaddamt.
ENDIF.
CLEAR : g_count, g_cnt_blank, g_cnt_hrly, g_cnt_inc,
          g_cnt_lng, g_cnt_ret.
Check Infotype 0008 Wagetype entries
DO 40 TIMES
      VARYING g_lga FROM i0008-lga01 NEXT i0008-lga02.
    g_count = g_count + 1.
    IF NOT g_lga IS INITIAL.      " Fill max no of field filled
      g_cnt_blank = g_count.
    ENDIF.
    IF g_lga = c_hlgar_0011.      " Get Rec Pos for Hrly WT
      g_cnt_hrly = g_count.
    ELSEIF g_lga = c_ilgar_0012. " Get Rec Pos for Inc WT
      g_cnt_inc = g_count.
    ELSEIF g_lga = c_llgar_0147. " Get Rec Pos for Lng WT
      g_cnt_lng = g_count.
    ELSEIF g_lga = c_rlgar_01e0. " Get Rec Pos for Ret WT
      g_cnt_ret = g_count.
    ENDIF.
ENDDO.
g_cnt_blank = g_cnt_blank + 1. " Next Avl. Pos for WT entry
Incumbency Processing
0011 and 0012 both not found
IF g_cnt_hrly = 0 AND g_cnt_inc = 0.
Do Nothing
0011 Not found but 0012 found
ELSEIF g_cnt_hrly = 0 AND g_cnt_inc > 0.
    CONCATENATE 'I0008-LGA' g_cnt_inc INTO g_wtype.
    CONCATENATE 'I0008-BET' g_cnt_inc INTO g_wrate.
    ASSIGN (g_wtype) TO <fs_wtype>.
    ASSIGN (g_wrate) TO <fs_wrate>.
    IF g_maxrate_inc <> 0.
      <fs_wtype> = c_ilgar_0012.
      <fs_wrate> = g_maxrate_inc.
    ELSE.
    If WT0012 has expired in IT9006, revert to WT0011 with
      default rate from T510
      <fs_wtype> = c_hlgar_0011.
      SELECT betrg FROM t510 UP TO 1 ROWS
                   INTO g_ht510_rate
                  WHERE molga = c_molga_10
                    AND trfar = i0008-trfar
                    AND trfgb = i0008-trfgb
                    AND trfgr = i0008-trfgr
                    AND trfst = i0008-trfst
                    AND lgart = c_hlgar_0011
                    AND begda LE i0008-begda
                    AND endda GE i0008-endda.
      ENDSELECT.
      IF sy-subrc = 0.
        <fs_wrate> = g_ht510_rate.
      ENDIF.
    ENDIF.
0011 found but 0012 Not found
ELSEIF g_cnt_hrly > 0 AND g_cnt_inc = 0.
    IF g_maxrate_inc <> 0.
    Update 9006 amount if greater. And Replace 0011 with 0012
      CONCATENATE 'I0008-LGA' g_cnt_hrly INTO g_wtype.
      CONCATENATE 'I0008-BET' g_cnt_hrly INTO g_wrate.
      ASSIGN (g_wtype) TO <fs_wtype>.
      ASSIGN (g_wrate) TO <fs_wrate>.
      IF <fs_wrate> < g_maxrate_inc.
        <fs_wtype> = c_ilgar_0012.
        <fs_wrate> = g_maxrate_inc.
      ELSE.
      Do Nothing
      ENDIF.
    ELSE.
    Do Nothing
    ENDIF.
0011 and 0012 both found
ELSEIF g_cnt_hrly > 0 AND g_cnt_inc > 0.
Rate in IT9006 exists.
    IF g_maxrate_inc <> 0.
    Remove existing 0011
      CONCATENATE 'I0008-LGA' g_cnt_hrly INTO g_wtype.
      CONCATENATE 'I0008-BET' g_cnt_hrly INTO g_wrate.
      ASSIGN (g_wtype) TO <fs_wtype>.
      ASSIGN (g_wrate) TO <fs_wrate>.
    If hourly rate < Max Inc Rate, Clear Hrly WT & update WT0012
      IF <fs_wrate> LT g_maxrate_inc.
        CLEAR : <fs_wtype>, <fs_wrate>.
      Update existing 0012 with new amount
        CONCATENATE 'I0008-LGA' g_cnt_inc INTO g_wtype.
        CONCATENATE 'I0008-BET' g_cnt_inc INTO g_wrate.
        ASSIGN (g_wtype) TO <fs_wtype>.
        ASSIGN (g_wrate) TO <fs_wrate>.
        <fs_wtype> = c_ilgar_0012.
        <fs_wrate> = g_maxrate_inc.
    If hourly rate > Max Inc Rate, clear WT0012
      ELSE.
        CONCATENATE 'I0008-LGA' g_cnt_inc INTO g_wtype.
        CONCATENATE 'I0008-BET' g_cnt_inc INTO g_wrate.
        ASSIGN (g_wtype) TO <fs_wtype>.
        ASSIGN (g_wrate) TO <fs_wrate>.
        CLEAR : <fs_wtype>, <fs_wrate>.
      ENDIF.
Rate in IT9006 do not exists.
    ELSE.
    Let 0011 be there but remove 0012.
      CONCATENATE 'I0008-LGA' g_cnt_inc INTO g_wtype.
      CONCATENATE 'I0008-BET' g_cnt_inc INTO g_wrate.
      ASSIGN (g_wtype) TO <fs_wtype>.
      ASSIGN (g_wrate) TO <fs_wrate>.
      CLEAR : <fs_wtype>, <fs_wrate>.
    ENDIF.
ENDIF.
Longevity Processing
Wage type 0147 already exists
IF g_cnt_lng > 0.
    CONCATENATE 'I0008-LGA' g_cnt_lng INTO g_wtype.
    CONCATENATE 'I0008-BET' g_cnt_lng INTO g_wrate.
    ASSIGN (g_wtype) TO <fs_wtype>.
    ASSIGN (g_wrate) TO <fs_wrate>.
IT9006 contains the rate.
    IF g_maxrate_lng > 0.
    Update the existing amount
      <fs_wtype> = c_llgar_0147.
      <fs_wrate> = g_maxrate_lng.
    ELSE.
    Remove Wage Type 0147
      CLEAR <fs_wtype>.
      CLEAR <fs_wrate>.
    ENDIF.
Currently no 0147 exists
ELSE.
IT9006 contains the rate.
    IF g_maxrate_lng > 0.
    Add 0147 with amount
      CONCATENATE 'I0008-LGA' g_cnt_blank INTO g_wtype.
      CONCATENATE 'I0008-BET' g_cnt_blank INTO g_wrate.
      ASSIGN (g_wtype) TO <fs_wtype>.
      ASSIGN (g_wrate) TO <fs_wrate>.
      <fs_wtype> = c_llgar_0147.
      <fs_wrate> = g_maxrate_lng.
      g_cnt_blank = g_cnt_blank + 1.
IT9006 does not contain the rate.
    ELSE.
    Do Nothing
    ENDIF.
ENDIF.
Retention Processing
Wage type 01E0 already exists
IF g_cnt_ret > 0.
    CONCATENATE 'I0008-LGA' g_cnt_ret INTO g_wtype.
    CONCATENATE 'I0008-BET' g_cnt_ret INTO g_wrate.
    ASSIGN (g_wtype) TO <fs_wtype>.
    ASSIGN (g_wrate) TO <fs_wrate>.
IT9006 contains the rate.
    IF g_maxrate_ret > 0.
    Update the existing amount
      <fs_wtype> = c_rlgar_01e0.
      <fs_wrate> = g_maxrate_ret.
    ELSE.
    Remove Wage Type 01E0
      CLEAR <fs_wtype>.
      CLEAR <fs_wrate>.
    ENDIF.
Currently no 01E0 exists
ELSE.
IT9006 contains the rate.
    IF g_maxrate_ret > 0.
    Add 01E0 with amount
      CONCATENATE 'I0008-LGA' g_cnt_blank INTO g_wtype.
      CONCATENATE 'I0008-BET' g_cnt_blank INTO g_wrate.
      ASSIGN (g_wtype) TO <fs_wtype>.
      ASSIGN (g_wrate) TO <fs_wrate>.
      <fs_wtype> = c_rlgar_01e0.
      <fs_wrate> = g_maxrate_ret.
      g_cnt_blank = g_cnt_blank + 1.
IT9006 does not contain the rate.
    ELSE.
    Do Nothing
    ENDIF.
ENDIF.
Typecast the PNNNN to PRELP structure
CALL METHOD cl_hr_pnnnn_type_cast=>pnnnn_to_prelp
    EXPORTING
      pnnnn = i0008
    IMPORTING
      prelp = innnn.
Show Data Again Switch to display the field values again
show_data_again = 'X'.
ENDIF.

LSMW VD51 , Validations in Begin of Transaction; how to Debug the code?

Hi All,
I have written code for validations i Begin of Transaction in the field mapping 5th step of LSMW for VD51.
Now this code not getting triggered at the time of Conversion of Data. How to debug the code. I have put a static break point 'BREAK-POINT' still not getting triggered.
Any suggestion / solution for this issue.
Thanks and Regards,
Narsimha Kulkarni

Hi Narshimha,
Make any mapping error during mapping and check the syntax of mapping it will drag you to the lsmw report there you can put your break point. You can check the report name from transaction code as well.
Remember this mapping block will execute when you execute the step Convert Data in LSMW.
Regards
Dhirendra

How to Debug a ABAP code running the background in Portal

How can I debug a ABAP code running in the background while executing a transaction code through portal.
e.g Presently I have to incorporate some checks in the portal. For that I know the function module where i need to put though checks. Now I want to know, how does the code during runtime. What values do we get in the function module. For this I need to get into the debugging mode while executing the portal.
So how can we do that???

Namit,
it doesnot matter whether it is a standard funtion module or a custom one .check whether you are debugging for proper user(portal user and backend user are same) and check debugging is activated

How to debug start routine for the custom code?

Hi Experts,
Can anybody tell me how to debug the start routine? Also could you please guide me where to write the custom code in the start routine.
Thanks in advance.
Sharat.

Rajkumar,
Thank you for your help. but the blog link that you send it to me does not mention anything about ABAP debugger screen.
What should I do once I get in to the ABAP debugger? the link only tells how to get to the ABAP debugger that I know.
Also it say that I have to use the infinite loop to debugg the start routine.
Can anybody tell me how to debugg start routine with the scren shots please. I don't know how to use infinite loop in the start routine. Is their any easy process step by step to see my particular record behavior in the start routine?
I will assing you the points. again thank you.

How to debug alchemy( i.e., c/c++) code?

Hi all,
i want to debug the alchemy code
can any one have idea how to debug,
waiting for inputs
thanks in advance

Please see my post further down these forums, "Debugging Alchemy Applications with Netcat" .
I have hacked together a perl script that functions similarly to gdb, but for alchemy applications -- they must be compiled with "-g". There is no breakpoint support. The debugger is run first, then alchemy will connect when run. http://alchemy-hacks.googlecode.com/svn/trunk/debugger/acdb

IS Test stand support Code written in VC++ ?..IF SO How to integrate with Test Stand

IS Test stand support Code written in VC++ ?..IF SO How to integrate with Test Stand

If you have LabWIndows-CVI, you may also look at these threads: (may be useful for TestStand)
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=5065000000080000003C1F0000&UCATEGORY_0=_318_&UCATEGORY_S=0

How to compare the codes written in two different windows?

Hi ,
I have a long code written for a FM.
Now I have got the same code in a notepad.
I want to check weather the codes in the two windows are exactly alike.
Is there any easy way to do this?

hi Harshit Rungta ,
T-code SE39 - ABAP split screen editor use to compare 2 different programs ,function modules ,class
just create a function module that available in notepad and compare the code which u have already .
choose the function radio button while checking the function module .
regards
chinnaiya

How to debug the smart forms

Hi All,
Can any body guide me how to debug the smart forms.
Thanks & Regards,
Satish.

Hi,
The the best way to debug the form is to put a breakpoint in the function module generated by the smartform.
Procedure:
Open the smartform we want to debug.
Goto Environment -> Function module name.
Open the function module in SE37. From the menu GOTO -> main program. Open the last include.
This incude contains the entire code ie the code we have written in initalization + form routines + program lines + sap generated code.
Even we can search for the text nodes, folders, templates, tables, graphics, address nodes etc with their names.
Put a breakpoint at any point you want.
If we issue any doc which triggers this form, when the control reaches the break point it will stop.
Please note that hard-coding the break points in the code ( Program lines ) is not recommended and it can´t be done unless if it is development server.
So, always put a session break point in the related function module.
We can use SFTRACE transaction to know the sequence of the control flow.
If you want to break at each and every text that is printed on the output form put the break points in the forms.
1. %write_text to break at text element.
2. %WRITE_TEXT_MODULE to break at text module.
3. %WRITE_INCLUDE_TEXT to break at include text.
Please put a break point at the first sy-subrc check.
If the control reaches this point, you can find the name of the element in the varible NAME and the content in the text node in %TEXT.
Its easy to understand the sequence of the printing if we put a breakpoint as stated above.
Regards,
Satish.

How to debug the abap program ?

how to debug the abap program ?Can anybody explain me in details.

Hi
Debugger
This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
Functional Overview
Use
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Direct Processing
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator
Select a report or transaction and choose Program ® Test ® Debugging.
From the ABAP Editor
Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
From any screen
Choose System ® Utilities ® Debug ABAP.
From any screen
Enter /h in the command field.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields
The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table
Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints
A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints
You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls
This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview
This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings
This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto ® Display data object.
Single field
Displays the contents and technical attributes of a field.
Structured
field
Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings
Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table
Displays the type, line numbers and contents of an internal table.
Object
Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
Displaying Program Attributes
You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
Restarting the Debugger
If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
Breakpoints
Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statement
The Debugger stops the program directly before the specified statement is executed.
Breakpoints
at subroutine
The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module
The Debugger stops the program directly before the specified function module is called.
Breakpoint at method
The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions
The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter that only activates the breakpoint after it has been reached
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1.Choose Breakpoint ® Breakpoint at ® Statement...
The following dialog box appears:
2.Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3.Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
The following dialog box then appears:
Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
Choose Breakpoint ® Breakpoint at ® Function module...
The following dialog box appears:
Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at Methods
You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
Prerequisites
You must be already running the program in the debugger.
Procedure
To set a breakpoint for methods:
1. Choose Breakpoint ® Breakpoint at ® Method...
The following dialog box then appears:
2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the list in the display.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint ® Breakpoint at ® System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
Position the cursor on the line of the source code at which you want to set the breakpoint.
Choose Utilities ® Breakpoints ® Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities ® Breakpoints ® Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
Position the cursor on the line in which you want to set the breakpoint.
Select the line by double-clicking it or choosing Breakpoint ® Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint ® Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint ® Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto ® Control debugging ® Breakpoints.
Example
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
You can set up to five watchpoints in a program.
See also Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
You can change and delete watchpoints.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
Decide whether you want to set a local or global watchpoint.
Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator
Meaning
<
Less than
<=
Less than or equal
=
Equal
<>
Not equal
=
Greater than or equal
Greater than
You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR
Only one of the specified conditions must be met
AND
All of the conditions must be met.
Changing Watchpoints
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list. The following dialog box appears:
Choose the pencil icon in the line containing the watchpoint you want to change.
Change the watchpoint attributes in the Create/Change Watchpoint.
Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint ® Delete or Breakpoint ® Deactivate/activate. Instead, proceed as follows:
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
&objectname
Displays the references of strings, internal tables as well as data and object references
*itab
Displays the table header of the internal table itab
Example
If a watchpoint is set for the object in question at runtime, the program is stopped as soon as the reference is changed. A short dump can be intercepted in this way to stop the program being terminated when the memory is overwritten.
Analyzing Source Code
The Debugger contains an extensive range of functions that help you to analyze the source code of a program. You can step through the source code of a program in four different ways. For further information, refer to Stepping Through the Source Code
For information about functions within the source code display, see Displaying the Source Code
There are also different display modes that provide various information and display the contents of individual fields, tables, and so on:
Reward if usefull

Unable to depoly Web Serivce for the source code written in other editors

Hi all,
I am planning to implement webservice with the following code. But I am facing few problems with this can some body help me with this.
The code looks like this AND IS NOT WRITTEN IN Jdeveloper BUT EDITPLUS
package package1;
public class Sum
public int getSum(int a, int b)
          return a+b;
package package2;
public class Sub
public int getSub(int a, int b)
          return a-b;
package package3;
import package1.*;
import package2.*;
public class Mul implements TestInterface
     Sum sm = new Sum();
     Sub sb = new Sub();
public int getMul(int a, int b)
          return sm.getSum(a,b)*sb.getSub(a,b);
public static void main(String [] args)
          Mul ml = new Mul();
          System.out.println(âThe result of (3+6)*(3-6) is â+ ml.getMul(3,6));
package package3;
interface TestInterface extends java.rmi.Remote;
     public int getMul(int a, int b) throws java.rmi.RemoteException;
I have written this in editplus. Not in Jdeveloper.
Now I want publish getMul() as web service using Jdeveloper.
I have created a new application work space. And from File-->New
I have choose project from existing source and imported âpackage3â.
At this stage it was unable to find the class files Sum and Sub so I placed Sum.class and Sub.class in Appliction1-Project1-classes-
Now the Mul class did not have any errors and it compiled fine. When run it gave the correct output.
Using the web service wizard I was able to generate wsdl file , deployment descriptors etc.
The problem I was facing was form this stage when I am trying to deploy it on to a standalone oc4j server it is not able generate the WebServices.war file and hence is not deployed on to the server.
With the same code written in Jdeveloper everything is working fine.
My doubts are
1)     why is it not able to generate WebService.war file?
2)     It is giving some ClassNotFound exception during the deployment. But when compiled and run its giving the correct output.
3)     Even when everything was written from within the Jdevelper it did not include Sum.calss and Sub.class in WebSevice.war. Is there any way we could mention during its (WebService.war) generation , the class files to be Included.
The other issue is how to add an existing source code to already existing project. In my case Once I have imported package3 I also want to import package2 and package1 in different steps.
I thank in advance for helping me.
Raja Vamshi k Gopu

Can you tell us what you mean by correct type of project?
You can start with an empty project. Then, you have to create an "EAR file" deployment profile (New Gallery / General / Deployment Profiles).
So when I deploy a J2SE module onto oc4j server should I specify the class path? If so where ? How can I solve this problem?
Once you deploy your code into oc4j, it becomes a J2EE application. You don't need to deal with the classpath - just make sure that all the required code is included in your .war file. To do so, check the list of classes packaged under the deployement properties dialog.
Can you send me the links of few articles where I can learn more about these kind of stuff?
If you want to assemble applications without to use JDeveloper wizard, you have another option: using the WebServiceAssembler tool that is par of the oc4j bits will help you to do this from a command line promt, and will handle the J2EE packaging aspect for you.
See online documentation (10.1.2): http://download-west.oracle.com/docs/cd/B14099_04/web.htm
In the "Developer's Guide", chapter 9 is about "Web Services Tools"
For JDeveloper J2EE samples, you can start by looking at the OBE: http://www.oracle.com/technology/obe/obe_as_1012/j2ee/index.html
Hope this helps,
Eric

How to Debug code written in Include RMCSUZ10?

Similar Messages

Maybe you are looking for