Certain transactions re-compile everyday after upgrade to NW2004S

[Former Member]

Hi,

We recently upgraded to NW2004S from 4.6C. I have users telling me that certain transactions re-compile every morning, notably IB12, IW37, 40 and 41 amongst others.

Has anybody else seen this happen?

I have checked the programs that are behind these transactions and they are active, yet still the transactions compile.

I am also wondering whether this is gui related.

We are using 6.40 patch level 21.

Any pointers are welcome.

Thanks

Stuart Banner

[Former Member]

HI

Please execute the sgen with the option "Regenerate Existing Loads"

This task allows you to regenerate all ABAP loads and invalidated loads that exist in your system, and to generate loads for objects of a Support Package queue. The following options are available to you:

Generate all Objects with Existing Load

Only Generate Objects with Invalidated Load

The load of an object becomes invalidated if changes have been made to the object or to the objects used by this object, since the moment the load was generated. Examples of such objects are includes and tables. This may occur by importing a Support Package ( SPAM) or a kernel patch.

If you want to generate loads for objects of a Support Package queue, start the task after importing the queue. The task determines the generation set using the invalidated loads in the system. In contrast with the Generate objects of a transport request task, this task also takes into account ABAP loads that were invalidated by modified Dictionary objects.

After choosing this task, a screen appears which allows you to search for the name of the transport request using the selection button, or to specify it directly.

Regards

Anwer Waseem

SAP BASIS

[Former Member]

Actually guys, thanks for all your suggestions.

I sent a message to SAP and they suggested running a $SYNC on all the app servers affected without any other app server up. Since I only have a db server and an app server, I shut the app server down and did the $SYNC on the db server, then brought the app server back up. No re-compiling so far.

Thanks again for your help.

Stuart Banner

SAP Basis Team

First Energy.

[Former Member]

Hi Stuart,

Have you checked to see if there is a time difference between these servers and the workstations? A difference between these might kick these recompiles off.

Hope that helps.

J. Haynes

Denver

[Former Member]

Hi Joe,

The workstations and the servers get their time from the same source.

Thanks

Stuart

[Former Member]

Have you run SGEN after the upgrade ?

select the option 'Regenerate After an SAP system upgrate'

should do the trick.

[Former Member]

James.

SGEN was run after the upgrade was complete.

These re-compiles are happening at the beginning of everyday.

Thanks

[Former Member]

Hi Stuart

We had a similar issue after upgrading to NW 7.0. After each client copy some transactions where compiling at the first execution. SAP Note 1115677 fixed our problem then.

If you are not client copying, then you have to dig further:

- start with one problem transaction

- find the abap program behind that transaction, it might be displayed in the sapgui just click at right bottom corner

- use transaction SE38 -> report RSDEPEND -> enter the abap program

Now you can see further depending programs and compilation details. Every time of the abap load is older, than the source, the load will be recompiled. This might be caused by a transport, a bug, or something like that.

Best regards, Michael