SAP NetWeaver Reviews

SAP NetWeaver is used to integrate SAP with other products as well as its own. It operates between SAP implementations.

SAP NetWeaver is doing its job, and it performs well. In the last year, I have not had any problems with it.

It is part of the overall implementation. You can't work without an integrated system. As a result, you require SAP NetWeaver.

I have heard through another job that I was working with that Sophos SAP was going to stop with the SAP NetWeaver technology, it was going to be set aside. And I'm not sure how they're going to change it or implement it in the S4HANA landscape.

SAP NetWeaver should be better integrated with other products outside of SAP.

I have worked with SAP NetWeaver in the past. It's part of the landscape.

I don't recall, what version was being used.

SAP NetWeaver is a stable solution, which is one of its offerings; it is a stable environment.

SAP NetWeaver is a scalable product.

Everything went well in terms of support. In general, I am pleased with the technical support.

The installation is straightforward when I worked with it. I didn't find it to be difficult.

It can take weeks to set up an interface.

SAP NetWeaver requires a license, but I'm not sure how the licenses and payments were coordinated.

For those who are interested in using this solution, I would recommend it. 

I would rate SAP NetWeaver an eight out of ten.

I'm a company director and we are both customers and partners with SAP. 

The solution is scalable. 

We're looking to move to the cloud because the solution has become somewhat unstable and we've experienced a lot of down time recently.

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

The product is scalable, we have 2,000 active users. 

The customer support is helpful and professional but sometimes the turnaround time is too long. 

We have four admins involved with maintenance. 

We think that the current setup of NetWeaver on-prem is a bit expensive and we're currently carrying out a comparison between the different cloud products on the market. 

We're currently researching and evaluating Azure and AWS because we intend moving to S/4HANA on cloud. 

I rate this solution eight out of 10. 

SAP handles all of our inventory and our raw materials. We haven't found another solution that was for time and attendance all in one. We have used ShopVue for our time and attendance and we use SAP for the back end. It keeps all of the materials moving. Anything that is a product that moves, we have some way of searching for it in SAP. 

I take a particular product, then go into the stock requirments and I type the product name or number. That will give me the current status and everything that is happening with it from within the same SAP requirement list, which is MD04. That is SAP's internal name for this page. I can go from there to the history where I can see the orders that are coming in, as well as the orders that are waiting. It's all on one very useful screen. It's a very useful tool to be able to get from point A to point B.

The most valuable feature would probably be that it's accurate in its historical data. When searching through the historical data, you can be very sure that the data you get is accurate. With SAP, you can trust what it tells you. With others, you can troll through and get data that has more outliers than good points.

SAP isn't particularly user-friendly and you have to develop a long list of favorites to be able to get around. I have a very long list of favorites, some I use every day and others just once in a while. I thought that BPCS wasn't user-friendly, although this is twice as bad.

One of the problems in SAP is when you open a screen and there are approximately ten different places you can click on to go to other places. Unless you know that they are there, you don't get anywhere. You have to know where to click to get to where you are going.

An instruction guide that would explain or tell you what to click and where it will take you would be useful. If you don't know what you are looking for, it would be better to have a dropdown list rather than having to type it.

On the front end, the menu screen I have 70 to 80 favorites and they are all the same color, same line, and all capital letters, but you can't make any changes. It would be nice if it could be color-coded, to allow your eyes to focus on something more specific.

I have been using SAP for about five years.

The system has been okay in terms of scalability. We have 70 or 80 people using SAP that range in roles from plant manager to warehouse, and everything in between.

Several people are constantly requesting access. To do that, we have to submit the request through SAP which requires another set of software. The information is entered then awaits approval from management. The SAP provides a list of people who have access to too many requests.

Technical support is fairly good. At times it can take three to four weeks to get back to us with a resolution. However, they do exactly what you ask of them.

Previously, we were using IBM BPCS. The corporate policy was to have everyone on SAP.

SAP is bigger and can handle more information and it's easier to work with. With BPCS, if you were away from it for a couple of days you would have to retrain yourself.

