Posts
s4 Hana our next-generation. ERP is different because it runs on the Hana in-memory platform now I get asked all the time why does it have to run on Hana.
let's explore that because the answer is pretty amazing and it starts without Hana simplifies the data model for ERP.
here's an example on the left is s AP inventory management when it ran on a legacy database we needed 26 tables most of the indices and aggregates for lookups and analytics and this was pretty typical for traditional database systems.
the complexity grew as your ERP did Hana is completely different it uses columnar instead of rows store and it runs with the speed of in-memory.
Now if you'd like some more technical details about how this works to follow the link at the end but for now check out the result.
inventory management is down to one table because Hana does not need redundant data to perform in real-time now scale this out beyond an inventory to an entire system a simpler data model.
IT helps IT allowing you to apply resources to business productivity and capability.
I'll explain specific examples of this new productivity like eliminating reconciliation in the financial closed process.
Now you may be wondering if in memory is so great why can't I just take what I've got now and run it on an in-memory option from my legacy database vendor and some vendors even claim.
To do what we're doing with the push of a button but count the number of tables was any complexity really reduced or are they just taking the same old design and wrapping it in some new data models and hoping that it will run faster in-memory.
these other databases cannot do for ERP what we're doing for Hana is the only ERP built to leverage the combination of columnar and in-memory for one data store dramatically reducing complexity and productivity.
 |
let's explore that because the answer is pretty amazing and it starts without Hana simplifies the data model for ERP.
here's an example on the left is s AP inventory management when it ran on a legacy database we needed 26 tables most of the indices and aggregates for lookups and analytics and this was pretty typical for traditional database systems.
the complexity grew as your ERP did Hana is completely different it uses columnar instead of rows store and it runs with the speed of in-memory.
|
Now if you'd like some more technical details about how this works to follow the link at the end but for now check out the result.
inventory management is down to one table because Hana does not need redundant data to perform in real-time now scale this out beyond an inventory to an entire system a simpler data model.
IT helps IT allowing you to apply resources to business productivity and capability.
I'll explain specific examples of this new productivity like eliminating reconciliation in the financial closed process.
|
Now you may be wondering if in memory is so great why can't I just take what I've got now and run it on an in-memory option from my legacy database vendor and some vendors even claim.
To do what we're doing with the push of a button but count the number of tables was any complexity really reduced or are they just taking the same old design and wrapping it in some new data models and hoping that it will run faster in-memory.
these other databases cannot do for ERP what we're doing for Hana is the only ERP built to leverage the combination of columnar and in-memory for one data store dramatically reducing complexity and productivity.
Post A Comment:
0 comments: