Break-point in BE process

Hi,
I want to put a break-point in synchronous inbound proxy which is in CRM. The How-to-guide says to put a HTTP breakpoint but i am not getting the pop-up menu for setting HTTP break-point. Would the session break-point enough to stop the process.? or else whats the way to stop. I dont have access to SICF to set a break-point there for my userid......
Thanks
ricky

Hi,
Have you checked this blog?
<a href="/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation">Debug your inbound ABAP Proxy implementation</a>
Regards
Bhavesh

Similar Messages

Where to put break point when debugging the inbound IDOC processing

Hi, Dear Experts,
If IDOC has error and want to debug, which program or function module to put break point when debugging the inbound IDOC processing
Thank you so much!
Helen

It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

External break point in sap r/3 system

i want to set external debugging to rfc in r/3
i tried to set it
its getting set
but when i call rfc from external system(webdynpro)
its not gng to that break point i.e its not linking to that break point
what could be the reason
and how we can set external breakpoint
are there any setting we need to do in r/3 so that break points will work
Regards,
Vani

Hi Vani,
First u have set ur Server to Debug mode...then only u can debug the code...
1. Select "Server0" from J2EE engine (To get this view navigate thru Window--> Show View --> J2EE Engine)
2. Make a right click on "Server0" and choose "Enabling Debugging of Process"
3. Now, Navigate to Run --> Debug --> Select your Project as "Webdynpro Application" and click "new" button
4. Now give some name and Click BROWSE to select ur project and then click APPLY and DEBUG
Or
if u use 2004s, then u can do the settings in Portal itself...which gives u more clear information... follow the link
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0cb32c5-36a7-2910-2c9b-ba4a5bbdbb56">WebDynpro Java Debug Configurator</a>
Hope it helps...
Regards / Guru

VS 2010 Silverlight project upgraded to VS 2013 - not hitting break point.

dear Readers,
thank you for taking the time to read this posting.
we had developed a SL project using VS 2010 and it was successfully upgraded to vs 2013. after a couple of hiccups, the application compiled and ran successfully. the SL app is still in .net framework 4.0.
due to some changes, we wanted to debug the application. Even after marking a couple of break points, we found that vs 2013 did not hit the breakpoints when we ran the app with F5.
We tried the following and it still would not hit the breakpoint:
1. deleted the /bin and /obj directories in SL and .Web projects.
2. deleted .xap file and /bin /obj directories.
We tried attaching/detaching the sl process in Firefox. IE, and chrome - no luck.
any suggestions will be appreciated.
regards
ravi.
Sr GIS App Developer Dallas Fort Worth area, TX

Hi,
Please check the upgrade report details.
Besides, below articles will help you when you upgarde your silverlight application.
https://msdn.microsoft.com/en-us/library/hh397894(v=VS.95).aspx
https://social.msdn.microsoft.com/Forums/silverlight/en-US/475d7dca-eebf-4d50-87f8-957f6415fb63/how-to-upgrade-a-silverlight-4-application-to-silverlight-5?forum=silverlightgen
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Export data in Excel file - Debug and Break Point

In the program RFUMSV00 the data been displayed on the screen with the function REUSE_ALV_LIST_DISPLAY.
With "Cntrl + Shift + F9" I exported the list of data in an Excel file.
How can I see, with Debug, where the program RFUMSV00 passed the data to Excel File? I can indicate the point, In the program, where I need to set the break point?
Thanks,
Serena

Hi,
This download functionality has nothing to have with program RFUMSV00. It is actually processed by REUSE_ALV_LIST_DISPLAY fm, which calls fm LIST_COMMAND which finally calls fm LIST_DOWNLOAD, where you will actually find the downloading part (in fact in another fm, DOWNLOAD_LIST)...
to resume: REUSE_ALV_LIST_DISPLAY->LIST_COMMAND->LIST_DOWNLOAD->DOWNLOAD_LIST
so I would put the break-point in the last one..
Kr,
Manu.
correction: I made a mistake, the break-point should be set in LIST_DOWNLOAD...where you will find the call to fm LIST_CONVERT_TO_DAT which is responsible of the download...
Edited by: Manu D'Haeyer on Dec 9, 2011 1:46 PM

Problem setting External break point..

Hi All,
I am using EP6 SP14 and R/3 4.6C. Java Webdynpro aRFCs to connect to R/3 BAPIs. I am having problems setting up external break points. I don't see Debug option in "Utilities -> Settings -> ABAP Editor". Do we have this option in R/3 4.6C? If yes how to enable the option? If no, what is the work around to debug the BAPI through Portal.
Helpful answers will be rewarded.
Regards,
Uday.

Hi,
Pl go through this
Debugging ABAP Code from within Web Dynpro Application
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0e9a9d90-0201-0010-478e-991dbea73a30
It explains step by step process
Regards
Ayyapparaj

Break point in EXIT_SAPLV05I_002

