The difficulty of setup depends on the individual. I am basically a finance professional by qualification. My academics and professional career have been focused on finance functions. The principles of accounting have been extensively followed and built into the solution. It is amazingly done. 

People who do not know the subject well might find the setup more complex. For example, some users might not have a manufacturing facility so do not have exposure to manufacturing accounting. 

The financial accounting is easy. All you have to do is set up the chart of accounts or other basic requirements, integrate with other modules, and you are done. Accounting entries will automatically post. At the end of the monthly, quarterly, or annual financial period you just close the account books. 

In general, every SAP project is quite unique. It depends on how well we understand the requirements and what is expected from this implementation. The success of the whole implementation is actually meeting these expectations or maybe lowering expectations somewhere. I have participated in several end-to-end implementations, but the time varied for each deployment process and the processes differ in each company.

It was set up for me. I didn't have to do anything.

I rate SAP ERP's initial setup a seven to eight on a scale from one to ten, where one is difficult, and ten is easy. It is not easy to implement SAP ERP because it's not a one-sided affair and requires joint efforts from SAP's partner and the tool's customer, making it a two-way effort or a joint effort. If you use SAP ERP with SAP Best Practices, then I would rate the initial setup a ten out of ten.

SAP offers users multiple options and allows SAP ERP to be deployed on the cloud. SAP ERP's latest or newer versions are all on the cloud, but it can also be deployed on an on-premises model.

The solution can be deployed in four to five months.

Depending on the requirements of my company's client, the product's deployment team varies anywhere between five to twelve people.

The solution's deployment process was easy for me since I have experience in deploying it. However, it may not be straightforward for someone else. Since it is not a PnP device and there are so many moving parts, there is a high chance of the person involved in its deployment process making a mistake. But, over time, one gets to know and learn what to do when something happens. Even though issues are there in the solution, I am able to use it after fixing it.

I was not a part of one of the latest instances involving the implementation process of the solution, but I have carried out the implementation process in many other places. So based on my experience, the implementation process takes about six months.

The product's initial setup phase was difficult as special people were required for the installation since it is an ERP software and not any hardware product.

A specialized person is required to deploy each module of the product. My company uses six modules of the product, so we need six different people to take care of the deployment of each module.

As it is an ERP product, the deployment part may take a long period of time to complete. The product deployment is usually taken care of as a part of a project.

The solution is deployed on an on-premises model.

The initial setup of SAP ERP is very easy because it provides best practices and building blocks. In the last version, it has greatly improved. For example, the user experience is now completely for the user. Users do not require training because the latest version of SAP HANA is very easy to use.

The implementation is very straightforward when implemented directly with the right team. However, if you are migrating from another system, the implementation is more difficult because you have many compatibilities, and the deployment timeline varies. For example, in one of the companies I previously worked at, we started in 2004 and ended in 2008, but other issues elongated the process. As a result, we did the complete handover in 2008. At another company, we began in 2014 and ended in 2016. However, they were already using the system, but it wasn't fully deployed until 2016, as the modules were completed based on business requirements.

I wasn't involved in the first deployment as it was in 2006. However, I was involved in the migration from the old version to the current version. That process was quite complex since we use a lot of specifics in our version. That made it difficult. We had to bring all the specific programs to the new version and also test all the specifics.

The initial setup is straightforward.

The initial implementation is very complex. It is a very large complex system.

The initial setup of SAP ERP is complex. However, if you have a good team it can be easier.

The deployment time can depend on the size of the company.

The setup is difficult so implementation consultants are needed. 

The deployment is quite complex. The preparation, setting up of all the systems, and the tests are complex. We need a lot of involvement from the key users. The maintenance of the product is easy if we have the right people for the modules. We work with third-party providers. The product works fine if they know what they are doing and we have the right links inside and out. We also need knowledgeable key users in the departments.

The tool is easy to deploy. 

The initial setup of SAP ERP is complex and it took a lot of time.

Deploying SAP ERP two years ago was a bit challenging. We moved from an existing instance to a new virtual one, rebuilding everything from scratch and converting Master DataOps. It took some effort, but with external support, we successfully made the transition. Deploying SAP ERP had its challenges because when we started using it six or seven years ago, it wasn't a new setup but a result of a merger. For the first three years, we were more focused on daily operations. When we decided to take full control three years ago, it was our first time setting up our processes. We needed external support to navigate the difficulties, given our limited familiarity with the new package.

It might be difficult for people who are new to the platform. I rate it seven out of 10 for ease of setup.

The initial setup wasn't that complex. We went live for about eight branches, and it was complex in terms of size only. Everyone uses this solution because it is used for timesheets.

The setup of SAP ERP can be simple because there are pre-configured setups. This allows for similar implementation for clients. Cloud deployment can be easier. The on-premise takes more time to build the servers and systems.

