READ_REPORT_LINE_TOO_LONG

Hi
I am getting a dump 'READ_REPORT_LINE_TOO_LONG'.
the program is Z, but the dump is coming in some standard table.
the thing is that I am getting this dump in quality but not in dev.
please help
Regards
Manu

If you are using read report statement in any of the programs and the report which you are reading exceeds line length of 72
it throws an exception.Check the report code and make sure that length wont exceed 72.
Its bcoz read report statement reads the report into an internal table which has a component of length 72
Regards,
Lakshman.
Edited by: Lakshman N on Oct 15, 2009 10:38 AM

Similar Messages

Unable to resolve the exception READ_REPORT_LINE_TOO_LONG in Abap program.

Hi,
I am getting the exception READ_REPORT_LINE_TOO_LONG in my abap program.Given below is the full analysis of the exception and then the program code :-
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 "K_KKB_FIELDCAT_MERGE" "(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 "ZANI_TEST_INTERACTIVE_ALV" 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=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72
characters wide. The program line is
91 characters wide.
Program Code :-
*& Report ZANI_TEST_INTERACTIVE_ALV
REPORT ZANI_TEST_INTERACTIVE_ALV.
TABLES: LFA1.
TYPE-POOLS: slis.
DATA: it_lfa1 TYPE TABLE OF lfa1,
      wa_lfa1 TYPE lfa1,
      it_fieldcat TYPE slis_t_fieldcat_alv.
SELECTION-SCREEN BEGIN OF BLOCK input WITH FRAME TITLE input.
SELECT-OPTIONS: acc_no FOR LFA1-LIFNR.
SELECTION-SCREEN END OF BLOCK input.
START-OF-SELECTION.
IF NOT acc_no IS INITIAL.
    SELECT * FROM LFA1
      INTO CORRESPONDING FIELDS OF TABLE it_lfa1
      WHERE LIFNR IN acc_no.
ELSE.
    SELECT * FROM LFA1
      INTO CORRESPONDING FIELDS OF TABLE it_lfa1.
ENDIF.
PERFORM form_build_fieldcatalog USING 'IT_LFA1' CHANGING it_fieldcat.
PERFORM form_display_alv USING it_lfa1 it_fieldcat.
*&      Form form_build_fieldcatalog
      text
     -->P_0058   text
     <--P_IT_FIELDCAT text
form form_build_fieldcatalog using    p_it_tabname TYPE slis_tabname
                              changing p_it_fieldcat TYPE slis_t_fieldcat_alv.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      I_PROGRAM_NAME               = sy-repid
      I_INTERNAL_TABNAME           = p_it_tabname
    I_STRUCTURE_NAME             =
    I_CLIENT_NEVER_DISPLAY       = 'X'
      I_INCLNAME                   = sy-repid
    I_BYPASSING_BUFFER           =
    I_BUFFER_ACTIVE              =
    CHANGING
      ct_fieldcat                  = p_it_fieldcat
    EXCEPTIONS
      INCONSISTENT_INTERFACE       = 1
      PROGRAM_ERROR                = 2
      OTHERS                       = 3
IF sy-subrc <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " form_build_fieldcatalog
*&      Form form_display_alv
      text
     -->P_IT_LFA1 text
