SAP's Plattner: How S/4Hana Simplifies ERP - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Software // Enterprise Applications
Commentary
2/4/2015
03:27 PM
Doug Henschen
Doug Henschen
Commentary
Connect Directly
LinkedIn
Twitter
RSS
100%
0%

SAP's Plattner: How S/4Hana Simplifies ERP

SAP chairman Hasso Plattner explains what's possible with S/4Hana. Analysts and customers comment on the evolutionary vs. revolutionary debate.

Cloud ERP: 9 Emerging Options
Cloud ERP: 9 Emerging Options
(Click image for larger view and slideshow.)

SAP customers have been hearing the company's "Hana offers dramatic simplification" yarn for more than four years. So what exactly changed with Tuesday's launch of Business Suite 4 SAP Hana, dubbed S/4Hana for short?

In a one-on-one interview with InformationWeek, SAP chairman and co-founder Hasso Plattner explained that all the advantages of Hana in-memory computing could not be realized with the SAP Business Suite of old. While the technical and performance improvements are compelling, the real questions for users center on the sub-applications of ERP (CRM, supply chain management, HR, project lifecycle, and management) that SAP will bring into S/4Hana, how soon the change will happen, and what industry-specialized capabilities it will offer.

To answer those questions, we have to first look at what's changed, and why the previous iterations of SAP Business Suite could not take full advantage of Hana's in-memory capabilities.

S/4Hana apps run without aggregates, indexes, materialized views, and multiple copies of data. The old SAP Business Suite required all that because it was designed to run on conventional databases that store all those interim views to spinning disks. Third-party databases including Microsoft SQL Server and Oracle have gained in-memory appendages, but they still maintain the aggregates and indexes of the past, creating yet more versions of the same data.

"The full benefits have not been there because the full data models [of the legacy apps] were still in the system," Plattner told InformationWeek. "Our own CFO had never worked on a system that operated without aggregates, so the idea of doing every single report and every P&L statement running through 250 million lines of data in memory scared him. S/4 Hana does this in less than two seconds."

[ Want more on this news? Read SAP S/4Hana: Big Bet On 'Simplified' ERP. ]

In getting rid of all of those copies of data, all of which required storage capacity and processing cycles to keep all those spinning plates running in sync, SAP was able to simplify and shrink the underlying data model of the ERP suite.

So, what does this mean for users seeking simplification of their ERP systems? Yesterday we reported one version of that roadmap from Wieland Schreiner, executive VP of S/4Hana. But SAP clearly didn't do a good job of presenting a clear, consistent, and comprehensive roadmap, because comments and questions remain.

Hasso Plattner's explanation of the simplification possible with S/4Hana's finance app: 593 GB reduced to 42 GB, with only 8.4 GB being dynamic, current-year data requiring high availability and backups.

Hasso Plattner's explanation of the simplification possible with S/4Hana's finance app: 593 GB reduced to 42 GB, with only 8.4 GB being dynamic, current-year data requiring high availability and backups.

"S/4Hana finally brings a native solution that can demonstrate in-memory computing's business value," wrote financial analyst Jason Maynard of Wells Fargo Securities in a research note. "That said, we still think a coherent application rewrite across the entire application portfolio is needed to truly usher in a modern cloud suite."

Maynard's assessment seems to allude to one big question as to whether acquired cloud apps, such as SuccessFactors and Ariba, will move into S/4Hana or whether those functions will be rewrites of Business Suite apps. Which app you use to run and account for HR expenses, for example, is obviously a big deal.

Some executives waffled on this question and told us SAP could have it both ways, using virtual views to carry forward legacy apps. Schreiner told InformationWeek that SAP will favor the cloud-based apps over redeveloping legacy Business Suite apps that handle the same functions. If Schreiner's

Doug Henschen is Executive Editor of InformationWeek, where he covers the intersection of enterprise applications with information management, business intelligence, big data and analytics. He previously served as editor in chief of Intelligent Enterprise, editor in chief of ... View Full Bio
We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
D. Henschen
50%
50%
D. Henschen,
User Rank: Author
2/8/2015 | 4:10:41 PM
Re: Run your enterprise on a cell phone?
SAP/Plattner was not seriously suggesting running the enterprise on the phone. He was making the point that when you get rid of of the redundant copies of data -- aggregates, indexes, etc. -- and no longer need to have copies upon copies along with a complicated data model with much to keep in sync, the total footprint of the system is dramatically reduced such that it's comparatively easy to manage it as well to back it up and have it maintained in a highly available state. A financial system that required nearly 600 GB using Business Suite and a conventional data was was reduced to 42 GB using S/4Hana on in-memory technology, according to SAP. The dynamic data -- open orders and current-year data -- amounted to 8 GB. That's small enough, technically, to run on a phone -- the point being that the in-memory server required need not be all that big or expensive. 
D. Henschen
50%
50%
D. Henschen,
User Rank: Author
2/5/2015 | 3:29:12 PM
Run your enterprise on a cell phone?
That 8.4 GB figure in the diagram above represents the dynamic data in the enterprise -- open orders, current-year transactions and anything related to current-fiscal-year results. That amount is small enough to run on a smartphone, Plattner pointed out. It's not that you actually would do that, but the idea is that you don't need much of a server and storage footprint, with in-memory technology, as compared to conventional apps, with their many copies of data.


That's the theory anyway, but it's notable what SAP last year added a store-to-disk option for "warm" and archival data, as opposed to the hot data that's managed in memory.
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

Slideshows
11 Things IT Professionals Wish They Knew Earlier in Their Careers
Lisa Morgan, Freelance Writer,  4/6/2021
News
Time to Shift Your Job Search Out of Neutral
Jessica Davis, Senior Editor, Enterprise Apps,  3/31/2021
Commentary
Does Identity Hinder Hybrid-Cloud and Multi-Cloud Adoption?
Joao-Pierre S. Ruth, Senior Writer,  4/1/2021
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Successful Strategies for Digital Transformation
Download this report to learn about the latest technologies and best practices or ensuring a successful transition from outdated business transformation tactics.
Slideshows
Flash Poll