SAP Community - SAP Readiness Check

Prepare your Selective Data Transfer to SAP Cloud ALM with SAP Readiness Check for SAP Cloud ALM

2024-06-12T09:58:09.325000+02:00

Dear All,

Note: This blog describes the addition of the Scope Analysis for Selective Data Transfer capability available within SAP Readiness Check for SAP Cloud ALM. You may refer to this blog for an overview of the other checks available in SAP Readiness Check for SAP Cloud ALM.

This blog was updated on 6/04/2025 with information about the new matrix "Used Solution Documentation Relations" - see the Branch Data section.

Today, we are excited to announce that SAP Readiness Check for SAP Cloud ALM has been extended to provide insights into solution documentation data in an SAP Solution Manager system in preparation for a solution documentation Selective Data Transfer project.

With the Selective Data Transfer tool in SAP Solution Manager, you can select and extract the data in a format compatible with SAP Cloud ALM. The process to transfer the data is structured in the following steps:

Step 1: Process hierarchy (folder, scenario, organizational unit, master data)
Step 2: Process steps and executables
Step 3: Business processes and diagrams
Step 4: Documents and test steps

The new Scope Analysis for Selective Data Transfer allows one to view all solutions and branches in the analyzed SAP Solution Manager system, providing the necessary insights to select a source branch for a Selective Data Transfer project from SAP Solution Manager to SAP Cloud ALM.

Scope Analysis for Selective Data Transfer - Overview

The overview in the dashboard summarizes the total number of solutions and branches in the SAP Solution Manager system. Additionally, the bar chart displays the total number of changes to the elements within the branches. You can switch between views showing the last 6 or 12 months to see the aggregated number of changes to branches within these two time periods. The chart displays the top 5 solutions, based on the number of changes. When you navigate to the detail page of this analysis, you can see the aggregated number of changes for all solutions.

For more information about Selective Data Transfer from SAP Solution Manager to SAP Cloud ALM, see Transition to SAP Cloud ALM for Implementation in SAP Support Portal.

Scope Analysis for Selective Data Transfer - Details

The detailed view provides information for all solutions in the analyzed system, including a summary of the changes to solution documentation elements recorded in the solution documentation history. You may navigate the solutions using the sidebar panel on the left side of the page. When you select a solution in the sidebar, the details of the solution are presented in the content panel. For each solution, the following information is displayed:

Solution Data: This tab displays general information for the solution, including created logical component groups, solution settings, public scopes, used custom attributes, and used business partner attributes relevant to preparing SAP Cloud ALM for the data transfer from SAP Solution Manager.
Branches: A tab for each branch in the solution displays the solution documentation elements that are part of each Selective Data Transfer process step. The details include the number of objects within the specific branch and the number of changes recorded in the last 6 or 12 months from when the data collector ran in the SAP Solution Manager system.
In the case of Step 4 of the Selective Data Transfer process, the number of documents and test steps, along with the total size in mebibytes (1 Mebibyte = 1.024^2 bytes), are displayed.
The analysis also shows which solution documentation elements aren’t part of the selective data transfer process. These objects are excluded because an export tool is not planned or there is no equivalent entity in SAP Cloud ALM to support the import.
The list of used logical component groups provides insight into which group is referenced by at least one solution documentation element within the corresponding branch.

Solution Data

This section displays general information for the solution, like the created logical component groups, solution settings, public scopes, used custom attributes, and used business partner attributes relevant to preparing SAP Cloud ALM for the data transfer from SAP Solution Manager.

Additionally, this section presents the configurations and customizations that need to be adapted or mapped to correctly transfer the selected branch data into SAP Cloud ALM.

The following configurations are displayed in this tab for the selected solution:

Logical Component Groups: Displays a table with the logical component groups created in the selected solution, with the information on whether sites are enabled and if the logical component group is referenced for any solution documentation element in any branch within the solution.
Configurations:
- Document types: Provides the number of custom document types in use.
- Status Schemas: Provides the number of custom status schemas in use.
- Content Languages: Provides a list of languages active in the solution.
Scopes: Shows the list of public scopes that exist in the solution.
Custom Attributes: Shows the list of custom attributes in use.
Business Partner Attributes: Shows the list of related business partner attributes used by at least one document in the solution.

Branch Data

This section details the solution documentation elements of each step within the Selective Data Transfer process. The details include the number of objects in a branch and the number of changes recorded 6 or 12 months before the data collection in the SAP Solution Manager system.

Additionally, it includes the list of elements from the solution documentation that aren’t part of the selective data transfer process. These objects are excluded because an export tool is not planned or there is no equivalent entity in SAP Cloud ALM to support the import.

The information for each branch is displayed in the same structure as the Selective Data Transfer process is expected to run. The details provide insights into how each branch is used, the elements changed in the last 6 or 12 months, and the expected sizing the future content management server should have to support the documents from the SAP Solution Manager system.

The number of changes for all solution documentation elements is obtained from the history of the solutions, and the figures for the last 6 or 12 months are calculated from the data collection date.

Note: The solution documentation elements in and out of scope depend on the current SAP Solution Manager transition strategy to SAP Cloud ALM and may change anytime.

Update on 6/04/2025:

The branch section now shows a matrix with the relation between the elements in solution documentation that are used and supported by both SAP Cloud ALM and the Selective Data Transfer Tool. The matrix shows where the branch contains data for these relations and combination with the availability, it helps to determine if the complete transfer of the solution documentation to SAP Cloud ALM using the Selective Data Transfer tool is possible.

Data Collection

The SAP Solution Manager data collector has been updated to include the required data for the new Scope Analysis for Selective Data Transfer capability. Ensure that version 31 (or higher) of SAP Note 3236443 is implemented before running the collector program in your SAP Solution Manager system. You can either create a new SAP Readiness Check analysis or update an existing analysis using the Update Analysis function to upload the enhanced data collection archive.

As always, we look forward to receiving your feedback!

Your SAP Readiness Check Team

New SAP Activate road map version "24Q3 " – Transition to SAP S/4HANA (on premise)

2024-08-01T18:29:31.734000+02:00

We are happy to announce the new release of the SAP Activate Methodology for Transition to SAP S/4HANA, the implementation roadmap which is intended to guide the project team step by step through the implementation of SAP S/4HANA on premise.

What we have changed for you:

Many new / updated accelerators linking you to great information sources you probably would miss otherwise. Want some examples?
- SAP Signavio customers can import and use an interactive "Activate Accelerator" which is describing in detail how the SAP Signavio suite can support them in SAP S/4HANA implementations.
- Here is an updated cookbook on "Employee Business Partner Integration".
- Don't miss the updated "Manifesto for senior IT leadership". Although targeting to private cloud, on premise customers can easily identify what is relevant for them.
- We added information on "SAP Cloud ALM vs. SolMan". In case you go with SAP Cloud ALM, this Best Practice document provides information also for on premise implementations (compressed on 300 pages).
- What I like very much is the SAP BTP Guidance Framework. It bundles information for both architects and developers: Architecture guidance, methodologies and developer guides are right next to each other.
The whole topic of enablement / learning has been restructured. It is now harmonized across the roadmaps in SAP Activate.
We also enhanced the content for system conversion. You will find new activities / tasks like "Conversion Readiness Assessment" or "Decide on Conversion Strategy", and we will continue on this topic in future.

You can find the new release of the “Transition to SAP S/4HANA” roadmap in the “SAP Roadmap Viewer”. And as you already know, we will push the updated content into SAP Cloud ALM for you within the upcoming days.

Hopefully you will enjoy it!

New Release of SAP Activate Methodology for SAP S/4HANA upgrades

2024-08-02T08:52:44.920000+02:00

Dear All,

we are happy to announce the new release of the upgrade roadmap for SAP S/4HANA (on premise), the SAP Activate Methodology for SAP S/4HANA upgrades.

Note: We have also updated the implementation roadmap for SAP S/4HANA (on premise), if you want to see the details, check this blog.

In this new release of the roadmap for SAP S/4HANA upgrades, we focussed on the topic of enablement / learning which has been restructured. It is now harmonized across all the roadmaps in SAP Activate.

In addition, we added some thoughts about introducing Artificial Intelligence with the next upgrade and introduced the PE service offerings AI Strategy service and Architecture Point of View: Artificial Intelligence.

Are you already in the middle of your upgrade project and use the roadmap tasks in SAP Cloud ALM? Here is how you can check the updates we delivered with the new roadmap release:

On the Overview page in SAP Cloud ALM for Project and Task Management, you find the tile "SAP Content Update Summary".

This card displays the number of new, updated, and obsolete tasks that are part of the last roadmap update in context with your project. By reviewing this summary, you can quickly identify the changes and take the necessary actions in your project. Simply click on the bubbles to review the task list. Whenever an update is made to the roadmap tasks, project leads also receive a recommendation with 'Warning' prompt, to assign a team member as 'Responsible' for the new tasks.

For further details, check this blog.

As always, we are interested in your feedback!

SAP S/4HANA Migration: Insights and Guidance for IT Leaders

2024-09-06T15:18:23.761000+02:00

As organizations worldwide continue to navigate the complexities of digital transformation, many that still rely on SAP ERP or the on-premises version of SAP S/4HANA are considering a major change: migrating to the cloud. This move isn’t just about a technical upgrade; it’s a strategic decision that could shape the future of your business. To help you get started, we’ve completely updated our guide, Mapping Your Journey to SAP S/4HANA, with practical insights, step-by-step instructions, best practices, and detailed background information.

Keeping up with the fast pace of digital change isn’t just beneficial — it’s essential. Industries like automotive, with their complex supply chains, clearly demonstrate the risks of not adapting quickly. That’s exactly why we created the original guide back in 2018, which quickly became a go-to resource for many companies. Now, I’m excited to share that we’ve just released a fully updated edition.

This edition brings together insights from dozens of SAP experts across the company, each sharing their unique perspectives and experiences. Inside, you’ll find a comprehensive guide that covers every aspect of the transition to SAP S/4HANA Cloud Private Edition. We’ve focused on the key technology elements to help IT decision-makers confidently plan their roadmap, avoid common pitfalls, and ensure a smooth path to a successful go-live.

What makes this guide special is the wealth of knowledge it offers — drawn from thousands of successful transformation projects. It’s more than just a collection of tips; it’s packed with real-world experience, brought to life with clear text and visuals. Since every project is unique, we’ve included plenty of links to additional resources so you can rely on this guide at every step of your migration journey. The feedback from our customers speaks for itself: the guide has been downloaded more than 180,000 times since it was first published.

Why an update to our key reference

You may be wondering why a new edition, and why now? As one of the co-authors, I can tell you that while we’ve always kept the guide up to date, the past six years have seen major changes in the SAP landscape. New tools and methods have emerged, and our RISE with SAP offering has grown significantly. These developments have changed the way we help customers move to Cloud ERP, so it’s the perfect time to update the guide with these innovations and the valuable feedback we’ve received from our customers and partners.

Our goal with this guide remains the same: to give IT leaders everything they need in one place to successfully implement SAP S/4HANA Cloud Private Edition. We've carefully organized the guide into three key chapters.

1. Strategic decisions

In the first chapter, we’ll help you make smart choices about the transition. We cover everything from deciding between public and private cloud options to understanding the unique benefits of the GROW with SAP and RISE with SAP programs, and even navigating the complexities of cloud operations.

2. Ingredients for project success

The middle section delves into the critical factors that determine the success of your project. We discuss change management, knowledge management, customer and supplier master data integration, the partner ecosystem, and more.

3. Essential tools from SAP

The final chapter provides an in-depth look at the 15 most important tools available to help you assess your systems, plan and execute the migration, and track project progress. These include SAP Data Services, SAP Readiness Check, ABAP development tools, and the SAP S/4HANA Migration Cockpit.

More than just a guide, Mapping Your Journey to SAP S/4HANA is your trusted companion as an IT leader navigating a complex transformation. Whether you’re diving into the theory or need practical tips to keep your organization on track beyond 2027, this guide has you covered. You can read it cover to cover for a complete understanding or use it as a quick reference for specific stages or challenges.

I invite you to download it today and take the next step in your digital transformation journey: Download now

Insights into Change Request Management usage with SAP Readiness Check for SAP Cloud ALM

2024-11-06T08:52:22.660000+01:00

Please note: The following blog describes the new Change Request Management Insights functionality available within SAP Readiness Check for SAP Cloud ALM. You may also refer to the other blogs about features in SAP Readiness Check for SAP Cloud ALM:

Prepare your Selective Data Transfer to SAP Cloud ALM with SAP Readiness Check for SAP Cloud ALM

Service and Administration Capabilities in SAP Readiness Check for SAP Cloud ALM

SAP supports your transition to SAP Cloud ALM with SAP Readiness Check

Availability of SAP Readiness Check for SAP Cloud ALM

Dear All,

Today, we are excited to announce that SAP Readiness Check for SAP Cloud ALM now provides additional insights into the usage of Change Request Management capabilities in an SAP Solution Manager system to support the planning of the transition of your change-controlled landscapes to SAP Cloud ALM.

The new Change Request Management Insights check reads and collects the usage details for all active change cycles in your SAP Solution Manager system. It allows you to quickly identify the usage of individual change request management capabilities within each cycle and see which systems of your landscape are managed by each cycle.

Change Request Management Insights - Overview

The chart in the dashboard card summarizes the total change documents created within the active cycles, aggregated by transaction type. This chart provides an overview of the change types being managed within the change cycles in your change-controlled landscapes. Note that only active cycles at the time of the data collector run are used to create this analysis. The data collector ignores closed change cycles; as a result, they are not considered within the statistics displayed in the findings of this check.

Select any item from the pie chart or the dashboard card header to open the detail view.

Change Request Management Insights - Details

The detail view provides complete usage figures for the analyzed change cycles. The information includes, for example, the aggregated number of change documents and transport requests, the integration of change documents with Solution Documentation, and the number of tracks the cycle controls.

The provided details help identify the change cycles that control most of the changes, where large or complex landscapes are being managed, and which change cycles use complex change request management scenarios. These insights help to plan the transition to SAP Cloud ALM. For example, it might be advisable to start with transitioning simple landscapes and continue with other more complex landscapes at a later stage.

The two charts on top of the detail view provide filtering options for the Items table below:

You can filter by Active Change Cycle Type by selecting a type in the pie chart at the top-left of the page.
The Usage of Change Request Management Capabilities Across Cycles chart at the top-right of the page allows for the filtering of the Items table based on capability.

Additional Information for Change Cycles

For each change cycle in the table, click the number of a Cycle ID to open a side panel with additional insights. This panel provides the details of the tracks, showing the systems and roles that are part of the change-controlled landscape. In addition, it shows how many Requests for Change and Change Documents have been created within the cycle, aggregated by transaction type. The Usage section of the panel provides the date of the latest usage of the individual change request management capabilities, helping to identify those capabilities not used recently.

The SAP Readiness Check for SAP Cloud ALM scenario already provides details for the availability of equivalent capabilities in SAP Cloud ALM for each displayed change request management capability. To see if required capabilities are already available or planned in SAP Cloud ALM, you can navigate directly to the Availability of Relevant Capabilities dashboard using the provided link at the bottom of the Usage section within the right-side panel.

Data Collection

The SAP Readiness Check for SAP Cloud ALM data collector, which runs in SAP Solution Manager, has been updated to include the required data for the new Change Request Management Insights capability. Ensure version 43 (or higher) of SAP Note 3236443 has been implemented before scheduling the collector. Once the data collector is complete, you can use the generated data archive to create a new SAP Readiness Check analysis or update an existing analysis (using the Update Analysis function to upload the enhanced data collection archive).

As always, we look forward to receiving your feedback!

Your SAP Readiness Check Team

Compatibility Scope Matrix for Production Planning.. 2025 is around the corner!!

2024-11-06T17:24:12.839000+01:00

The Readiness Check Report helps us understand the mandatory changes when moving from ECC to S/4HANA or just upgrading to the newest version on S/4HANA. Through this information, all the customers will be able to plan their projects accordingly to have the system ready for a smooth transition. From a functional perspective, this report shows us 2 main pieces of information, the first one is the Simplification Item list, which highlights the mandatory changes and the items that are out of the architecture target in S/4HANA and won't be considered for further innovations. The second one is the Compatibility Scope Matrix, which lists the compatibility packages (CP), this contains the details of the functionalities that have a limited use right to SAP S/4HANA and recommends the solution alternative and the strategy to move forward.

This blog will explain the common items relevant as part of the compatibility scope under the Production Planning module, describing the details and the alternative function to be considered when replacing it. Functions that are part of the compatibility scope can be used just until the expiry date of the compatibility pack license, meaning at the end of 2025. Even when SAP recently announced the maintenance extension for SAP Business Suite 7 until the end of 2027, the usage rights of the compatibility packs were not included in this extension.

Luckily and because the complexity of each item, there is a specific extension of compatibility scope usage rights for a few modules until 2030. Under manufacturing, this applies to selected items under the component of Production Planning in Process Industry (PP-PI). If you are interested in checking the full details list of the compatibility Scope Matrix please review the attachments of SAP Note 2269324. There you will find the components marked with (D), meaning whose are the items relevant for the extension.

My intention through this blog is to mainly aware and remind all the readers about what items are relevant considering the timing! But in the end, is up to each customer to decide when they will keep it or will start to migrate to the designated alternative functionality. The decision, of at which point in time this will be done, should be taken early in advance to plan accordingly for the migration efforts!! Keep in mind the end of 2025 is around the corner!!

Now, let’s get started and finally introduce some of the items for the Production Planning scope. Keep in mind this list doesn't contain a description of all of them, just explains the common items that I typically see relevant, based on my experiences with multiple customers.

Classical MRP list: This is one of the main items, and in most cases applies to those customers who are still running the classic MRP as part of their process. The majority decided to keep it due to the restriction by using MRP live and/or some custom developments where MRP list tables need to be read. In S/4HANA the MRP live code has an optimized logic, where is no longer needed the creation of an MRP list without causing a huge concern from a performance point of view. In addition, the evaluation based on the MRP list isn't optimal because is not going to consider new requirements that could be created meanwhile the finished of the MRP run and the real-time when the planners have to do the checking, because is just and snapshot of the result.

In general, the creation of the MRP list by running the classic MRP won't be possible anymore after the end of 2025, but the classic MPR will still work for those customers that have other restrictions to be considered before moving to MRP live.

Now what happens if we still need the MRP list creation? The best suggestion will be to check always read stock/requirements lists via API MD_MDPSX_READ_API or BAPI BAPI_MATERIAL_STOCK_REQ_LIST., as suggested in the SAP Note 2268085. In addition, SAP offers the standard report RMDMRPEXTRACT01, which extracts the planning data and saves it into a custom table, similar to the results generated by the MRP list. You can find more information about the MRP lust alternative by checking the blog MRP Lists are gone with MRP Live! What should I do now?

Flow Manufacturing: Flow manufacturing in ERP includes functions for line design, line balancing as well and rate/takt-based sequence planning. It is part of repetitive manufacturing solution and only suitable for repetitive manufacturing planned orders. Because is now part of the compatibility scope, means that you need to migrate from ERP line design, ERP line balancing, and ERP sequence planning to its designated alternative functionality which is now fully covered by PPDS model mix planning and sequencing.
Graphical Planning Table: Currently there are a bunch of troubles and open incidents due to the complexity when managing the chart and graphical planning tables provided in SAP GUI. Even when the transactions CM21, CM22, CM23, CM25, with graphical planning table or Gantt Chart are still available in SAP S/4HANA on-premise are not part of the target architecture in S/4HANA and remain as obsolete. To have a better user experience and make easier the understanding and the analysis by the planners, the recommendation is to replace those by using new Fiori Apps like "Manage Work Center Capacity", "Capacity Scheduling Table", and "Capacity Scheduling Board" in SAP S/4HANA. If you are interested in knowing more about this new application on PP-CP, please check my previous blog: Did you know this about Capacity Planning in S/4HANA?

In addition, you can consider SAP Digital Manufacturing Cloud - DMC component Resource Orchestration REO. REO works on more granular data defined in DMC. In a job-shop environment, for example, work-centers could be defined in SAP S/4HANA and the individual machines only in DMC.

Last but not least, is important to know you can also have the possible to use embedded PP/DS if exists complex scheduling problems, for example, planned and production orders of different BOM levels need to be synchronized, or if material availability needs to be considered in scheduling, or if multiple bottleneck resources must be aligned by optimizing the schedule.

Logistics Information System In PP: LIS data can be analyzed based on statistical data, which is contained in "information structures". Important key figures are directly updated from the operative application to the information structures. Where historically, Historically, following LIS tables (mentioned below) were used for standard or custom reports in Production Planning (S021, SFIS, S022, SFIS, S023, SFIS, S024, and S026). However, LIS in PP is part of the S/4HANA compatibility pack and even when you can continue using LIS tables, and are available, won’t be considered as part of the new technologies anymore.

Considering future production analytics will be based on HANA, CDS views will be able to aggregate transactional data dynamically, and powerful analytical UIs for multi-dimensional reporting, resulting in the best option to replace the current LIS. Once switching you will note improvements in the performance of many transactions (fewer tables to update, fewer locking conflicts) and less memory consumption. Please refer to the following blog for further information: Custom Analytical Queries as an alternative for LIS in SAP S/4HANA Production Planning (PP)

Forecast-Based Planning: Forecast-based planning (MRP type VV) is not strategic anymore within SAP S/4HANA and should be avoided if possible. This is because the MRP creates planned orders or purchase requisitions if the total forecast demand up to a certain point of time exceeds the total firmed receipt quantity up to the same point of time. The total firmed receipt quantity includes inventory, production orders, purchase orders, firmed planned orders, and firmed purchase requisitions.

An alternative exists and is by using PIRs (Planned Independent Requirement) instead of forecast demands. Provides several advantages in S/4, allowing benefits like APIs available to handle PIRs, new FIORI-apps like 'Maintain PIRs' for better management, PIRs allow for consumption with sales demands and dependent requirements or stock transfer demands, the possibility to split PIRS and re-organize unused PIR demands.

So what should we do if MRP type VV is still in place? First, convert forecast requirements into planned independent requirements (PIR) and then change MRP type VV to one of the MRP types as PD, P1, P2, P3, or P4 which doesn’t have direct consideration of forecast.

Control Recipes/Instructions: Due to the several improvements in the used communication technology (currently via t-RFC), the usage of control recipes/control instructions in conjunction with browser-based PI sheets and work instructions is part of the SAP S/4HANA compatibility scope. As an alternative, it is possible to keep using the control recipes/control instructions in conjunction with linking process control systems and other external systems by using Manufacturing Execution Connect (classic).

SAP S/4HANA provides new Process Order integration capabilities with new SOAP and oData APIs, where the Control Instruction capabilities will be offered now as part of SAP Digital Manufacturing Cloud and can be sent to MES, e.g. to SAP Digital Manufacturing Cloud, with new SOAP APIs. Please refer to SAP S/4HANA Feature Scope Description or note 3035649 FAQ : Manufacturing Execution Connect (classic).

A similar recommendation applies for Process Messages, also an item relevant for PP in compatibility scope, you can check further details on the SAP Note 2270231

Process Instruction Sheets: Browser-based PI sheets are used in the regulated environment (pharmaceutical production, and so on) to control and track the production execution. The content of the PI Sheet/Work Instruction is rendered as plain HTML and displayed in the SAP HTML Viewer of ABAP SAP GUI screens and depends on MS Internet Explorer. The new architecture recommends the usage of Digital Manufacturing Cloud’s (DMC) Production Operator Dashboard (POD) which provides similar functionality as PI-sheets. It will allow displaying Work Instructions, recording of actual data, and enforcing predefined production processes.

Please be careful and after switching from browser-based PI Sheets/Electronic Work Instructions to SAP DMC, remember to check your custom code in the context of data transfer from browser-based PI Sheets/Electronic Work Instructions to whatever receiver and clean up your custom code that makes use of this functionality.

Hope you find helpful the information provided in terms of understanding the compatibility pack and start to think about the action plan to complete the replacement of the function and adopt the S/4HANA strategy within the given timeline.

Further information:

SAP Support Portal

The Future of Compatibility Packs in SAP S/4HANA

Do not forget to follow us via @SAP and #S4HANA, or myself via @Jennicherrera and LinkedIn: Jennifer Carolina Herrera Suárez | LinkedIn

Have a nice day!

Regards

Jennifer

SAP supports your transition to SAP Cloud ALM with SAP Readiness Check

2025-01-23T11:15:42.570000+01:00

Please note: The following blog recaps the SAP ALM Summit EMEA in autumn 2024, where the transition journey from SAP Solution Manager to SAP Cloud ALM, supported by SAP Readiness Check, was a central topic.

For information about features and functionality of SAP Readiness Check for SAP Cloud ALM, you may also refer to the following blogs:

Prepare your Selective Data Transfer to SAP Cloud ALM with SAP Readiness Check for SAP Cloud ALM

Insights into Change Request Management usage with SAP Readiness Check for SAP Cloud ALM

Service and Administration Capabilities in SAP Readiness Check for SAP Cloud ALM

Availability of SAP Readiness Check for SAP Cloud ALM

One central topic on the SAP ALM Summit EMEA in autumn 2024 was the transition journey from SAP Solution Manager to SAP Cloud ALM, supported by SAP Readiness Check.

You may recap the SAP ALM Summit EMEA sessions on youtube:

SAP Readiness Check for SAP Cloud ALM - Introduction

With SAP Readiness Check for SAP Cloud ALM, SAP provides a self-service tool to analyze an existing SAP Solution Manager system in preparation for a transition to SAP Cloud ALM. SAP Readiness Check for SAP Cloud ALM helps customers to better understand the usage of their SAP Solution Manager system, and to plan and scope the transition of application lifecycle management capabilities to SAP Cloud ALM. This transition can be performed either completely or by taking a capability-by-capability approach. SAP Readiness Check provides a mapping of equivalent capabilities between SAP Solution Manager and SAP Cloud ALM, while also showing the availability status of capabilities in SAP Cloud ALM. It also helps customers to engage with partners and SAP to discuss options for the most appropriate transition plan.

Learn more in this blog post and the following assets:

SAP Activate Roadmap "Transition to SAP Cloud ALM"

The SAP Activate roadmap provides comprehensive guidance on the transition from SAP Solution Manager to SAP Cloud ALM in the well-known format of SAP Activate Best Practices. Read the Transition Planning deliverable in the Discover phase to learn how SAP Readiness Check supports the transition from SAP Solution Manager to SAP Cloud ALM, and the underlying tasks:

Perform SAP Readiness Check for SAP Cloud ALM
Define Project Scope and Objectives
Define capability scope for transition to SAP Cloud ALM

Go to the SAP Activate Roadmap

Services for SAP Cloud ALM

SAP offers services which help you with your transition to SAP Cloud ALM:

Services for SAP Cloud ALM

Check the Application Lifecycle Management page for Transition to SAP Cloud ALM to learn more, from the strategy overview and a functional comparison of SAP Solution Manager and SAP Cloud ALM, to recommended transition steps and transition support.

Business Partner Synchronization: defining the phases of conversion

2025-02-25T19:05:26.320000+01:00

Introduction

When migrating from SAP ECC to S/4HANA, there are preparatory steps that need to be done before the actual system conversion. There may be some clients that even prefer to have the pre-conversion steps implemented through pre-projects before closing the deal with the ultimate conversion project, as mentioned here. This is widely recommended especially because some of these steps don’t affect the day-to-day system functionality and can be implemented without impact on SAP ERP. Nonetheless, in all possible project scenarios, the customer/vendor synchronization is mandatory as a pre-conversion step for S/4HANA conversion due to the Business Partner Approach, meaning that the business partner is now the leading object for legal entities. Being so, the BP synchronization can be achieved by following the steps of the well-known KBA 2713963. When doing this activity for a big pharmaceutical client in Brazil, I have faced a complex scenario where I had to elaborate a flowchart to facilitate the definition of phases of conversion, which appeared difficult to assess at first glance. In this blog post I am going to disclose details about this flowchart to help others that may have the same complex scenario.

The scenarios

1. Keep the same numbers between BP and customer/vendor

A question that must be answered is if there is a desire to keep the business partner and the customer/vendor with the same number. This means that when maintaining the entity’s master data in transaction BP, the number entered is the same used in the creation of transactional documents.

In the above example, customer 11 has the same number as its BP, but the vendor doesn’t. If it is not mandatory to keep the same one, then the BP range number can be configured independently, and the BP conversion is not complex in terms of number assignment. But if there is the desire to keep all possible numbers the same, then an analysis must be done of the current account groups range number customizing, using transaction OBAR and OBAS together with XDN1 and XKN1, which may culminate in the next scenarios.

2. Customers/vendors out of the current customized number range

As well described in SAP documentations about BP conversion, all created customers/vendors are scope of the conversion, even though they are marked for deletion, unless they are archived. This means that in some scenarios, the number of an old customer or vendor may be out of date, because its account group number range could have been changed through time.

The result is existing customers/vendors with a number range different than the current customizing for its account group in OBAR/OBAS, like in the above example, where the customer highlighted is a DEBI, which is configured to numerate from 900000 to 999999, therefore its number “1” is out of date. If this is part of the project scenario, then these entities with old range numbers can have their number reassigned*.

*Of course, the number reassignment is only an option. Even though the number may be out of the current customized range, one can always do a temporary configuration just to run the BP synchronization for these customers/vendors and then configure back to the current customizing. But this could result in several phases of conversion in production system, that may not be feasible in certain clients. Also, as standard the transaction BP shows a warning message when the number range of the opened BP is out of the current number range customized, so this may not be desirable.

3. Customers and vendors with same number

The last check that can be made is if there are customers and vendors that do not belong to the same legal entity but have the same number. This happens because the account groups for customers are different elements in SAP than the account groups for vendors, meaning that they can have the same number range.

As the business partner is now the leading object and have only one central number range configured, if a customer and vendor have overlapping numbers and do not belong to the same legal entity, one of them would need to have its number reassigned, because only one corresponding BP with this number can be created.

Phases of conversion

The result is two amounts of customers/vendors to be converted: those that are going to have its number kept, and those that are going to have its number reassigned. The BP conversion for these entities must be done in two phases, because they demand different number range configuration. Note that the steps for the CVI configuration regarding number ranges are very well documented on SAP S/4HANA Cookbook CVI, so in the next topics only the specific customizing are going to be commented.

1. Customers/vendors that are going to keep the same numbers in BP

To run the synchronization in this phase, the flag “External” must be checked in BP number range transaction BUCF, and the “Same number” field must be flagged in the assignment between BP grouping and account groups, in transactions V_TBC001 and V_TBD001.There is a KBA 24303080 describing this scenario. After running the BP conversion, then the next phase can be started.

2. Customers/vendors that are going to have the BP number reassigned

In this phase, the remaining entities are going to have their number defined internally according to the BP number range customizing, so the flags described in the previous phase must be unflagged.After finishing this conversion, it is likely that for the account groups that share the same range number with BP groupings, the numbers used in BP are different than the used in account group, meaning that for the same range, the “NR Status” is different between BUCF and XDN1/XKN1.It is highly important that these numbers be equalized after the conversion.

An important observation is to make sure to use CVI_COCKPIT filters to capture only the desired customers/vendors for each phase, being the selection by number the most recommended. Additionally, as after the conversion any new customer or vendor created in XK01 and XD01 will synchronize a BP automatically, a final request must be transported to production system to make sure those flags are back in place for the automatic BP creation. Finally, note that the BP number is only relevant to the transaction BP, meaning that the number used in transactional documents is untouched.

Conclusion

In this blog post it was possible to establish a flow of questions and decisions to achieve the phases of conversion in a BP synchronization step as a SAP ECC to S/4HANA pre-conversion project.

This flowchart can be used as a guide to analyze the scope of customers/vendors' number range in client’s scenario.

As mentioned before, the CVI conversion is very well documented by SAP and the steps of configuration and synchronization are described accurately in the official Cookbook. It is recommended that one reach this CVI Cockpit FAQ, as this is a very complete blog post that contains answers to most of possible scenarios that a client could have.

I hope I helped you organize the thoughts regarding the range numbers on complex master data scenarios based on an experience that I had, please comment below if you have any further. questions.

S/4Hana Brownfield Conversion Project

2025-03-06T17:06:34.720000+01:00

First, the system needs to be prepared, that is, the ECC system is moved to the S4 HANA structure by technical consultants (BASIS-ABAP). For this, they upload the relevant sap notes to the system and create a sandbox system. All module consultants provide testing and controls in this test system, then if necessary, the 2nd sandbox system can be installed as a development system or directly to the QA system, then the live system will be switched.

Throughout the project you will hear the following terms very often SI Check List and SI items

SI: Simplification Item.

Technical consultants run Simplification Item Check Report and if there is an error or inconsistency, they assign it to the relevant module consultants.

All module consultants check their own inconsistencies and errors and make the necessary corrections.

go to se38 /SDF/RC_START_CHECK

You can check SI ıtem and sap notes in this report

SAP Readiness Check Cloud Application

ZIP files are created and uploaded to the SAP Readiness Check Cloud App. The data here can be read by consultants and verified before being uploaded to the application.

For more information on this part, see this video published by SAP

https://support.sap.com/content/dam/SAAP/SAP_Activate/RC_Version_3.mp4

After this technical transition, module consultants start working on the transaction codes, tables, structures that change with S4 Hana in the sandbox system.

The most important topics are as follows;

-CVI integration, also called BP Configuration

-Transfer of price and credit master and credit management and control of the changing structure

For example, additional processing is required for Condition Master Data mappings because the data will now be used in the PRCD_ELEMENTS table instead of the KONV table. For more detailed information you can take a look at this note

https://me.sap.com/notes/2267308

If there is a Rebate Process, the Settlement management- conditon contract structure that comes with S/4 Hana can be recommended or not configured

If there are licensed products such as DSD, Aatp, etc., their licenses will be renewed and system connections will be made so that they can be used in S/4. For more detailed information, you can take a look at these notes

Aatp

https://me.sap.com/notes/2267745

https://me.sap.com/notes/2209696

Rebate

https://me.sap.com/notes/2267377/E

Except for these

Some data model simplifications have been implemented for the SD field. Removed status tables VBUK-VBUP instead status fields have been moved to tables VBAK and VBAP for orders, LIKP and LIPS for deliveries, VBRK for billing documents for more details https://me.sap.com/notes/2267306

Instead of S066, S067 tables used in Credit Management, UKMBP_CMS_SGM & UKMBP_CMS tables came in S/4 Hana. For more details https://me.sap.com/notes/2270544

For Customer master data, KNA1, KNB1, KNVV, KNVP tables were used in ECC System. BP master data will be created in S/4 Hana, BUT000-BP: General data I BUT100-BP: Roles tables will be used.

Apart from these, there are CVI_LINK tables. Customer-BP and Vendor-BP information is kept in these tables. When the numbers do not match, it can check through these.

Customer-BP table V_CVI_CUST_LINK

BP and Supplier table V_CVI_VEND_LINK

I would be happy to read your thoughts and comments and if there are better ways to fulfil the requirement, please leave them in the comment section below.

Thanks so much

SAP Readiness Check for SAP S/4HANA now supports SAP S/4HANA private Cloud / RISE Target Versions

2025-04-14T17:32:18.629000+02:00

Dear All,

SAP Readiness Check for SAP S/4HANA can now be used for both SAP S/4HANA (on premise) and SAP S/4HANA Cloud Private Edition (PCE/RISE) target product versions.

SAP S/4HANA and SAP S/4HANA Cloud Private Edition are developed in the same codeline and are identical concerning the relevant simplification items. Nevertheless, there are differences in the compatibility scope items and successor functionalities (for example the successor of FI-TV on premise is Travel Management, on PCE the successor is SAP Concur).

The correct target SAP S/4HANA version is selected in the dropdown list in the SAP Readiness Check data collection report RC_COLLECT_ANALYSIS_DATA:

Please note: To see the "SAP S/4HANA private Cloud" entries in the list, you may need to update your local replica of the simplification item catalog.

To determine whether any action is required, go to transaction SA38 in the system to be analyzed and run report RC_COLLECT_ANALYSIS_DATA. If the SAP S/4HANA private Cloud versions are not yet visible in the Target S/4HANA Version list, the local replica of the simplification item catalog needs to be updated.

To update the Simplification Item Catalog, perform the following steps:

Execute the report /SDF/RC_START_CHECK in the source system via transaction SA38.
Choose the Update Catalog with latest version from SAP button.

As a result, the local replica of the simplification item catalog will be updated. You can now run report RC_COLLECT_ANALYSIS_DATA again, and the Target S/4HANA Version list will now include the latest generally available SAP S/4HANA product versions.

----------------

Manual Upload of the Simplification Item Catalog

Alternatively, if the SAP-SUPPORT_PORTAL RFC destination is unable to connect with the SAP support backbone, you can update the simplification item catalog content manually:

Open the simplification item catalog content in SAP for Me
Choose the Download Simplification Item icon to download the content to your local computer.
Run the report /SDF/RC_START_CHECK.
Choose the Upload Simplification Item Catalog from the file button and upload the content from where you saved it in step 2.

Now you can execute report RC_COLLECT_ANALYSIS_DATA again. The latest SAP S/4HANA product versions will now be visible in the Target S/4HANA Version list. Proceed as described in SAP Note 2913617 (SAP S/4HANA conversions) or SAP Note 3059197 (SAP S/4HANA upgrades) to perform the data collection and create the new analysis.

Helpful links for your SAP transformation

2025-05-15T06:41:47.799000+02:00

The architecture chapter can use and recommend the tools and services below to guide and equip (and create principles and guardrails to) professionals and managers to support evidence-based decisions for your business and digital transformations.

The links below can help to provide visibility and clarity of your SAP ecosystem, especially to non-SAP professionals and leaders, so they can also make better questions when discovering and exploring the myriad of capabilities that SAP can offer.

You will need an SAP S-user (me.sap.com) and an SAP account (sap.com) to access the content.

SAP Best Practices based on SAP Signavio Process Navigator, alternatively, SAP Signavio Process Explorer is the gateway to get insights into SAP’s process portfolio and leverage related process implementation guidance and reference business and solution architectures. These include business-capability and solution maps, process models, metrics, industry best practices, and SAP best-practice and product recommendations.

SAP Fiori Apps Reference Library to explore, plan and implement SAP Fiori, the latest user experience from SAP including all relevant content for the SAP Fiori launchpad.

SAP Business Technology Platform to explore and understand different architecture patterns which can be implemented using SAP BTP services.

SAP BTP Guidance Framework for architects, developers, and administrators.

SAP Business Accelerator Hub (or Intelligent Enterprise Reference Solution Architecture) to help discover, consume, and create integrations, extensions, and innovations.

SAP Activate provides a clear guided methodology to deploy, adopt and extend new capabilities with different approaches, e.g., agile or waterfall, cloud, hybrid or on-premise, implementation or upgrade.

SAP Road Maps support the journey to SAP’s future product portfolio. Before customising, check for future enhancements.

SAP Customer Influence offers a range of programs that give customers the opportunity to influence SAP software development decisions, request specific enhancements or features, and adopt new innovations early on. Before customising, check (and vote) for opportunities and ideas to speed up SAP’s development and delivery of new requirements. Customers should engage the SAP account team to work internally with the development and product management teams.

SAP Secure Operations Map ensures smooth operation of SAP solutions by taking action proactively, before severe security problems occur.

Depending on use case, when the company is ready for transformational initiatives, use the tools and services available to customers:

SAP Value Lifecycle Manager for a value analysis, total costs of ownership calculation and more.

SAP Readiness Check conducts a detailed analysis of our existing SAP system to help plan our digital transformation. For example, SAP S/4HANA Conversion, SAP S/4HANA Upgrade, SAP BW/4HANA Conversion, SAP ERP Usage and Data Profiling, SAP Customer Experience Solutions, SAP SuccessFactors Solutions, SAP Cloud ALM, SAP Datasphere, SAP BW Bridge.

SAP Custom Code Analytics uses aggregated Custom Code Management (CCM) data from your SAP Solution Manager. The application gives an overview about the custom code footprint of the ABAP systems and provides insights about code quality and usage.

SAP Continuous Quality Check & Improvement Services are included in the SAP Enterprise Support contract. After each service, you receive a service report with an executive summary, findings and a detailed action plan to mitigate risks or improve your situation.

SAP Customer Evolution Kit for cost-free engagement to accelerate digital transformation to the cloud.

SAP Signavio, Process Insights, discovery edition, the successor of Process Discovery and Pathfinder on Spotlight, can get innovation recommendations based on the usage of the current system.

SAP AppHaus and its network partners offer different engagement types. From discovering innovation opportunities like rethinking business processes and user interfaces to delivering scalable solutions.

SAP Cloud Appliance Library offers a quick and easy way to create SAP workloads in our cloud infrastructure.

SAP Digital Discovery and Assessment is used to plan the scope of a planned SAP S/4HANA project (for SAP partners only).
SAP Simplification Item Catalogue helps better prepare for the transition to SAP S/4HANA and SAP BW/4HANA. It provides a description of all relevant changes that might have an impact when converting from SAP ERP to SAP S/4HANA or SAP BW to SAP BW/4HANA.

SAP Extensibility Explorer for SAP S/4HANA Cloud covers a broad spectrum of topics that allow us to adapt standard business software to our business needs by leveraging the extensibility patterns and sample scenarios from SAP.

When customising is required (Clean Core), refer to the following frameworks and additional resources:

SAP Store is a digital marketplace with over 2000+ extensions where we can discover, try, and buy solutions from SAP partners.

SAP Partner Finder to find the best SAP partners to meet our needs.

SAP Cloud Application Programming Model helps build cloud-native applications with maximised productivity at minimised costs, based on proven best practices served out of the box.

SAP UI Development Toolkit for HTML5 is a platform for developing rich user interfaces for modern web business applications.

SAP Learning offers free online courses, tutorials, trials, and official SAP help documentation for anyone who wants to build in-demand SAP skills and prepare for SAP certifications.

SAP Community offers access to experts, knowledge sharing, the latest news, resources, and insights on SAP solutions and technologies.

SAP for Me is the digital companion to interact with SAP and aggregates important alerts, metrics, and insights about the SAP product portfolio with a single access point.

Microsoft Azure Architecture Centre on guidance for architecting solutions on Azure using established patterns and practices, including SAP on Azure (as Microsoft is our strategic partner).

I hope it also helps guide and drive your project. It is a starting point to prepare your colleagues to support business and tech decisions.

Surely I missed many helpful links here, so feel free to add yours in the comments too. Thanks!

Originally posted on LinkedIn.

Release of the New Scenario SAP Readiness Check for SAP Supply Chain Solutions

2025-05-28T09:39:25.035000+02:00

As SAP Advanced Planning and Optimization (SAP APO) is a component of SAP Supply Chain Management (SAP SCM), and SAP SCM 7.0 will reach the end of mainstream maintenance in the coming years, customers need to plan and migrate from SAP APO to SAP Integrated Business Planning (SAP IBP), leverage the integrated supply chain planning functionality within SAP S/4HANA, or a combination of both.

Today, we proudly announce the general availability of SAP Readiness Check for SAP Supply Chain solutions to assist in planning this transformation. This new SAP Readiness Check scenario provides customers and their partners with insightful information on how SAP APO is used today.

By analysing active SAP APO modules, SAP Readiness Check for SAP Supply Chain solutions supports the definition of the target solution architecture.

SAP Readiness Check for SAP Supply Chain solutions provides customers, implementation partners, and SAP consultants visibility on how the existing SAP APO modules, like SAP APO Demand Planning, SAP APO Supply Network Planning, SAP APO Production Planning and Detailed Scheduling, and Global Available-to-Promise, are implemented, tailored, and consumed.

Unlike the existing verification points presented by SAP Readiness Check for SAP S/4HANA, where the checks reveal “must-dos” in support of a possible conversion project to SAP S/4HANA, SAP Readiness Check for SAP Supply Chain solutions is purely informative and is intended to be used as input for discussions between customers, their partners, and SAP to identify the best-fitting target architecture, as well as to help scope initial effort estimations.

What is SAP Integrated Business Planning (SAP IBP)?

The SAP Integrated Business Planning (SAP IBP) solution is a cloud-based supply chain planning solution that scales to accommodate business growth and integrates with other SAP and third-party systems. It integrates key aspects of the planning process, including demand, supply, inventory, and sales and operations planning (S&OP). Designed to help you streamline planning and improve performance, SAP IBP supports data-driven decision-making and simplified collaboration to increase operational efficiency. SAP IBP delivers this with the help of advanced analytics, artificial intelligence, and powerful optimisation algorithms that enable real-time visibility, better forecasting, and faster decision-making across the entire supply chain.
For further information, check the SAP Integrated Business Planning Community.

Supply chain planning functionality available in SAP S/4HANA

SAP S/4HANA ePPDS
SAP S/4HANA offers Embedded PP/DS, which brings the SAP APO capabilities into the SAP ERP core. Embedded PP/DS brings many advantages, such as simplified master data maintenance, simplified integration, and planning PP/DS materials in MRP Live.
The major innovation, however, is related to the user interface with SAP Fiori apps for capacity monitoring and capacity leveling. The SAP Fiori app Monitor Capacity Utilization provides an overview of the capacity load in the resources assigned to the area of responsibility and a detailed capacity overview of a selected resource, including charts and additional details of the capacity load.
For further information, see S/4HANA Embedded PP/DS: Shift Maintenance in Monitor Capacity Fiori App. | SAP Blogs
SAP S/4HANA aATP
Advanced Available-to-Promise (aATP) is a business function in SAP S/4HANA that responds to order fulfillment requests in Sales and Production Planning.
An order fulfillment request consists of the required material, plant, requested quantity, and material availability date. The response to the request is based on the current stock situation, future stock receipts, and real-time orders.
Furthermore, additional restrictions can be applied based on other order attributes (like region or customers). The ATP function generates confirmation proposals for the requested material and plant, including confirmed quantities and dates.
For further information, see Advanced Available-to-Promise (aATP) | SAP Help Portal.

SAP Readiness Check for SAP Supply Chain solutions

Overview
The dashboard contains the following three tiles:

Master Data: Shows a summary of active SAP SCM master data components, their identified dependent levels, and the corresponding data volumes in the analyzed system.
Key Data by Application Area: Provides insights into the key data of the different SCM components used in the analyzed system. This analysis can help to define the target system architecture and the main processes to be activated.
System Configuration Settings: Offers a summary of the main settings active in the analyzed system to identify requirements for the future solution architecture.

Master Data
The Master Data tile provides the top 6 objects, while the detail view provides insights into all active objects.

The detail view shows the active master data objects and the number of entries, together with additional details like table name, number of objects created last year, and number of user-created objects over the past year. The table can be exported, including all the detailed information provided.

Key Data by Application Area
This tile provides insights into the key data of the different SAP SCM components used within the analyzed system. This analysis helps to define the target system architecture by highlighting the scope and scale of the active capabilities, thus delivering input to the complexity of the data migration project.

The detail view shows the application areas in use for:

Demand Planning (DP)
Supply Planning (SNP)
Capable-to-Match (CTM)
Global Available-to-Promise (GATP)
Production Planning and Detailed Scheduling (PP/DS)
APO Documents

The object level detail helps define what data may need to be replicated to the target SAP Supply Chain solution.

System Configuration Settings
This tile provides an immediate high-level overview of the scenarios used within the system and the relevance of the analyzed objects, supporting the identification of recommended target solutions.

The following configuration settings are considered during the SAP Readiness Check analysis:

Type of planning used (Building Block / Campaign / Bottleneck / pull capacity planning / Trimming)
Used statistical models for demand generation
Used heuristic planning profiles
Used planning areas for each module
Planning strategy used, including customized configuration
Global configuration information referred to module GATP (Global-Available-to-Promise)
Distribution configuration information
Layout of the delivery network
Customized key figures and attributes in the system
Feature-based prediction settings
Number of documents managed in APO

Getting Started
To set up and run SAP Readiness Check for SAP Supply Chain solutions, the subsequent steps need to be performed:
Follow the instructions in SAP Note 3477050 - SAP Readiness Check for SAP Supply Chain solutions to install the check framework and transport the changes into your target system, such as the productive client of the production system. The note provides detailed and technical information on how to set up and perform the analysis.

Initiate program RC_SCM_COLLECT_ANALYSIS_DATA via transaction SA38 or SE38 to initialize the data collectors.

Select the scope of the analysis by activating or deactivating the corresponding checkboxes. Use the Schedule Analysis button to schedule the data collection. The process runs as a background job to avoid timeout issues.

The runtime of the data collectors depends on many factors, like server capacity, data volumes, and component usage. Therefore, it is difficult to predict the runtime. The data collection process was intentionally designed to avoid contention or interference with production workloads; consequently, you may see longer than expected runtimes. The best way to forecast the runtime for a production system is to conduct the data collection process in a copy of production using a similar hardware configuration.

Once the analysis has finished, you can download the results to your local filesystem using the Download Analysis Data button. The generated data collection archive is a ZIP file containing multiple XML files. All collected data is human-readable and can be easily inspected with appropriate XML viewers.

Launch the SAP Readiness Check cloud application on SAP for Me or from within your SAP Cloud ALM tenant and choose Start New Analysis to upload the ZIP archive. After a few seconds, the results of the newly created SAP Readiness Check analysis can be explored.

As always, we look forward to receiving your feedback!
Your SAP Readiness Check Team

Enhanced Organizational Structure Profile in SAP Readiness Check for SAP ERP Usage & Data Profiling

2025-05-28T13:36:56.955000+02:00

Organizations planning a transition to SAP S/4HANA require comprehensive tools that offer insights into their existing SAP ERP Central Component (SAP ECC) systems. The Organizational Structure Profile within SAP Readiness Check for SAP ERP Usage and Data Profiling serves this purpose. Today, we proudly announce the availability of the new version of the Organizational Structure Profile as part of SAP Readiness Check for SAP ERP Usage and Data Profiling. We deliver significantly enhanced analysis features in this latest version, providing better clarity, deeper analytical capabilities, and a more user-friendly interface.

Figure 1: Updated Version of the Organizational Structure Profile

Understanding the Business Context

