SAP ECC VS HANA.pdf

SAP ECC vs S/4HANA Introduction

Comparisons of the versions •

SAP ECC6

•

SAP ECC/Suite on HANA

•

SAP S/4HANA Finance

•

SAP S/4HANA Enterprise Management

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

Internal

2

SAP HANA SAP HANA is an in-memory database: It is a combination of hardware and software made to process massive real time data using In-Memory computing. It combines row-based, column-based database technology. Data now resides in main-memory (RAM) and on a hard disk. It’s best suited for performing real-time analytics, and developing and deploying real-time applications. An in-memory database means all the data is stored in the memory (RAM). This is no time wasted in loading the data from hard-disk to RAM or while processing keeping some data in RAM and temporary some data on disk. Everything is in-memory all the time, which gives the CPUs quick access to data for processing.


Internal

3

SAP Suite on HANA (also known as Business Suite on HANA) Suite on HANA is ECC running on an SAP HANA database. ECC, or Enterprise Core Component, is a set of ERP tools for core business functions like finance, logistics, warehouse management, and sales and distribution. SAP ECC was designed to run on a range of databases including Sybase ASE, MS SQL Server, Oracle, and others. SAP Suite on HANA came first. It has all of the traditional functionality of an ECC environment but the engine (database) is now a HANA engine. Nearly all of the SAP transaction codes are available and there is no concept of data simplification. Because SAP ECC predates SAP HANA, companies using it generally started on other databases. When ECC users perform a SAP HANA migration without changing the front end, it becomes SAP Business Suite on HANA. This lets businesses benefit from the performance boost of SAP HANA without restructuring the application layer.


Internal

4

SAP Business Suite vs. S/4HANA Suite on HANA is ECC running on an SAP HANA database. SAP ECC was designed to run on a range of databases including Sybase ASE, MS SQL Server, Oracle, and others. SAP Suite on HANA has all of the traditional functionality of an ECC environment but the engine (database) is now a HANA engine. Nearly all of the SAP transaction codes are available and there is no concept of data simplification. Because SAP ECC predates SAP HANA, companies using it generally started on other databases. When ECC users perform a SAP HANA migration without changing the front end, it becomes SAP Business Suite on HANA. This lets businesses benefit from the performance boost of SAP HANA without restructuring the application layer.


Internal

5

What is the fundamental difference between the SAP Business Suite code line and the new SAP S/4HANA product code line? The SAP HANA in-memory database stores data in rows and columns. It is this combination of both storage approaches that produces the speed, flexibility, and performance of the SAP HANA database. In-memory database means that data is read from memory i.e data always reside in main memory RAM (though Write happens in hard disk) and hence in-memory database reads data much faster w.r.t traditional databases (fetching the data from hard disk).Hana’s column based tables provide faster access (as only affected columns need to be read in a query), better compression (due to few distinct values compared to rows), parallel processing (different columns can be easily processed parallel).OLTP and OLAP capability in same system with real time reporting and predictive analysis. There will be no aggregate (total), index and history tables in S4H. Aggregates are created dynamically based on line item table instantaneously (on the fly). Single source of truth SAP S/4HANA will only run on SAP’s HANA platform, and it will not run on any other platform. This is extremely significant because previously, all SAP products were designed to run on any database platform, including those from Oracle, Microsoft and IBM in recent years. To be clear, SAP S/4HANA will run only on the HANA platform. SAP S/4 is a replacement to the SAP R/3 or Business Suite platforms that have been in place in many global businesses since the release of SAP R/3 in 1992 with HANA database. © 2016 SAP SE or an SAP affiliate company. All rights reserved.

Internal

6

Comparisons of the versions •

SAP ECC6

•

SAP ECC/Suite on HANA

•

SAP S/4HANA Finance

•

SAP S/4HANA Enterprise Management


Internal

7

SAP ECC VS SAP S/4HANA When SAP built R/3 SAP ECC, it was built to run on any database (AnyDB), and used the capabilities of the lowest common denominator. This led to tremendous complexity in the software design which has persisted through over two decades. For S/4HANA, SAP is in the process of renovating the ECC code, simplifying and optimizing the software, and adding new functionality. There’s a complete S/4HANA Finance module today and an improved logistics module . The remainder of ECC systems functionality with S/4HANA add-ons behaves like SAP Business Suite on HANA from the user’s perspective. SAP S/4HANA is a new product. It is based around the core ECC solution. SAP realized that Business Suite customers wouldn’t want to undergo this level of change, and so they built S/4HANA on the original Business Suite.There are a number of differences, however: The data has been 'simplified'. This is achieved by replacing the core tables within certain processes into a single table. New functionality has been released, however some traditional functionality is no longer available due to the ‘principle of one’. Embedded reporting. SAP BW and SAP BPC can be embedded within the S/4HANA environment. It is worth noting that S/4HANA will not replace BW or BPC but it enables certain scenarios to be performed within the new product – not all, however. © 2016 SAP SE or an SAP affiliate company. All rights reserved.

