Professional Documents
Culture Documents
SAP published a well established procedures that includes all the aspects of the SAP migration to HANA or S/4. HCL
will follow these processes as best we can. The documentation for all of the upgrade/migration processes is available
on SAPMarketPlace and can be made available if required.
Make needed adjustments based on the outcome of the three steps above (lessons Learned)
In certain cases the above first two steps can be combined into a single step.
Go-Live Phase
Ongoing support
System Prerequisites
To migrate your system to SAP Business Suite powered by SAP HANA, your system must meet certain prerequisites,
minimum releases for example.
Be aware of benefits provided by SAP Business Suite - Innovation 2013 that help you to continue to innovate without
disruption
Be aware of the minimum releases of your SAP ERP, SAP CRM, SAP SCM, and SAP SRM for SAP Business Suite
powered by HANA
Check the release notes for all enhancement packages for details of current restrictions and release restrictions
Be aware of the optimizations available with SAP Business Suite powered by SAP HANA
Know about the impact on third-party solutions and add-ons
For all relevant information about the system prerequisites, see Prerequisites linked in the information section.
Technical System Landscape Design provides guidance on the appropriate IT infrastructure for SAP HANA, based on
your requirements
Migration to SAP HANA only involves the switch to another database. Everything else in your landscape will stay the
same
HANA Sizing provides guidelines for a hardware-efficient approach
Multi-SID HANA installation can provide TCO benefits and greater flexibility of system operations
DEV and QAS systems can be combined with the MCOS scenario in a single hardware in a multi-tiered landscape
System Sizing
Due to the appliance character of SAP HANA, sizing is easier and at the same time more complicated. It is easier
because the choice of hardware configurations are limited at the moment, and SAP offers tools and procedures that
help to determine the required hardware for exact requirements. Sizing is more challenging because of data growth
and thus careful planning and aggressive housekeeping have a much higher impact on cost of ownership than with
traditional RDBMSs.
Sizing Principles
The most important sizing driver is the memory, and the second most important is the CPU requirement. I/O sizing is
also extremely important, but can only be performed during the realization phase. There is also a disk space
requirement for persistence and log data, but this sizing is completely dependent on memory and thus fairly straight
forward.
Memory (most important sizing driver)
1 Memory sizing is determined by the data footprint in SAP HANA (business and metadata in column
and row stores)
2 Memory is also used by other components, for example SAP HANA caches and the operating
system
CPU
1 To forecast the DB CPU requirement is challenging. This is true for both SAP HANA and AnyDB
2 CPU usage is different for SAP HANA than AnyDB
Disk
1 Disk is required for data persistence and for logging data
Sizing formula is independent of whether the system is an OLAP or OLTP system
On Premise
Appliance
Cloud
Private Cloud, Managed Service
Public Cloud,
Pay-as-you-go
In November 2015 (1511) updates have been released for both, SAP S/4HANA, on-premise and cloud edition. In
November 2015, SAP delivered a massive wave of simplification and innovation in the core of SAP S/4HANA. With
this delivery, enterprises can drive unprecedented business value with innovative use-cases - in core financial and
operational areas such as in logistics taking full advantage of a simplified data model and a responsive user
experience.
Key simplifications and innovations include:
Optimized working capital with new accounts payables and receivables cockpits
Decreased stock buffers with simplified data model in inventory management for real-time, high-volume processing
Increased visibility with real-time stock and material flow insight
Reduced manufacturing cycle time with streamlined material flow for internal requirements (MRP)
Augmented reactivity with real-time monitoring of production orders regarding flow and critical issues
Improved operational decisions with easy simulation of supply alternatives
Lower procurement costs with standard integration to the Ariba Business Network
Better customer service with new sales order fulfillment cockpit for instantly identifying bottlenecks and issues
For more information see as well the SCN blog from Sven Denecken: Link
New Implementation
New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
System Conversion
Customers who want to change their current system into a SAP S/4HANA system.
Landscape Transformation
Customers who want to consolidate their landscape or to selectively transform data into a SAP S/4HANA system.
The SAP S/4HANA, on-premise edition 1511 system conversion supports one-step procedure (Database, SAP
NetWeaver and application transition in one step) for SAP ERP 6.0 EHP x7 systems. System Conversion requires
a Unicode (UC) source system. Non-Unicode source systems will require a two-step approach (first move to Unicode
then to SAP S/4HANA, on-premise edition 1511).
Basically it can be distinguished between technical and semantic tasks during the system conversion. The
technical installation procedure is based on established lifecycle management tools (Maintenance
Planner, Software Update Manager [SUM] and Database Migration Option [DMO]). Due to the fact that
SAP S/4HANA is a new product line (and not the successor of SAP Business Suite) things are done
differently in SAP S/4HANA.
Many of the changes are technical in nature and have no or only limited impact on peoples work and thus
do not trigger business change management. Such changes will be mandatory when converting a system
to SAP S/4HANA.
Other decisions are more of a strategic nature determining which version of functional support will evolve
into the digital era and provide the capabilities demanded from the unstoppable business process
innovation. Where those strategic directions demand change management through adoption, SAP at
large keeps the traditional capabilities available as compatibility scope enabling a rather technical
migration of these processes and leaving the time of change management at customer decision that may
well happen when initially converting or at a later point in time.
To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the
Simplification List for SAP S/4HANA, on-premise edition 1511. In this list we are describing in detail on a functional
level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged
certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP
Business Suite products.
The Maintenance Planner is a pre-requisite for the system conversion to SAP S/4HANA, on-premise edition 1511.
The Maintenance Optimizer (MOPZ) is not used
For more information regarding Maintenance Planner see SAP Help: http://help.sap.com/maintenanceplanner
Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA, on-premise edition
1511.
Note:
You must run the Maintenance Planner before the SUM.
Ensure that the latest version of the Software Update Manager is used:
For all information about using the SUM, please see the document Conversion of SAP Systems to SAP S/4HANA,
on-premise edition Using Software Update Manager available at:
support.sap.com/sltoolset (LINK)
Section "System Maintenance"
See the following SCN Blog with helpful information regarding DMO, and regarding SUM for System Conversion
Database Migration Option (DMO) of SUM - Introduction
System Conversion to SAP S/4HANA: SUM is the tool
Conversion Pre-Checks
Pre-checks are shipped as SAP Notes to customers that want to convert to SAP S/4HANA. Customers can use these
pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the
instances that need addressing before attempting the conversion process. The checks are run twice again during the
conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist.
Implement SAP Note 2182725, and all the related notes attached to it. Make sure to use latest version of
this note and regularly check for updates of all attached notes. Implement and run these reports on every
system (Sandbox, DEV, QA, PROD) you want to convert to SAP S/4HANA, on-premise edition 1511.
Report R_S4_PRE_TRANSITION_CHECKS.
For more information about the Custom Code Check tool, see SAP Help Portal: Link and the following SCN blog:
SAP S/4HANA Custom Code Migration Worklist.
Link
Maintenance Planner
Link
Software Update Manager (SUM) for SAP S/4HANA, on-premise edition 1511Software
Link
Link
SAP SCN
SAP S/4HANA Cookbook
Link
Link
Link
Link
Link
Link
Link
Link
Link
Link
SAP S/4HANA, on-premise edition: Additional remarks regarding Business Functions (FPS2)
Link
Miscellaneous
SAP S/4HANA @SAP Learning Hub
Link
S/4HANA Trial
Link
Link
SAP Activate
Link
Link
Link