Deploying Oracle E-Business Suite, the cloud version, is straightforward - no need for complicated setups. Just choose a username and password, and you are ready. Configuration tasks like workflows and organization structures are handled by partners like Triad. Unlike traditional software, Oracle doesn't require deploying databases, making it hassle-free. The timeline for implementation varies. Simple processes may take three to four months following the Oracle Unified Method. However, more complex modules like manufacturing could extend to around six months. The duration also depends on client involvement, from gathering requirements to user acceptance testing. It is a collaborative effort with both the partner and the client. I am involved in troubleshooting and providing Managed Services and SNA. After a system goes live, clients often need ongoing support, especially if they lack a dedicated IT team. We step in as tier one or tier two support, offering what some call "day two services." It is a crucial part of our service portfolio and ensures comprehensive 360-degree support for our clients.

It was not complicated, but you need a business analyst to bridge the gap between the implementation team and the business team. We had around three people on our team. We still haven't fully deployed it, but the expected duration is about nine months. 

It's not implementation time per se. It's more like evaluating the solution to understand the strengths and weaknesses of the product. After deployment, you don't need to maintain anything. Some change requests crop up now and then from the business team. They ask us to adjust the business rules or transfer the approval authority from one person to another because someone has left the company or gone on vacation. 

You need someone with technical expertise, and Oracle-certified engineers are somewhat costly compared to other ERP products. For example, there's a German ERP product with an easy mechanism that allows any software programmer to change the configuration. Still, Oracle, SAP, and Microsoft Dynamics require certified professionals to change the configurations.

Installation has become simpler and takes less time. Before, there were lots of dependencies and it required lots of expertise. 

The deployments have a much shorter cycle. Previously, we were doing projects that went on for a year or three years. Nowadays with the cloud implementation, I've done projects in three months or six months maximum, maybe a year. They have consolidated most of their features and functions. It makes training and chain management much easier, so your project time gets shortened basically.

All the big companies – even midsize or smaller – use some sort of ERP or business suite because it's impossible to go back to the smaller products or homegrown legacy systems because of the maintenance and dependencies.

The deployment took one and a half years. The solution is deployed on-premises. The deployment process has two phases. It took us nearly two years. We need at least ten people to deploy the product.

The initial setup is not simple. it's quite complex, very difficult. In terms of ease of implementation, I'd give it a 3.5 out of five. 

We implemented it a long time ago before I was a part of the organization, however, it tends to take seven to eight months. 

The deployment, implementation, and integration are very easy.

The initial setup was quite straightforward. I have worked with SAP, Oracle, Dynamics, and now I'm using ISS. With all of them, you need to have some basic expertise before you jump into the pool, otherwise, your life could be complicated. If you have that basic guidance and experience, it's not complicated when it comes to Oracle. Still, there are prerequisites for each of them — especially when it comes to Oracle. You need to have had hands-on experience with PL/SQL or developer experience with Java.

The best part about Oracle is that it has openly published its documentation on its implementation checklist — how to follow, configure, etc. For this reason, it's much easier to implement Oracle compared to ISS or SAP, for example. This is due to the fact that they insist that you need to follow their documentation and it's not publicly available everywhere. This makes things a bit easier when it comes to Oracle.

The setup was difficult. Implementation happened prior to my tenure at the company but colleagues said it took a long time and much effort. 

To this day, we still have opening balances in some modules that are not configured so they don't match the GL. We have to add data, ignore some periods to match the GL, and export data to Excel to work on it. The solution itself does not provide enough reports or analysis and we have many, many issues. It doesn't seem that the implementation was a success. 

Based on feedback from colleagues, the setup is rated a one out of ten. 

As Oracle E-Business Suite is an ERP system, it has a complex implementation process. It's unlike any other software you can install and start using immediately. The system requires installation, then configuration, so depending on the complexity of the business, it takes around three to six months to configure and run it within the organization.

Installing the software onto the server, for example, isn't a matter of one to two days maximum. The steps to deploy Oracle E-Business Suite depend on your business requirement, how you map your business requirements into the system, and how you want the system to operate according to your needs. It varies based on the complexity of your business where Oracle E-Business Suite would be implemented.

