Maintenance Planner has to be used beforehand to check the system and to provide the stack.xml for the SUM (as well as to provide the required software archives).The data conversion is partly triggered by the SUM, partly an activity after the SUM run (for FIN and ML data: IMG activities). Data Conversion: conversion of table content to new data model.Database Migration (if source system is based on non-HANA database): migrate existing database content to SAP HANA database (using Database Migration Option DMO of SUM).Software Update: Provide new applications & new tables (as part of the new data model) by providing new software components (like S4CORE) & updating existing software components.System Conversion: three tasks for SUM to enable Simplification of SAP S/4HANA Software Update Manager (SUM) is the tool for this transition.
System Conversion transitions an existing SAP ECC system to SAP S/4HANA (on premise).System Conversion: SUM 2.0 is the tool for the transition to SAP S/4HANA on premise Part 3 (DT103): Reduce Downtime for a System Conversion to SAP S/4HANA.Part 2 (DT102): System Conversion (Part 2) – Latest News for Experts.Part 1 (DT101): System Conversion (Part 1) – Get Your Road Map to SAP S/4HANA.Recordings on system conversion at SAP TechEd 2020: DT200 “Build Your System Conversion Road Map to SAP S/4HANA”:.Recording on system conversion at SAP TechEd 2021:
Readers should be familiar with the transition paths to SAP S/4HANA, like described in Recording on system conversion at SAP TechEd 2022: System Conversion: the transition of an existing SAP ECC system to SAP S/4HANA. This blog discusses the technical aspects of Software Update Manager (SUM) for a
0 kommentar(er)
