SAP HANA Reviews

The dashboard is great.

It's user-friendly so long as you use it frequently.

The product is stable.

You can scale the solution.

Technical support has been good.

Some production features are lacking. For example, we cannot see any dashboards in the production department. The generation of reports needs to be better. We have sales reports and yet no production reports.

It's a complex initial setup.

It can be an expensive solution.

I've used the solution for six years.

The stability is very, very good. There are no bugs or glitches. It doesn't crash or freeze. 

The scalability is very good. It's very capable.

I've used technical support in the past. They are good.

I did not use a different solution. I use what my company uses in order to get reports.

The initial setup is difficult and complex. It's very complex compared to SQL, for example.

The initial deployment took 15 days, however, nowadays, it takes one or two days. Mostly, I can complete it in one day.

I'm a business consultant. I do implementations for various parts of my customers' organizations.

The licensing is typically chared yearly. It was rather expensive.

We deploy the solution mostly on-premises and sometimes on the cloud. When we use the cloud, we usually use the AWS cloud. 

I'd warn new users that it might be difficult the initial time they use it if they are changing their ERP, however,t it'll be very helpful in the future if they're using it frequently.

I'd rate the entire product an eight out of ten. There are other well-known ERPs, such as Salesforce, and companies expect to have the same features. However, not everything may be on SAP, and that's something they need to work on.

I was using the product for some research in technical drawings - in terms of making some drawings, the different parts, and the structure of the machinery. I don't know if it's available in the SAP HANA, however, there is a model for this to schedule the maintenance. The company wasn't using it. Sometimes the product furnishes a lot of insights, cultural insights that the company still is not ready to implement.

The solution offers advanced features that the company was struggling to implement. For example, in terms of parts, you can't implement a lot of structures of the machinery, however, you still need to use the codes. They're not related one to another, which makes them hard to find, typically. That means every time you need it to buy an entire assembly of parts, you need to know exactly which one you had. You have to use a drawing, a technical drawing, that specifies each code that you need. SAP saves you from asking to bring an entire assembly with a lot of parts. That's a powerful aspect that could help to reduce hours of work that are wasted in this way.

A documents preview could be helpful. Today we have a lot of documents, for example, in PDF formats, which we would like to preview. We'd even just like to click on an icon and have it open another tab. That way, I can see the document directly inside SAP HANA. In the company I was working with, we had a parallel system which meant we needed to go to SAP, see the code, see the drawing number, and then go to another system that is finished by Autodesk, and then find the drawing and open it. This is a lot of work.

I really would like to just have it inside this app. 

I'd like the product to have more mobile aspects. Many younger users want mobility and flexibility.

The solution can be expensive. In Brazil, many companies still do pretty much everything in Brazil, and, if they want to try a new solution, they want to try it at zero cost. Many, therefore, will look for open-source solutions before they even consider SAP.

I've used the solution over the last 12 months. 

It's very stable. Sometimes it gets a little slow, however, that might be a company issue. When it came to the internet the entire site wasn't that good. Sometimes you had too many people connecting and the company was using a lot of Google solutions. You noticed that when a lot of people are in virtual meetings, we would have internet connections affected.

I'm not sure about the scalability.

I don't know if you can use it in a Docker or if you can scale it in SQL and you can maintain the speed, or if you are talking about, for example, big data. The infrastructure of the company seemed to be weighed down, for example, when there were a lot of virtual meetings and it affected the internet. I can't speak to if this problem would also affect being able to scale the product.

I would describe technical support as good. It's always worked for me and therefore I have no complaints. 

I didn't handle the initial implementation. The company furnished all the equipment needed for me to work. They gave me the computer, which Red Hat was installed on. They just give me access and showed me where to access what I needed and where to put the ID and password. I didn't do anything.

Typically there are six people that are available for maintenance tasks. They're IT technicians.

SAP solutions are typically quite expensive.

I'm a partner and consultant. 

I'm not sure which version of the product I am on.

I'd advise new users that it's important to first find a solution that can understand the culture that's involved inside this solution. Sometimes people think that ERP software like SAP are magical things that you just install it and it makes life easier. It doesn't work like this. You need to have the culture, you have to have this knowledge. You need to understand how it works and how much it requires from you. It requires more than you think. It doesn't work like magic.

I'd rate the solution at a nine out of ten. It's very good, however, there's always room for improvement. 

We work with the latest update.

We use the solution as a database. We primarily use it for the SAP application. Some of the use cases involve CDS Views, which provides a quicker processing of the report and the application.

The in-memory database is a good and valuable feature.

Since we use BW, we are required to use an SLT tool to carry out the data for generating the reports. But, when it comes to in-memory database in respect of the realtime reporting, I do not see why this report cannot be made available from the system itself. This would allow for some partitioning of the database, so that there would not be a need for the EMP in respect of the realtime data.

The initial setup was complex. I am talking about how the data is replicated to the site. We had an Oracle Database and did replication to the VR site. Yet, when it comes to HANA, we are forced to work out the method for ensuring that this replication works as it should. It is at this point that the solution becomes stable. 