form form_display_alv using p_it_lfa1 LIKE it_lfa1 p_it_fieldcat TYPE slis_t_fieldcat_alv.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_INTERFACE_CHECK                 = ' '
    I_BYPASSING_BUFFER                = ' '
    I_BUFFER_ACTIVE                   = ' '
      I_CALLBACK_PROGRAM                = sy-repid
    I_CALLBACK_PF_STATUS_SET          = ' '
    I_CALLBACK_USER_COMMAND           = 'USER_COMMAND'
    I_CALLBACK_TOP_OF_PAGE            = ' '
    I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
    I_CALLBACK_HTML_END_OF_LIST       = ' '
    I_STRUCTURE_NAME                  =
    I_BACKGROUND_ID                   = ' '
    I_GRID_TITLE                      =
    I_GRID_SETTINGS                   =
    IS_LAYOUT                         =
      IT_FIELDCAT                       = P_it_fieldcat
    IT_EXCLUDING                      =
    IT_SPECIAL_GROUPS                 =
    IT_SORT                           =
    IT_FILTER                         =
    IS_SEL_HIDE                       =
    I_DEFAULT                         = 'X'
    I_SAVE                            = ' '
    IS_VARIANT                        =
    IT_EVENTS                         =
    IT_EVENT_EXIT                     =
    IS_PRINT                          =
    IS_REPREP_ID                      =
    I_SCREEN_START_COLUMN             = 0
    I_SCREEN_START_LINE               = 0
    I_SCREEN_END_COLUMN               = 0
    I_SCREEN_END_LINE                 = 0
    I_HTML_HEIGHT_TOP                 = 0
    I_HTML_HEIGHT_END                 = 0
    IT_ALV_GRAPHICS                   =
    IT_HYPERLINK                      =
    IT_ADD_FIELDCAT                   =
    IT_EXCEPT_QINFO                   =
    IR_SALV_FULLSCREEN_ADAPTER        =
IMPORTING
    E_EXIT_CAUSED_BY_CALLER           =
    ES_EXIT_CAUSED_BY_USER            =
    TABLES
      t_outtab                          = p_it_lfa1
    EXCEPTIONS
      PROGRAM_ERROR                     = 1
      OTHERS                            = 2
IF sy-subrc <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " form_display_alv
Please suggest a solution for this problem.. Thanks in advance.

hi,
it is getting because of fieldcat hear ur internal table is having all fields in lfa1, lfa1 is having more fileds alv cont display that much fields at a time . for that u are getting that messgae . u can solve this problem by filling fieldcat table manuvally insted of by FM 'fieldcat_merge'. fill filedcat table some fields which are need to display by manuvally.
thanq,
rajesh.k

Runtime Errors         "READ_REPORT_LINE_TOO_LONG"

i am using a include program to alv list display.
and when i execute the main program.. it gives the following dump.
Runtime Errors         READ_REPORT_LINE_TOO_LONG
Exception              CX_SY_READ_SRC_LINE_TOO_LONG
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 "K_KKB_FIELDCAT_MERGE" "(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 "ZSM_INVFNL" 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=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72
characters wide. The program line is
88 characters wide..
can some one tell me how to resolve this...??

In first screen of transaction SE38, go to menubar Utilities->Settings. In the ABAP Editor tab of the popup dialog box look under subtab Editor. At the bottom of the dialog box there should be a checkbox named Downwards-Comp.Line Lngth(72). Uncheck that, press Enter and leave the transaction. Now run your report again, it should be fine this time.
Cheers,
Sougata.

'READ_REPORT_LINE_TOO_LONG' dump

Hi,
I am getting dump 'READ_REPORT_LINE_TOO_LONG' when I checked in Run time analysis, it tried to read the program "FMCB1900" from the database. The READ REPORT statement allows you to copy a program's source code into an internal table. The lines of source code must not be longer than the width of the internal table. The internal table is 72 characters wide. The source code line is 95 wide.
"FMCB1900' is standard program but I have seen some version changes in the program itself.
Please kindly suggest me regarding this for further process.
Regards,
Jyothi CH.

Hi,
Increase the length of your internal table. It might be of 72 length .Suppose ,some where in the program FMCB1900 if the code line length exceeds more than 72 characters the system throws you a dump.As it is a standard program you cannot change the compatibility length.Try to increase the length of internal table.
types:begin of ty_tab,
code type char255,
end of ty_tab.
data:it_report type standard table of ty_tab .
Regards,
Lakshman.
Edited by: Lakshman N on May 14, 2010 12:03 PM

Runtime Error: READ_REPORT_LINE_TOO_LONG

Hii All,
I have created a report in ALV. i have used the function module "REUSE_ALV_FIELDCATALOG_MERGE".I have debugged the whole report but when watch point comes at this fynction module it gives runime error as READ_REPORT_LINE_TOO_LONG.
Can anyone help me why this error is coming and how to handle this.
Regards,
Sany

