If you selected the Standard or Downtime-optimized scenario strategy, you need to choose an execution strategy for the ABAP load generation (transaction SGEN).

You can select one of the following SGEN execution modes:

• Release upgrade only: Do not start ABAP load generation during the upgrade

  Enhancement package installation and SPS update: Do not start ABAP load generation during the update

  If you plan to apply a high number of relevant changes to your system after the update in the form of a transport or a Support Package, we recommend that you generate the ABAP loads manually after the update.

  For more information about starting the load generation manually, see Generating Loads.

• Generate ABAP loads on shadow system during uptime

  With this option, the Software Update Manager uses the maximum number of processes entered below to generate the loads in the shadow system during the uptime.

• Start asynchronously in post downtime

  If you select this option, transaction SGEN automatically starts after the downtime during the Postprocessing roadmap step to regenerate the ABAP loads that were invalidated during the downtime.

• Generate ABAP loads on shadow system during uptime and start asynchronously in post downtime.

  With this option, the Software Update Manager uses the maximum number of processes entered below to generate the ABAP loads in the shadow system during the uptime. The transaction SGEN automatically starts again after the downtime during the Postprocessing roadmap step to regenerate the ABAP loads that were invalidated during the downtime.