SAP WM Compatibility Scope Check for S/4HANA - step by step guide

How to identify the use of SAP Compatibility Scope

The upcoming expiration of usage rights for SAP Compatibility Scope on 31 December 2025 presents many companies with the challenge of transitioning their existing systems to alternative solutions in SAP S/4HANA. This is particularly relevant for organisations that continue to rely on compatibility packages that are no longer supported in the latest version of SAP.

Recommendation: To fully prepare for the transition, we recommend using both the SAP Readiness Check and the Simplification Item Check. The Readiness Check provides a high-level analysis, while the Simplification Item Check enables detailed checks necessary for the technical conversion. Using both tools together ensures that all relevant compatibility packages and potential risks are identified early. Here is an overview of the SAP Readiness Check.

To ensure a smooth transition, it is crucial to determine early whether and to what extent these functions within the compatibility packages are being used in your system. This can be done by utilising the Simplification Item Check and the Relevance Check. In this guide, you will learn step by step how to identify the use of compatibility packages in your system and what steps are necessary for a successful migration.

Step 1: Ensure report prerequisites

Before starting the Compatibility Check, the following prerequisites must be met:

  • Latest version of the Simplification Item Catalog: Ensure that the latest catalog has been loaded into your system. This catalog contains the relevant simplification items for your SAP S/4HANA version.
    -> Simplification Item Catalog
  • RFC connection to SAP (optional): If your system has an RFC connection to SAP, you can update the catalog directly via the SAP Support Launchpad. Without an RFC connection, the catalog must be uploaded manually.
  • Implement SAP Notes: Before conducting the Simplification Item analysis, it is recommended to implement the following SAP Notes: SAP Note 2502552, SAP Note 1668882, SAP Note 2399707.
    If you are checking a copy of a production system, implement and follow SAP Note 2568736.

Simplification Item Catalog Source
© 2022 SAP SE or an SAP affiliate company. All rights reserved. Image source: SAP Community

Tip: Check whether the catalog should be updated manually or automatically by selecting the option “Upload from RFC system” or “Manual Upload” in the SYCM (Simplification Item Catalog Management) transaction. SAP Note 2399707 describes the minimum required versions, and we strongly recommend always using the latest version of this note to avoid potential errors and issues.


Step 2: Run the Relevance Check via SA38

The Compatibility Scope includes many functions that have been replaced by newer ones or will no longer be supported in the future. To determine whether these functions are being used in your system, run the Relevance Check as follows:

  1. Open transaction SA38.
  2. Enter the report /SDF/RC_START_CHECK in the “Program” field.
  3. Click Execute.

Simplification Item List SAP S/4HANA 2021
© 2022 SAP SE or an SAP affiliate company. All rights reserved. Image source: SAP Community

Important: Perform the consistency check in client 000, as the Software Update Manager (SUM) uses this client to ensure that all relevant data is fully checked. Running the check in other clients may result in missing critical data and undiscovered inconsistencies. -> SAP Note 2399707
Tip: It is recommended to run the check in the production system, as the analysis will only provide meaningful results in this environment. If you are running the check in a system copy, make sure that ST03N data is available (see SAP Note 2568736).


Step 3: Select target version and mode

After starting the program, you have the following options:

  • Select target version: Choose the SAP S/4HANA version to which you plan to migrate or the one you are already using.
  • Select execution mode: You can run the check in online mode or as a background job. The background job is useful if a large amount of data needs to be processed or if the check should run outside business hours.

Tip: Once the check is completed, you can view the results of the last check.


Step 4: Filter Simplification Items

After the check is run, a list of all simplification items that have been checked in your system will be displayed. To display only the compatibility packages, you need to filter the list:

  1. Go to the Category field.
  2. Set the filter to “non-strategic” or to options explicitly marked as outdated or no longer actively developed.
  3. Filter the list of items so that only the compatibility packages are shown.

