on 11-12-2014 11:53 AM
We are in early investigation around SAP HANA and trying to understand how this impacts our business processes. Have a few questions where some additional input would help.
1. What happens to existing tables in ECC. Do they get automatically migrated to Column store format as part of new Data Model or is that something that we as customer need to decide between Row and Column based storage as part of migration?
2. Current processes such as MRP and Billing leverage the ABAP processes in App server quite a bit. Post HANA, we understand the DB operations are much faster. So, what happens to current long running jobs such as billing - are they optimized for HANA or do the processes remain the same ABAP based?
3. What is the persistence layer for the data? In addition to holding the data in memory - is it persisted in disk somewhere for failover? (Kind of similar to APO livecache where the data is written to planning cubes)
Vicky,
thank you for looking into SAP HANA as your database for your ECC system.
We have a comprehensive FAQ for SAP Business Suite on HANA with lots of additional details:
Quick answers to your questions:
1. The migration effort is fully automated, most tables are converted to columns tables and all ERP cluster tables are being de-clustered during the migration to SAP HANA. SAP HANA Studio allows you to choose between column or row tables for custom applications, but for the SAP applications the choices are made by SAP.
2. With regards to batch processes and also dialog processes, SAP provides optimizations with SAP HANA. Some are automatically available (like instantaneous SE16 look-ups), some need to be activated in the IMG for example, and others are only available as innovations, like sFIN for example. sFIN is available either as add-on for on-premise or as cloud applications in public or private cloud deployments.
Details for optimizations can be accessed here: https://scn.sap.com/docs/DOC-59889
More information about s-innovation are presented in the TechED keynote form Berlin 2014.
3. Currently SAP HANA still has a persistence layer outside the DRAM, which is called the SAP HANA storage and which is provisioned by SDD and/or HDD. Once HW vendors will provide non-volatile memory we do expect further simplification, as SAP HANA writes first to in-memory, and only in a second step to the persistence layer to guarantee ACID capabilities.
thank you
erich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here's a current link for the FAQ
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.