Advancing your SAP Solutions A review of future options around SAP on IBM i and SAP HANA

Transcription

1 Advancing your SAP Solutions A review of future options around SAP on IBM i and Ron Schmerbauch, SAP on Power IBM i rschmerb@us.ibm.com November 2016 Enhingen, DE

2 Agenda What do things look like in 4Q2016? Quick review of IBM i and history What guidance does IBM have? What is coming in the rest of the Summit?

3 comments from past Summits Maturity of HANA as a DB layer Improved quality allows porting to POWER Columnar capabilities DB2 for IBM i EVIs also provide columnar capability IBM i still leads SAP BW-EML benchmark category (500M rows) Design point - HANA was designed to run OLAP queries Not OLTP ie Business Suite In-memory challenges SSD and Flash speeds are also orders of magnitude faster than disk HANA requires fast disk (for initial load and paging) Memory capacity limits are reachable - core/memory ratio 3

4 SAP and IBM development perspective Business as usual another development interlock this week We have a growing number of installations to support We have new OS/DB requirements to fulfill for SAP SAP is still implementing functions IBM i has already delivered Customers have not consumed everything we can offer today Including IBM i 7.3, LaMa, NW 7.50, SAP HA, Flat infocubes There is another kernel and NetWeaver release to prepare In expectation of another Business Suite release in the future And another IBM i version and Power9 in development

5 IBM i and Integration LPAR support for Linux and IBM i on the same Power box IBM i Application server for HANA DB ERP Sidecar small subset of ERP tables on HANA for queries Why are so few using this if reporting directly from ERP is so important?

6 The S/4HANA vision From: One DB per application Point-to-point integration Long running queries, e.g. in batch mode To: S/4HANA One DB per landscape No integration necessary Real time execution 6

7 Current State Business Suite and S/4 family on HANA on HANA DB2 for IBM i SAP BW SAP BW DB2 for IBM i Finance SAP BW/4 HANA SAP S/4HANA Core

8 Definitions - Migration vs Conversion Migration Primarily a DB exchange Most business logic does not need to change Some risk, some effort and more HW cost Some things improve, some may get worse as a result of DB change A Migration does not solve: Sizing problems lack of resources Application server tuning issues Application or process logic problems Ex - Oracle to IBM i, SQL Server to IBM i, SAP ASE to IBM i, etc.

9 Definitions - Migration vs Conversion Conversion Often a DB and/or OS change Business application logic definitely changes, users notice New customization required More risk, more effort and more cost Some things improve, some may get worse as a result A Conversion does not solve: Sizing problems lack of resources Application server tuning issues Application or process logic problems Ex - SAP R/2 to SAP R/3, SAP ERP to S/4HANA

10 Why Migrate Business Suite ERP? OLTP is not a HANA strength Still no SD benchmark DB2 for IBM i App server and DB work does not change significantly it s still OLTP on HANA Business Suite growth on AnyDB allowed by new technical foundations 7.50 NetWeaver OpenSQL Core Data Services (CDS) Fiori Migration business case is difficult to justify

11 S/4 HANA Conversion? AnyDB or S/4HANA is a different application Do not underestimate the effort required to convert Significantly more change, cost and effort required to hope to reach HANA s potential benefits Simplification, Reimagination = Reimplementation SAP S/4HANA Core Have you customized SAP to your business? Are you planning to redo all of it? Or will you change your business process to fit S/4? Cloud versions severely restrict customization Success must be guaranteed to justify any move

12 Migration of Business Suite BW? Remember EVIs and Benchmark successes on HANA SAP BW SAP BW DB2 for IBM i POC experiences have been mixed Some things improve, some may get worse as a result of DB change BW application tuning needs exposed Simpler efforts are often more cost efficient SAP BW EVI button BW application tuning DB2 performance health check SSD/Flash Flat Infocube

13 BW Migration & Conversion realities on HANA SAP BW SAP BW/4 HANA SAP BW DB2 for IBM i BW4/HANA is another new product line Like Suite to S/4 BW to BW/4 S/4 does not accept your existing BW Infocubes Reports Instead they move to BW/4HANA S/4 can be a source for BW/4HANA S/4 does not allow other data sources S/4 allows only it s own reports Very new no experiences yet