Technical support could be better. When we have requested this, the tendency has been to instruct us to implement a note and keep them apprised. In reality, there is no one who helps us with actual troubleshooting of the problem. 

The pricing is a bit on the high side. 

While I would definitely recommend the solution, I would caution that one should employ the proper resources that are geared towards the system. Unfortunately, SAP does not provide a structured training program, which means a person must rely on multiple system integrators and some service providers.

We have been using SAP HANA for more than three years.

The stability is very good and we have encountered no issues regarding it. 

The initial setup was complex. I am talking about how the data is replicated to the site. We had an Oracle Database and did replication to the VR site. Yet, when it comes to HANA, we are forced to work out the method for for ensuring that this replication works as it should. It is at this point that the solution becomes stable.

The solution is easy to scale.

Technical support could be better. When we have requested this, the tendency has been to instruct us to implement a note and keep them apprised. In reality, there is no one who helps us to actually troubleshoot the problem. 

We had already been using SAP when we switched from it to Oracle, because all of the innovations were taking place on HANA. 

The initial setup was complex. I am talking about how the data is replicated to the site. We had an Oracle database and did replication to the VR site. Yet, when it comes to HANA, we are forced to work out the method for for ensuring that this replication works as it should. It is at this point that the solution becomes stable.

The deployment lasted six months. 

We deployed with the help of a vendor.

No real maintenance is required. Data volume management is needed and all the reports are available, based on which the maintenance is easy. 

The pricing is a bit on the high side. 

The use of hardware does not incur additional costs. 

There are 40,000-plus users making use of the solution in our organization.

I rate SAP HANA as an eight out of ten. 

Our primary use of SAP HANA is the use of modules, such as Material Management (MM), and Sales and Distribution (SD).

We have found the solution to be customizable and it is beneficial it comes as a bundled package. Additionally, it is user-friendly.

SAP HANA is not perfect and they could improve by having more options and more integration.

I have been using SAP HANA for approximately eight years.

The performance of SAP HANA is very good.

The solution is scalable.

We have a complete team size of approximately 12,000, including all the consulting and project managers.

We have approximately 36 end users, that directly impact the business. We might increase usage in the future but this depends on the business.

I have contacted the technical support from SAP HANA and they are providing a complete solution to customers. I have been satisfied.

The installation is straightforward and took approximately six months.

We used an in-house team to do the implementation.

We pay annually for the license of the solution.

I rate SAP HANA a ten out of ten.

We use this solution for our CRM, and for our ERP, inventory, and supply chain management. It's basically used to run the majority of the company. We are customers of SAP HANA and I'm an account executive. 

SAP is great for what it does. There are likely better solutions out there but I'm not aware of them. It's a solution for big companies and in that sense it makes management of the databases much easier for higher-level people to know what's going on. 

The user interface and CRM need to be more user-friendly, it's abnormally painful. I'm a frontline user of the CRM, and it requires lots of clicks that are unnecessary. Less is more on the internet and quite often I'm clicking five, six, seven times to get where I need, and that's not effective. When an item in a certain category is not done properly, it can either lock up a system or not complete the process. We see it on a daily basis and we have to figure out a workaround to solve it. It's a technical issue that SAP's had since the beginning, and it hasn't yet been solved. With SAP everything has to be categorized. If it's not, it causes system issues and then you have to decipher the issue to try and undo it. It's an algorithm argument flaw. In the near future, I'd like to see better user interfaces and better connectors between modules.

I've been using this solution for about eight years. 

The solution is rock stable now. We have an SAP team and five or six people fixing day-to-day issues with up to 30 people working on it all the time. There is an additional team that implements new functionalities. 

It can scale infinitely. We have 12,000 users internationally and we use the product extensively. 

I have previously used Salesforce and I don't like it. It runs like a 1980s webpage in the current era.

The initial setup was painful and required a lot of work. Systems would go down all the time because there were initial errors with the SAP system. but once it was up and stabilized, things were good. It still has flaws but it's a good solution as a whole. They've implemented extra modules from SAP. If you don't implement it properly you'll feel the pain. It probably took around six months to solve all the issues because SAP is so big and so integrated and so integral, it can take a while to fix the problems. You can limp along until things are solved and find workarounds, but it takes a lot of effort. SAP helped us with the implementation. 

SAP is expensive but it's a good solution for what it does. You're going to get a $20 answer, for a $20 product. For all the functionality it offers, the cost is worth it.

It's important to plan and then plan again before implementing. If you don't plan properly, you will fail. The solution requires planning the implementation, making sure your company is the right size for the product. If you're an SMB, this might not be the right product for you. It might cost you more than you think. If you're enterprise size, you should look at getting into SAP, because it is the right solution. It's a solid product despite some minor issues - if SAP were to fix them it would raise the level of the solution. 

As a user, I rate the solution eight out of 10. 

We are end users of SAP HANA and I'm assistant vice president of our company. 

The solution's in-memory computing and the efficient response time are very good features. It's a good solution. 