Hi, I nead your help.
I've already put a break point in EXIT_SAPLV05I_002, INCLUDE ZXV05U05 but when I crete a delivery the debuging is not started.
Dou you know in what moment this exit should stop?
Thanks
Dora

Hi Venkat
Your user exit does get processed during the delivery save.
Your breakpoints are not stopping in it because all the indexes tables VKDFS, VEPVG etc
are handled in the update task, so you have to use update debugging.
The quick wat to get to your user exit to see what is is doing is as follows:
Create a delivery in VL01n
Before you hit the save button switch on the debugger
then press save
In the debugger oput a breakkpoint on the ABAP statement COMMIT WORK
The program will stop at this statement which is the end of the application processing.
In the debugger go to SETTINGS > UPDATE DEBUGGING
Then press F8 to contunue
A new screen will appear with the update task.
In the new screen put a breakpoint in function module RV_DELIVERY_INDEX_SAVE
( If this were from a sales order you would do the same but with function RV_SALES_DOCUMENT_INDEX_ADD)
Your user exit is called below marked :
RV_DELIVERY_INDEX_SAVE
Billing type appears in the index if there is at least one R/3
billing relevant item in the delivery
     if vbuk_wa-fkstk ca 'AB' or
        vbuk_wa-fkivk ca 'AB'.
perform lk_01.                   "Fakturaauslöser           >>>>>>>
    EXIT_SAPLV05I_002 is called in here....
I hope this helps explain the system behaviour
Kind regards
Brian

Can any one explain me about break point

Hi gurus
What is break point what is the use of it? please let me know what is the use of it?
Thanks in advance

Hi
Hi,
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 Debugger is activated when the program reaches this point.Max 30 breakpoints we can use.
Session Breakpoints exist only until you are logged in or until ur session is active. Even if u forget to remove the session break points, they are automatically removed once ur session becomes invalid or u logged out.
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.
Regards
karthik

Break point in ABAP Routine

Hi Gurus,
In working on 3.5 version. In one of the update rule by mistake break-point is included in the routine which is written for master data look up. and v r calculating the simple formula in the update rule thats it.
For this ODS only my loading performance is very slow does the inclusion of break-point is impacting the loading ..
Pls let me know
Regards

Also one more thing is that even if you have a break point - very often loading is deon through process chains - this would mean that the load is done through a background user - this should not imipact the data loads since debugging cannot be done using a background user and it should skip these -
IMHO - I have put in break points and transported the same into production to help debug any exceptional cases which could not be caught in development.
Arun

Break point in a program

i kept a break point in a user exit with the statement
BREAK-POINT.
but the control is not stopping there , i am not testing it so didnt give it as user specific . what might be the mistake ? is it not the proper user exit , i have created a project and activated it . i have activated include and all .

Hi,
When you start transation in which you have put a break point, start debugging on(\h). add break-point at statement CALL CUSTOMER-FUNCTION.
keep on pressing F7. You may reach to your exit if it come in way of executing you process.
Could you mention for which functionality you have created using user exit, it will more easy to provde help.
Regards,
Amit R.

How to place a break-point in update rules

Hi All,
Can any one let me know how to place a break-point in update rules. I used the hard code BREAK-POINT in the code, but it did not work out. After placing the BREAK-POINT in the update rules code, I executed the info package and the load was successful. In order to go into the debug screen can any one let me know the procedure.
Regards,

Hi,
In the monitor screen goto "details" tab and under the "Processing" select the option "Data Package 1" and right click over that you can find an option simulate update.
In that select the option "Activate Debugging in Update rules" and select "Perform Simulation".
You can search for your code using the option ctrl+F and double click the code over there.
now the breakpoint is set.
Hopr this helps.
Regards,
K.Manikandan

How many break points and watchpoints are allowed in ECC 6.0

Hi,
Can any one say how many break points and watchpoints are allowed in ECC 6.0

Hi ,
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 Debugger is activated when the program reaches this point.Max 30 breakpoints we can use.
There is 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 ie...Watchpoints allow you the option of monitoring the content of individual variables.The Debugger stops as soon as the value of the monitored variable changes.You can use max of 5 watchpoints.
Difference
1. Break Point.
At particular LINE of SOURCE CODE,
the system will STOP there.
2. Watch Point.
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.
(For this, we have to give some
VARIABLE NAME & VARIABLE VALUE - with relational operator)
When this CONDITION gets satisfied,
(anywhere during the execution of the program),
the system will AUTOMATICALLY STOP THERE.
(EG when the value of matnr reaches the specified value)
That is the purpose of WATCHPOINT
(the system will WATCH it, like a dog)
Please go through this link:
Watchpoint Vs breakpoint
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
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. Watchpoints allow you the option of monitoring the content of individual variables.
The Debugger stops as soon as the value of the monitored variable changes.
In addition, conditions can be specified. The Debugger also checks whether such a condition is fulfilled.
For more details...
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cd9e68c11d2b2ab080009b43351/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/f1/792442db42e22ce10000000a1550b0/frameset.htm
If satisfied, rewards me..
Kind Regards
Yogesh