14 ERP migration and conversion issues on HANA SAP S Finance 1503 SAP S Finance 1605 SAP S/4HANA 1511 SAP S/4HANA 1610 DB2 for IBM i None have everything Business Suite offers All are less stable than Business Suite Reliance on OLTP not HANA s best subject What sacrifice is made for new function?

15 Conversion paths from S Suite to S/4 today SAP S Finance 1503 on HANA SAP S Finance 1605 SAP S/4HANA 1511 SAP S/4HANA 1610 DB2 for IBM i S Suite to S/4 is another conversion Regular upgrades become necessary to keep up with application fixes and redesigns Expect continuous business impact

16 Adopt 2.0 at Your Pace? 2.0 is just announced in Nov HANA no new SPS coming maintenance revisions until May 2019 HANA 2.0 DB Upgrade required after two HANA SPSs are released to remain compliant with maintenance support Regular required HANA updates Simplifies Support for SAP but makes work for customers Run your business not your computer

17 HANA DB evolution continues. Independent of application space Virtualization still evolving for in-memory Multiple HANA DBs per server Performance sensitivity limits in-memory on large machines Why so many DBs in the first place? New HANA DB requirement Tenant concept additional small HDB instance per LPAR Return of MCOD again, why so many DBs? HANA HA options still evolving as experience is gained Options are good to have proven best practices are better Code check tools and Data Volume Reduction requirements

18 SAP NetWeaver bridges Suite-S/4 boundary SAP NetWeaver 7.50 DB2 for IBM i New application foundation Used for both Business Suite & S/4HANA 7.50 based tools can check for HANA readiness SAP S/4HANA Core SAP wants to use more SQL features that all DBs have now, but not all DBs had in 1990s 7.50 allows many things to work in EITHER world

19 SAP NetWeaver 7.50 brings options DB2 for IBM i SAP S/4HANA Core BW flat infocube (actually 7.40) Was HANA only, now available on AnyDB SAP NetWeaver 7.50 Open SQL enhancements Available to any customer for own ABAP coding JOIN, GROUP BY, UNION, string functions, etc Core Data Services DB push-down for HANA and AnyDB Foundation for simplification ABAP development in Eclipse Fiori capabilities Possible on AnyDB SAP does restrict some solution availability - Basing on proprietary HANA functions - Customers must have a voice

20 Business Suite is ready for you. Now. Leverage your Business Suite investment Allow CDS infrastructure and S/4 app to stabilize Avoid temporary products Business Suite is supported through at least 2025, perhaps longer POWER9 brings more capacity per square meter in the data center In the meantime there s real work to be done in Business Suite with NW 7.50 SAP BW DB2 for IBM i DB2 for IBM i

21 Summary IBM and SAP are here together to support partners and customers SAP on IBM i topics for the Summit show the way forward Enjoy the rest of our sessions today and tomorrow! IBM i 7.3 and DB2 Storage Customer and consultant experiences Current NetWeaver release info and hints New technology for SAP on i 7.50, CDS, Fiori, LaMa, BW

22 Questions? Thank You! Contact: See our blog and discuss with us at 22

23 Legal Information Please Note IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. 52

24 Legal Information Trademarks, Copyrights Information contained in this material has not been submitted to any formal IBM review and is distributed on as is basis without any warranty either expressed or implied. The use of this information is a customer responsibility. IBM MAY HAVE PATENTS OR PENDING PATENT APPLICATIONS COVERING SUBJECT MATTER IN THIS DOCUMENT. THE FURNISHING OF THIS DOCUMENT DOES NOT IMPLY GIVING LICENSE TO THESE PATENTS. The client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions. It is the user s responsibility to evaluate and verify the operation of any other products or programs with IBM products and programs. IBM, the IBM logo, ibm.com, AIX, BatchPipes, BladeCenter, DB2, DB2 Connect, Netezza, GDPS, GPFS, Netfinity, Intelligent Miner, OpenPower, Parallel Sysplex, POWER, RACF, Redbooks, RETAIN, System Storage, System p, System x, System z, Tivoli, WebSphere, zenterprise, z9, z10, and z/os are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. A current list of IBM trademarks is available on the web at Copyright and trademark information at: Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. SAP, R/3, SAP NetWeaver, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. 53