1 / 29

Yves Brennwald / Stephan Elster Juni , 2013

SAP Suite on HANA: Strategie & Roadmap. Yves Brennwald / Stephan Elster Juni , 2013. What does it mean for you?. SAP HANA Appliance – New Focus. Traditional approach: strong separation of concerns. Work together for implementing SAP HANA. Applications (SAP). Consider: Appliance Shipment

fleta
Télécharger la présentation

Yves Brennwald / Stephan Elster Juni , 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SAP Suite on HANA: Strategie & Roadmap Yves Brennwald / Stephan ElsterJuni, 2013

  2. What does it mean for you?

  3. SAP HANA Appliance – New Focus Traditional approach: strong separation of concerns Work together for implementing SAP HANA Applications (SAP) • Consider: • Appliance Shipment • User management • Wiring / set up process • New development process • Operations concept Project planning Database Operating System Network Storage • SAP HANA

  4. Think about… …The potential…Get familiar with the benefits you would get when porting your Suite to Suite on HANA – increase transaction/batch speed, boost operational reporting (HANA LIVE), ease the UI (improved selection screens) 1 …Quick wins…Discover low hanging fruits and realize quick wins for your business. 2 …New innovations…Think about new/optimized processes that can leverage the HANA foundation. 3

  5. How to get there?

  6. Suite on HANAPlan – Build – Run Plan Build Run • Prerequisites • Landscape Impact • SAP HANA Appliance • Installation • Update • Migration • Optimization • Monitoring • Operation

  7. Suite on HANAPlan – Build – Run Plan Build Run • Prerequisites • Landscape Impact • SAP HANA Appliance

  8. PrerequisitesSAP Business Suite Powered by SAP HANA • SAP ERP 6.0 • SAP Enhancement Package 6 for SAP ERP 6.0, Version for SAP HANA • SAP CRM 7.0 • SAP Enhancement Package 2 for SAP CRM 7.0, Version for SAP HANA • SAP SCM 7.0 • SAP Enhancement Package 2 for SAP SCM 7.0, Version for SAP HANA • Please note: not all scenarios / industries are already released for productive use with SAP HANA (note 1774566) • Others will follow soon … Plan Build Run

  9. PrerequisitesDual-Stack / Unicode • Dual-Stack Systems • „[…] as of SAP Business Suite 7i2011, it will no longer be possible to upgrade an SAP dual-stack system to a higher release […].“ (note 1655335) • Suite on HANA is based on NetWeaver 7.40, not supporting dual-stack installations • Dual-stack systems have to be split before a SAP HANA migration • A dual-stack split tool is included in the SL toolset, available on SAP Service Marketplace • Java stack stays on current database, since Java is not yet supported to run on SAP HANA • Unicode • SAP HANA runs natively on Unicode only • Unicode conversion can technically be done during the database migration, but preparatory steps are required Plan Build Run

  10. System considerations – what changes and what doesn’t?Hardware Impact - Migration of database server only + benefits • No Change • No change of frontends • Re-use of available application servers • Sizing of current application servers remains valid • Change • Migration of database to SAP HANA appliance required • Co-deployment ofapplication servers(e.g. central instances)on database hardwarenot possible with SAP HANA Frontends Application Servers AnyOS AnyDB/AnyOS SAPHANA/ SUSE Linux (SLES) SAP HANA migration No Functional Changes: IMG, Customization, Modifications, Connectivity, Security, Transports, Monitoring (DBACockpit & SolMa) stay all the same Application and Reporting Benefits: No dialog process in batch, acceleration/elimination of batch, Run operational reports in real-time inside Suite

  11. Landscape OptionsPlan – Build – Run Productive Systems • “Classical” scenario Appliance approach for optimal performance • 1 x Hardware • 1 x SAP HANA DB • 1 x DB schema • 1 x Application (e.g. BW) • “MCOD” Multiple components on one database • 1 x Hardware • 1 x SAP HANA DB • n x DB schema • n x Applications Productive usage allowed, e.g. SAP NW 7.3 BW together with Business Suite Accelerators. See note 1661202 DYY QYY PYY AS ABAPSID: ABC AS ABAP SID: ABC • ApplicationXYZ Hardware options: • BW on HANA appliances available in different T-shirt sizes. Single node and scale-out solutions available. SAP HANA SAP HANA SAP HANA SAP HANA <HDB> <HDB> Schema ABC Schema ABC Schema XYZ

  12. ApplianceScaling SAP HANA • Scale-up (scale vertically) • Increase the size of the hardware (main memory, number of CPUs) • Challenge: • availability of suitable hardware • Scale-out (scale horizontally) • Several nodes (servers) are switched together for one database • Data are distributed over the main memories of these different nodes • Challenge: • Cross-node communication is expensive • Avoid cross-node joins / views • Table distribution has to be customer / usage pattern specific • Dynamic re-distribution must be allowed Plan Build Run

  13. Suite on HANAPlan – Build – Run Plan Build Run • Installation • Update • Migration

  14. Migration Options Option 1: New installation Option 2: In-place migration Option 3: Copy, upgrade + migrate • Clean installation, take chance to tidy up • Not suited for replacement of current production system • Data migration may be required • Avoids changes to the overall landscape – keep SID, host-name, application server, connectivity • Downtimes during upgrade and migration • Ideal setup for PoCs and pilots: compare before & after, keep fallback • Short downtime of production system • BW-only: good option to run BW powered by SAP HANA parallel to original BW system productively

  15. Update and Migration Update (EhP) SUM 1.0 SP6 Migration SWPM 1.0 SP1 • Currently Available (SPS02): • Two-Step Migration • One-step update to EhP for HANA • Afterwards Database migration • Also available as RDS. • Planned: • One-Step Migration via Database Migration Option for Software Update Manager (DMO for SUM) • Available for pilots with BW on HANA • Pilot planned for Suite on HANA in Q2 2013 • Pilot with built-in downtime optimizations planned for Suite on HANA in Q3 2013. • GA planned in Q4 2013. • Also planned to be provided as RDS. Plan Build Run ERP 6.0x // CRM and SCM 7.0x ERP 6.0x // CRM and SCM 7.0x ERP 6.16 // CRM and SCM 7.12 for HANA ERP 6.16 // CRM and SCM 7.12 for HANA ERP 6.16 // CRM and SCM 7.12 for HANA DMO for SUM AS ABAP 7.0xKernel 7.x AS ABAP 7.0xKernel 7.x AS ABAP 7.40Kernel 7.40 AS ABAP 7.40Kernel 7.40 AS ABAP 7.40Kernel 7.40 Any DB Any DB Any DB HANA 1.0 HANA 1.0 SPS5

  16. Suite on HANAPlan – Build – Run Plan Build Run • Optimization • Monitoring • Operation

  17. Code OptimizationMaximal Flexibility – Minimal Disruption Display Business Function (SFW2) • SAP HANA optimizations: • Additional views • Stored procedures (code pushdown to SAP HANA) • To be activated via switch framework ‒no change in business logic after migration to SAP HANA • All switches are reversible • Switches can be activated independently • Maximal flexibility in consumption of optimizations • Minimal disruption for customer business • Custom Code (ABAP reports) • Regression tests for own code recommended after SAP HANA migration Plan Build Run

  18. Using Standard CTS for Suite on HANA ABAP CTS • How it works? • Develop ABAP in ABAP workbench; develop HANA in HANA Studio • Export HANA developments (views, stored procedures) into transport container (TLOGO object) • Assign transport container to a transport request in ABAP Transport Organizer • Use standard Change and Transport System (CTS) to transport and deploy changes ABAP Dev ABAP Test Export SAP HANA Artifacts Import SAP HANA Artifacts SAP GUI SAP GUI Application Logic Application Logic SAP NetWeaver SAP NetWeaver Plan Build Run SAP HANA SAP HANA • Result • Use well-proven technology for transport of changes • Utilize full change control of SAP Solution Manager for SAP HANA

  19. SAP HANA Administration and Monitoring • SAP HANA Studio • Administration & development tool for SAP HANA • Start / stop • Backup / recovery • Configuration • SAP HANA modeler • SAP HANA user management • Table management • SAP Solution Manager • SAP HANA monitoring and alerting are integrated into SAP Solution Manager • Guided procedures for processing SAP alerts • End-to-end workload analysis for SAP HANA • SAP Solution Manager is used by SAP support for early problem analysis • SAP Solution Manager serves as backbone for CTS+ transport integration Plan Build Run

  20. How can we support you?

  21. From traditional to “powered by HANA” – Your path SoH Technical Planning/Upgrade Suite on HANA Migration Suite on HANA Post Optimization

  22. Different SAP Services for different stages • Rapid-deployment solutions provide an end-to-end solution for migrating an existing installation of the SAP Business Suite to the SAP HANA® database without disruption of existing content. Rapid Deployment Solutions SAP HANA Assessment SAP HANA Sizing/Installation/Configuration Authorization Migration Unicode Conversion Software Service Content Prerequisite RDS Post Optimizations Enablement Technical Planning/Upgrade Technical Upgrade Functional Upgrade Database Migration SAP HANA Optimization Services(Suite on HANA)

  23. From traditional to “powered by HANA” – Your path HANA Post Optimization Technical Planning/Upgrade X on HANA Migration • Service Portfolio • HANA Technical Assessment for Suite on HANA • Upgrade Implementation for Suite on HANA • Predefined HANA Installation • HANA Data Replication Installation/Configuration • Service Portfolio • Database migration for Suite on HANA • Service Portfolio • Suite on HANA Optimization Service

  24. A goodstartingpoint - Businesss Scenario Recommendation Report (BSR) http://www.suiteonhana.com

  25. HANA LAB to test Suite on HANA • Hardware • Latest HANA HW technology in collaboration with HW vendors • 4tier landscape covering the most important HANA scenarios • Software • HANA • SLT (Trigger based replication) • Data Services (ETL based replication) • BO BI 4.0 (incl. BO BI Mobile) • IDES System (ERP on RDMS for data provision) • BW on HANA und BW on RDMS • CRM on HANA (in preparation) • ERP on HANA (in preparation)

  26. Summary

  27. Migration to SAP HANABenefits with SAP Services and Tools Risk mitigated Comprehensive 1 5 Holistic end-to-end view to all aspects of entire project Keep risks under control Fast time-to-value Expertise 2 6 Services expertise on supporting top companies Benefit from existing knowledge to speed up migration Tailor fit Cost controlled 3 7 Careful planning and strong services partnership guarantees costs under control Flexible plan service to local customer situation Content Quality optimized 4 8 Services actively manages QA during entire project Leverage existing RDS to boost the migration How to get this?  Approach your Service Account Manager

  28. The SAP HANA Project Guide • The SAP ® HANA Project Guide • In this book, the authors share their findings to help ensure the success of your SAP HANA project. The SAP HANA project guide will also help you identify suitable scenarios for your company to get started with in-memory technology, while sketching out a long term plan to provide innovation to your entire business using SAP HANA. We’ll cover the following key topics: • Delivering innovation with SAP HANA • Creating a business case for SAP HANA • Thinking in-memory • Managing SAP HANA projects • More Information & link for download www.hana.infoKindle Edition

  29. Thank you Contact information: F name MI. L name Title Address Phone number

More Related