Oracle E-Business Suite requires special resources to install it, not every user can install it. You require a technical professional to install it and to configure it

The setup is very straightforward, and most old practices have been corrected with Oracle E-Business Suite. There are no complications with the applications. We bought several modules from Oracle, and it took approximately one and a half years to implement all the models across the organization.

The deployment process was straightforward. We implemented Oracle with the data center, and we didn't try to customize Oracle EBS to map with our processes. So we implemented the straight line of Oracle EBS extended. One of our local partners aligned with us for the implementation because we didn't have the expertise to implement and configure it independently.

Setting up Oracle E-Business Suite wasn't complex, but there was a huge need for skilled manpower to implement it because of the huge demand for ERP resources in the market, so that has been a big challenge. Whether it's Oracle or SAP S/4HANA, getting good resources to stick to a project and implement it has become a challenge.

The deployment of Oracle E-Business Suite took one year.

The solution was very simple to set up. It was not complex at all. The deployment itself took about four months. 

The installation is a little tricky If you are using the on-premise version. We need to set up the infrastructure and plan for company growth and scalability. If you're on-premises, you need to build a structure and then deploy the system, so that takes a little time.

We have to consider many parameters, including security. For example, we need to implement policies if we want to access the system outside the company network. We need to plan for the number of nodes, like the knowledge application and database nodes. 

The other aspect is the number of instances required and the production capacity of each instance. We need to set up the test, development, and regression environments, then configure the backup and disaster recovery policies. 

Initial setup is complex, hence it is recommended to use a system integrator (SI).

Nothing is simple with Oracle. The initial installation was not easy but manageable and took a couple of days to complete.

The setup was very straightforward. Now, it's well documented and we can import setups. It's nothing to worry about.

It is straightforward, but maybe that is because I have been working in Oracle for the last 20 years and so I find it easy. But I think with Oracle products, the set up and to understand everything is very easy and user friendly.

I think the initial setup is done in a very smart way. It is not very complex. If a person is technical enough to do it, it will be easy for him or her. If someone is not comfortable doing the installation, it will be difficult for him or her. 

The deployment was about nine years back, so I do not remember everything exactly. I think it took us around two to three days. What I consider deployment may have a different definition for some people and may not be the same definition for me. As long as by 'deployment' it means just the installation and initial configuration, then it is just a few days. When it comes to setting up and finalizing all of the business requirements and going live with the system, it took us four to five months.  

The solution is deployed on an on-premises model.

The solution can be deployed in a few months.

The initial setup is a bit complex. The EBS takes more than 12 months to implement from scratch. We're a team that carry out deployments as well as provide service and support for our customers. We have a team made up of architects, project managers, consultants, functional analyst developers, DBAs, close to 20 people in total.

The solution's initial setup is average because you cannot directly install the version you need. Firstly, you should install all the database versions, take some steps to enable online patching, use the ETCC script, upgrade the database, and upgrade the application to the version you need.

We over-implemented and customized Oracle, leading to stability issues. It's like buying a BMW and driving it for 20 years. Tomorrow, you shift to Tesla, and you still want to drive it like you drove a BMW. So, you start modifying Tesla for BMW's pleasure. Modifying it excessively compromises its inherent capabilities. Our process owners, accustomed to SAP, sought similar workflows in Oracle despite its different approach. The software has inherent rules; tweaking them too much can cause instability. Additionally, our system integrator, E&Y, might have over-engineered processes, making them fragile. Unlike our 9-month SAP implementation with a stable product, Oracle took two years with issues.

The deployment of the Oracle E-Business Suite was simple. I have done many deployments and I find it simple, but for others, it might not be easy.

The initial setup was complex. The migration took a very long time, approximately four months.

The initial setup takes three or four people. One is the DBA, one is the technical guy and then we have the functional person which could be two roles; one for testing the application for its functional gain, the business process etc., and the other, who does the setups and support work. Within our company we would have more than 100 users of this product. 

Deployment is more complicated and challenging than you'd find in comparable solutions. We normally have multiple iterations for the deployment. One iteration from a DBA perspective normally takes a few days but then there's the functional part, technical part. I expect it would take two to three weeks for that.

