Symptom
From the transaction code SM37, you can see below error on SGEN process. Double click on see long text for details.
Received Task: 7 at 184013 with SY-SUBRC = 0 onreturn TSGEN Generation stopped due to 522 generation errors (see long text) TSGEN Job cancelled after system exception ERROR_MESSAGE 00
Generation stopped due to 522 generation errors (see long text) Message no. TSGEN228
Caused
Unable to generate many objects (the generation status displays the value ‘E’, meaning that no syntax errors are involved). There are several reasons for why these generation errors may occur. The most frequent cause is that the tablespace containing the load tables is full.
Solution
1. Execute transaction code SM21, ST22. Analyze and determine the cause of generation errors. Most probably it was caused by the tablespace free space. You can check the tablespace from transaction code DB02. If this the caused, you will need to extend the tablespace.
2. All the generation status are stored in table GENSETC. You can use the generation status of the objects in the database table GENSETC to determine how many objects:
Were generated successfully (GENSTATUS ='X'), Are currently being processed (GENSTATUS ='P'), Are still in initial status (GENSTATUS ='I'), Showed a syntax error durin generation (GENSTATUS ='S') Showed an error of a different type (GENSTATUS ='E').
3. After you have extend the tablespace. You can resume the generation after it has been stopped, choose the generation task ‘Regenerate the objects of the last run’ when you recall transaction SGEN and then choose ‘Resume’. The servers that you select for parallel generation must have the same machine type as those before the generation was stopped. The transaction now resets the generation status of all objects with generation errors (GENSTATUS =’E’) to ‘I’ (initial). If you now restart the generation, all objects that have not yet been edited (GENSTATUS =’I’) are generated.
