ECC 5.0 - Program to check if Z* prograsm have syntax errors

[former_member195355]

Hi,

We're upgrading from 4.6B to ECC 5.0 (we're not going to be switching on the unicode) and so I've been asked to put together a list of all our Z* prograsm that encounter errors.

Rather than going through each and every program, I thought someone may be able to share a program with me?

Anyone got anything useful?

Many Thanks!

[Former Member]

You can use the following approach.

Work with your Basis guys. Get the list of failed transports that were applied to ECC 5.0. Go through the object list of failed transport and see if there are any custom programs locked into that. If yes, then check the transport log to see if there were generation errors. If there were, it means the program has syntax errors.

[former_member195355]

Thansk Sharad,

That is an interesting idea but I was thinking or perhaps automating this checking, rather than manually sitting down and going through all the possible programs...

Does anyone else have any other useful ideas/suggestions?

Thanks!

[Former Member]

How are you going to simulate ECC 5.0 syntax check process in your current 46B environment? Do they have syntax errors now in 46B or you think there may be some? How can they be in production if they have syntax errors? How are you planning your upgrade?

I think what you need to identify is all the custom objects and be prepared with that list. After that you just have to wait for the upgrade to be completed in your development system and see which ones error out and handle them.

If you want to preempt some of these errors, then you may have to go through the release notes and see if there are any function modules, structures etc that are not valid anymore in the new version.

But I don't think it is as easy as one program doing it all.

Srinivas

[Former Member]

Look at RS_SYNTAX_CHECK function module if you are looking at automating the syntax check process.

[thomas_jung]

There is already an SAP utility to do the scan for you. Check out TCode SAMT. If you just want a basic syntax check, copy from the task with Program RSAMTSTD

and Subrountine SYNTAX_CHECK. You can create program sets that narrow down your programs however you like (wildcard on name of program, Dev Class (Package), etc).

[thomas_jung]

I might add what we did.

We upgraded a sandbox system very early in our upgrade project (a great exercise to do right away). We ran the scan in SAMT right after the system was built. This allowed us to see what we were facing in Dev and properly plan for the amount of development time it would take. We were also able to fix some of the problems in advance.

The day we upgraded dev, we ran SAMT again. We worked right off the results listing (errors only) fixing programs. It took 3 ABAP developers about 3 hours to fix the syntax problems, thanks to the fact that we knew what to expect.

I know you said you weren't doing a Unicode conversion, but you can also use SAMT for Unicode Scans as well. The transaction UCCHECK can be used for small scans, but if you want to run a full scan (and save the results); use SAMT with program RSUNISCAN_FINAL and subrountine SAMT_SEARCH.

[former_member195355]

Thanks Thomas!

I really regard you highly and your answer is, as always, concise and full of great info

I'll give this a try tomorrow (I work in the UK and it's way past my hometime), but I think it may well solve our problem - expect an extra 10 juicy point coming your way

Thanks again!