Phases Running ABAP Programs

These phases use the SAP system to operate. If you improve the performance of the SAP system, this can speed up these phases.

Phases TABSPC_PREP and CNV_LIST

You experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST. Although you have applied the actions recommended in SAP Note 871455 , the runtimes of the phases have not decreased considerably.

Proceed as described in SAP Note 762426 .

Phase RUN_RDDIT006

This phase analyzes the SAP system to find objects modified by the customer and customer objects. Therefore, the runtime of phase RUN_RDDIT006 is longer for SAP systems with many modifications or customer objects. Since this phase starts an ABAP program, you can use the respective ABAP transactions to analyze the performance of this phase.

DIFFEXP Phases

Since these phases perform copy-to-shadow actions or export the transport requests generated during phase RDDIT006, they take longer for SAP systems with many modifications or customer objects.

SHADOW_IMPORT Phases

Release upgrade only:

These phases import the upgrade data into Customizing tables, as well as the transport requests of add-ons, support packages, and languages. During this phase, only the part for the shadow system is imported. The remaining parts are imported during the TABIM_UPG phase. These phases take longer for upgrades where many add-ons and support packages have been included in the upgrade or where many languages have to be imported. The duration of the import also depends on the number of clients in the system.

If you chose the scenario strategy Standard or Downtime-optimized, it uses the number of parallel background processes that you have entered during phase INITSUBST.

SPS update only:

These phases take longer if you have included many support packages.

Phase PARCONV_UPG

In this phase, tables are converted to the target release structure. The PARCONV_UPG phase uses the number of parallel background processes you specified and three tp processes.

The runtime of this phase can be longer for the following reasons:

• Very large tables have to be converted. The tables that are converted are listed in the analysis file, which also displays the conversion time for each table.

• If tables get a new index on the target release or an index needs to be regenerated, these tables are listed in the analysis file under DDLs. The time needed to create the index depends on the size of the table.

• In case of other DDL statements, the runtime of ALTER TABLE or ADD FIELD statements with fields that contain default values depends on the size of the table.