02-24-2022 2:58 PM
I know below statement cause dump, I try to find whcih line is too long during debug, but failure.
how to find which line of l_prog_tab_local cause error during debug?
how to using debugger script for this?
read report l_prog_tab_local into l_abap_source.
Can anyone help me in this?
02-24-2022 2:59 PM
Search for the line of your report bigger than 72 char.
02-24-2022 2:59 PM
Search for the line of your report bigger than 72 char.
02-24-2022 4:32 PM
This doesn't seem to be possible directly (at least not on 740 system I have access to). As a workaround, you can declare table of strings as your target internal table and do READ REPORT into that table - it should not short dump. Then you can inspect the contents of this internal table and find row(s) longer than whatever the line length of your original l_abap_source is.
02-25-2022 3:03 AM
Hi,Milos,
It's 800 client, I can not add my our code directly. I want get dump reason of which line of Report Code during debug.Because code is larger,It's not possible to view code line by line.
Thanks
02-24-2022 7:25 PM
You may search the forum/SAP Web site with your favorite Web search engine. I see many answers for search below. Based on the results, if it still doesn't solve, you may anyway refine your investigations and provide more information here.
read report line too long site:sap.com