We followed the active SAP methodology for the implementation of the solution. We then gather all the details needed for the business to complete the implementation, such as realization, customer training, and integration. We then support the customer for a few months after we deploy it.

A typical project can take seven to eight months to finish implementation.

The initial setup was medium difficulty. We had more than 100 people working on it for two years.

The deployment process depends on various factors. For the bare minimum setup, the solution would take six to nine months to deploy. But the likelihood of it taking six to nine months is very low. It's probably going to be more like a year to eighteen months to get the whole thing up and running and fully working as you expect for an organization of over six thousand people. 

The time taken to deploy the solution depends on the implementation approach. More than likely, you would roll it out to one part of the organization, which could take six to nine months. Then you would expand it to other parts of the organization, which would take longer. So, there's a deployment that could be done in six months, but it's unlikely that the entire organization would be fully onboarded in that time.

If we're talking only about administration, setting up our landscape is very complex. 

We have a huge number of servers. The SAP software itself is more than 100 gigabytes. It takes two to three days to download SAP software from the SAP service marketplace. And installing the server itself takes months. It's not easy.

Initial setup is complex. I would rate the setup a 4 out of 5.

The initial setup has some complexity to it.

From the user's point of view, the solution is easy to set up. You don't need to modify anything while setting up the solution. I rate the initial setup a nine out of ten.

The time taken to deploy the solution depends upon many factors, such as the number of modifications, change requests, and the complexity of data migration. It also matters if it is for one or a few small countries. Setting up SAP ERP can take half a year or several years.

The solution's initial setup process is complicated.

SAP ERP is difficult to set up. You need to configure lots of things during the deployment. The deployment time depends on the company's size. It might take a couple of years to fully deploy SAP ERP for a multinational corporation. 

You need to undergo the initial setup and a few testing rounds. Some companies can do it in a year, but large enterprises have multiple systems to integrate. Smaller companies can do it in under a year. It takes time to deploy it across several departments, such as finance, logistics, etc.

The tool’s setup is straightforward. From the technical perspective, we can complete the solution’s deployment in less than a month. However, on the business side, the deployment depends on the customer’s requirements such as finance, supply chain, etc. It can take around four to six months for those aspects to complete. We follow the SAP Activate methodology for the tool’s deployment. This methodology has different phases to deploy the solution. Apart from the methodology, we use a tool called Solution Manager for the deployment.

Its initial setup is quite a complex task because many business people are involved from different areas. It is not a simple solution that is being used by five or ten people. In our company, it is being used by thousands of people. Its implementation requires many consultations and discussions with different business communities. It also requires customization, configuration, and testing before you start using it.

I rate SAP ERP's initial setup phase a four on a scale of one to ten, where one is a difficult setup, and ten is an easy setup.

SAP ERP's initial setup phase was quite difficult.

SAP ERP's initial setup phase was complex, as my company had to seek help from a third party while maintaining a lot of coordination and months of discussions with them to get the tool fully usable.

The solution is deployed on an on-premises model.

The solution can be deployed in twelve months.

SAP ERP has three modules or sections that help with the installation areas like the development, quality, and deployment of SAP. SAP takes or collects the data from each of the departments and the processes, and then it gets put into the area that deals with quality in SAP. The signoff of the UAT and any other agreements is done before proceeding with the final deployment.

The company was already using SAP ERP when we joined, so I didn't have to do any setup here. But in my previous job, we did set it up.

It wasn't straightforward. We had to first align the HR processes. IBM was the implementation partner. We had to speak with SAP and also IBM. They understood our processes and they proposed the best solution. Some parts we did not agree to, so there were workarounds, but it went through. Once the design architecture was finalized, the implementation was smooth.

The deployment took six months.

I didn't do it, but I'm sure it's complex.

In terms of maintenance, due to the fact that the solution is complex and nobody can know everything, it's important to have at least two people on staff for maintenance that can handle it and understand how everything - or mostly everything - works. That means either hiring out experts of having in-house personnel.

Normally our customers are in retail, the chemical industry, and energy companies. The setup is usually quite complex. When we want them to transform to S/4HANA it has been mainly customized. There are a lot of specifics because their processes are generally not straightforward.

The deployment will take perhaps two months, on average.

The initial setup is complex. One of the main difficulties is that there are a lot of processes and you need to integrate all of your ecosystems. When you have a very complex environment you have to understand the details and complexity.

The deployment can be done either on-premises or in the cloud, depending on the requirements. It can be an ongoing process.

The deployment process requires a lot of resources and is expensive. It takes a lot of time to configure and deploy SAP applications. We need around 50 to 60 skilled resources for configuration setup. For finance, we may need another 50 resources. The process involves technical modules. Thus, we need expertise in finance and cost to handle the functional models, including warehouse, production, and plant maintenance. SAP provides good support services to help us set up the application.

The deployment time depends on the size of the data records and their processes. Some implementations might happen for years together.