Hi,
To Fix this short dump in the report program Just go through the program and see there would be any line present in the report exceeds beyond 72 Character. So just Make sure no line should contain the text or any statement Beyond the 72 Characters.
If you are using the latest editor of ECC 6.0, then you will have the option in settings also.
SE38 -> UTILITIES -> SETTINGS -> ABAP EDITIOR -> EDITOR -> Please check the check box for 'DOWNWARDS~Comp. Line Lngth(72),
Automatically when you use PRETTY PRINTER, it will remove the line exceeding 72 char and will come in the next line.
Regards,
Santhosh.

Error "READ_REPORT_LINE_TOO_LONG" at a report

Hi
I have an error at a report, it's the first time that i see this error,
Erro tpo.exec.         READ_REPORT_LINE_TOO_LONG
Exceção                CX_SY_READ_SRC_LINE_TOO_LONG
Data e hora            12.11.2008 14:57:22
Texto breve
The ABAP program lines are wider than the internal table.
O que aconteceu ?
Error in the ABAP Application Program
The current ABAP program "SAPLSKBH" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Análise do erro
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 "K_KKB_FIELDCAT_MERGE" "(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 "ZRPSD_REL_RECL" 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=K_KKB_FIELDCAT_MERGEDATA=L_ABAP_SOURCE[]" is 72
characters wide. The program line is
73 characters wide.
Falta cláusula RAISING na interface
Programa                                SAPLSKBH
Include                                 LSKBHU12
Linha                                   1
Tipo de módulo                          (FUNCTION)
Nome do módulo                          K_KKB_FIELDCAT_MERGE
Can somebody tell me how can i correct this ?
Thanks

You are getting this error because some of the lines in your source code are more than 72 characters.
It seems you are using the FM REUSE_ALV_FIELDCATALOG_MERGE with option of Internal table.
There are some options to correct it:
1. Make sure you have all your source code are not more than 72 characters. If program is very big than you have to work a lot in this option to make sure all lines are less than 72 characters.
2. Create a Structure of the internal table in SE11 and use it in the Function module REUSE_ALV_FIELDCATALOG_MERGE instead of the internal table.
3. Fill the Field catalog by directly appending entries in the FIELD CATALOG table instead of using the FM REUSE_ALV_FIELDCATALOG_MERGE. If you have lots of fields than this option is also not good.
Regards,
Naimesh Patel

Dump READ_REPORT_LINE_TOO_LONG

Hi SDNers,
I got the following dump: "READ_REPORT_LINE_TOO_LONG" in the standard object %_CABAP.
Since it's a standard object, I would like to know if there is some program which regenerates this program or perhaps some note to apply.
Thanks in advance for your support.
Best Regards,
Leandrp

Hi Leandro:
When do you get this error? While loading data? Could you please provide more details?
Regards,
Francisco Milán.

Dump in READ_REPORT_LINE_TOO_LONG

hi Experts ,
while executing a report in ECC 6.0 , i was facing a dump error "READ_REPORT_LINE_TOO_LONG"
exception :CX_SY_READ_SRC_LINE_TOO_LONG
the error comes out to be in line
read report l_prog_tab_local into l_abap_source.
suggest some helpful solution.
thanks & regards
Saurabh Goel

Hi,
Check the program present in l_prog_tab_local once .Some where the length the code should have exceeded 72 characters.
It should not be greater than 72
Goto SE38 open the program Goto utilities>Settings>Check the check Box Downwards--Comp.LineLngth(72)
Regards,
Lakshman.
Edited by: Lakshman N on Dec 1, 2009 7:07 AM

'Read_report_line_too_long' runtime error

An exception occurred that is explained in detail below...
The exception which is assinged to the class 'CX_SY_READ_SRC_LINE_TOO-LONG', was not caught in porcedure
'K_KKB_FIELDCAT_MERGE'.
The reason for the exception is: 'there was an attempt to read the program 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=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72 characters wide. The program line is 88 characters wide.
please kindly help me to solve this error.

Hi,
Please check if the note 902476 is relevant for your system version.
902476 - READ_REPORT_LINE_TOO_LONG dump during upload usingIDOC
Thanks,
Rafael