Internal

8

What modules are available for SAP S/4HANA? Currently, there is support for core finance (GL). and extended to Logistics in 2017, and other modules will follow. It’s worth noting that the existing Business Suite code lines are backwards compatible with HANA, so all the existing supported modules will run. SAP will rewrite the existing modules for HANA over a 3-5 year period, based on popularity.

SAP is committing all of it's development resource to rewriting some 400million lines of code – so this is the most strategic development decision in SAP’s 40-year history.


Internal

9

ECC VS SAP S/4HANA? S4H combines the data structures of different components (for FI , AA , CO , CO-PA and ML) into a single line item table ACDOCA, called as Universal journal . It eliminates several aggregate and index tables. Now, data needs to be inserted only a single table instead of several tables thus reducing the data foot print drastically. MATDOC is also a new line item table for inventory management and it eliminates 26+ tables. Material documents will be stored in MATDOC but not in MKPF or MSEG tables. Merger of CO and FI In ECC , FI GL accounts are mapped to CO primary cost elements . In S4H, only one field of universal journal is used to store both GL account and cost element. Cost elements (both primary and secondary) are now GL accounts and hence created / maintained (in FS00) with relevant Cost element category. Reconcilation (as in case of CO to FI) is not needed now. Period end closing also will be faster. New GLS4H is technically very similar to new GL of ECC due to its data structure. Customers using classic GL need not use Document split or parallel ledger. However, new GL’s functionality (Parallel ledger) is a pre-requisite for new Asset accounting . CO-PA Account based CO-PA is now the default option with Costing based CO-PA as optional. Both options can be run simultaneously.


Internal

10

SAP S4/HANA VS SAP ECC

Business partner All customer and vendor master need to integrated / migrated as Business partner . Probably, SAP is trying to align the concept of business partner as in other SCM applications like APO , EWM , TM etc as these SCM applications also will be natively integrated with core of S4H in future releases. Customer-vendor integration (CVI) is a mandatory step. Refer URL https://websmp201.sapag.de/~sapidp/012002523100007374172016E.pdf for more details. Extension of Material number field : Material number can now be 40 characters from existing 18. It is a optional feature. Impact of this extension on custom coding, interfaces, other SAP applications need to be evaluated before switching on 40 characters. Refer note 2267140 for more details.


Internal

11

What if I am still on MSSQL, Oracle. Will I still get support from SAP? Yes, and SAP to retain its relationships with other database partners. There is an install base of tens of thousands of Business Suite customers running other databases, and these will not be forgotten. It’s important to remember that ERP systems have extraordinary longevity – the lifespan can be 10-20 years or more, and SAP will continue to support existing systems in the long term. SAP notes that it will continue to innovate in the Business Suite for AnyDB – for example, by porting any innovations which are created for S/4HANA which will run on AnyDB back to the Classic Business Suite code base. In practice, this means that existing Business Suite customers will continue to be supported, but those that want innovation will need to move to S/4HANA.


Internal

12

SAP S/4HANA versions One is SAP S/4HANA Finance which is Suite on HANA with a simplified Finance module and full ECC scope. SAP S/4HANA Enterprise Management simplifies Materials Management and Operations as well as Finance. This has a different base component as “SAP_APPL” has been replaced by “S4CORE”. Each of these products are still evolving and therefore the solution may not provide all of the functionality we currently have in ECC solution with certain Industry Solution functionality not available yet. With Simple Logistics release of a SAP ERP product. This paved the way for a separate installation for SAP S/4HANA and the regular Business Suite and S/4HANA parted ways. Modules such as Sales and distribution, Production Planning and Quality Management are in the roadmap to be simplified within S/4HANA Enterprise Management. The HR module will not be simplified within S/4HANA, although the functionality will still be available.


Internal

13

What databases will SAP S/4HANA run on? As its name suggests, SAP S/4HANA will only run on SAP’s HANA platform, and it will not run on any other platform. This is extremely significant because previously, all SAP products were designed to run on any database platform, including those from Oracle, Microsoft and IBM in recent years. To be clear, SAP S/4HANA will run only on the HANA platform. Unfortunately, SAP HANA is sufficiently innovative that the rewritten S/4HANA software performs terribly on the traditional RDBMS systems.


Internal

14


15

Content Guidelines


Delete this page of instructions when sharing the template with your customers

Internal

16

SAP ECC VS HANA.pdf

Recommend Documents