If it's just installation of the ERP then you're looking at a few days but you need to consider the environment, amount of customization, functionality, etc. That takes about three weeks because it involves testing, functional setups, technical setups, and the DBA.

Oracle is a vast domain. For a skilled person, it is not complicated, but for a new person, it is a bit complex.

There are OS and EBS within compatibility libraries. Most issues and bugs are due to the compatibility of configurations. Otherwise, it's not so difficult. 

The initial setup is straightforward and simple. For maintenance, two consultants might be needed to address any issues. 

Technically, it is straightforward. However, there are challenges in the functional side. This is expected as implementing ERP is a complex subject. 

When managed with a proper project plan and right resources, projects are completed on time and with success.

The initial setup is easy and takes six to twelve months - about eight to nine on average.

The initial setup was a little complex for us and I think it took close to seven months to complete using an integrator team; it's a continuous process. We have a team that deals with the maintenance of the solution and there are around 400 users in the company. 

I am not responsible for installation or setup. You need a huge setup and a lot of servers before installing it.

We have a separate team that manages the installation, and I expect that it was a straightforward process for them.

We have about 15 to 20 people on-site and off-shore for maintenance, deployment, patches, etc.

The initial setup is easy.

Oracle E-Business Suite does have a complicated deployment model. It is a SaaS solution, so deployment entails multiple databases and server configuration. The connection between the database and the application has to be configured as well. 

You do have to have expertise to carry out the implementation, however, I would rate the overall difficulty of the employment at a medium. 

The average deployment would require five skilled consultants. Some very basic deployments could be done with one or two deployment developer consultants. 

The initial setup is easy. Oracle provides step-by-step documentation.

With resources and experience, it is easy.

It was not easy to set up.

That's actually one of the reasons we use Salesforce; we're loving it. We use Salesforce for our sales and marketing; no software, no maintenance. I have only a 2-3-person team. I myself oversee the department. I have one developer and one support person. Effectively, that support person is not even 100%, so he probably uses 20% of our time, maybe sometimes a little more than that. The developer is very rarely used. If you add all these three persons, it's not even one person who is actually managing the entire team.

Oracle, oh, my God. I have a team for hardware; you need some Oracle-related hardware stuff. Of course, they're not only doing the Oracle stuff, but you have to have someone. We have an Oracle apps DBA. I'm outsourcing that one. I have a functional guy; he uses 25% of his time now, but at one point, he was using 50% of his time. We also have our in-house PL/SQL developer. You can see how many people. It’s a lot of resources. Oh, man.

Upgrading is a nightmare. I mean, I shouldn’t describe it as a nightmare, but I get nervous whenever they upgrade. It's a lot of work; a lot of coordination; a lot of testing and all those things.

If it was in the cloud, I wouldn't worry about any of those things.

I am more on the development side so I didn't install it. The initial setup was done by OBPS. It seems that because it's a popular product, we can find answers on the support site. For my part, development for it has been easy.

It's application-specific in terms of setup. If you don't have the expertise, it's very, very hard. It's necessary to have this experience with this software. If you don't have the experience, maybe will be very hard to implement. If you do, it won't be that bad. 

You don't need a huge team for maintenance. It's very stable throughout the year. 

It is not easy to set up a project.

We do workshops with the clients and all of their departments to find out the business processes that they have. We then try to match these processes with the features we have in Oracle and if there are any gaps, we try to customize the system to answer their business processes. Or, we try to convince them to change the way they work so it matches what Oracle is bringing. It may take a year, or sometimes a year and a half to be implemented. However, it does answer a lot of business problems.

Speaking from a functional perspective, I don't believe that the initial setup of Oracle ERP would be a particularly complicated task for the team responsible for handling it.

Here's a possible rephrased version, based on my understanding:

The Oracle ERP software doesn't require any specific maintenance beyond normal routine maintenance.

It was straightforward because we wanted to use Oracle out-of-the-box. There were a few extensions, but we wanted to adopt the processes rather than change the system to support our processes. We knew that there was going to be expanded scope and implementations globally. We wanted to keep it simple.