Because SAP HANA is completely in-memory, it requires the use of bigger systems which have a higher amount of RAM. If the system does go down then coming back up is difficult and can take 30 to 40 minutes. It's a big drawback of the solution and one they ought to solve because the multiple downtimes are a problem.

I've been using this solution for six years. 

The solution is scalable so if you want to increase your node capabilities, it's very easy to scale out. You just have to add the node and it gets started.

The technical support people are very competent.

The initial setup is straightforward and there were no problems with deployment. 

I recommend this solution but running SAP HANA requires deep pockets - it's costly.

I rate this solution eight out of 10. 

We always make use of the latest version. 

We like that SAP HANA is a new technology. We also like that the product is both vertically and horizontally scalable, allowing us to do around 86 percent compression of documentation from 50 to seven terabytes.

In light of the hosting cost, we find this to be very interesting. We also like the warm and cold data in respect of the solution's technology. There is a real team involved. The customer can initially utilize SAP ECC on the HANA interface and then go on S/4HANA. From this point on, doing upgrades will be very easy and smooth and the risk management will be extremely light.

Since only some accommodation exists, there is a need to enquire of SAP about which environment would be good. While I know the HANA database on the Azure environment comprises a good solution, for example, it does not easily accommodate SAP. HANA is a new technology which only dates back to 2004 and we must give it adequate time before assessing its room for improvement. This is in contrast to DB2, which has been  around for 40 years or more years. Perhaps the flow will be improved. As of now, the technology is too new to properly comment on.   

The documentation is not an issue and, if anything, a surfeit of it is made available. This is actually one of SAP's stronger points.

Capabilities are also not at issue at present. When it comes to how EAP connects with SAP we are looking at a revolutionary paradigm. For now, we could not ask for there to be more features. This area is wonderful. We find the solution to be very helpful, safe, good and secure. Only with the passage of time will we be afforded a proper understanding of where the technology can be improved. 

This said, it would be nice to know when SAP plans to stop its maintenance of a previous version of SAP ECC ERP because, at this point, anyone utilizing SAP will have no choice but to go on S/4HANA Database. This will be contingent on when SAP will stop doing maintenance for the ECC version 6.0. 

We saw this with the 4.6 version ECC. Once SAP stopped its maintenance those with SAP were forced to go on the new version. 

We have been using SAP HANA for a couple of years. 

The solution is secure and stable. 

As the solution allows for document compression, I would consider it scalable. 

We have had occasion to make use of technical support, although its level varies according to the locale of SAP's global presence. 

While I was not personally involved in the installation, my engineers were. 

My deployment and maintenance team comprises around seven people, although I could not tell you which percentage of this is made up of managers, administrators and engineers. 

A monthly or yearly license must be purchased, although its utility will be based on the cost-benefit analysis that is reached by the individual customer. 

The solution is cloud based

I would recommend S/4HANA to other users. 

I rate SAP HANA as a nine out of ten. 

We are solution providers. We are a supply chain organization and we deploy and supply chain solutions for our customers.

We have a host of solutions and for each of our customers based on their environments. We customize their platform and deploy it.

SAP HANA is one of our database endpoints.

It's easy to use, and the Hana Studio is pretty good.

The main issue that we are facing is with the connectors. The JDBC connectors are very slow. We have been trying to connect with our SAP HANA database to our customers.

It's a simple Java driver and there is no proper documentation available anywhere with clear steps. We have to rely on several documents which creates confusion.

The initial setup could be simplified.

Also, we don't have to option to pull up the data from the object structure in SAP HANA. We can only pull up certain objects. It doesn't provide you with a comprehensive list.

There are limitations in connection with SAP HANA. There has to be a better or easier way to connect the databases with other platforms, maybe using Java code or other types of code. It would be very good to have the documentation on how to connect.

I would like to have flexible connecting mechanisms for connection with Java or different types of solutions to SAP HANA on cloud or non-cloud solutions.

They could come up with something similar to the SAP HANA Studio type of modeling.

I would also like to see the capabilities to extend the API. If they had specific APIs, it would be easy for us to connect.

My company has been using SAP HANA for ten years.

We are using the latest version.

It's a stable solution.

It's a scalable solution. Because it's an on-premise infrastructure and SAP this is the best support for most of our customers, scalability is taken care of.

We are an SAP house. We have more than 1,000 people who use this solution.

I have not interacted with the technical support. Other teams may have, but my involvement is more with the integration. 

The initial setup was a bit complex. We were told to download it from the marketplace, but when we tried, it didn't work. We may have been doing something wrong, but we did not have a clear understanding of how it should be done. We also had difficulties with the trial version, it was not working.

There are two options:

1. Download SAP HANA then import it
2. Go to the marketplace and download the connector

For testing purposes, if they could provide us with clear documentation, it would be very helpful.

Licensing is on a yearly basis.

We are using the paid version. We pay $200 on a monthly basis.

I am not an expert in HANA. I build the enterprise bus that integrates with SAP HANA as well as other systems. We have built our own integrated platforms.

The recommendation of this solution would depend on the use case and the requirements, and the price will be considered.

I would rate SAP HANA an eight out of ten.