For the initial setup, we jumped in with both feet and it worked almost like it was out of the box.

From the time that SAP arrived, it took about a year to install the program and adjust it to meet our standards. We had a series of meetings where we discussed functionality, what had been fixed, and what changes still needed to be made.

We had assistance from consultants here in France. There were perhaps five of them who helped us. They knew exactly what they were doing and I am still in contact with one of them.

The licensing costs are on a yearly basis.

Before we initiated SAP, we had to decide where ShopVue would end and where SAP would take over. The two software solutions are not compatible. ShopVue is labor and attendance, which is one thing that SAP didn't have. We had to make the two communicate together.

ShopVue is easy to use. I am surprised that more companies don't invest in it.

When you look at the screen, you can hit that button and it will do something. Don't give up, the answer is there somewhere. Picasso said, "Inspiration does exist, but it must find you working."

Because of its versatility, I would rate this solution a nine out of ten.

The presentation is the most valuable feature. It's very conceptual. We had to follow the instructions very strictly. It's a Dutch or German product and we had to follow it step-by-step. There is the transaction layer and it has to be put on in a database. Then just make a copy and you can work from the database and go further to NetWeaver.

It can always improve. It should have the ability to connect with other databases. It was a little bit tough to do that. I would like to have the ability to research certain markets and then integrate it with NetWeaver. I'd like to compare it with other databases from other companies being used in the world so we can integrate it with our own products to compare if we are still current on the market.

I have been using SAP NetWeaver for five to six years. 

We have needed to clean some of the base transactions up. I see that as a positive thing.

It is easy to scale. 

I deal more with business modeling and haven't needed support. It is possible our technical team has. 

We didn't have any problems setting it up. You can integrate it into your company. If you know what ABAP, it's no problem to set up. 

The deployment took around six to seven months. The implementation of an SAP solution is not very fast.

We got help from SAP consultants for the deployment. We were satisfied with then. They are experts.

It's a good product. I would recommend it because it is stable. And if you do it the right way, by following the rules, then you get what you want from it. SAP is very strict in the way you make your next step.

I would rate it an eight out of ten. Not a ten because there's always room for improvement. It could be more like Informatica. They are graphic. It's very easy to put your transaction data in a graphic way to your model. In a graphic way, Informatica is better but overall I would recommend NetWeaver.

My use case is on ERP systems. We run full ERP.

Finance and distribution are the most important features. There's also the CRM, Customer Relationship Management.

No, it's fine. It does what it's supposed to.

We have been working with SAP NetWeaver for about fifteen years.

We have had no issues with Stability.

We have had no issues with scalability.

The technical support for SAP NetWeaver is not too bad. The response time was slow.

We are currently testing HANA because our support contract for SAP NetWeaver ends in 2025 or 2027.

The initial setup of SAP NetWeaver always has issues to customize the business, it's complex. You've got to customize it to run your business. It takes six months to a year to set up. Some solutions can take two years.

We are currently looking at HANA because our support for NetWeaver end in 2025 or 2027.

I would rate SAP NetWeaver at a seven out of ten.

We primarily use the solution for our day to day business, and we use the solution to analyze the data and arrive at actions based on that.

We strongly rely on our SAP data. We need access to the information to analyze it, so the solution allows us to make use of the data that we get from SAP. This is the most valuable aspect of the solution.  

The scalability should be simplified. We're in many countries and every time we do a change in one place it should change everywhere and needs to scale more data across the board.

The solution needs to better integrate Salesforce. It is a key player in the market and a lot of companies are looking for a lot more integration around it.

Every time we do an integration with SAP, it's a complicated and it's expensive. You also don't know if it's working or not. We need a connector that allows you to easily integrate it.

The solution is tricky to update and it ends up being expensive to do so. This is generally the case with SAP products.

I've been using the solution for four years.

I'm unsure about the stability of the solution.

The scalability of the solution is limited. There are potentially hundreds of users on the solution currently.

I don't think that we contacted technical support. We might have, but I can't speak to the experience.

