Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SGEN/RSPARAGENER8: transactions are still compiling with first call


we did an upgrade from SAP R/3 4.7 to SAP ECC 6.0.

During installation report RSPARAGENER8 is started through upgrade program. This report took a long time in our system - about 140.000 seconds. In summary of generation 212.837 objects were successfully generated.

We chose "standard resource use" (there SGEN is included).

After finishing upgrade (including SPAU) I tried a standard transaction like VA03 - report SAPMV75A - and system is compiling program.

Same manner with ME23N and other transactions.

I thought SGEN is used to avoid this?!

During releasechange on sandbox system I had same problems. I started SGEN report after upgrade manually with option "New generation after upgrade", but transactions where still compiling with first call.

This is the summary generation of the Job RSPARAGENER8:

1) Information on the generation set

Selected generation task:

Generation of all invalid loads

Data basis: all_components


The load format corresponds to the machine type 391 .

The generation set comprises 213.883 objects.

212.837 objects were successfully generated.

1.046 objects show (syntax) errors.

(Further information can be found in db table GENSETC.)

2) Runtime statistics

The generation required 142.067 seconds

(resp. 1 day, 152747 (hhmmss)).

The generation rate averages 1,51 objects per second

(resp. 5.436 objects per hour).

In table GENSETC I can see for example for program SAPMV75A:

Status of generation: X

What can I do that SGEN is working properly?



Not what you were looking for? View more on this topic or Ask a question