The setup to me is straightforward, but I've been using it for so long. For a new person, I don't think that companies could use the software without consulting help of some sort. You need to understand your business. There are very good consultants who could come in and they will ask you the right questions to help drive the setup. They're decisions that need to be made that, if wrong, you can still live with. But, there are other, more critical decisions that you make that you can't undo. So is it easy to set up? Physically going into the screens is as simple as can be. The question really needs to be, how much time do you need to put in prior to sitting down to set the system up? You really need to understand your business and you need to understand what you're trying to do.

The initial setup was a little complex, and deployment took between twenty and thirty minutes to complete.

The initial setup was very easy.

It was quite complex to setup, taking about six years. We currently have three employees maintaining it.

We did not find the initial implementation to be complex. It was rather straightforward. As time went on there were some little customizations being made, however, it was just rather straightforward in general. We didn't struggle with the implementation at all.

The initial setup is neither too complicated nor too simple. If you are experienced, it doesn't take too long.

The initial setup was definitely not straightforward. One reason is because we've customized the product and it's not as-is. We have so many customizations and interfaces and reports and other things, that we have to make sure that they all work with the new versions. And that takes time: for example, we did an upgrade two years ago from version 11 to 12.1.3. This was an eight-month process for us from development to testing to production. So this was a huge project.

Even when Oracle releases patches just to upgrade maybe one module, we still go through a testing just to make sure everything works. We don't just blindly put it in production because we have seen a lot of issues. We have faced a lot of issues earlier when we put up bad patches, something stops working, and then we have to fix it again. We just make sure that we test that patch before we put it.

Oracle implementations are complex and require that the customer understands, and reviews their business processes. Often time it is difficult to revert from one configuration to another. Customer need to wisely consider things like set of books and general ledger account structure and how their business processes align with best practices and what Oracle has to offer.

The implementation took a long time but it was for many reasons. However, Oracle made sure that the solution and systems were up and running. 

ERP solutions are hard to evaluate for implementation because the process is more of a journey. When an ERP solution is implemented in an organization, it's a journey, it's not a simple out-of-the-box installation. The whole process is different from other solutions.

It's okay, but the real pain comes when you're moving from one area to another. Configuring the APR system is not that easy and it is not easy to get something out of it that you configured. You need to keep on working on an environment’s configuration to bring it up to speed. Now, you're sure this environment is all up-to-date, and everything is working fine. Now, we need to move into the next environment where people are going to test the system.

Currently, there is no automation for migrating an entire configuration to a different instance. You need to manually resolve all the errors. It is very difficult to even identify where and what went wrong. If you are really senior, and you have a lot of experience working on it, then it might easy for you to go and see, "We are missing that."

It would also benefit from a full-fledged comparison when something went wrong. If we could run something that will identify, "Here is the configuration here.This is a mismatch." That would also work well.

E-Business Suit setup was complex, but I think that every Oracle product has a complex setup. It wasn't easy and it wasn't straightforward. In fact, it took us one to two years to complete the setup.

Yeah, the initial setup is highly straightforward. It takes four or five days to install. Once we installed it, we made a copy and started using it. The first installation takes time — four or five days. Then, using the same installation, with cloning, it takes only one or two days, maximum. So it's easy to install.

The initial setup was pretty straightforward, and we didn't start out with any customizations or anything like that. I think it was pretty straightforward, getting that business process around it.

The initial setup is pretty good now. Every page has help associated with it.

I think that the initial setup is complex, especially since we were unfamiliar with the software. We were talking to consultants who were unable to relate to us. We were coming from a mainframe world and a lot of our decisions were wrong. I don't fault Oracle for that, though. It's just part of any implementation.

It is very complex as its tightly coupled with business processes and also involves a very large number of interfaces.

If a person is knowledgeable, it’s good enough.

It is straightforward and quite good. In the Oracle application, we don't have an issue with that.

Since we are hosted, we can’t do rollouts ourselves. We have to schedule them. A lot of our issues have been with our patching, since our hosting partner always seems to break something, which is frustrating. If we had the product all in-house there would be no issues. It’s relatively straightforward to set up.

There were some modules that were more complicated. All I would say is that it wasn’t too simple and it wasn’t too complex.

