cancel
Showing results for 
Search instead for 
Did you mean: 

READ_REPORT_LINE_TOO_LONG dump during import of SAPKE60043

Former Member
0 Kudos

We are getting the ABAP Dump- READ_REPORT_LINE_TOO_LONG dump during import of SAPKE60043.

The import of SAPKE60043 is terminating in stage XPRA_EXECUTION due to

the following dump :-

Runtime Errors READ_REPORT_LINE_TOO_LONG

Exception CX_SY_READ_SRC_LINE_TOO_LONG

The foolowing are our current support pack levels :-

SAP_ABA 700 21 SAPKA70021 Cross-Application Component

SAP_BASIS 700 21 SAPKB70021 SAP Basis Component

PI_BASIS 2005_1_700 21 SAPKIPYJ7L PI_BASIS 2005_1_700

ST-PI 2008_1_700 0 - SAP Solution Tools Plug-In

SAP_BW 700 23 SAPKW70023 SAP NetWeaver BI 7.0

SAP_AP 700 19 SAPKNA7019 SAP Application Platform

SAP_APPL 600 15 SAPKH60015 Logistics and Accounting

SAP_HR 600 42 SAPKE60042 Human Resources

The ABAP dump details are as follows :-

Runtime Errors READ_REPORT_LINE_TOO_LONG

Exception CX_SY_READ_SRC_LINE_TOO_LONG

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 "REPORT_VORHANDEN" "(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:

There was an attempt to read program "RPCASFG0" 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 "\PROGRAM=RPUCT300\DATA=RPRO[]" is 72 characters

wide. The program line is 79 characters wide

Can anyone please advice ?

Regards

Arun Brelvi

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear All,

  • Make sure that the program statement should not exceeds to 72 Characters. Just delete the text or move any statement to next line when any statement goes beyond 72 Characters.
  • Even commented code also need to check that should not be greater than 72 characters.
Former Member
0 Kudos

From the dump file, we can see the following:

-


The reason for the exception is: There was an attempt to read program

"RPCASFG0" 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 "\PROGRAM=RPUCT300\DATA=RPRO[]" is 72 characters

wide. The program line is 79 characters wide.

-


The program RPCASFG0 has two lines (commentaries) which are larger than

72 characters (the limit for the internal table

\PROGRAM=RPUCT300\DATA=RPRO[])

-


FUGBLGP "CD GBLGP

*Start of changes| GUPTAM| ED1K900373| 14/05/2009| to incorporate PRD

changes.. <----


FUZZNIC "CB ZZNIC

*End of changes| GUPTAM| ED1K900373| 14/05/2009| to incorporate PRD

changes.. <----


-


To fix this issue during XPRAS phase, just change those commented lines

(maybe break them in two parts). After that, continue with SPAM.

Former Member
0 Kudos

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.

Things to Keep in mind while creating a field catalog through 'REUSE_ALV_FIELDCATALOG_MERGE'.

  • Make sure that the program statement should not exceeds to 72 Characters. Just delete the text or move any statement to next line when any statement goes beyond 72 Characters.