Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
TammyPowlas
Active Contributor

SAP provided this webcast to ASUG Volunteers, which is a nice benefit to being a volunteer. Please note these are my notes as I heard them and the usual disclaimer applies that things in the future are subject to change.

Figure 1: Source

Why focus on simplicity?

Today we have a lot of different information sources, complex business processes, and there is a lot of technology change.  The challenge is to be on top of technology.

Profit losses is your personal experience in the three dimensions; SAP “targets” to solve these problems.

Figure 2: Source: SAP

Figure 2 spans several years

Mainframe to client server with R/3

2004 was ERP

With technology move to HANA it is now S/4 HANA, driven by “ultimate simplicity & UI to change user experience”

Figure 3: Source: SAP

SAP will simplify data model; changing the basis of the software but not change the business.  No updates of indices/aggregates.

More than 280 customers live with ERP/CRM systems in 40 countries around the globe; every size of customers

The user experience, Fiori, has to be web-enabled, HTML5, supporting automatically any device.

Configuration does not have to be complex or take a lot of time.  SAP will use the guided configuration especially in cloud, also for on premise

Figure 3 on the right shows the key benefits S/4 HANA family.

S/4 HANA is offered for different deployments, for on premise, in cloud – private & public.  These products will be sharing the same code and key benefits.  The cloud can be a subscription service, with a new offering on the license model.

SAP natively used the major benefits of HANA – directly linked to data footprint

This supports a clear, embedded standalone analytics with merged OLAP/OLTP.

No more locking due to not update multiple tables

Actual / historical data where historical data can be node or disk and you only work on actual data and reduce data footprint

In the past the UI was driven by transactions which you maintained; now you can combine OLTP/OLAP with the in-memory database.  During transaction runs, the data is fast enough to gather predictions, simulations, recommendations – you don’t need the selection screen any more.  You can work on a screen showing the best options to solve the business problems.

Co-deployment is S/4 HANA - ERP, CRM on ERP in the future to simplify landscape

You can run on a HANA multi-tenancy database; use HANA Cloud Platform to build extensions

Figure 4: Source: SAP

“Technology change leads to tremendous business advantage”.  If you update an FI document with 3 lines items – BKPF and BSEG – to support a row-based database with aggregates the with 10 inserts and 5 updates.

SAP Simple Finance runs with 4 inserts and no updates for an update as shown in Figure 4.

Figure 5: Source: SAP

Figure 5 shows the result of the Simple Finance example and with a reduced footprint with less updates, good for throughput and performance

Figure 5 shows measures with customers.  Benefits include on the fly aggregations, used for search, fact sheets, analytics inside OLTP to be used with OLTP transactions.

Figure 6: Source: SAP

If you run a financial close, you can simulate financial close

Then we saw a demo on the last 8 quarters based on SAP data (scrambled)

Figure 7: Source: SAP

Fields are available in the screen below in Figure 7

He dragged and dropped revenue on the canvas

Analytics are directly on the OLTP system with aggregates on the fly, and no separate analytics solution is needed any more

You can go down to line items, cost and revenue, and compare

You can perform simulations and comparisons

You can do a “Financial close on the fly everyday”

Figure 8: Source: SAP

Business benefits “are easy”, the SAP speaker said.

Figure 9: Source: SAP

S/4 HANA is completely “Fiori-sized”

Figure 10: Source: SAP

Figure 10 shows the Roadmap for 2015

S/4 HANA is available with Simple Finance

Q1 will release a public cloud – will include the logistics part, procurement, inventory, sales & distribution

SAP will focus on Professional Services first with a simplified offering

Managed cloud will be in May SAPPHIRENOW timeframe

In Q4 SAP will have an update for the on premise solution.

Figure 11: Source: SAP

The three solutions are built on SAP HANA, NetWeaver code, and extend on HANA Cloud Platform (HCP)

They come with Fiori experience

It integrates (or will integrate)  with cloud offerings e.g. HCM SuccessFactors

Figure 12: Source: SAP

Figure 12 explains the role of the HANA Cloud Platform, “platform as a service”.

In the cloud, you want to extend solutions in cloud

Important to getextension platform out of cloud - e.g. Fiori as a service, to build UI’s on the SAP solution

You can build on app services, and rich services

HCP comes on an open stack which means it is “easy to adopt” for partners; there to build extensions, integration and new applications.

Question & Answer

Q: GRC 10.1 on HANA is already available – will it be available to be co-deployed with ERP?

A: Suite on HANA in market – not all solutions are simplified in data model – need to follow up

Q: Will I still be able to classify customer exits?

A: in the three different deployments different solutions – for on premise, no change

Web IDE is an extension of exits but not modification

Q: Do we need to repurchase on premise?

A: Promotion for S4/HANA – foresee to sign an amendment to Suite on HANA

Q: Explain migration from ERP to S4/HANA?

A: First go to Suite on HANA – upgrade to latest enhancement package and change database

Simple Finance – install a package for that

"Dropping of tables" is not tables, just aggregations and indices

Technology – replace tables with views – code is still executed

Migration for on premise is similar to Simple Finance

He says to call it an upgrade than migration

Q: When are industry solution be available?

A: Several industry is in standard – working on a roadmap

Q: 280 customers live?

A: Suite on HANA – January 2013 launch, 9 live customers at SAPPHIRE 2013

More than 200 customers are now live Suite on HANA (ERP)

More than 50 CRM on HANA Live

Q: What does co-deployment mean?

A: Add-ons to ERP – one system

Q: Can S4 work on side car accelerators?

A: Since out with Suite on HANA (SoH) customers move to SoH to get OLTP/OLAP combination

S4 is the upgrade of complete suite- not a side by side solution

Q: Is Simple Finance a prerequisite for S4?

A: Yes

Q: What is release plan for modules like manufacturing?

A: S4 is a complete new suite

Q: Is S4 only available on premise or cloud?

A: S4 is a family of solutions with 3 capabilities – public, managed, on premise

All three deployment options

Q: Since CRM/ERP/SRM is on the same instance with S4 is XI/PI still relevant?

A: Communication between systems – different middle wares are needed – will come out with scenarios where not needed any more.  To not disrupt, will not replace that.

Q: Can I go from Business Suite to S4/HANA?

A: Go from Business Suite to S4/HANA but will include Simple Finance

Will provide/work as one process

Q: Will all the add-ons be supported on S4/HANA

A: Will look at those add-ons; may need to redesign to remove aggregates – will have a roadmap

Q: When will S4 be GA?

A: With Simple Finance already in market, already there

Cloud – look for customer collaboration in Q1

Managed cloud – May

Update for on premise in Q4

Q: From skill how advise an SAP expert to transition to S4/HANA world?

A: Need to adopt HANA; many see as a big step

Application perspective – keep business objects in place

Technology – guarantee non-disruptiveness that code still run

Code on a column based in-memory database is an opportunity to run faster – code inspector updated for this; scan and code to learn what is good for your code

SELECT SINGLE on all columns – don’t do it

SAP built into code inspector and proposes what you should change

SAP has lessons learned

3 Comments
Labels in this area