SAP Readiness Check for SAP ERP Usage and Data Profiling

To prepare for an S4HANA migration, you can use the SAP Readiness Check for SAP ERP Usage and Data Profiling. This analysis will provide data insights in your current ERP system usage.

Tool installation and run

The tool can be installed by applying OSS note 3112362 – SAP Readiness Check for SAP ERP Usage and Data Profiling. Transport this note to your productive system. The tool needs to have the actual production data. Start program RC_UDP_COLLECT_ANALYSIS_DATA:

Start with the Schedule Analysis. A batch job will collect the data. Once done, you can use the Display Analysis Data button to see the results. The Download Analysis Data allows you to download the data. The data needs to be uploaded to the SAP Readiness site.

Tool result

After uploading to the SAP readiness site, give SAP about one hour to process the data.

Then the analysis result is available:

From left to right:

  • Detailed data profiles
  • Module based data profiles
  • Top list of data volumes

Zoom in on the module based data profiles:

For each part, you can now drill down to table level:

This way you can see if a certain S4HANA change will have much impact or not (due to amount of records).

SUIM_CHDOC_USER: new transaction to show user changes

In SUIM there is a function to show changes for users, but this transaction can be performing very poor with higher data volumes.

SAP has developed successor transaction SUIM_CHDOC_USER that is giving the same data, but faster.

How to get transaction SUIM_CHDOC_USER?

It is import to know transaction SUIM_CHDOC_USER only works on HANA database. If you are not running on HANA, don’t continue.

Implementation steps:

  1. Apply OSS note 3399100 – SUIM | change history calculation for user/profile assignment
  2. Apply OSS note 3418682 – SUIM_CHDOC_USER | Implementation prerequisite for SAP Note 3405921. Run the generation program.
  3. Apply OSS note 3405921 – SUIM | Read Change Documents for User. Important here: do execute the manual steps here first. These final steps are NOT covered in the previous note.


Now you can start transaction SUIM_CHDOC_USER:

Input is the same as you were used to. Output as well. The new transaction is simply faster.

PFCGMASSDELETE: mass deletion of roles

To get the function for mass role deletion, you first need to apply OSS note 3360981 – PFCGMASSDELETE: Mass deletion of roles.

Mass deletion of roles

After the note is applied transaction code PFCGMASSDELETE can be started:

The I information button provides the description of the functions of the program:

The SCC4 functions are described in OSS note 1723881 – Application of client-specific customizing settings to role maintenance.