Scribd
Upload
383 views

System Conversion To Sap S4hana Sum Is The Tool

The document discusses the Software Update Manager (SUM) tool for transitioning an existing SAP ECC system to SAP S/4HANA on-premise. SUM is used for either a single-step transition if the source is already on Unicode and SAP HANA, or a two-step process involving database migration and data conversion if the source is not on Unicode or HANA. SUM performs software updates, database migration from non-HANA databases, and conversion of table content to SAP S/4HANA's new data model. A two-step approach is typically required for non-Unicode systems or older releases like ECC 5.0 and 4.7 due to missing integration with business partners.

Uploaded by

shaozhiqiong
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
383 views

System Conversion To Sap S4hana Sum Is The Tool

The document discusses the Software Update Manager (SUM) tool for transitioning an existing SAP ECC system to SAP S/4HANA on-premise. SUM is used for either a single-step transition if the source is already on Unicode and SAP HANA, or a two-step process involving database migration and data conversion if the source is not on Unicode or HANA. SUM performs software updates, database migration from non-HANA databases, and conversion of table content to SAP S/4HANA's new data model. A two-step approach is typically required for non-Unicode systems or older releases like ECC 5.0 and 4.7 due to missing integration with business partners.

Uploaded by

shaozhiqiong
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Logistics: System Conversion to

SAP S/4HANA: SUM is the tool


Posted by Boris Rubarth Nov 24, 2015
This blog discusses the technical aspects of Software Update Manager (SUM) for a System Conversion:
the transition of an existing SAP Business Suite system to SAP S/4HANA on premise.
Readers should be familiar with the transition paths to SAP S/4HANA (seeThe road to SAP S/4HANA: the
different transition paths) as well as with the technical procedure of a System Conversion (see The System
Conversion to SAP S/4HANA, on-premise edition 1511 - Technical procedure and semantic adaption tasks).
System Conversion: SUM is the tool for the transition to SAP S/4HANA on premise
System Conversion is the process of transitioning an existing SAP ECC system to SAP S/4HANA on
Premise
Software Update Manager (SUM) is the tool for this transition: either with or without DMO
If the source is already on SAP HANA DB, it is SUM w/o DMO
If the source is not yet on SAP HANA DB, it is SUM w/ DMO
System Conversion: three tasks for SUM to enable Simplification of SAP S/4HANA
Software Update: Provide new applications and new tables (as part of the new data model) by
providing new software components (like S4CORE) and by updating existing software components
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)
Data Conversion: conversion of table content to new data model
One-step or two: depends on Unicode (UC)
General rule:
If the source system is already on UC, the transition is a one-step procedure
If the source system is not yet on UC, the transition is a two-step procedure
Exception
For SAP R/3 4.7 and SAP ECC 5.0 Unicode systems: these releases do not include the
Customer-Vendor-integration (with Business Partners) that is required for SAP S/4HANA, so a
two-step approach is required

Yes, in general DMO may include the UC Conversion - but not for target NW 7.5:
NW 7.5 is only UC: no non-UC kernel (and no non-UC export load) available
DMO builds up a shadow system for the source system on the new release
For non-UC systems, this shadow system has to be non-UC -> not possible for NW 7.5
Recommended path for non-UC source systems is discussed below
Even if one-step is possible, for business reasons customers may decide to have several steps, as
discussed by Frank Wagner (see above)
Important:
it is relevant for all target systems based on SAP NetWeaver 7.5 (also for systems part of SAP Business Suite
7 Innovations 2016, like SAP ECC 6.0 EHP 8) that the source system has to be already on Unicode.

Generated by Jive on 2016-07-11Z


1

Software Logistics: System Conversion to SAP S/4HANA: SUM is the tool

SAP S/4HANA Simple Finance 1503 is a special member of SAP S/4HANA family
SAP Simple Finance on premise edition 1503 (fka sFIN 2.0) is a part of the SAP S/4HANA family
Still "1503" is slightly different from a technical perspective
it is based on NW 7.4 (not 7.5)
Usage of Maintenance Planner is not mandatory (but recommended)
Transition to "1503" with SUM/DMO including Unicode Conversion is possible
Note that "sFIN" is not the official name
Note that the next release, SAP S/4HANA Finance 1605, is based on NW 7.5, so source has to be
Unicode!
Recommended path for two-step approach: goto 6.17 [this section was edited on march 8th 2106]
As discussed above, a two-step approach is required: for all non-UC systems and for R/3 4.7 & SAP
ECC 5.0
Recommendation:
first step to for SAP ECC 6.0 EHP 7 (6.17) with SUM
second step later then with SUM (w/ DMO) to SAP S/4HANA 1511 f
Alternative for SAP ECC 6.0 EHP 0...7 on anyDB:
You may only do the Unicode Conversion without update & migration (stay on software level)
Benefit: no change of business processes, so project effort may be reduce
Discussion:
Targeting EHP8 not possible, because it is based on 7.50 => requires UC source system

Generated by Jive on 2016-07-11Z


2

Software Logistics: System Conversion to SAP S/4HANA: SUM is the tool

Best regards, Boris Rubarth


Product Manager Software Update Manager, SAP SE
4084 Views Tags: sum_tool, sum, software_update_manager, dmo, systemconversion

Shubham Srivastava
Mar 31, 2016 11:35 AM
very well explained...good document
Ning Tong
Mar 31, 2016 9:28 AM
Hi Brois,
For customer starting from 4.6c on anyDB, it is better to do the following steps, right?
1. CU&UC to ERP 6.0 EHP 7
2. SUM/DMO to S/4HANA?
Regards,
Ning Tong
Sergio Guerrero
Mar 8, 2016 9:25 PM
great post... all this is now more clear that is also presented on the S/4HANA implementation openSAP course.
thank you for sharing
Andy Silvey
Mar 8, 2016 9:18 PM
Hi Boris,

Generated by Jive on 2016-07-11Z


3

Software Logistics: System Conversion to SAP S/4HANA: SUM is the tool

long time no see, nice blog.


Hope you are doing fine,
Andy.
Sandeep Hanumaihgari
Nov 25, 2015 5:30 AM
Excellent post Boris Rubarth...this makes me very clear now on system conversion to SAP S/4HANA.

Generated by Jive on 2016-07-11Z


4

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy