topic Re: Code inspector problem in Application Development and Automation Discussions

Code inspector problem

RicardoRomero_1 — Thu, 01 Mar 2012 17:16:54 GMT

Hi all,

I'm checking the syntax before to release my order requests and I have several errors in code inspector.

Ok, I've fixed these errors. The problem is if I execute the code inspector again the errors are displayed again... but the code is ok, there are no errors.

It happened to me a lot of times, with several object types, may be the next day if I pass the code inspector the errors dissapears or may be not.

It's very strange. I've tried with other users, doing log off and login again... but nothing...

Do you know if exits some transaction code for "refresh" the code inspector? the buffer or something?

Thanks in advance.

Re: Code inspector problem

RicardoRomero_1 — Thu, 01 Mar 2012 17:50:59 GMT

With transaction /$sync I've solved some of these problems, but others still appears...

Re: Code inspector problem

marcin_cholewczuk — Thu, 01 Mar 2012 18:30:09 GMT

Hi,

I've worked with code inspector quite a lot and I've never spoted this kind of problem. I would suspect that this is not code inspector problem but rather something is wrong with your repository objects.

If I were you I would try to debug code inspector. There is somewhere inside SCAN ABAP-SOURCE command used. Check what input is being used.

Marcin Cholewczuk

Re: Code inspector problem

Former Member — Fri, 02 Mar 2012 05:41:24 GMT

Hi,

we had code inspector failures after an incomplete basis support stack upgrade on one of our development systems. They were remaining until the next support stack upgrade had been finished successfully.

Regards,

Klaus

Re: Code inspector problem

former_member222709 — Fri, 02 Mar 2012 05:43:02 GMT

Hi Ricardo,

When I faced a similar kind of a problem of irrational behaviour of the system, it was traced to be a BASIS issue. Please consult with your BASIS Team about insufficient disk space or any Patch upgrades that have happened in the recent past with errors.

Regards,

Pranav.