The Organizational Structure Profile provides a holistic overview of an organization's SAP ECC 6.0 system structure. This profile is essential for understanding the relationships between various organizational units and identifying opportunities for optimization before transitioning to SAP S/4HANA. The Organizational Structure Profile automates a previously manual and resource-intensive process, enabling organizations to reduce the time and cost associated with scoping and assessing organizational objects.

The enhancements in this new version address several shortcomings of the previous version, including:

Limited scope: The previous version lacked coverage for certain organizational items (e.., controlling areas, storage locations, distribution channels, etc.), preventing a comprehensive analysis.
Lack of relationship data: The absence of explicit relationship data hindered a complete understanding of organizational dynamics.
Simplistic user interface: Users were unable to efficiently access and interact with detailed and interconnected information due to a flat and feature-limited user interface.

The latest version addresses these shortcomings, transforming the Organizational Structure Profile into a more robust and insightful tool.

Key Capabilities of the Enhanced Organizational Structure Profile

Expanded Scope and Coverage of Organizational Item Types

The updated version significantly broadens its scope by including additional organizational item types essential for a comprehensive understanding of the organizational structure. These include:

Controlling Areas
Cost Centers
Profit Centers
Company Codes
Plants
Shipping Points
Storage Locations
Purchasing Organizations
Sales Organizations
Distribution Channels
Divisions

This expanded coverage gives organizations a holistic view of their structure, ensuring that all relevant organizational elements are considered and more thoroughly examined during the transition. This insight allows project teams to make informed decisions during the transition planning phase.

Enhanced Visualization of Organizational Relationships

This new version offers improved visualization capabilities to clarify the complex relationships between organizational items. These include:

Hierarchical network graphs: Graphical representations display parent (ancestor) and child relationships, clearly visualizing organizational hierarchies.
Color-coded structures: Different organizational types are represented with distinct colors, improving the clarity and usability of network visualizations.
Expandable/collapsible elements: Network components can expand and collapse, allowing users to focus on specific areas of interest within the organizational structure.

Figure 2: The Parent Object and Child Object Network Graphs of a Sales Organization Item

These advanced visualization capabilities facilitate a more intuitive understanding of organizational structures and interdependencies, empowering project teams to make well-informed decisions during transition planning.

Detailed Usage Analysis for Making Informed Decisions

The enhancements include incorporating detailed usage analysis to help organizations quickly identify actively used organizational items and those that may be obsolete. Historically, determining whether an organizational unit is actively contributing to business processes or is no longer relevant is time-consuming. This new version now simplifies this process with advanced usage indicators, enabling teams to streamline assessments, accelerate decision-making based on usage data, and optimize resources by eliminating obsolete elements.

To evaluate the usage status of an organizational item, related business objects for all organizational item types in scope were identified and are used to analyze their data volumes and activities regarding the selected organization. The resulting data for these business objects are presented in the "Usage Indicator" card of the detail view (see figure 3). Each business object is assigned a usage status, categorized as "Active," "Likely Not Active," or "Not Active":

Active (Green): Indicates that the business object is currently actively used for the organizational item in focus, having a data volume higher than 20 items and recent activity over the last three years.
Likely Not Active (Yellow): States that the usage status of this business object is uncertain about the selected organizational item, with limited data volumes or lack of recent activity, warranting further investigation.
Not Active (Red): Confirms that the business object is not being used for the selected organizational item, with a data volume less than 20 items and no recent activity over the last three years.

Based on the usage indicators of the related business objects, the usage status of the selected organizational item is determined and presented in the header of the detail view (see figure 3):

Active (Green): The organizational item is currently actively used. It has at least one related business object which is actively used.
Likely Not Active (Yellow): The usage status of the selected organizational item is ambiguous, demanding further investigation. No related business object is actively used, but there are objects with usage status "Likely Not Active" and/or "Not Active."
Not Active (Red): The organizational item is not being used. All related business objects have the usage indicator value "Not Active."

For a more detailed understanding of calculating usage indicators, click on the 'Learn More' button to access the Organizational Structure Profile help panel.

Figure 3: Detail View of a Plant Organizational Item, Including Usage Indicators Card and Open Help Panel

We strongly recommend that the project team, particularly the business owners of the involved organizational units, conduct further investigations to validate and confirm the findings from the usage data analysis. This additional validation ensures the accuracy and reliability of the insights, facilitating more informed decision-making.

Identification of Orphaned Organizational Items

The enhanced version automatically identifies, and flags orphaned organizational items that lack proper parent-child hierarchy links, signaling potential structural inefficiencies or errors. By highlighting these gaps, the Organizational Structure Profile enables organizations to address structural inconsistencies proactively, minimize transition risks, and ensure the integrity and completeness of their organizational model throughout the transition process.

Figure 4: A Plant Without a Corresponding Company Code is Marked as an Orphaned Item

Redesigned User Interface for Enhanced Usability

To address usability concerns, the enhanced Organizational Structure Profile features a completely redesigned user interface that significantly improves usability:

Flexible column layout: The interface is divided into two main sections - a list of organizational items on the left and detailed information about the selected item on the right.
Intuitive filtering: Users can filter organizational items by type through a view selector or search for specific items using a text-based search field.
Detailed information sections: The detail view includes:
- Master data information
- Usage indicators showing the status of related business objects
- Dependent data sections displaying related organizational items
- Network graphs visualizing parent and child hierarchies
Export capabilities: Users can export both the list of organizational items and detailed information about specific items for further analysis or reporting.
Related data access: Links to related data collectors enable users to access additional information relevant to the selected organizational item type.

Figure 5: Detail View of a Company Code Organizational Item and Available Filter Options

This newly designed user interface makes it easier for project teams to navigate and analyze complex organizational structures without requiring specialized knowledge.

Cross-Profile Integration

The enhanced Organizational Structure Profile integrates seamlessly with other profiles within the SAP Readiness Check for SAP ERP Usage and Data Profiling:

Usage indicators are linked to the Initial Data Migration Profile, allowing users to navigate directly to detailed information about related business objects. This integration provides a more holistic view of the system landscape and facilitates comprehensive analysis.
Hyperlinks to related data collectors enable users to access additional information and gain a more comprehensive understanding of their system landscape.

Figure 6: A Company Code Organizational Item and its Collection of Links to Related Data Collectors

Use Cases

Transitioning to SAP S/4HANA can be more than just a data migration exercise - it could be a strategic opportunity to optimize business structures and eliminate inefficiencies. The enhanced Organizational Structure Profile is a powerful tool that offers valuable insights regardless of the transition scenario.

Selective Data Transition Planning

Understanding the organizational structure and usage patterns is crucial for projects involving selective data transition. The new version helps identify actively used organizational elements, highlighting those that should be migrated versus those that can be discarded, optimizing the transition process.

Organizational Structure Optimization

Many organizations use the transition to SAP S/4HANA as an opportunity to streamline their organizational structure. The enhanced analysis provides the insight needed to identify redundant or unused organizational elements, supporting informed decision-making during this optimization process.

Transition Sequence Planning

Understanding dependencies between organizational items is essential for planning the transition sequence. The network visualization capabilities of the Organizational Structure Profile make these dependencies clear, helping project teams develop more effective transition strategies.

Data Quality Assessment

Orphaned item detection and usage analysis contribute to an overall data quality assessment. This evaluation enables organizations to address inconsistencies and ensure that only relevant, high-quality data migrates to the new system.

Next Steps for Users

Follow these steps to take advantage of the new Organizational Structure Profile:

System preparation and data collection: Implement the latest version of SAP Note 3112362 and run an SAP Readiness Check for SAP ERP Usage and Data Profiling analysis by following the instructions described within the SAP Note, including uploading the data collection archive to the SAP Readiness Check cloud application.
Explore the analysis results: Identify organizational items of interest and examine their usage and dependent data.
Visualize hierarchical relationships: Use the network graphs to understand the relationships between specific organizational items.
Filter and search: Use the filtering and search capabilities to focus on specific segments of the organizational structure.
Identify optimization opportunities: Review usage status indicators to identify potentially unused or redundant organizational items.
Investigate orphaned items: Address organizational items with disrupted hierarchy paths to ensure structural consistency.
Explore related data: Use the links to associated data collectors to gain additional insights about specific organizational item types.
Export for collaboration: Export relevant data for sharing with stakeholders and for further analysis.

As an alternative to creating a new analysis in the SAP Readiness Check cloud application, you can update your existing SAP Readiness Check for SAP ERP Usage and Data Profiling analysis. Start by implementing the latest version of SAP Note 3112362 and rerun the data collection process in your SAP ECC system. Then, using the newly created data collection archive, update the existing analysis data using the Update Analysis option within the header of the dashboard view in the SAP Readiness Check cloud application on SAP for Me or your SAP Cloud ALM tenant.

As always, we look forward to receiving your feedback.

SAP Readiness Check team

New SAP Readiness Check Landing Page in SAP for Me

2025-06-10T14:29:00.987000+02:00

Dear all,

SAP Readiness Check has evolved over the last years to become a vital planning tool for the most critical SAP transformation journeys. Currently, SAP Readiness Check includes support for nine scenarios and has processed over 85,000 analyses since its inception in 2019.

With our continuously growing number of SAP Readiness Check scenarios, we felt it was time to revamp the SAP Readiness Check cloud application landing page. We are happy to provide you with a restructured landing page in SAP for Me and SAP Cloud ALM, offering easy navigation and orientation at first glance, and being the one-stop shop for all things related to SAP Readiness Check.

The Getting Started section contains the How to Start link, which opens a guided procedure explaining the steps to create a new SAP Readiness Check analysis.

Familiarize yourself with the steps to prepare for creating your first SAP Readiness Check analysis.

The Supported Scenarios section contains links to the central guidance note for each SAP Readiness Check scenario. Each SAP Note lists the requirements to implement and run the SAP Readiness Check data collectors for the specific scenario in your system. Please read the respective SAP Note carefully before scheduling the data collection job; it contains essential hints to avoid long-running data collection jobs and other valuable information.

After the data collection jobs finish, you can create a new analysis by uploading the generated data archive to the SAP Readiness Check landing page. To do so, click Create New Analysis in the top right corner of the Analyses section.

Enter a name for the analysis, verify your customer information, and select the results archive from your local filesystem. Accept the Terms of Use and decide if you want to authorize SAP employees access to your results.