Important: Perform the consistency check in client 000, as this is the client the Software Update Manager (SUM) uses during the technical system conversion. This ensures that all relevant data in the system is analysed.


Step 5: Check the Relevance of Compatibility Scope

non-strategic-function
© 2022 SAP SE or an SAP affiliate company. All rights reserved. Image source: SAP Community

In the filtered list of the Compatibility Scope, you will see various relevance icons:

  • Green checkmark (irrelevant): The item is part of the Compatibility Scope, but it is not used in your system.
  • Yellow checkmark (unknown relevance or probably relevant): You need to check whether the affected functionality is being used in your system.

Step-by-Step:

  1. Double-click the ID of the respective simplification item to display detailed information about it.
  2. In the Relevance Check section, you will find information about tables, functions, and transactions affected by this Compatibility Scope.
  3. Check your system to see if these elements are used in production.

Step 6: Review Business Impact Notes

Each simplification item has a corresponding Business Impact Note, which provides detailed information about the affected functionality and transitioning to alternative solutions in SAP S/4HANA:

  1. In the “Note” column, you will find a link to the Business Impact Note.
  2. These notes often contain further details about the transition, technical mappings, or reports to facilitate the process.

Technical Summary with a Warning
© 2022 SAP SE or an SAP affiliate company. All rights reserved. Image source: SAP Community


Step 7: Check IDOC Usage

An important part of the check is reviewing the use of IDOCs in your system. Many IDOCs may be part of the Compatibility Scope, so it is important to identify them early.

  1. Go to transaction SYCM.
  2. Filter by the Non-Strategic category.
  3. Select the object type IDOC.
  4. Copy the displayed list of IDOCs to your clipboard.
  5. Go to transaction EDIDC in your production system.
  6. Paste the list of IDOCs and check which incoming and outgoing IDOCs are being used in your system.

Display Simplification Database Content
© 2022 SAP SE or an SAP affiliate company. All rights reserved. Image source: SAP Community

Tip: Be mindful of retention periods for IDOCs in your system, as deleted or archived IDOCs can affect the results.


Step 8: Further steps for unclear relevance

If the relevance of a compatibility package is unclear, take the following steps:

  1. Check in the Details section whether an implementation of a check class is required to successfully run the report.
  2. Follow the instructions in the related SAP Note to ensure that all relevant check classes are installed and active.

Data Browser - IDOC Selection Screen
© 2022 SAP SE or an SAP affiliate company. All rights reserved. Image source: SAP Community


Step 9: Completion and migration planning

After identifying all relevant compatibility packages, you should plan the next steps for the migration. Consider the following points:

  • Adapt custom code: If your custom code uses compatibility packages, it must be adapted.
  • Data migration: Existing data must be migrated to alternative solutions.
  • User training: Your staff should be trained to use the new functionalities.

Important: Regularly run the Simplification Item Check throughout the project to ensure that no new inconsistencies arise. Experience shows that many inconsistencies emerge during the project implementation. By repeating the checks regularly, you can avoid delays during the system conversion.


Conclusion: Early identification and review of the compatibility packages used is essential for ensuring a smooth transition to the new SAP S/4HANA functionalities. Use the step-by-step guide above to identify the relevant areas and develop a solid migration strategy.

 

If you need support with the analysis or migration, feel free to contact us. We offer tailored consultations and solutions to make your SAP system future-proof.

 

 

 

 

 

Author Information
Marek Siudmak

Author
Marek Siudmak

Marek Siudmak has been an SAP consultant since 2007 and has served as Managing Director of agisolo GmbH since June 2021. As an expert in SAP EWM and its integration with adjacent modules (SD, MM, QM, PP), he has contributed to over 20 successful full cycle SAP projects, optimising warehouses. His broad experience spans national and international projects in various industries, and he continues to support companies in the implementation and integration of SAP S/4HANA.

MORE BLOGPOSTS

agisolo ©️ 2024