I was involved in System Conversion projects, and had the chance to collect the news that I came across since last year. This blog aims to collect these news that are relevant for a System Conversion – listing new tools and aspects that are available with SAP S/4HANA 1709, or that are new since SAP S/4HANA 1610. Readers should be familiar with the general approach of a System Conversion, as described in the blog https://blogs.sap.com/2016/11/02/sap-s4hana-system-conversion-at-a-glance/
The Maintenance Planner now allows to include the un-installation of an AddOn as part of the planning for a System Conversion. Of course, the prerequisite is that you do no longer need the AddOn on the SAP S/4HANA target system. See the section in the SAP Help Portal on that: https://help.sap.com/viewer/62c8d2b1a71046a09b9c7ec745910ae4/latest/en-US/1bde39e1bbf84e47aea07486b7ad9da0.html
Simplification Item Catalog
It is obvious that SAP S/4HANA 1709 as new product release comes with new features and scenarios, but we do not cover these in here. Nevertheless, this is correlated with potential new Simplification Items. Sure you know the Simplification Item List – but now we have a better way to search for items: the Simplification Item Catalog as an online tool. The central place to find the latest simplification items for SAP S/4HANA (and SAP BW/4HANA as well), and to download the content: http://launchpad.support.sap.com/#/sic
Precheck report goes Simplification Item check
For checking the business aspects of the Simplification Items, the Simplification Item Checks are the successor of the precheck report – relevant for target system 1709 only. The new approach offers a more granular information, and it is based on a new framework. The implementation is easier than before, and it offers two levels of checks: relevance checks and consistency checks.
The Readiness Check provides an important first insight into the relevant aspects for a System Conversion. It bundles the checks of the Maintenance Planner, the Simplification Item Checks as well as Custom Code checks, and is available as a self-service without additional costs.
The following blog is an excellent introduction into the Simplification Item Catalog as well as for the Simplification Item Checks and the Readiness Check: https://blogs.sap.com/2017/09/15/simplification-item-catalog-simplification-item-check-and-sap-readiness-check-for-sap-s4hana/
Custom Code checks
The coverage of checked custom code was now improved. Custom code checks now scan all custom code in Enhancements, Modifications, Customer EXITs, Smart Forms and ignore findings in SAP includes and generated code. Additionally simplification item information (e.g. OSS note) is displayed in ATC result list including filtering and sorting capabilities.
Check out for more: SAP S/4HANA System Conversion – Custom code adaptation process.
SUM 2.0 for technical conversion
Software Update Manager (SUM) is available as SUM 1.0 and SUM 2.0 in parallel – still for a System Conversions, only SUM 2.0 is used. It is based on the proven coding of SUM 1.0.See this blog for more background on SUM 1.0 and 2.0:
SUM 2.0 offers a new prerequisite check now. This quick and non-invasive check covers the source OS- and DB- as well as SPAM-versions.
SAP HANA 2.0
SAP S/4HANA 1709 is the first product version that is based on SAP HANA 2.0 exclusively. So for the System Conversion with a source system on a non-HANA database, you require a SAP HANA 2.0 database, as appliance or via TDI.
For a source system on SAP HANA 1.0, for example SAP ERP 6.0 EHP 7 on HANA, you must first run the database update to SAP HANA 2.0 prior to starting the System Conversion. For details, check the following SAP note: SAP Note 2524661 – SAP S/4HANA 1709 – SAP HANA Database Requirements.
Product Management, Software Logistics, SAP SE