All the options I have listed except for the last 2 are priced based on the size of the database (sold in blocks of memory).This type of usage is often referred to as native HANA as you are allowed to develop directly in SAP HANA.For SaaS this basically means you only get to access what the SAP developer decided you could access, for the on premise Runtime license you can access the SAP HANA engines only via the Applications programming language e.g ABAP which usually means a more limited scope of features compared to using native HANA.
You can then overlay your non-functional requirements (High Availability, Disaster Recovery, Security, Performance, CloudOn Premise, Budget etc) to get to a Physical SAP HANA Model. Yes I Can Run My Business Runtime Edition License SAP HANAIn reality you may end up tweakingcompromising the Physical SAP HANA Model to take account of the licensing metrics, lets call that the License SAP HANA Model. If you find that the Physical Model and the License Model are very diverged or you feel the License Model is too compromised, I would recommend active dialogue with SAP to see if you can create a customer specific model that works for you and SAP. Before you make ANY decisions on how you are going to use SAP HANA you should get pricing from an SAP AE and have any use-cases included into your contract with SAP. You may want to use this blog to help guide the conversation with the SAP AE. If Im paying 15 HANA uplift for say BSI TaxFactory and OpenText then I should be able to run those on HANA if the 3rd party vendor supports it. Yes I Can Run My Business Runtime Edition Install XSA AndDoes it mean, we cannot install XSA and WebIDE to develop native HANA applications although in reality the results will be consumed by ABAP layer For example:- A Graph script cannot be created from ABAP layer.
0 Comments
Leave a Reply. |