on 02-26-2014 7:01 AM
Hi,
Please ask your Abaper to remove this break point but you can also tackle this issue at your functional level.
Click on Debugger at the top menu and from there you can choose either Continue by pressing F8 button (which is nothing but execute button) or you can also choose Exit Debugger from that menu where in an option will come whether you really want to exit debugger then click on Yes.
It wont hamper your work and you will proceed further.
Regards,
Amit Rajoria
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
check with the ABAP consultant,for the displayed screen shot, and ask him to remove the break point.
Which transaction code you are using for the creation of the external activity for wbs elements is it CJ20N or CN22 check with both transaction codes for creation of activities
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
it looks like a Z code (custom program created by a member of your team) and obviously has a BREAK-POINT statement. You need to access it and set the BREAK-POINT statement in comments so the system will not "stop" there...(check it with an abap colleague to help you out)
Panagiotis
ps...you could check on your Debugger's screen the "Standard tab" and specifically the "Abap and Screen Stack" to help you understand the physical flow of the code. This way you will reach the originating caller function.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.