Chemtura Project Approach 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.
The System Conversion to SAP HANA The SAP HANA Cookbook is link to this process is included. https://proddps.hana.ondemand.com/dps/d/preview/6932132d32b54f58a961a755e043e21e/1.0/enUS/index.html#url=e25e8322ed6a44b097afd7d08adcc59d.html The approach is summarized below. Planning Phase Determine all prerequisites for : o Sizing o HW o OS o Storage o Database o SAP o Custom Code o Deployment Options o HA/DR Deployment Phase The migration/upgrade tasks to be performed on SBX, DEV and QA (Pre-Prod) systems Migrate Systems to required prerequisites levels as listed above Upgrade/migrate systems (SAP/DB) Test the upgrade 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 Migrate/Upgrade per the final adjustments of the deployment phase Support 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.
Executive Summary and Key Takeaways • • • • •
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 Landscape Planning Technical Landscape Planning involves a variety of activities, such as sizing, deployment and installation options, data volume management, architecture options, and target landscapes.
Executive Summary and Key Takeaways • • •
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
Migration Impact on Landscape Switching to SAP HANA does not break the connectivity to other systems, such as third-party systems and central hubs like Portal or PI, or cross-application connections such as CIF and ALE. From a technical point of view, migration to SAP HANA is just a switch to another database. Most other things in your landscape stay as they are. A SAP Business Suite system running on SAP HANA can still connect to and be integrated with other systems and hubs in the same way as a SAP Business Suite system running on any other database. You can still use the same front ends and clients to connect to your system. Even the application servers can be reused as they are, provided they are running on separate servers and not on the database host. What will change is the kind of database currently running. SAP HANA has a few operational specifics, for example that it runs on SUSE Linux Enterprise.
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
Choose from a variety of SAP HANA deployment options Move to the SAP HANA platform quickly and seamlessly by choosing the deployment option that best fits your business needs, budget, and resources. SAP HANA can be deployed on premise for maximum control, in the cloud for fast time to value, or through a hybrid model that supports a variety of deployment scenarios – from on-premise to cloud to third-party.
On Premise Appliance
Go live quickly with a pre-configured appliance. Preconfigured hardware Preinstalled software Solution validation by SAP and partner
Tailored Data Center Integration
Choose your hardware and infrastructure. Existing hardware and infrastructure Reduced cost and risk Increased flexibility and control
Cloud Private Cloud, Managed Service
Deploy in a fully managed, secure cloud – with SAP HANA Enterprise Cloud. Reliable hosting environment Managed services approach Increased flexibility and low TCO
Public Cloud Infrastructure-as-a-Service
Bring your own SAP HANA license to run on Amazon Web Services (AWS) or Microsoft Azure clouds – via SAP HANA Infrastructure Services. Fast time to value No hardware investment Flexible scalability
Public Cloud, Pay-as-you-go
Deploy SAP HANA One in third-party clouds: Amazon Web Services (AWS), or Alibaba. Hourly pay-as-you-go rate Single database instance Run custom applications only
Rapid database migration of SAP Business Suite to SAP HANA V5.10 This rapid deployment solution supports the migration of an existing SAP Business Suite installation to the SAP HANA database system without disruption of the existing Business Suite scenarios. This new deployment approach provided with SAP’s rapid deployment solutions which leverage out-of-the-box accelerators and predefined scope will help accelerate your adoption of SAP HANA to supercharge your SAP Business Suite. The simplified process eliminates any migration guesswork and uncertainties regarding realization timeline, due to automation of steps as well as planning security due to standardization of the approach.
The System Conversion to SAP S/4HANA, on-premise edition 1511 - Technical procedure and semantic adaption tasks Release of SAP S/4HANA, on-premise edition 1511
• • • • • • • •
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
The System Conversion to SAP S/4HANA, on-premise edition 1511 Different transition paths are supported with SAP S/4HANA, on-premise edition 1511:
• •
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 x…7 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 technical procedure – well established tooling Maintenance Planner The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the conversion.
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)
• • • ◦
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"
Database Migration Option (DMO) DMO - the one-step-migration to SAP HANA database for SAP systems. It is called "database migration option (DMO) of Software Update Manager (SUM)". For SAP S/4HANA it combines the installation of the SAP S/4HANA, on-premise software and database migration to SAP HANA in one tool
• •
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
Adoption Tasks – how SAP support the customer Simplification List for SAP S/4HANA, on-premise edition 1511 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. For more information see Simplification List for SAP S/4HANA, on-premise edition 1511 (FPS1): PDF
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.
Custom Code Checks These checks are based on the Simplification list concept. Before converting to SAP S/4HANA, on-premise edition 1511 you need to check your custom code against the SAP S/4HANA simplifications. These simplifications are loaded into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA 1511, on-premise edition
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.
Related information – at a glance SAP S/4HANA, on-premise edition – General Information SAP Help SAP S/4HANA, on-premise edition 1511 documentation
Link
Getting Started With SAP S/4HANA, on-premise edition 1511
PDF
Conversion Guide for SAP S/4HANA, on-premise edition 1511
PDF
Simplification List for SAP S/4HANA, on-premise edition 1511
PDF
Maintenance Planner
Link
Software Update Manager (SUM) for SAP S/4HANA, on-premise edition 1511Software
Link
Logistics Toolset 1.0 --> Section "Documentation" --> System Maintenance
Custom Code Check tool (SAP Help)
Link
SAP S/4HANA Feature Scope Description
PDF
SAP SCN SAP S/4HANA Cookbook
Link
Simplification List for SAP S/4HANA, on-premise edition – XLS-based format
Link
Simplification List TOP Items
Link
SAP S/4HANA, on-premise edition – the transition paths
Link
Maintenance Planner – SCN Blog
Link Link
Software Update Manager (SUM) - SCN Blog with more information
Link
DMO Database Migration Option – SCN Blog with more information
Link
SAP SCN - SAP S/4HANA Custom Code Migration Worklist
Link
Custom Code within SAP S/4HANA On-Premise
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
SAP Best Practices for SAP S/4HANA, on-premise edition
Link
SAP Activate
Link
FIORI App Library
Link
Elements for Designing a Transition Roadmap to SAP S/4HANA
Link
SAP S/4HANA, on-premise edition – Important SAP Notes General Information SAP S/4HANA, on-premise edition 1511: Release Information Note
SAP Note 2189824
SAP S/4HANA, on-premise edition 1511: Restriction Note
SAP Note 2214213
SAP S/4HANA, on-premise edition 1511: supported industry solutions
SAP Note 2214213
SAP S/4HANA, on-premise edition 1511, Country Versions: Release Information & Restriction Note
SAP Note 2228890
Simplification List for SAP S/4HANA, on-premise edition – XLS-based format
SAP Note 2313884
Blacklist Monitor in SAP S/4HANA on premise
SAP Note 2249880
SAP Fiori for S/4HANA
SAP Note 2214245
Process integration with other SAP on-premise systems
SAP Note 2241931
Pre-Check related information Delivery of the S/4H System Conversion Pre-Checks
SAP Note 2182725
Custom Code related information Custom code check content for SAP S/4HANA, on-premise edition 1511
SAP Note 2241080
Running Custom Code Analyzer and Downloading ZIP File(s)
SAP Note 2185390
Business Function related information SAP S/4HANA, on-premise edition 1511: Always-Off Business Functions
SAP Note 2240359
SAP S/4HANA, on-premise edition 1511: Always-On Business Functions
SAP Note 2240360
Add-On / Partner related information SAP S/4HANA, on-premise edition 1511: Compatible Add-ons
SAP Note 2214409
SAP S/4HANA, on-premise edition 1511: Compatible partner products
SAP Note 2244450
Add-on Product Versions released on SAP NETWEAVER 7.5
SAP Note 2156130
Uninstalling ABAP add-ons
SAP Note 2011192
Conversions to SAP S/4HANA On-Premise with 3rd Party / non-SAP Add-ons
SAP Note 2308014
SAP NetWeaver 7.5 Additional Information about the update/upgrade to SAP NetWeaver 7.5
SAP Note 2197259
Minimal DB system platform requirements for SAP NetWeaver 7.5
SAP Note 2158828
[DocumentBodyEnd:6183db21-23cc-4411-977e-33ae6b281869] BEGIN attachments END attachments