Note: With the Authorization checkbox, you grant SAP employees access to your SAP Readiness Check results. Alternatively, you can grant individual access to specific e-mail addresses later within the analysis dashboard.

Clicking Create, the application immediately processes the provided data collection archive file and produces a new analysis, accessible as an interactive dashboard. You can select the analysis from the list and start reviewing the results.

The list of analyses can be expanded by selecting the Show All button in the Analyses section, which will display all analyses your user is authorized to access. Within the analysis list, you may search for an analysis or use the filter options to limit the view to a specific scenario or analysis status. In addition, you can create a list of favorite analyses.

New feature: Combined Scenarios

Released with the new SAP Readiness Check cloud application landing page, you can now combine analyses of different scenarios for the same system and client.

For instance, you can now update an existing SAP Readiness Check for SAP S/4HANA analysis with the data collection archive produced by SAP Readiness Check for SAP ERP Usage and Data Profiling and/or SAP Readiness Check for SAP SuccessFactors Solutions for the same system and client. Similarly, you can update an SAP Readiness Check for SAP S/4HANA Upgrades analysis with the data collection archive produced by SAP Readiness Check for SAP SuccessFactors Solutions.

To combine analyses, use the Update Analysis button within an existing SAP Readiness Check for SAP S/4HANA or SAP Readiness Check for SAP S/4HANA Upgrades analysis to add the additional scenario. The resulting combined analysis includes a tab for each scenario within the dashboard header.

The What’s New section of the SAP Readiness Check landing page always shows the latest blogs from the SAP Readiness Check Community to keep you up-to-date on new scenarios, features, and enhancements.

The Additional Information section provides links to the SAP Help Portal, SAP Community, learning areas, SAP Activate, related topics, and recommended training material.

We hope you enjoy the new look and feel!

How to prepare the system for SAP S/4HANA upgrades - SAP Readiness Check

2025-07-14T20:14:00.017000+02:00

If you're planning an upgrade to SAP S/4HANA, the SAP Readiness Check is a valuable tool to help you assess your system's current state and identify any potential issues before the upgrade.

An accurate Readiness Check analysis starts with collecting important system information—such as usage statistics, custom code analysis, and configuration details.

This information is gathered using data collectors, which are ABAP-based tools that extract relevant data from your SAP system.

To set up the data collectors, refer to the SAP Notes outlined in the section below for step-by-step instructions.

Step 1: System preparation

Before implementing the required SAP Notes for the data collectors, make sure the following Notes are already applied in their latest versions:

SAP Note 1668882 – Note Assistant: Important notes for SAP_BASIS 730,731,740,750,751,752,753,754,755,756,757,758
SAP Note 2971435 – SNOTE – Delta calculation issue when 'mod unit' positions are changed

These Notes help ensure your system is up to date and minimize the risk of errors during setup.

To make the implementation process easier, you can use the Note Analyzer tool available in the Note Assistant. For instructions and the input file, refer to SAP Note 3365856 – Note Analyzer Input File for SAP Readiness Check for SAP S/4HANA upgrades.

2758146	SAP Readiness Check Framework	SV-SCS-S4R	RC_COLLECT_ANALYSIS_DATA	If SAP Note 2310438 has been implemented previously, it must be reverted prior to implementing SAP Note 2758146.
2399707	Simplification Item Relevance & Compatibility Scope	CA-TRS-PRCK	TMW_RC_SITEM_DATA_COLL	Enables simplification item relevance, compatibility scope analysis, and target S/4HANA version selection in RC_COLLECT_ANALYSIS_DATA. Implementation is mandatory. SAP Note 2502552 and the consistency check from this note are optional but recommended.
2903677	Effort Drivers for Simplification Items	CA-TRS-PRCK	TMW_RC_EFD_DATA_COLL	This SAP Note offers the ability to include the effort driver analysis for simplification items with the initial effort ranking of Potentially High. The result is that effort ranking for some simplification items could be recalculated based on the scope and complexity of the system being analyzed.
2502552	Consistency Check for Simplification Items	CA-TRS-PRCK	TMW_RC_SITEM_DATA_COLL	This SAP Note enables the optional data collection process for the consistency check. If you opt to include this data in your analysis, please ensure that you always use the latest version of this SAP Note. It is an addition to SAP Note 2399707. You must read and implement SAP Note 2399707 first and follow all steps, including the implementation of related SAP Notes listed in SAP Note 2399707.
3061414	Integration Analysis	SV-SMG-MON-BPM-DCM	–	This SAP Note details the steps required to enable successful execution of the Integration check data collectors. The check results provide insight into interfaces that could be impacted as part of an SAP S/4HANA upgrade project and provides guidance on mitigating the impact. Please note that the data collector for this extended analysis is delivered starting with version 56 of SAP Note 2758146. SAP Note 3061414 only outlines the steps necessary for successful execution of the check, including required prerequisite SAP Notes.
2827612	Innovation Potential Dashboard	SV-SCS-S4R	TMW_RC_INNOVA_DATA_COLL	This SAP Note is responsible for enabling the optional Innovation Potential analysis, which populates the Innovation Potential dashboard with guidance on possible areas for future innovation based on current system usage statistics. If the ST-PI component version in the landscape is less than or equal to ST-PI 2008_1_700 SP27, ST-PI 2008_1_710 SP27, or ST-PI 740 SP17, you need to implement the SAP Note 2827612 to enable innovation potential sub check.
2781766	Custom Code Analysis via ATC	BC-DWB-CEX	–	Requires ATC setup and variant S4HANA_READINESS. See SAP Notes 2436688 and 3293011.

Step 2: Necessary authorizations

The user who is used to schedule the data collectors must have the following authorization:

Authorization object S_PROGRAM with values P_GROUP = RC_COLL and P_ACTION = SUBMIT, BTCSUBMIT, VARIANT.

The user ID used for scheduling the data collector for Custom Code Analysis must have the following authorizations:

Authorization object S_Q_ADM with values ACTVT = Add or Create (01), Change (02), Execute (16) and ATC_OBJTYP = Check run (01), Configuration (04)
Authorization object S_Q_GOVERN with values ACTVT = Delete (06), Confirm (31) and ATC_OTYPGO = Exemption (01)

Step 3: Data Collection

Launch the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA).
Choose Schedule Analysis to schedule the master job to collect data.
Select the Download Analysis Data option in the data collection report once the collection process completes.

Optional: Review the data collected in the compressed file.
Optional: Alter the data collected as required to address any potential data protection concerns and then repackage the contents.
Optional: Check the XML file content via the browser.

Step 4: Custom Code Analysis (Recommended)

Via the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA) in a non-productive system

Launch the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA).
Choose the target release, select the Custom Code Analysis check, and deselect any other checks.
Choose Schedule Analysis to schedule the master job to collect data.
Select the Download Analysis Data option in the data collection report once the collection process completes.
Choose Update Analysis at the top of the dashboard view to add the ABAP test cockpit export to the SAP Readiness Check analysis.

Note: The custom code analysis results of a non-production system can be uploaded to an existing SAP Readiness Check analysis created for a production system.

Manually via the ABAP Test Cockpit

Schedule an ABAP test cockpit run using the S4HANA_READINESS variant for the current product version (to create a baseline).
Using the results from the previous step, maintain the baseline to exempt the findings. You can do this within the Manage Results screen in the ABAP Test Cockpit by selecting the relevant results and following the dropdown menu option: Maintain Baseline -> Add Selected Results To -> Exempt Findings.
Schedule a second ABAP test cockpit run using the S4HANA_READINESS variant for the selected target release, ensuring the Consider Baseline setting is enabled.
Export the results of the second ABAP test cockpit run by selecting the context menu option Export to -> File for SAP Readiness Check in the ABAP test cockpit result browser.
Choose Update Analysis at the top of the dashboard view to add the ABAP test cockpit export to the SAP Readiness Check analysis.

Additional information:

To learn more about how to use SAP Readiness Check for S/4HANA upgrades, please refer to SAP Note 3059197 - SAP Readiness Check for SAP S/4HANA upgrades.

Modernize with SAP Business Data Cloud using the SAP Business Data Cloud Modernization Assessment

2025-09-09T15:06:53.392000+02:00

SAP Business Data Cloud is the evolution of SAP data and analytics solutions and embodies the path forward for SAP Business Warehouse customers.

Start exploring the modernization journey with the brochure
“How to modernize SAP Business Warehouse with SAP Business Data Cloud.”

Since organizations are in different stages of their cloud modernization journey, SAP supports customers with the expert-guided SAP Business Data Cloud modernization assessment, analyzing your currently used SAP on-premises data and analytics solutions and helping to find your specific path to cloud modernization with SAP Business Data Cloud.

The SAP Business Data Cloud modernization assessment is a complimentary, limited-time readout that provides deep insights into your SAP Business Warehouse, SAP BusinessObjects, and SAP HANA environments. Based on usage, discover which investments are most active, identify areas that can be modernized, and receive best practices for an actionable modernization plan for SAP Business Data Cloud.

With the results from this readout, you can:

Understand the usage patterns of your SAP Business Warehouse, SAP BusinessObjects, or SAP HANA environments to help with modernization prioritization.
Explore modernization options to begin your SAP Business Data Cloud journey.
Define a data strategy with scalable cloud solutions that prepares you for the era of AI.

Apply here for your free SAP Business Data Cloud modernization assessment!

Explore your Enhancements and Extensions with SAP Readiness Check for SAP Cloud ALM

2025-10-15T12:00:00.034000+02:00

Note: The following blog describes the new Enhancements & Extensions functionality available within SAP Readiness Check for SAP Cloud ALM. For an overview of the other checks available in SAP Readiness Check for SAP Cloud ALM, refer to this blog.

Dear All,

Today, we are excited to announce that the SAP Readiness Check for SAP Cloud ALM now incorporates one additional check to provide details about the custom objects and customizing within the SAP Solution Manager system.

All these details are summarized in a new check called Enhancements & Extensions, which will support your transition project in the decision to eventually decommission your SAP Solution Manager system landscape, and also to identify any custom modifications or enhancements to Application Lifecycle Management processes.

Knowing which custom objects or customizations exist is important to evaluate the impact and additional efforts to move all required functionality to SAP Cloud ALM. Moreover, if you find that your system and ALM processes run close to the standard, you can start planning the move to SAP Cloud ALM directly using the other checks of the SAP Readiness Check analysis.