How to put break point in the update routine

I am trying to create a break point in update routine. I can do that in the start routine but I would like to know how I can include a break point in update routine in Q.
Thanks

Go to Monitor Screen of the data load -> Details tab -> data processing -> right click on Data Packets -> select simulation -> select update rules and give no.of records you want to debug and then system will display the code where you can debug by giving break points.
Hope it helps..

What is External Break points?

Hello,
What are external Break points...?
My issue : I need to check a condition in the Source code...
What do I need to do to get control at that condition directly to check whether the data is passing in those tables or not?
Any suggestions would be appreciated...
Regards,
Krishna Chaitanya

Hi,
Breakpoints
Setting and editing breakpoints, too, in the new Debugger is almost identical to the classic Debugger. However, several breakpoints can be set simultaneously in the new Debugger if you choose the path Breakpoint ® Create Breakpoint. Afterwards, the system displays a window in which the following options are available.
Here it is obvious that, in contrast to the classic Debugger, all the input fields u2013 with the exception of those in the ABAP command tab u2013 have a search help function (function key F4). For example, under the Method tab you enter a certain class. Then, in the search help, all the methods that belong to this class are proposed.
There are also certain differences when setting and deleting breakpoints. A double-click within a source code line creates a breakpoint in this line in both Debugger types, provided the cursor was not positioned on an ABAP keyword. A second double-click in the same line deletes this breakpoint in the classic Debugger, while it is only deactivated in the new Debugger.
Breakpoint Types
When you set a breakpoint in the Debugger, it is created as a debugger breakpoint by default. A debugger breakpoint is only valid while the Debugger instance, in which it was set, is active. When the Debugger is closed, all debugger breakpoints set in it are deleted.
If you set a breakpoint in the ABAP Editor, for example, this breakpoint is a session breakpoint. Session breakpoints remain active independently of the existence of a Debugger and are valid for all external sessions of a logon. Within the Debugger, you can convert a debugger breakpoint into a session breakpoint and vice versa.
If the setting Session Breakpoints Active Immediately is checked (via Utilities ® Settings ® ABAP Editor ® Debugging in the ABAP Editor or Object Navigator), you can set a session breakpoint in an external session of a logon to force a running program into the Debugger that runs in the same logon (for example, in an external session) and will process the point at which the session breakpoint was set.
User breakpoints (previously known as external breakpoints) are valid for all user logons on the current server of the current system. User breakpoints are specifically required when debugging BSP or Web Dynpro applications. In these cases, you do not log on using the SAP GUI but via a browser, for example. Therefore, any breakpoints must be set before logging on.
User breakpoints are only valid for a period of 2 hours.
As of Release 7.00, user breakpoints set for BSP or Web Dynpro applications are also valid for SAP GUI logons.
Within the Debugger, you can convert debugger or session breakpoints into user breakpoints and vice versa.
External Debugging
Use
You can use debugging in order to carry out detailed troubleshooting. With the debugger, you check a given section of code in the Request Handler or an ABAP function module for errors.
Basically, there are two different types of debugging:
·        With conventional debugging, you can analyze programs that you call up within your own user session on the server, with breakpoints being set at corresponding points in the coding.
·        With external debugging, you can analyze programs that are called up by an external user with HTTP. For the purpose of external debugging, special breakpoints (external breakpoints) are set on the target server.
Two variants are available for conventional debugging: the classical variant and the new (2-processor) variant, which creates a separate session for the debugger. At present, external debugging can only be performed with the classical variant.
This section deals especially with external debugging, as it is generally makes sense to call up an external user completely (with all sent parameters) in one step when investigating ICF processes.
Prior to Release 640, the external debugging described below was known as HTTP debugging.
Prerequisites
·        If you use load distribution for your system environment, the server group (logon group) is reduced to one server before debugging commences.
·        Ideally, the user who performs the debugging should not be a collective user.
Activities
Note that the troubleshooting method described here can affect your system performance. You should therefore only activate it if you really need it. You are advised to monitor the corresponding settings regularly and to deactivate any functions you no longer require.
In transaction SICF, you can use the external debugger to set external breakpoints and check the debugging of the relevant section of code:
       1.      Select the required service in the service hierarchy.
       2.      Choose Edit ® Debugging ® Activate Debugging.
       3.      Enter the required data (if you have selected the service previously, the system will propose the service path for you).
Reward If Helpfull,
Naresh.

Break Points for Dual Layer Discs

I've read and re-read the DVDSP4 manual on break-points. They are giving me the hardest time even still. Is there any way to by-pass the muxing process and not have to wait that long to find out if there is the correct balance of space used for each layer on the disc? IOW, is there a way to automatically check if the layers are right without choosing the "auto break point" option?

Hi Drew, when you say set a bunch of markers in the general area, what types of markers are you talking about (ie. chapter, button, dual layer break point)? I can only set one "dual layer break point", should i be able to set more than one? I'm working on this dual layer project and it is driving me nuts!

Break-point in BE process

Similar Messages

Maybe you are looking for