Error in getting in K_KKB_FIELDCAT_MERGE

Dear friends ,
I am getting following error.Please suggest me solutions.
for more details write to me
Runtime errors         READ_REPORT_LINE_TOO_LONG
Exception              CX_SY_READ_SRC_LINE_TOO_LONG
       Occurred on     25.07.2007 at   20:08:52
The ABAP source code lines are longer than the width of the internal
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSKBH" had to be terminated because one o
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
in debugger
        l_prog_tab_local = i_inclname .
      endif.
      read report l_prog_tab_local into l_abap_source
      check sy-subrc eq 0.
scan abap source for ddic references of fields
      l_tabname = i_tabname.             " FGS
eld names                 1 - 4                    Fi

Hi Juan Carlos,
Have a look at the your dump description...doesn´t the dump points out this?
+
   361
   362 *    class cx_sy_read_src_line_too_long definition load.
   363 *    data: ex_too_long type ref to cx_sy_read_src_line_too_long.
   364 *    try.
>>>>>     read report l_prog_tab_local into l_abap_source.
   366 *      catch cx_sy_read_src_line_too_long into ex_too_long.
   367 *    endtry.
   368     check sy-subrc eq 0.
+
I simulate the same problem in my system... I know it is quite dificult the find the line in a program of 2749 lines...
Pay attention especially to comment lines.
There are also alternative solutions for your problem, but I think since your are on a upgrade project they would not be the nicest solution.
1. Create the fieldcatalog manually, like the post before
or
2. Create a DDIC struture of your internal table, and then you can use the name of the DDIC struture directly with the function you use to show the ALV.
But my suggestion really is to check again the program of a line that seemes to be too long. More than 72 caracters. Make a commet line of the maximum size or maybe less, like for example 70 caracters and than ajust the whole code on this line.
Let me know some news,
Regards,
Marcelo Moreira

The ABAP program lines are wider than the internal table.

Hello;
i use FM REUSE_ALV_FIELDCATALOG_MERGE to fill in fieldcat from an internal table but i receive dump message READ_REPORT_LINE_TOO_LONG. Is there smt. like a type mismatch or waht can that be?
detail explanation of the dump is
The internal table "\FUNCTION=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72 characters wide. The program line is
81 characters wide.
source of the call is like:
DATA: ALV_FIELDCAT     TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE,
      ALV_HEADER       TYPE SLIS_T_LISTHEADER WITH HEADER LINE,
      ALV_EVENTS       TYPE SLIS_T_EVENT WITH HEADER LINE,
      ALV_LAYOUT       TYPE SLIS_LAYOUT_ALV,
      ALV_PRINT        TYPE SLIS_PRINT_ALV,
      ALV_REPID        LIKE SY-REPID,    " program name
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      I_PROGRAM_NAME     = alv_repid
      I_INTERNAL_TABNAME = 'ITAB'
      I_INCLNAME         = alv_repid
    CHANGING
      CT_FIELDCAT        = alv_fieldcat[]
    EXCEPTIONS
      OTHERS             = 3.
thx in advance
Ali

Hi,
At least one line of the source text is longer than the lines of the internal table itab then,
READ_REPORT_LINE_TOO_LONG. error occurs.
Cause: At least one line of the source text is longer than the lines of the internal table itab.
Runtime Error: READ_REPORT_LINE_TOO_LONG
check the link below for further info
http://www.s001.org/ABAP-Hlp/abapread_report.htm
one more thing, whether u have given report name
ALV_REPID = 'ZXYZ'.
if ZXYZ is u r program name

Problem with OSS note

Hello. I do not know if there is anybody in here that has encountered this problem but....
We have NEW GL activated so we have to use transaction FAGL_FC_VAL with program FAGL_FC_VALUATION for closing year and converting some documents from local currency to other currencies.
When I run the program, there is a error concerning string length:
Runtime Errors READ_REPORT_LINE_TOO_LONG
Exceptn CX_SY_READ_SRC_LINE_TOO_LONG.
I have looked for a SAP note that corrects this error. I have implemented it but still...there is no effect. Suggestions?
The error takes place in K_KKB_FIELDCAT_MERGE function at line 366.
I do not thing that trimming the variable from 75 to 72 chars is a solution.
Thank you,
Cristian.