The initial setup was quite complex because ERP can manage a lot of processes; therefore, a company must consider what it wants to manage and set up.

I've been through two of the upgrades. We went live the year before I joined the company, but then I was involved with the 11i upgrade and the R12 upgrade. They were pretty complex. We had both functional and technical assistance for both of those upgrades. It was a lot of work and a lot of long hours. But, getting on the R12 helped with some issues we were having with the 11i.

It has been a very slow process that's very complicated and very rocky. We have used a consulting partner to get it implemented and there have been a lot of bumps and hurdles to get over.

While I was not part of the initial setup, I did have the opportunity to work on another one. For me, I did not find that it was difficult. I think it's a question of one's knowledge of the system.

The initial setup time depends on the size of the implementation. In a medium-size business, the implementation could take between six months to one year to complete.

The initial setup is complicated. For the end-user, it'll take about two or three weeks to use one of the modules.

The initial setup is complex.

It was easy.

When we introduced Oracle E-Business Suite, I was part of the implementation team. We used to be PeopleSoft, so I was part of the PeopleSoft internal auditing team, and I was also involved with the upgrade. The new implementation was very challenging because we needed to do a lot of customization. There were also many new business requirements at that point in time. But, when we later performed an upgrade, it was not too complex.

It was seamless and went very well.

The initial setup complexity depends on how you map Oracle facilities with the business process.

The initial setup was straightforward. Our team has a lot experience in the Oracle E-Business Suite implementation and we also cooperated with professionals from Oracle Romania. Lastly, the client was actively involved in all the stages of the project.

Initial setup was complex because it extends to a lot of our applications’ integration points. Once you find out the solution, what to do then, the next time, it kind of streamlines the process.

I haven't done a setup in the U.S., but I've done them in three Latin American countries. The business analysts are the implementation team and then we do the setups for the test instances. And then we go to our support team to do the configuration for UATs in Prague.

Sometimes we take advantage of all the things that Oracle gives you to go beyond just the basic stuff. We get a little creative so that there's a little more complexity to the setup in the end.

I wouldn't describe the initial setup as straightforward. It's very complex. Even Oracle themselves would say that this solution has the most complex implementation of their products. It might even be one of the most complex in the world.

Deployment took almost one year. This was due to the fact that the analysis design alone took almost six to seven months. Implementation and testing alone took another five or so months. 

I wasn't actually at the company at the time, but for upgrades for which I've been apart, they did seem to be a little bit more difficult. A lot of it could be on our end, mainly because of how we do a lot of customizations. We had to do these customizations, unfortunately, because E-Business Suite didn't allow for a specific industry like ours to have more to an 'out-of-the-box'-type of developed software. There was a lot of customization. Now, they have improved from version to version, but for our business, we're still very much away from being cloud-based. Our software sits on a non-internet network. It really is hard for us as an organization to sometimes do business in the environment of, 'Everyone wants to move to an internet system', i.e. the cloud. There are organizations such as ours that have trouble at this point being on an internet-based system.

With our customizations, it stopped a lot of the upgrade that we just had last year. When we did the upgrade, a lot of these customizations were a constant battle where one would not work, another would work, and then when you'd fix one, something else would happen. There were a lot of issues, which we are, as an organization, trying to pull away from customizations. Oracle has not really been geared a lot towards what our line of business was. We have to do a lot of customizations in order to allow for that software to work as we need.

Initial setup is complex. I think any ERP is going to be a complex setup. That's just the nature of the beast.

Usually you'd have a partner that can add the bandwidth. I know we did an upgrade about three years ago. We had a partner come in and help us with that. It's a probably nine-month project, end to end, to do a major upgrade from 11 to 12.

The initial setup is straightforward. While you can complete the installation yourself, you will need to know the product and how the product is configured.

An understanding of the business process is required to easily configure the application.

You must have the knowledge to know the subsequent actions, how they are done, and how the links are set up together. For example, I can define lookup, and to do this I will research to know if it will use the standard form, or if it will use the value set or the standard use for one report or other types of validations.

Overall, I believe that it is always best to ask someone who is experienced. For example, if we consider the iPhone mobile, we may ask how can we take a picture, If you are coming from Android to iOS, you will ask someone with experience in this type of operating system, how you can do related things or supporting context.

