topic Re: Extended Program Check Errors in Application Development and Automation Discussions

Extended Program Check Errors

Former Member — Mon, 09 Oct 2006 17:37:34 GMT

I am running SLIN against some code. I am getting 240 red error messages, like the one shown below. The line number noted does not correspond to anything in my source code. In fact, in a lot of cases, it corresponds to a line containing only a comment.

How should I interpret these messages? Could they be reporting on obsolete code in type group source modules, etc, that my code is referring to?

For instance, no where in my source code do I use "OCCURS", yet that is being flagged.


The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
The addition OCCURS is no longer supported in the OO context. Use "TABLE OF ...
INITIAL SIZE" instead.
The message can be hidden with "#EC *)

Re: Extended Program Check Errors

Former Member — Mon, 09 Oct 2006 17:41:17 GMT

That definition of internal table might be in any include. so search globally for OCCURS, as you are telling double click on that error is not giving any good information.

Thanks,

Srikanth.

Re: Extended Program Check Errors

Former Member — Mon, 09 Oct 2006 21:18:46 GMT

Hi,

In abap OO context you can not create a table with header line.

It seems you are usingtables with header line in Object Oriented context of your code, that is the reason its giving such error.

You can avoid such error messages by declaring the tables with out header line or the message hidden by "#EC *

Regards,

Azaz.