5 (five) easy debugging techniques
Debugging tool is probably one of the most powerful tools in SAP and there is no excuse not having the basic knowledge of debugging if you are a SAP consultant. Sometimes, functional consultants shy away from debugging because of their lack of ABAP knowledge. ABAP knowledge makes debugging easier and you can leave the heavy debugging on ABAPer but here are some tips that can help you in basic debugging. So next time don’t wait for the ABAPer.
- Debugging an error message: If you are stuck in a SAP transaction due to an error message, you can use this technique to find the reason (or place) of the error message. This may provide valuable insight. Follow the link to know more.
- Looking for function modules: ABAPers love to throw this on functional consultants and vice versa as well. If you need to replicate a standard process to custom program, generally a FM or BAPI is required. By debugging you can verify or find if any FM is getting triggered in that particular transaction. Click on the heading to read more.
- Check the value of a variable (or table entries): It comes in handy if something is going wrong in SAP transaction and you have an idea which variable may be causing the issue or in case of the dump. Post coming soon.
- External debugging: This is becoming more important as now more and more transactions are moving to Fiori or UI. In this case, for any debugging you need to set up external debugging points. Click on the heading to read more about it.
- Delete the breakpoints: I have seen many functional consultants getting stuck because ABAPer was using their machine and have not removed the breakpoints after analysis. Learn once and for all how to remove the debug points. Post coming soon.
If you like our content, please follow our LinkedIn page for the updates.