Hi. I have looked for OSS notes for this error. There is a note 1013501 that say this is an programming error and it can be fixed with correction instruction 844370 or install package SAPKH50016.
Still, after implementing the correction instruction, it didn't work.
For the moment I do not want to install packages.
My system is 5.0. Retail configuration.
Could you tell me the line numbers of that code?
Edited by: Cristian Boartes on Dec 21, 2007 4:01 PM

Read report line too long error ?

hi friends.
my program allowed this error.
read_report_line_too_long
what do I do ?
help me please

Don't do any setting changes, try to modify the code if it is custom namespace.
assume this the code with more than 72chars..
read table itab into wa_itab with key matnr = v_matnr vbeln = vbeln transporting something binary search
you have to break that into two lines like the below..
read table itab into wa_itab with key matnr = v_matnr
vbeln = vbeln
transporting something binary search
where ever you find the line more than 72 chars you change it. not event comment lines should not exceed more than 72 chars.
what are you doing exactly can you let me know..
if you are using READ REPORT if you have a program with more than 72 chars length then you will end up with that error. see the standard SAP documentation
DATA prog TYPE c LENGTH 30.
DATA itab TYPE TABLE OF string.
prog = '...'.
READ REPORT prog INTO itab.
Catchable Exceptions
CX_SY_READ_SRC_LINE_TOO_LONG
Cause: At least one line of the source code is longer than the rows of the internal table itab.
Runtime Error: READ_REPORT_LINE_TOO_LONG

Error at XPRA_EXECUTION while installing SAPKINDA7A

Guys,
I face this problem while I was installling SAPKINDA7A (PI 2004.1):
   Program Terminated: (job: RDDEXECL, no. 21323601)
   Execution of programs after import (XPRA)
Job log as below:
   Job started
   Step 001 started (program RDDEXCL, variant, user ID DDIC)
   All DB buffers of application server were synchronized
   Function module MATGRP_OBJ_WRITE_DOCUMENT deleted
   Saved
   Function module WRMA_LIVDT_WRITE_DOCUMENT deleted
   Saved
   ABAP/4 processor: READ_REPORT_LINE_TOO_LONG
   Job cancelled
Appreciate any idea.
Thanks

Ty,
I'm in the process of upgrading the R/3 Plug-in and have received the same error message as you. I have a case open with SAP, but because this is our Development environment, they are not moving very fast on the request. Looking at the root cause, it appears simply to be a program error where the program currently allows 70 characters, but the upgrade wants to insert 72 characters.
I'm sure that you must of resolved this issue by now. Would you be willing to share your solution?
Thanks.
Matthew

BW ABAP program "LOOKUP_FINDER" by Lijo John

Hi everyone,
There is a ABAP program that Lijo John created and posted on the SAP WIKI site that I would like to use in BW but it has an internal error that I was hoping that the ABAP expert forum could help me fix. The WIKI site of his program is:
https://www.sdn.sap.com/irj/scn/wikipath=/display/BI/ABAPprogramtofindBIlookupsandcodePatterns
The error that I am getting is: "READ_REPORT_LINE_TOO_LONG"
It is occuring in the Function Module "K_KKB_FIELDCAT_MERGE" where a 73 characters is trying to be put into a 72 character wide table.
Here is the section of the error report that explains this:
The internal table "FUNCTION=K_KKB_FIELDCAT_MERGEDATA=L_ABAP_SOURCE[]" is 72 characters wide. The program line is 73 characters wide.
I am not an ABAPer and have tried copying the various FM's to 'Z' programs and making the changes to correct this but I just keeping coming up with more problems that I don't understand how to fix. If someone could look at the program and let me know of "simple" fix that I could do I would appreciate it.
Thank you,
Dave

Remove the last line of the program:
It has 73 asterisks and doesn't do anything.
Rob

READ_REPORT_LINE_TOO_LONG

Similar Messages

Maybe you are looking for