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.

Similar Messages

'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

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

XPRA_EXECUTION error while PI upgrade

Hi
I ran into an issue upgrading the R3 plug-in from PI from 2002_1_470 to
2004_1_470 in SAINT. The update terminated during phase XPRA_EXECUTION with dump READ_REPORT_LINE_TOO_LONG. We are on 4.7 with HPUX and Oracle. Could'nt find much help in Notes or online. Any help will be appreciated.
The log file in SAINT shows this error
"Program terminated (job: RDDEXECL, no.: 07431301)
See job log
Execution of programs after import (XPRA)
End date and time : 20071204074418
Ended with return code: ===> 12 <==="
The trace file is as shown below.
Mon Dec 3 17:33:15 2007
ABAP/4 Program SAPMV80H .
Source MV80HF0A Line 751.
Error Code READ_REPORT_LINE_TOO_LONG.
Module $Id: //bas/640_REL/src/krn/runt/abdbif4.c#3 $ SAP.
Function readreport Line 982.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end no http/smtp
RABAX: end RX_BTCHLOG|RX_VBLOG
The ABAP source code lines are longer than the width of the internal
table..
***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12372]
ThWpRestart: restart wp (pid=706) automatically
WARNING ==> PfFileIndUpd: new starttime < starttime
Disconnecting from ALL connections:
Thanks
Vic

Hi Vic,
I was trying to draw your attention to the cause of the error. To me I think you may have missed some Basis support pack.
I suggest you raise an OSS message if you are unable to reset the SPAM/SAINT Queue.
Regards,
Siddhesh

Can you read Reports and Tables through RFCs and BAPIS?

Is there any way to read established reports and tables through RFC or BAPI function calls? We have a middleware that can execute various BAPIs and RFCs. I see a few promising ones: RFC_READ_REPORT, but no examples anywhere what the parameters needed are for the inputs.

Hello Scott,
Check below FMs for reading tables and programs.
Tables : RFC_READ_TABLE
Program : RFC_READ_DEVELOPMENT_OBJECT
Please note that for reading program using RFC_READ_DEVELOPMENT_OBJECT , lines in program should not exceed 72 chars else FM will throw dump(READ_REPORT_LINE_TOO_LONG).
Program code will appear in table QTAB which is 72 chars wide.

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

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.

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.

'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

Going to dump

Hi Abapers,
I have done one alv which was executing fine. suddenly it went to dump
Runtime error: READ_REPORT_LINE_TOO_LONG.
please help me... very urgent....
points will be rewarded.

Hi Premraj,
In SE38 from the top menu, goto Utilities --->Settings
in the ABAP editor tab open editor tab
you will see a checkbox at the bottom "Downward-Compat.Line Length"
Check this checkbox and activate your program.
I hope this will resolve the problem.
Regards,
Pankaj Sharma

Lock ups and dumping psyical memory!!!

Hi i have just installed a new pc most of the stuff im useing is from my old computer so i know they work fine im running a:
P4 3GHZ Prescot 800MHz, HT-Enabled
865PE Neo2-P
512 DDR-400 Twin moss
ATI Radeon 9000 pro
PSU-400
XP Pro
My computer locks up alot when running intense games (games have worked before no problem) i also get a error saying dumping pysical memory, i have looked about and tried to solve this myself, i found that someone was haveing the exact same problem as me and he fixed it by turning the FSB down as his memory wasnt compatable with his motherboard if doing that works how do i do it ?
Many thanks Jonathan

Flappa, Your memory " clock" is fine and there is no need to "underclock it" as long as you did not mess with the Bios.
I had the same problems. I could not even get thru a Clean install of windows as it would Blue Screen
1- are you running in " Dual Channel Mode"?
2- If so is your memory a " match Set"?
some times memory even thought it has the same markings is not matched . Dual channel sets are matched and made to run together in "Dual Channel Mode"{
( Even though I had the same manufacturer memory my set would not run in Dual Channel without " Blue Screening" I bought a Matched Set of Kingston Valueram and have not had a problem since
3- If it is not a matched set, pull one stick out and run it for a while , if it still bluescreens try the other stick
4- raise your memory voltage to 2.7 or 2.8 ( which ever is the lowest that it runs stable)
5- If all this does not work , run MEMTEST to see if there is a problem with both sticks
6- you are running a Bios Version that supports the " Prescott Microcode" right?
Let us know what your findings are
Good Luck
Dave

Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
    When changing or deleting one or more lines of the internal table
    "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
    the line index. An index less than or equal to zero is not
    allowed.
    The error can occur when using the following options:
    1. "INDEX idx" for specifying the line number in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
       where you want to change, insert or delete.
    2. "FROM idx" for specifying the start index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    3. "TO idx" for specifying the end index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    At the time of the termination, the table contained 17008 lines.
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TABLE_INVALID_INDEX" " "
    "J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
    "FILTER_DATA"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...

Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash

Short dump 'Table does not exist in database'

Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
    Table does not exist in database.
What happened?
    The table or view name used does not
    exist in the database.
    The error occurred in the current database connection "DEFAULT".
What can you do?
    Check the spelling of the table names in your report.
    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_NATIVE_SQL_ERROR', was not
     caught in
   procedure "DYN_LIC_SEL_TOT" "(FORM)", 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:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.

Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.

Short Dump while scrolling in a maintenance view

A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.

Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay

Is it possible to create manually a dump?

Dear all,
I have a question about Dumps created in SAP while programs run with unpredicted errors.
I have a specific table defined in the dictionary which has two coloumns progId and path.
The first one is a unique identifier given to a program and the second column is an absolute path on the
unix server where SAP is installed.
For example
MyProg | /usr/tmpbatch/data/E200
Means that the ABAP program named 'MyProg' will run and its output file (the output of the program) and the
log file are created in /usr/tmpbatch/data/E200.
In each of my programs, first of all I check the content of this table in order to ensure that the path is defined for the
given program (and therefore I may be able to create avec success both output and log files). If there is no entry
in the table for the given program, I leave the program by calling the STOP instruction.
My programs run at night, so the next day the corresponding users read the content of the generated output/log files.
As a result, if the path is not defined properly for a given program in the table, the program is not run and therefore
there will be no output/logfile the next day.
My question is How can I inform the user who arrives the next day observing that one program has not been run? How
can I tell him by some kind of system message that the program exited because the path for the files had not been defined in
my table?
Each morning, we can analyse the dumps which were produced during the precedent day. So that we may know
(approximately) what went wrong. But as far as I know, dumps are generated automatically by the system. Is it possible
to generate a dump (by calling some fucntion) with an appropriate error message for my problem?
Thanks in advance,
Dariyoosh

Hello again,
First of all I would like to thank everybody for their attention to my problem and
for spending time for answering my question. Thank you all very much.
Currently, Thomas' solution about MESSAGE_TYPE_X seems to work pretty well
for my problem. As all of you mentioned that, there should be softer methods to inform
users. One main problem is that the program which lanuches my programs during night
is not a sap user, it is a Unix scheduler (please forgive me I don't know these administration
details and how they work) so according to what the administrator told me it is not possible
to send email. As a result, I think I may go with MESSAGE_TYPE_X until I found another proper way.
Once again, thank you all for your help.
Kind Regards,
Dariyoosh

Dump READ_REPORT_LINE_TOO_LONG

Similar Messages

Maybe you are looking for