{"id":39104,"date":"2025-02-20T11:16:44","date_gmt":"2025-02-20T10:16:44","guid":{"rendered":"https:\/\/www.blue.works\/?p=39104"},"modified":"2026-02-18T16:22:17","modified_gmt":"2026-02-18T15:22:17","slug":"sap-cloud-alm-whats-new-in-week-8","status":"publish","type":"post","link":"https:\/\/www.blue.works\/en\/sap-cloud-alm-whats-new-in-week-8\/","title":{"rendered":"SAP Cloud ALM \u2013 What\u2019s New in week 8"},"content":{"rendered":"\n

Welcome back to our bi-weekly<\/a> SAP Cloud ALM update blog! As SAP continues to refine and enhance the Cloud ALM experience, we\u2019re here to keep you informed about the latest innovations designed to boost efficiency and simplify your workflows. In this edition, we\u2019ll walk you through the key enhancements from week 8, showcasing how SAP is helping you achieve more with every update. Let\u2019s dive in!<\/p>\n\n\n\n

SAP Business Transformation Center<\/strong><\/h2>\n\n\n\n

This time SAP has made 4 new features available for Scoping<\/strong>.<\/p>\n\n\n\n

In the Manage Digital Blueprints<\/strong> app, there is a new chart which displays the distribution of transactional data per year. The chart is visible in the Solution Patterns<\/strong> section for time slice. This allows visualizing the impact of a time slice-based data reduction on the scope of digital blueprint and helps to make an informed decision when selecting a year for a time slice.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the Select Company Codes<\/strong> app, it\u2019s now possible to check the fiscal year start date of each company code in the company code list view. This helps to make scoping decisions for a digital blueprint for which it\u2019s planned to activate the time slice solution pattern.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When a system scan fails due to an incorrect setup in the backend system, SAP Business Transformation Center now displays detailed instructions on how to fix the issue. These messages are visible in the system scan\u00b4s Activity Log<\/strong> section in the in the Manage System Scans<\/strong> app.<\/p>\n\n\n\n

Additionally In the Manage System Scans<\/strong> app, when the software component check of a system scan fails, the activity log now provides more information on the missing system requirements, including the necessary SAP Notes to install on the source system and which software components are missing the minimum version required for the system to pass the check.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Implementation<\/strong><\/h2>\n\n\n\n

Test Preparation<\/strong> has 2 new features.<\/p>\n\n\n\n

To prevent accidental loss of test results, the deletion of test cases with existing test runs is now restricted to users with the role Project Administrator<\/strong> or Project Lead<\/strong>. Users with the Project Member<\/strong> role can still delete test cases that haven’t been executed yet.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

It\u2019s now possible to assign application library elements to test cases. This helps to ensure the application’s test coverage and improve overall traceability throughout the implementation project. It also allows to track the statuses of related test cases from the Libraries <\/strong>app.<\/p>\n\n\n\n

The assignment itself takes place in the new Relations<\/strong> tab, which now also contains process hierarchy nodes.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Test Plans<\/strong> introduced Role-based restrictions on deleting and unassigning. To prevent accidental loss of test results, the following actions are now restricted to users with the role Project Administrator<\/strong> or Project Lead<\/strong>:<\/p>\n\n\n\n