Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
ravindra_devarapalli
Active Contributor

Hi Friends,

   I would like share my knowledge on Debugging, will  discuss on the  how to find the logic which is developed for field in Report.

Client raised issue on  report which is not working its either may standard report or customized report. Normally Standard report are working as their standards in some cases if values are not updated in structure  then may be values will not get. But as per standards the report will work.

Let's take example of standard report, Client raised issue as quantity showing wrong it is showing only single line item qty it should be cumulative qty of document.

Go to report and execute report

see example for doc number p3h05391 it is showing 293 but actually posted 293+ 50 = 343 qty

now will search what is logic in report . Actually for debugging will use /h to find debug program. But this is easy to find simple and save time also.

Go to menu bar system ---> status

go to se38 enter your program or you can double click on the program name.

The following it is showing tables are used in report to fetch the data.

the following it is showing selection screen it is linked to our main input selection screen

Normally out put report fields data getiing from fieldcatlog check in your report FCAT or field catlog.

in field catlog some times seltext will directly name but some times they will write as a text-xx. double click on this and find the field name.

click on find and enter you field name and select in main  program

Data always it will search from table where data fetching

and check any condition is there

Same way you check in table how data is getting, here in table two entries is there but in report it is showing one entry because of if condition greater value shown in the report.

3 Comments
Labels in this area