Debugging using breakpoint from a functional perspective
As a part of this explanation , I have taken sales order creation into consideration and showed the process of debugging using breakpoint instead
of using watch point that we do in common.
T. Code : VA01
Enter ‘/h’ in command field to activate Debugging and click enter
If you Execute now using f8 you will reach your error message point where you can find out your error.
Once you reach the point you need to check the values in kunnr,vkorg,vtweg,spart by double clicking on those fields.
It should now be evident that the issue was a missing combination of the sales area and the customer.
Any queries or suggestions to this document are welcome.
Regards,
Sambasiva Reddy Gurrala
SAP SD Functional Consultant
Dear,
I appreciate your efforts on this doc .You have explained nicely but the first 3 images are not appearing .Please have a look into that and replace the images .
Thanks,
Naren
Thanks Narendra I will
Hi Siva,
Really useful document for Functional consultants.
Good work.
Regards,
Krishna,
Thanks Krishna
Hi Sambasiva Reddy Gurrala
Helpful post...keep it up 🙂 and thanks 😳 .
regards,
sausap.
thanks
Hi Sambasiva,
Really helping and useful effort....thanks alot,
Regards,
Abhinav
Hi Shiva,
Thanks a lot...i really needed it..thats y i posted in SD but they reroute in ABAP..i got my answer but from functinal guy it is easier to understand..anyway thanks again.
Regards
Deep
Hello Sambasiva,
This is a useful document. Just add the couple of mising screenshots in the doucment. Thank you.
Regards,
Jignesh Mehta
Very nicely explained and useful for functional consultants. I am going to bookmark this and I hope you will change the screen shots which are not visible 🙂
Thank$
Hi samba siva reddy,
Thank you for your Contribution,this is very useful to us.
Very nice one. Thank you for sharing. Debugging is always handy for functional consultants, at least to know where the issue is coming from.
Could you please update the missing screen shots and You seem to have good experience in debugging, Could you please continue posting Debugging tips with few more examples ? Thanks in advance
GOOD IDEA BUDDY. IT CAN SAVE LOT OF TIME.
Hi Sambasiva,
Simple, Understandable & cool also.
Regards,
Balaji
Nice presentation.Thanks for the post.
Keep it up.
Thanks,
Suman$
Hi Sambasiva & others,
I have tried it in the system today and I see options only until breakpoint at system exception. However I dont see the option "breakpoint at Message option". I tried also tried in new ABAP Debugger option, but still does not appear. I once used the option breakpoint at statement and entered message, but if the program has more messages then it stops at all the messages, similary setting watchpoing and enter sy-msgno also an option, but I found your solution by using breakpoint at messaeg option is more convinient. would be great if you or anyone who knows let me know if I have to activate any setting (I tried but didnt find any) I'm using ECC 6.0.
Thanks in advance, br,
Sats
Hi ,
I think you are using ehp4 so please upgrade to ehp5 then you can see this.
Thanks,
samba
Thanks Samba
that answers my question 🙂
Hi
Thank you for your effort.
Some additional comments, if you agree. As we are talking about messages, we could read in ABAP this details.
Usually in SAP, customizing tables begins by T*, for instance T001, related with company code
Command select refers to reads on database tables. READ TABLE or LOOP refers to internal table. When SY-SUBRC is not equal (<> OR NE) zero means SAP don't find.
Sometimes it's possible to read this kind of comments in coding
These comments refers to notes. So it's possible to improve the research and made the right decision.
Other useful coding to search (no only tables, customizing or other data) is related with user parameters, so, look for around the message the command SET PARAMETER
Sometimes I've found modifications when with a simple parameter in SU01 it was solved.
Other question is how to search standard modifications (userexits, enhancements, implicit enhancements, BTE, VOFM and BADI).
Regards
Eduardo
sambasiva,
I do not understand the purpose of debugging, when (this type of) error message is got, in the sales order E.g. Ship to party not defined for sales area ZTES, ZT, 10
By going in to debugging mode, one is getting the exact same information that he/she gets during creation of sales order.
There is no information, suggestion, way given to solve this "issue".
Ofcourse, there could be other instances when debugging mode would be beneficial.
E.g. is customized errors where there is no proper description given.
Eduardo Hinojosa request you to give your comment on this.
I suppose the purpose of debuggin this was to demonstrate the debugging, an example that is easily understood by most of SD consultants has been selected.
If Sambasiva had choosen an example of customized message, am sure most of us would not have been able to related to this article!
The same approach can be used to debug cutomized errors as well. BTW, if the customized messages can have the desired level of description/information similar to standard messages, then it can eliminate debugging of code for customized messages as well...
Hi TW
Sometime, the developer with an error message or abendt message wants to avoid some output, but sometimes the logic of error isn`t understandable for the end user or the consultant. Of course, this is more usual in messages from non-sap developments, for instance in enhancements, badi, userexits, BTE or in VOFM (for instance, in copy rules requirements).
Regards
Eduardo
Hello Sambasiva
Thanks for sharing this...is much helpful
Regards
Shiv
Dear Sambasiva,
Thanks a lot for this post. Its very helpful for beginers.
Regards,
Nikk
Hello Sambasiva,
Handsome post for beginners in functional consultant.
Thanks,
Pratik Parmar
Hi Sambasiva,
Thumbsup for your document,
Very useful information for SAP functional consultant
Keep posting
thanks
sri
Hello,
Sambasiva I have an error which doesnt display the message number .
What should I do in that case ?
Please help
Where are you getting that error message? May be it is some Z error message which is written in some Z piece of coding. Did you check with ABAPER?
Hello Mozzam,
I got the error on a IDES server. I did not consult with an ABAPer. will shortly post a screeen shot.
thanks,
Kishor
Post it as a thread in respective space. Please dont post your query in comments here.
Thank$
Thanks Mozzam,
I have already done it in the past . http://scn.sap.com/thread/3370409
I got the solution that there was a User Exit used.
My question is that how would I detect the error using ABAP debugging technique for the above thread.
Hi
For this you must have any message number. Either this is standard error message or some customized one you must have message number defined for that message.
Thank$
Ok. Thank you for valuable guidance.
Thanks for the help.
Dear Siva vasi reddy
Thanks a lot For your time in explanation but one thing i want to ask you You found rout cause, but my doubt is how it is possible , what you done after finding route cause
Because , i have not understand where is the problem ?
Thanks a lot
Hi Siva,
Really useful.
Regards
Raja