Conversion to SAP S/4HANA using SUM: ABAP Systems on UNIX and Linux

Checking Pool and Cluster Tables

We recommend checking all pool tables or cluster tables in the source system before the migration.

Context

For example, you can check whether

  • corrupt or initial cluster records exist

  • the pool tables contained in a certain table pool are readable

  • the BCD numbers in a table, which you must specify individually, are correct

We recommend that you perform the check using the cluster data check that is integrated in SUM. To use it, select the option Check Cluster Data in the initial dialogues of the Software Update Manager, which are described in the SUM Guide in section Making Entries for Scenarios Without Configuration File.

This check is similar to the SAP_BASIS report SDBI_CLUSTER_CHECK. It is performed by the R3load executable in discard mode and uses the same technology as the benchmarking tool. However, the check integrated in SUM is more performant than the report SDBI_CLUSTER_CHECK. Its runtime is significantly lower because the check can work with highly parallelized processing.

In addition to the report SDBI_CLUSTER_CHECK, further reports are available such as SDBI_POOL_CHECK. For more information about the cluster data check and the reports, see SAP Note 1784377 Information published on SAP site.

Procedure

  • Option 1 (recommended): Check cluster tables using the built-in cluster data check.

    In the initial dialogs of SUM to get the roadmap, select the scenarios without configuration file and choose Check Cluster Data. Then follow the instructions in the subsequent dialogs.

  • Option 2: Check pool and cluster tables using the reports that are described in SAP Note 1784377 Information published on SAP site.