Easily debug error messages in SAP processes


Matthew Billingham

说明:这是我在searchsap上看到的一个tips,在一次项目中帮了我很大的忙,觉得还是很好用的东西,因为比较简单,所以我就不翻译了,有不明白的朋友可以给我留言.其实这也是关于debug的技巧,记得我曾经写过check-point的使用,这个则是关于watch-point的使用,简单而强大,强烈推荐.

Sometimes, an SAP process will stop working with an error message, or an abend. Unlike with a dump, it can be difficult to find exactly where the problem occured. What you should do, is get the technical name and number of the message – e.g. RS 100. Set a breakpoint at the start of the process (or run the process with the debugger switched on). As soon as the debugger is in some abap code, set a watchpoint for sy-msgno. In this example, you should set a watch point for sy-msgno = 100. Then hit F8.

The process will continue to run until sy-msgno has the value 100.

Check that the message ID is correct, according to the message – RS in this example. If it is, then you are at the place where the error occurs. You can usually back trace a few steps to find out precisely what was causing that error to be triggered.

原文地址:http://searchsap.techtarget.com/tip/0,289483,sid21_gci1314665,00.html


About The Author

从事SAP行业有些年头,对SAP技术稍有了解; 如无特别声明,本博客文章为原创,转载请注明; 博主MSN:xuchunbo0901@hotmail.com; 博主邮箱:bob.xu@abaptech.com。

No Comments

Leave A Reply


注意: 评论者允许使用'@user空格'的方式将自己的评论通知另外评论者。例如, ABC是本文的评论者之一,则使用'@ABC '(不包括单引号)将会自动将您的评论发送给ABC。使用'@all ',将会将评论发送给之前所有其它评论者。请务必注意user必须和评论者名相匹配(大小写一致)。

无觅相关文章插件,快速提升流量