The initial setup was complex. We had a lot of professional services around the setup and especially after version 9 because it was like doing everything all over again. For some reason, we could not upgrade our version 8. We had to do a new installment and had to migrate all of our applications again.

We had assistance with a third party, but there was room for improvement in terms of handling the implementation with them.

Generally, the solution is expensive to update and integrate with other solutions.

I don't have too much experience with the solution, except from a procurement perspective.

I'd advise others to try to understand the extent of how much they want to use it. If they decide to go on-premises, they need to consider how much they will use the application and for the data they will want or need.

I'd rate the solution seven out of ten. We're not completely satisfied, but from a procurement perspective, it's a fair rating. If the integration capabilities were better, I'd rate it a bit higher.

I like that I don't need any extra tools to keep the solution up and running. 

I would like to see an improvement in the price of the solution because it is very expensive. I would also like to see an easier user-experience.

It's a very stable solution, since you have it in place and it does what you want it to do. You don't need any extra tools to manage it and to keep it up and running.

I don't think the solution is scalable. For instance, if we want to scan something, two to three walls, we must use a different approach, different architecture, etc. We know that if we change it, we must go to something different. Something perhaps radically different. Perhaps something small, perhaps something simpler. So right now we are trying to figure it out.

We have used the technical support team once, and their service was very good.

The initial setup was not very easy. The point is that you don't do it every day - it's something you do once every few years. That is why it is difficult. The deployment is a five-year process because it's constantly being deployed. We take five years in the project to create an environment and then we start using it. We have our own technical team, a specialist technical team, that come to our country for five years to help us with this.

It's a very expensive solution.

My advice to others would be to know what they want to implement and then to leave it in the hands of the external team. I think it's a complete solution - if you want to do something, it has that module or that solution. It is a very holistic approach. 

The solution is not very easy to use, though, as it takes a lot from you to understand how to do everything. It's not something that you can learn in six months or one year. It is a constant learning process. I would, therefore, like if they were to simplify the program to make it easier to use. On a scale from one to 10, I would give a nine. I think it's a very good product.

So far, this solution has performed well. The only thing that is bothersome is end of life. They stopped support sometime around 2008, so it has been out of product support for quite a long time. We currently use it as our central master MDM database where our systems link.

It is the central point for all our data storage. We have one single version of the truth that we can communicate to all our customers. We have one place that we need to update, so we don't have to go to multiple sources and platforms to maintain the data.

The flexibility and customizability of this solution when adapting to our business requirements is a huge benefit.

Scalability would be a good improvement in future releases, if they do release future versions. They tried to create a seamless style, but it's not necessarily scalable to big development environments that we're trying to achieve.

It works really well. 

We have had issues with the performance, and performance is key: 

1. We are limited by the number of instances running because it is at the end of service life.
2. The product is not as scalable as we would like it to be.

Currently, it is very limited. We work with partners to fix their loads on their systems. They have to have separate instances, because the instances are tied to the number of users. However, it is a bit of a tedious process to get this done.

We are using a third party for technical support. So far, their support is good.

This is the first solution that was used.

We are currently looking at SAP MDG to implement in two or three years.

Currently I would rate it as an eight out of 10, because it is at its end of life and I would like to see more out of the product.

When searching for this type of solution, you have to come up with the requirements of what exactly you want to achieve. Then, you need to go through the tools available in the marketplace and analyze each one based on specific criteria to see which ones you would get the best deal on. Aside from that, it comes down to cost and what you want to achieve with the solution. One of the reasons that we started with NetWeaver was to do some product logging, and it ended up being the full end-to-end solution. It came in for another requirement initially, and we ended up using it for much more. Typically, you need to look at what you can do with it other than the current needs and anticipated use cases.

Local support is the most important criteria when selecting a vendor. We have to have bodies on the ground that can come in and assist us. Therefore, local support is at the top of the list. Additionally, the overall flexibility of the vendor itself. They need to be good at introducing new features or advising us on how to meet the business requirements.