Objective:
This FAQ provide answers to commonly asked questions regarding SGEN. We have gathered few commonly asked questions about SGEN from our customers. Please review the information below:
What is SGEN?
SGEN is the transaction to generate ABAP loads for large numbers of programs, function groups, module pools, and so on as well as Business Server Page applications (BSP applications).
SAP Note 379918 contains report name and table name which are used during SGEN execution. Report RSPARAGENLOD, RSPARAGENJOB and RSPARAGENER8 are replaced by RSPARAGENLODM, RSPARAGENJOBM and RSPARAGENER8M respectively in the latest version. table GENSETC is replaced by GENSETM.
SGEN execution consists two parts. The first part determines the so-called generation set through the options given in the first screen. generation set is stored in table GENSETC or GENSETM. The second part is compiling source code into load. this part is triggered by background job RSPARAGENER8 or RSPARAGENER8M.
Where can I find more information about SGEN?
You can go to SGEN transaction and click the pushbutton Information. there is detail explanation about how to use the transaction. You can also go to SAP online help and search SGEN.
When should I run SGEN?
SGEN is designed for large-scale program generations. You can consider to use SGEN in following scenarios. SAP Note 438038 and 162991 explains other generation tools as well.
How to improve SGEN performance?
Compared against the calculation of SGEN generation set, the second part of SGEN takes longer time. However, the second part is out of control of SGEN. This is SAP system related and depends on resources of the system itself like main memory, number of CPU and last but not least, the database performance. The runtime of the generation jobs is heavily depending on the database performance of the system. If you noticed that generation job long time, you can following below:
- Make sure there is enough system resource (CPU, memory) and free background work processes. SAP Note 1651645 describes a known issue.
- Make sure that database performance is fine. Please involve your database expert if necessary.
How to handle generation system error?
You need to analyze SM37(Job name:RSPARAGENER8 or RSPARAGENER8M), SM21, ST22 and ST11.
How much free space is required in database for SGEN execution?
If you want to regenerate loads, make sure that there is enough space available in the database. The space required can be several hundred MB. Generation over all components requires around 2 GB of free space.
See Also:
162991 - Generation tools for ABAP programs
379918 - Redesign of the SGEN transaction
413912 - Shorter runtime for specifying generating quantity
438038 - Automatic regeneration of invalidated loads
589124 - Performance improvements when Support Package imported
1132507 - SGEN: Using maximum number of free work processes
1147789 - SGEN does not generate all loads after release upgrade
1230076 - Generation of ABAP loads: Tips for the analysis
1630356 - SGEN terminates after 500 generation errors
1645864 - SGEN generation errors do not cause an error message
1651645 - Maximum number of SGEN processes cannot be greater than 9
1869363 - SGEN: Correction for selection of WebDynpros / BSPs
ℹ Note: For more information please refer to SAP Note 1989778 - FAQ: SGEN |
Also refer to SAP System Upgrade & Update Troubleshooting Wiki Space for any information needed before a system upgrade & update.
Please leave any feedback in the comments section below. You can also post any questions in the .
James Wong
