ABAP Extractor - Dump: READ_REPORT_LINE_TOO_LONG

system · December 16, 2014, 4:06pm

Hi all,

i’ve a serious issue with ABAP Extractor (generated ABAP code from DS)!

i’ve updated an ABAP Extractor with additional WHERE Clauses in DS and generated the ABAP code.
Afterwards i’ve sent it to the SAP Team to overwrite the existing code with new one.
I can call the ABAP Program directly in SAP without any issues. But when i try to execute from DS i get the DUMP:

Runtime Errors READ_REPORT_LINE_TOO_LONG
Exception CX_SY_READ_SRC_LINE_TOO_LONG
Date and Time 16.12.2014 16:57:47

Short text
The ABAP program lines are wider than the internal table.

What happened?
Error in the ABAP Application Program
 The current ABAP program "/BODS/SAPLBODS" had to be terminated because it has
 come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
 To process the problem further, contact you SAP system
 administrator.

 Using Transaction ST22 for ABAP Dump Analysis, you can look
 at and manage termination messages, and you can also
 keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class ‘CX_SY_READ_SRC_LINE_TOO_LONG’, was
not caught in
procedure “/BODS/JOB_RUN” “(FUNCTION)”, nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
There was an attempt to read program “ZW_SD_COPA_SEP_CE1XEUR” from the
database.
The READ REPORT statement allows you to copy a program text into an
internal table. The occupied line length in the program text must not
exceed the width of the internal table.
The internal table “\FUNCTION=/BODS/JOB_RUN\DATA=PROGRAM” is 72 characters
wide. The program line is
78 characters wide.

How to correct the error
Probably the only way to eliminate the error is to correct the program.
-
The exception must either be prevented, caught within proedure
“/BODS/JOB_RUN” “(FUNCTION)”, or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:

It seems that the machine generate ABAP code cannot be executed from DS any longer!

We’re on Version: 14.1.3.875

Does anybody know a workaround? Or how to fix it?

barthodo (BOB member since 2012-04-18)

system · April 14, 2015, 2:17pm

I have the same issue; currently in the process of implementing this fix.

http://newscentral.exsees.com/item/d77ae6165faecd2d17b230f7c69d1107-b8c8af0eacdfd755374bbf648f55b12d

OSS note: 1971036

Hope this helps…

ScSi (BOB member since 2013-10-08)

system · April 16, 2015, 7:09am

Hi ScSI,

in the meantime i’ve fixed the issue.
My problem was that i had a very long WHERE clause and the brackets around this where statement brought one line to be longer as the allowed 72 chars.

I simply made another carriage return to not break the limit and now it’s working…

barthodo (BOB member since 2012-04-18)

system · April 16, 2015, 10:32am

That would have been my other suggestion, as I ran into that issue myself as well.

THanks for your feedback, glad to hear you solved it!

ScSi (BOB member since 2013-10-08)