topic Re: Run time error in Application Development and Automation Discussions

Run time error

Former Member — Wed, 17 Dec 2008 06:33:02 GMT

Hi experts,

It was working properly in 4.6C after upgradation into EEC 6.0 When we excute this ALV Report it is going to dump.

Plz tell me the reason i am attaching screen shot here with,

rror 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 "ZFINRR2012" 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

82 characters wide.

Thanks in advance

Re: Run time error

Former Member — Wed, 17 Dec 2008 06:38:14 GMT

HI,

Please have a look into this.....

The internal table "\FUNCTION=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72

characters wide. The program line is

82 characters wide.

Here I think you are calling a new program by using READ REPORT....

When ever we are reading a report, the entire code will be stored in the form of an internal table whose width will be 72 characters.

So better format your called program to adjust below 72 lines. I think then it will not give any errors.

Thanks & regards,

Venkatesh

Re: Run time error

Former Member — Wed, 17 Dec 2008 07:02:41 GMT

Hi,

I used fm like this

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

i_program_name = w_repid

i_internal_tabname = p_tabname

I_STRUCTURE_NAME =
I_CLIENT_NEVER_DISPLAY = 'X'

i_inclname = w_repid

I_BYPASSING_BUFFER = 'X'
I_BUFFER_ACTIVE = 'X'

CHANGING

ct_fieldcat = t_fieldcat

EXCEPTIONS

inconsistent_interface = 1

program_error = 2

OTHERS = 3.

Plz give me advice

thanks

Re: Run time error

rainer_hbenthal — Wed, 17 Dec 2008 07:06:09 GMT

What part of "your code contains lines with at least 82 characters in length but the FM only allow 72 characters" you didnt understand?

Re: Run time error

Former Member — Wed, 17 Dec 2008 07:08:10 GMT

HI,

Are you getting any more run time errors ?

Regards,

Venkatesh

Re: Run time error

Former Member — Wed, 17 Dec 2008 07:11:51 GMT

Hi,

My program code does not contain more than 72 char but comments have more than 72 char eventhough

it will be get dump.

plz give me suggession

thanks

Re: Run time error

Former Member — Wed, 17 Dec 2008 07:26:43 GMT

Check the settings click the check box Downward Comp Length length 72.

Then also use Pretty printer and try

Regards

Shiva

Re: Run time error

rainer_hbenthal — Wed, 17 Dec 2008 11:35:28 GMT


> Hi,
> My program code does not contain more than 72 char but comments have more than 72 char eventhough
> it will be get dump.
> plz give me suggession
> 
> thanks

You are kidding, arent you?

Again, what part of "your code contains sourcelines with 82 chars abut only 72 chars are allowed" you didnt understand?

Re: Run time error

Former Member — Mon, 22 Dec 2008 11:43:55 GMT

Hi, what have you used in w_repid variable???

Re: Run time error

Former Member — Fri, 16 Jan 2009 11:10:33 GMT

Hi ,

This kind of an error occurs if in your source code you have exceeded the length.

Cut short all your lines of code to that maximum or still even lesser than that and it will work fine.

The problem is with creating the Field Catalog using the REUSE_ALV_FIELDCATALOG_MERGE.

So ensure that all your lines are within the range.

Even if you build your filed catalog not using this FM it would work.

Regards,

Radhika.

Re: Run time error

Former Member — Fri, 16 Jan 2009 11:27:50 GMT

Hi Srinivas,

I also came across through same run time error, if possible for u , u can try this, copy all your code into another new report and execute it, might be it will work, as it worked for me.

regrds

Regards

Vinod