Automatic Regeneration of Invalidated Loads (SAP Library - Technical Operations Manual for mySAP Technology)

Automatic Regeneration of Invalidated Loads

Use

To minimize waiting times for users or developers by regenerating invalidated loads, you can schedule the report RSGENINVLAS to run periodically, such as every night. RSGENINVLAS automatically regenerates all invalidated ABAP loads for every machine type that exists in your system.

Note

The load of an object is invalidated if, since the time the load was generated, activated changes were made to the object or to objects used by this object, such as includes or tables.

The load format depends on the machine type.

Prerequisites

ABAP loads can be invalidated for a variety of reasons. Typical causes during operation are:

Activating a DDIC object invalidates the loads of all ABAP objects that use the DDIC object.
After changing and activating an ABAP object, only the load for the machine type of the current server is generated. The load for other machine types in a heterogeneous system remains invalidated.
Importing Support Packages leads to the invalidation of the loads of the ABAP objects that are contained in the Support Packages. In addition, the DDIC import means that the load of the user of the imported DDIC objects must be regenerated.
When importing transports, the load of the imported ABAP objects and the user of the transported DDIC objects also become invalidated.
Applying kernel patches may lead to the invalidation of all loads.

Activities

To use the functions of RSGENINVLAS, you must schedule the report with job name RSGENINVLAS to run periodically in the background (for example, transaction SE38 ® Execute ® Background ® Schedule ® Schedule Periodically). We recommend that you schedule the report for times when the system load is low, such as every night.

At runtime, RSGENINVLAS automatically defines the invalidated loads of the possible different machine types in your system. It then starts the parallel generation (report RSPARAGENER8 of transaction SGEN), where it incorporates the available servers of your system into the parallel processing, for each machine type.

When you call transaction SGEN while the report RSGENINVLAS is running, you are given information on the Job Monitor Screen regarding the progress of the generation. Here you can also stop the current generation, if required. For more information, see the job logs of the jobs RSGENINVLAS and RSPARAGENER8 (you can view these from Job Overview on the Job Monitor screen, or by calling transaction SM37).

The date and number of generated objects of each run of the report is stored in the GEN_HISTORY table. The entries are ordered chronologically for each machine type, giving you a compact overview of the regenerations of invalidated loads.

The report RSGENINVLAS enhances the functions of the SAP Load Generator (transaction SGEN) by including the automatic regeneration of all invalidated loads. The advantages of this are:

The generation effort of the user/developer is kept to a minimum.
The generation runs for example at night, or at other times where the system load is low.
To implement the functions of RSGENINVLAS, you only have to schedule the report to run periodically.
Memory space problems in the database, which would cause the system administrator to get involved, cannot occur, since purely invalidated loads are regenerated.