The number of engineers and architects required depends on the existing data and processes. On average, we need a minimum of 10 executives to work on each module. We have around 20 modules in total. We may need overall at least 100 resources to implement the product.

I did not manage the initial setup process. I cannot speak to how easy or difficult it was. 

I've carried out deployments for about 10 customers. For those without experience, the implementation can be quite cumbersome and complex, although, over time, they realize that all the business processes are properly mapped. Maintenance requirements depend on the number of users, which modules are being implemented, and the like. It really depends on the scale and size of the implementation. 

It was easy to install. It took more than a month. It was done around 2012.

It's a complex application to initially set up. It takes time and you have to save a lot of small integrated details. There's so much configuration and features are available which makes the setup relatively hard. That said, it works. If you know it well, you can do it well. If you don't have the background, you will struggle.

The initial setup is simple. It's not complex. You have a range of requirements on the system, therefore, you don't need more complexity configuring the system.

While we used a business partner who assisted us originally, we now have the internal knowledge to handle everything in-house.

Our IT handles any aspect of the maintenance that might be required.

The initial setup is somewhat complex and requires advanced planning. 

The initial setup is not easy. To deploy SAP ERP you need consultants and you need training. There's a lot to learn before you can properly use the product because it's a huge solution. It took us a year to complete deployment. We deployed the ERP, the central component and the HCF, the human resources module and industry solutions for healthcare that is EHS and EHSM in a year. 

Complex. SAP ERP, even with its so-called industry-specific best practice, does not fit everybody. It must be custom configured to fit your company.

As a consulting company, we can deploy ERP quickly. Our clients are unable to implement alone, it requires some expertise. Our last couple of deployments have taken six to eight months. The solution is easy to maintain but it requires support, either external or internal. SAP charges a maintenance fee that is quite high at 25% of your initial license cost. 

The implementation of the solution took approximately one year. However, this might seem like a long time but it is typical for ERP solutions.

The initial setup is straightforward. 

Initial setup is a little complex when compared with Workday and SF.

The initial setup is straightforward.

It is an extremely complicated deployment. The deployment is completely customized for my customers here, and it could not be made simpler. 

It was complex. As we moved forward, we slowly got used to it. I won't say it is straightforward now. It is still complex, but somehow we got used to it, and we are working with it. The deployment took around eight months.

I was involved in the setup and it was not easy. We had to bring a technician from another country, from Brazil. He had to come for three to four weeks to do the installation. So it wasn't easy at all.

But once they did it, they documented it. So today, it's not that hard because we have everything written. Today, we can install another system and do it with internal IT staff. So we learned from the process.

The initial setup can be quite complex. You need to have someone who is quite knowledgeable on the solution in order to successfully implement it. SAP is quite difficult.

It was complex, as the company policy needs to evolves at the pace of system functionality and the design direction.

The initial setup was straightforward.

The initial setup is a little bit complex. In the beginning, it takes some time for the business consultants to prepare the environment and set up everything. Usually, if you give the consultants the appropriate time to do the setup correctly the first time, everything will go smoothly.

The initial setup is somewhat difficult but with the kind of support we have it's not a problem. The installation or implementation is a tough thing for SAP, there are multiple factors which have to be taken into consideration.

The initial setup of SAP ERP was complex and very rigid.

The initial setup is very complex.

The initial setup was complex and took approximately three hours for all the computers.

It wasn't easy to install SAP ERP. It has its own sequence of steps that we need to follow, but it isn't that complicated.

The setup complexity depends on how strong of a team you have. If you have enough experience, then no major problem with implementation. For the cloud solutions, now you don't even really install. You just get your own tenant developed or created by the SAP itself.

The size of the technical team you will need depends on your business scale. You can do it with a small team of two or three people if it's a small implementation. You can also deal with the thousands of mandates if it's a complex enterprise implementation. That said, it's the same or very similar with any other tool as the complexity is not driven by the tool itself. Rather, it is the business processes of a customer.

Straightforward

Complex as there was a lot of data conversion involved

Deployment is costly and it takes a lot of time, but once it is done it is very smooth. We deployed SAP in a phased manner, country by country. We started with one country, gave it a year or so, and then we moved on to the second country. We have rolled this solution out in six countries over six years.

I don't set the solution up. It's just for me to play with the keyboard.

The initial setup was pretty straightforward. I don't believe it was complex.

We require 10-12 people to handle the maintenance on the solution.

If you have good resources and quality people who understand the business and procedures, the implementation is not a big challenge. 

The initial setup was quite straightforward.

The initial setup is complex. It took us about a year and a half to fully deploy.

Overall, initial setup is very complex.

The initial setup is a bit complex.

It took approximately six months to deploy.

This is an easy product to install, although the process can be more difficult depends on the customer's requirements and environment. Sometimes, we have to interact with customers a lot before it is complete.