I'm an implementer, so the Oracle E-business Suite's initial setup is easy for me.

Initial setup really depends on the module. It’s not very consistent, I think because different people have developed the different modules. You have to get used to it.

I was not involved in actually setting up the product, but I am involved in some of the customization we do. Sometimes we have to do setup, but that is not initial setup. We make some modifications.

Setup was mostly straightforward; it was not that complicated. We had some user manuals and some recordings, which made it easier.

Setup is always complex because you have to choose the server configuration, hardware configuration, bandwidth, and so on. On-premise setup is always very difficult. Now that services are cloud-based, it is Oracle’s headache, not my headache.

The complexity of the setup depends on whether you have a lot of requirements and are using many modules. It can be as simple or complex as you make it.

The initial setup was complex from our perspective because we were new to all Oracle products at the time.

I was involved in the initial setup and had help along the way. The setups were easy for me, but I know that the technical portions of the install with our IT guys had some glitches.

The initial setup for E-Business is pretty complex. I think that the difficulty is similar to implementing NetSuite as well. With NetSuite, you can get it up and running in three to four weeks for core financials. With Oracle, on the box, it says that it can be done with the setup rapidly and that may be true. But it is actually the internal change and adoption that are the biggest problems. In other words, I think that it is actually more of a problem as to how quickly business people can change rather than how difficult it is to deploy.  

Initial setup really depends on the module. It is not very consistent, because different people have developed the different modules. You have to get used to it.

I do the setups in production, and afterwards, I'll do the support. It can be complex.

I wasn't involved with the company that I'm at now, and it was definitely complex in the previous companies that I've been with.

This is a complex implementation. It took approximately eight months to deploy.

The initial setup was simple and straightforward because we kept it vanilla with out-of-the-box functionalities.

It was already implemented, and then I came on.

No, none at all. We did start with two products, but it was not perfect in terms of integration.

The setup was moderate.

I wasn't involved in the initial set up. I was involved in all the upgrades thereafter. They vary, some were great some were pretty straightforward others were problems all the way along. Their migration paths, they've gotten better over the years so they're not quite as bad.

For one thing, we do a lot of work with the federal government, but the federal government isn't the federal government. It depends on which piece of the federal government you work with. Each of your customers in the government have different requirements and you really do have to do some customizations around billing. Because we have all these different federal government customers, some of them want the bills uploaded into a certain system that they have to process their bills, or they want the bills to be in a certain format and your other government customers don't need it in that format. We do a lot of things based on the customers’ needs, but I think the functionality in this next release is taking some of those considerations and putting them in the software, so they're there already. So the 10-34's and 10-35's that the government requires, their putting that into the Oracle functionality, whereas before we had to make those on our own.

It took about a year and was a painful process. I would never want to do it again, but we went from a system we used for 30 years to something much more dynamic and new.

The complexity of the setup depends on what we're doing. When we upgraded to R12, the setup was painful. It depends also on consultants, functional leads, and others involved. So the setup is not just about the product itself. Also, because we were early adopters, we experienced a lot of bugs that hadn't yet been worked out, and some of the consulting at that time wasn't the greatest.

The initial setup of Oracle EBS is easy, it is plug and play.

The initial upgrade, as I’ve mentioned, took away some of our valuable reports that were in the original Oracle EBS. That was really annoying.

The other thing was that, when we did the upgrade, it brought up some bad data from prior years. It took a few years to figure out what was going on. It still, even to this day, four years later, still pops up information from 10 or 11 years ago. Luckily, we're not a big, big company; we're just a local government.

Initial setup is very, very good; straightforward.

The initial setup was very complex. Installing it is not bad, but it's configuring it that's difficult. It's getting the setup correct, and that's what takes time. It's company-specific, but we're pretty vanilla. Even with that, it still takes many months to upgrade. The documentation is there, but it might be helpful to have someone who's done this one or two times before.

The initial setup was not easy.

It was not complex.

The initial setup is very complex. I wasn't there for the initial implementation, but just knowing what I know, it's very complex to get it set up. You need an implementation team or consulting firm to come in and help.