Enhancements & Extensions – Custom Objects

In the custom objects section of the new check, you will find the objects created in a customer namespace. These objects can represent an enhancement or extension to a standard process in SAP Solution Manager, or a completely new application running in the same system. If the check identified enhancements, you can evaluate if such modifications are still needed when you move your processes to SAP Cloud ALM, or if they are covered by the standard extensibility options offered in SAP Business Technology Platform and SAP Cloud ALM APIs. Additionally, after your transition to SAP Cloud ALM is complete, you might consider decommissioning your SAP Solution Manager system landscape. The custom objects results and the Add-Ons details will help you identify the impact on other processes running in the system.

The custom objects section contains the following tables describing different types of custom enhancements:

ABAP Enhancements: lists programs, transactions, and classes that exist in a customer namespace.
Custom Tables: lists custom-created tables and the number of records.
Custom Application Enhancement Fields (AET): lists custom-created fields in CRM WebUI applications, typically done to create enhancements in the area of Incident and Change Request Management.
BSP Enhancements: lists enhancements to Business Server Pages application logic, typically representing enhancements or extensions in the area where BSPs are used, such as Incident and Change Request Management.

Enhancements & Extensions – Add-Ons

The Add-on section helps identify the installed add-ons and their vendor in the SAP Solution Manager system. Use this information to determine the impact of decommissioning your SAP Solution Manager system landscape.

Enhancements & Extensions – Change Request Management

The Change Request Management section provides details about the customizing related to specific Application Lifecycle Management processes, highlighting whether such enhancements exist in Change Request Management and what is no longer equal to standard. Generally, if only a few modifications are identified, it suggests that the transition of your Change and Request Manager should be smooth, and the capabilities in SAP Cloud ALM are likely sufficient. You can supplement this analysis and confirm if the capabilities you use are available in SAP Cloud ALM through the Availability of Relevant Capabilities check in your SAP Readiness Check analysis.

If a high number of modifications are identified and your processes contain multiple enhancements or extensions that are still needed and are not provided by SAP Cloud ALM, you can explore the extensibility options in SAP Cloud ALM.

The Change Request Management section contains the following details:

Transaction Types Modifications: compares custom transaction types with the standard delivered customizing for the original transaction type and shows where differences from standard exist. These differences can be either changed entries representing an enhancement or adaptation in the process, or new entries meaning an extension in the process.
Custom Change Cycles: Change cycles are not recommended to be copied. This list shows if custom transaction types of type cycles exist, with the assigned change transactions.
Focused Build Modifications: Focused Build is delivered as a turn-key solution and should not be modified. Modifications of the standard customizing are detailed in this list.
Active BADI Implementations: this list contains the custom implementation of Business Add-ins in the area of Change Request Management that are also active.

The described details will allow you to identify where enhancements and extensions exist to more precisely understand how you run your Change Management processes in your SAP Solution Manager system, to help you measure the impact of moving this process to SAP Cloud ALM and evaluate where extensions are possible, but generally, it should not prevent you from starting your transition project.

Data Collection

The SAP Readiness Check for SAP Cloud ALM data collector, which runs in the SAP Solution Manager system, has been updated to include the data required for the new Enhancements & Extensions capability. Ensure version 68 (or higher) of SAP Note 3236443 has been implemented before scheduling the collector. Once the data collector is complete, you can use the generated data archive to create a new SAP Readiness Check analysis or update an existing analysis (using the Update Analysis function to upload the enhanced data collection archive).

As always, we look forward to receiving your feedback!

Your SAP Readiness Check Team

Accelerate Your Transformation journey with the SAP Customer Evolution Kit

2025-10-30T18:26:58.385000+01:00

Are you running SAP ERP, SAP S/4HANA On-Premise, or other SAP LoBs and thinking about your next steps?

The SAP Customer Evolution Kit is available and designed for customers like you – those with active SAP support agreements looking to future-proof their business. Best of all, participation is free of charge!

What Is the SAP Customer Evolution Kit?

The SAP Customer Evolution Kit is a personalized, high-touch engagement lasting just 3–5 days. 1:1 virtual sessions with dedicated SAP experts, your team receives tailored insights, real-time simulations, and practical guidance to plan your cloud Transition.

The objective is to help business owners, IT leaders, and key users make informed decisions about modernization, digital transformation, and the evolution of your SAP landscape.

Who can benefit?

The program is designed for SAP ERP/ECC, S/4HANA On-Premise, and a broad array of LoB solutions (finance, supply chain, procurement, HR, CX, and more). If your organization is considering the future – migration, process innovation, or simply staying ahead – this engagement gives you the clarity and support needed.

Why Consider Moving to SAP Business Suite?

Migrating to SAP Business Suite (S/4HANA – cloud or hybrid editions) unlocks the power of in-memory computing, AI-driven automation, and real-time analytics. It ensures compliance with the latest security and regulatory standards, seamless upgrades, and access to the newest ERP features. Data moves more freely, processes are optimized, and your business is prepared for tomorrow’s opportunities, among many others today's and future Business

Maintenance Strategy: Key Dates to Know

SAP has announced important changes:

Mainstream maintenance for SAP ECC EhP 0-5 ends in Dec 31, 2025 and for EhP 6-8 & Business Suite 7 ends in 2027.
Extended maintenance is available (with additional fees) through 2030.

Moving to S/4HANA or SAP Business Suite is not just a technical migration—it’s a strategic imperative to stay secure, and remain competitive.

Check the information about SAP software releases: release types, maintenance durations, planned availability, and upgrade paths at Product Availability Matrix (PAM).

Learn more about the SAP Release and Maintenance Strategy

Get Started:

If your organization has an active SAP support agreement, you can sign up for the SAP Customer Evolution Kit free of charge here: https://events.sap.com/sap-customer-evolution-kit/en_us/home.html

Also, you can expand the scope with Solution Area(s) of your choice:

Register today here and don’t miss this opportunity to accelerate your journey with confident planning and expert support.

Contact Us: customer.evolution.kit@sap.com

Congratulations, SAP Readiness Check!

2025-11-19T13:51:29.394000+01:00

As we get ready to celebrate the 100,000th SAP Readiness Check analysis processed, we would like to pause with a brief look at our milestone moments.

Following the release of SAP S/4HANA 1609, customers understood that SAP S/4HANA is different from SAP ECC and started asking questions about the impact of making the move and whether their systems were ready to undergo the transition. These inquiries led to the introduction of the SAP Readiness Check in 2016 as a manual service session to prepare service deliveries for MaxAttention customers looking to convert to SAP S/4HANA.

The first, semi-automated version of SAP Readiness Check for SAP S/4HANA went live in May 2017, followed by SAP Readiness Check on the current platform in 2019. Since then, SAP Readiness Check has continued to evolve, not only extending the depth of the checks but on top making SAP Readiness Check available for transitions beyond the conversion to SAP S/4HANA, expanding the coverage of SAP products and solutions to SAP SuccessFactors, SAP Supply Chain solutions, SAP Customer Experience solutions, SAP BW/4HANA, and SAP Cloud ALM. As of today, SAP Readiness Check is available on SAP for Me and SAP Cloud ALM, offering nine variants to support various transformation scenarios and has supported over 15,500 customers across 150 countries/regions.

And there’s more on the roadmap: In the future, we are planning to use genAI features in SAP Readiness Check that will guide users during setup, interpretation, and follow-up tasks. Furthermore, new SAP Readiness Check scenarios for RISE with SAP and SAP Business Suite customers are in the pipeline, evolving SAP Readiness Check to a continual source of information for customers, partners, and SAP teams to discuss where and how further SAP Business Suite products and offerings could optimize and enhance the customer’s active business processes. Stay tuned for more to come that supports the transition to new SAP solutions!

“SAP Readiness Check is a cornerstone of every successful SAP S/HANA transformation we support”, states Markus Schuetz, Senior Lead Architect at the SAP Partner Claranet Addon GmbH and workstream lead of the DSAG (German SAP User Group).

A big thank you to all customers and partners trusting in SAP Readiness Check as the basis for planning and preparing the transition to new strategic SAP solutions and into the cloud, and congratulations to all SAP colleagues contributing to the continuous success of SAP Readiness Check!

We invite you to comment on this blog to share your congrats, thoughts, and SAP Readiness Check success stories with the SAP Readiness Check Community!

Your SAP Readiness Check team

SAP Readiness Check - Easier SAP Note Implementation for Combined Scenarios

2026-02-11T11:38:31.992000+01:00

Following up on the “Combined scenarios” feature on the new SAP Readiness Check cloud application landing page (see blog New SAP Readiness Check Landing Page in SAP for Me), we aim to simplify customers’ change management efforts related to implementing the SAP Readiness Check data collectors.

Therefore, we enhanced the SAP Note Analyzer input files for SAP Readiness Check for SAP S/4HANA and SAP Readiness Check for SAP S/4HANA upgrades with the SAP Notes required for related SAP Readiness Check scenarios. For SAP Readiness Check for SAP S/4HANA, this includes the data collector notes for SAP Readiness Check for SAP ERP Usage and Data Profiling, as well as SAP Readiness Check for SAP SuccessFactors solutions. In the input file for SAP Readiness Check for SAP S/4HANA upgrades, we included the data collection note for SAP Readiness Check for SAP SuccessFactors solutions.

This extension supports customers:

Planning a combined project like transitioning from a SAP ERP ECC with HCM to SAP S/4HANA and SAP SuccessFactors.
Customers that are currently in an evaluation phase, trying to determine the best-fitting transition path to SAP S/4HANA – conversion, strategic new implementation, or a selective data transition.

In a one-time effort, customers can install all required SAP Notes for all related SAP Readiness Check scenarios from a single SAP Note Analyzer input file. This adaptation to the input files simplifies customers’ change management efforts as they can now easily combine all relevant SAP Notes into a single change request. Thereby, avoiding multiple rounds of approval and last-minute expedited change requests to fulfill service delivery prerequisites.

The SAP Note Analyzer input files are attached to SAP Note 3308130 – Note Analyzer Input File for SAP Readiness Check for SAP S/4HANA and SAP Note 3365856 - Note Analyzer Input File for SAP Readiness Check for SAP S/4HANA upgrades.