JD Edwards EnterpriseOne Reviews

Our primary use case for the solution is for finance, such as payroll, sales and production but not full-fledged manufacturing because we have an in-house system developed for that. We deploy the solution on-premises.

We find the ease of use, customization, and user interface valuable.

The solution can be improved by including a built-in data warehouse and BI functionalities. So the end user could report by themselves, depending on the IT. Currently, the solution has many good features, but the issue is that people need to be very well-trained and have the right resources to do any work. For example, if you want to make a new system out of it for your business, you need to have a specialist and an architect available. In addition, some specialized resources are required for each module, which is sometimes difficult.

We have been using the solution for approximately nine years and are currently using the latest version.

The solution is stable. I rate it a nine out of ten.

The solution is scalable and easy to integrate with others. It can extend to many things, including interfacing with other applications and API-based interfacing through databases. Approximately 150 people, from operators to the CEO, are currently utilizing the solution across different countries, including Bahrain, Singapore, U.S. and Australia. I rate the scalability an eight out of ten.

When we have issues, we usually contact our in-house team first, and if we need further support, we reach out to Oracle support, but we have not directly used support from JD Edwards Enterprise One. I rate Oracle support a five out of ten because the technical, licensing, and sales teams do not communicate with each other and provide varying information depending on the agents we speak to.

Neutral

We used an internal system on the IBM platform before moving to JD Edwards Enterprise One 25 years ago. JD Edward Enterprise One has a lot of functionalities, but they are costly. So we have developed in-house systems to take care of them. For example, we have our time and attendance systems outside JD Edward Enterprise One. We also have our procurement, which liaises with our suppliers and vendors outside JD Edward Enterprise One because we cannot afford to manage everything from JD Edward Enterprise One. The fundamental functionalities are on the solution, but for any extra features and self-service workflow, we handle it outside of JD Edward Enterprise One.

The initial setup without a lot of customization is straightforward. I rate it an eight out of ten. However, suppose there are many customizations, and you want to tweak the system to meet your particular function, depending on the complexity. In that case, it may be complex, but it is straightforward with minimal customization and more towards parameterization and customization.

The period for the initial setup could take up to a year or more, depending on the complexity and availability of resources. If you're starting from scratch and don't have a JD Edwards Enterprise One solution and want to implement it in the organization, configure it and set up the system to be functional.

We implemented it in-house because our team has been there for many years and knows the whole system and the business. So they are like internal consultants. They are process experts and JD Edwards Enterprise One experts, and they are the IT guys. A minimum of two people are required for maintenance.

The licensing is expensive compared to other solutions on the market, and getting the resources in Bahrain is not easy because very few of us use JD Edwards Enterprise One. I rate the pricing an eight out of ten, with one being the least expensive and ten being the most expensive.

I rate the solution a seven out of ten. The solution is good but can be improved by including a built-in data warehouse and BI functionalities. I do not recommend the solution for users in Bahrain or Gulf because limited resources are available. However, if they can support it, then I recommend it. However, I recommend it to users in the U.S. or other countries with enough resources to support it.

It is an ERP platform.

I use it for admin privileges to create a user and delete a user or granting with the usage of our user is different in their perspective. They use it for logistics or ERP functionality, whichever is applicable to them.

It’s a web-based application and it is easy to use. It offers a wide range of solutions for the industry part.

The product is easy to set up.

It’s a stable product.

The solution can scale.

The solution is already pretty refined. If they can continue to do so, it will continuously get better.

We’d like to see technical support integrated within the application so that it is not required to raise additional incidents or do manual outreach to support. We can reduce the manual process for technical support by having it within the solution itself. That would be easier than sending tickets.

I’ve used the solution for more than three years.

We’re on the cloud now. There are some integration and migration issues, however, apart from that, the application is stable. Probably once everything is sorted after the implementation, it should be good.

The solution is scalable. We already have a scaled version of it.

We have around 5,000 users right now.

We haven’t really had issues with the solution. It’s very easy to use and therefore we haven’t needed the help of support so much.

It’s easy to initially set up. It’s not hard at all.

I’m not sure how long it takes to deploy the product.

I'm not sure about the license part. I don't have any details.

I’m not sure if the company evaluated anything else beforehand.

I am a reseller.

I am not a regular user of it, I'm an admin user of it and I am not aware of the application part of it.

New users can use the solution as a web implementation of the application and it is a user-friendly application.

I’d recommend the product to others.

I would rat ether solution eight out of ten.

We are a consultancy and we use this solution to provide services for our customers.

Over time, I have used JD Edwards for a variety of use cases. One of the very recent ones was converting from strong discrete costing to actual costing in a manufacturing setting. Some other examples are capital asset management and AP automation.

The most valuable feature is the user experience, where you can create your own queries, it sends you alerts, and it's very flexible.

The interface is very user-friendly. As long as you apply logic, it is easy to do the technical stuff. It is structured well so you don't always have to depend on technical people to do things like create reports.

It has the latest features in terms of embedded mobility and orchestration.

The integration with other products is easy to do.

Customization is easy to do, as long as you stick to their rules. It can be customized in a cloud-based deployment, as well.

There are tools in place that allow users to update the system themselves, without any technical support.

Support for developers is easy because they have their own toolset. They have options for using SQL, RPG, and different languages, depending on the hardware that you're using.

I would like to see the HR features enhanced with respect to localization for South Africa and other countries. They have perhaps 12 localizations but I think that for countries like South Africa, where the payroll system is unique, they should start investing more heavily.

I would like to see more training documentation, or alternatively, training that you can do without having to go offsite. Unfortunately, when training with Oracle, it is quite expensive. Also, the instructors come from India and the dialect is very difficult for people from South Africa to understand. Consequently, a lot of people feel that it's a waste. It could have been very good but they didn't understand what the trainer was saying. This is a big thing that I would like to see more with. The documentation that they have is good, but it's very expensive so people would rather not buy it.

I have been working with JD Edwards EnterpriseOne for about 20 years, since 2000. Prior to that, I had been using JD Edwards World since 1991.

EnterpriseOne is used on a daily basis and the actual solution is very stable, whether deployed on-premises in on the cloud. Stability will depend on who did the setup, as with any system. When you try to take short cuts then you end up short anyway.

It is absolutely easy to scale this product. We have about ten users in the company.

I have a little bit of experience with similar products from several vendors, including Microsoft Dynamics and SAP. I have found that the user experience is much nicer within JD Edwards, compared to anything else that I have seen. It is not rigid and allows you to change or customize things within the framework that is provided.

NetSuite is a little bit cheaper than JD Edwards, although they are catering more to smaller enterprises rather than medium-sized organizations. They compromise certain functionality or applications. A lot of the applications out there are good for startups, but the moment that you start diversifying, you have to start looking either at add-ons or re-implementing different ERPs. The trend lately is not to just replace everything. Rather, have additional or complementary products that suit your needs

With JD Edwards, it is a fully integrated system so you can run just certain modules, but it's optimized if you use the full ERP system. For example, if you need procurement, work orders, and financials, then there is a benefit to moving everything into one system.

Provided you understand the framework, it is quite easy to install and set up. After this, it is easy to maintain and manage. The length of time required for deployment depends on whether you have a proper blueprint because all of the processes are embedded. With all of the blueprints available, for a new installation, it can take between six and nine months.

The deployment will also depend on the state of your data. It may already be clean, or it maybe needs to be pre-processed before migrating. I would say that every situation is unique. You can do the majority of the setup offsite, just by getting all of the business processes in advance. Then, when you start UAT and other testing, you go onsite and go live. It's not that complex. I came from a financial background and moved into the IT sphere, which was not that difficult to do.

The maintenance is done with our in-house team. Normally, you have one person for every module. However, on the technical side, you only need one person because everything has been automated and is orchestrated to do a lot of the work for you. It just pops out some reports and alerts as it monitors the system for you.

In some cases, we used assistance from the vendor during the implementation, although we have also deployed it ourselves. These days, a lot of the migration, upgrades, or updates are done internally.

When it comes to supporting our customers, we are able to do functionality support because we've got in-house business analysts who do the actual applications. 

The licensing is for mid-market businesses, where it is cheaper than Oracle Cloud, EBS, or SAP. It is very much on part with Dynamics, although Dynamics can become quite pricey in the end.

The cost of licensing depends on the modules that are being used. It varies because some of them are user-based, whereas others are employee-based. 

There is a lite license and a normal license. People who use it full time, like in procurement or for someone doing purchase orders, use a normal license. On the other hand, when you get people that only do approvals, for instance, then they can get a lite license and it's a little bit cheaper.

Most of my experience is with on-premises deployments, although I have also worked in an environment where we hosted it on the cloud. If you have a cloud-based deployment then it's managed and maintained by the vendor, although you can still have your own customizations that are unique to the business.

The vendor continuously improves this product, basing their changes according to the feedback provided by customers. At this point in time, it is difficult to asks for specific features because they're very compatible with any other system in the market.

They are very strong in the manufacturing, construction, and engineering industries.

My advice for anybody who is implementing JD Edwards is to make sure that all of your processes are stabilized and standardized. Follow the best practices. Make sure that the processes are not coming from somebody who had good ideas 60 years ago but in reality, are no longer effective.

The best thing to do is make sure that the data is clean and you have the blueprints for the business processes according to best practices.

I would rate this solution a ten out of ten.

It has simplified the process completely, and even though it has many features which are available in the market now, but it is on par with the other ERP software solutions available in the market now.

One feature is that J.D. Edwards supports any software it integrates with.

It's a 100% stable product. In past versions, there were issues of instability. But, now it is entirely stable, as long as it is properly maintained and properly implemented.

It can be scalable to any extent. There are no issues and no boundaries. We find for J.D. Edwards to scale. It can serve small medium and large enterprises at the same time.

Originally, there were some complications with implementation. But now, it is very simple to set up and get everything going in a couple of months. Oracle has done tremendous work on improving the issues that we were facing on the J.D. Edwards front, and they fixed all those issues. Now we do a straight forward, simple plug-and-play installation, so there are no problems technically now.

The pricing of this solution costs an arm and a leg. This keeps the customers away from going for J.D. Edwards.

We compared:

• JD Edwards EnterpriseOne vs Dynamics AX
• JD Edwards EnterpriseOne vs SAP
• JD Edwards EnterpriseOne vs Red Hat. 

We selected JD Edwards because technically it was sound, and commercially, it came at a good price. It was a great value.

When looking for a new product, definitely consider:

• Stability
• IT technology
• Value

JD Edwards EnterpriseOne is used by our clients that use different modules, such as payroll and finance. I primarily use the payroll module.

The most valuable feature of JD Edwards EnterpriseOne is the flashback it quickly takes you to the data browser. Additionally, one of the newer tools is the orchestrator which is very good.

JD Edwards EnterpriseOne could improve the speed because sometimes it takes time to load into the environment. This is typical when the ESU patch packages are used.

I have been using JD Edwards EnterpriseOne for approximately three years.

JD Edwards EnterpriseOne is stable.

The scalability of JD Edwards EnterpriseOne is good.

We have approximately 40 clients using

I rate the support from JD Edwards EnterpriseOne a four out of five.

The setup of JD Edwards EnterpriseOne difficulty depends on the module being installed by the client. The setup does not take much time but the implementation of the modules can take approximately 18 weeks to complete. If there are multiple modules being implemented it can take approximately six months.

I am a consultant that does the JD Edwards EnterpriseOne implementations.

The price of JD Edwards EnterpriseOne is high. However, every ERP solution has a high price.

I would recommend this solution to others.

I rate JD Edwards EnterpriseOne eight out of ten.

We basically provide the consulting and we just do the implementation for the clients with JD Edwards.

The accounting portion is very good for one. The financials are great. 

The integrations are good. Right now, the orchestration is very good. The new feature, which is coming as orchestration and UDO, offers different objects, which are currently in demand now. The integration with the different third-party systems is great.

The solution is easy to set up.

It's quite stable. 

They are trying to provide one-view reporting. They have the interface with Hubble and other reporting, however, we just want that to be a part of JD Edwards. They should have the reporting, the financial reports, however, right now, people use other software. They take on third-party software, like Hubble. It's an Oracle product only. They interface with JD Edwards. 

I've been working with the solution for 13 years. 

The solution is stable. There aren't bugs or glitches and it doesn't crash or freeze. 

You can scale the solution if you need to. 

For support, we have tickets. The support varies from client to client. We've got the solution from Oracle. My support is there. Once we raise the queue with Oracle we receive that feedback.

The solution is easy to set up. It's not overly complex or difficult. 

We handle installations for our clients. 

The cost is a bit expensive, however, the licensing model is good. There are some items, such as reporting, that will cost extra. Clients might need to purchase BI tools. That's where it can get expensive for them.

We are partners with Oracle.

If it's a medium or large-scale operation, I'm happy if people go for that ERP. If they want to not spend too much on their solution, like on an SAP or Oracle, this is a good option. I work for bigger clients, they have this product and they are using it for more than 12 or 15 years now and they're really happy and they're big, big, big. Therefore, the customer, if they want, could go for this product first, and if they want to go for EBS or SAP, or any other ERP, they can move over.

I'd rate the solution eight out of ten.

The most valuable feature is customization through E1 tools because Oracle JDE is neither prepared nor updated in time for Latin America localizations.

Financial reports are clearer and better aligned with business expectations.

I would like to see the following:

• Improvements in GL, AP, AR and sales and supply chain
• A standard solution for the deployment server to automate, assemble, build, and deploy packages by schedule. We need to develop or look for third party solutions. The same goes for E1 Pages.
• An easier setup

We have used this solution for five years.

We did have some stability issues. We currently use IBM WebSphere 7.1 and it sometimes does not look like it is 100% compatible.

I did not encounter any issues with scalability.

I would give technical support a rating of 7/10.

We used to work with JDE World Software Version A7.3. We changed because the business required more advanced technology functions like mobility and financial reporting.

The setup was absolutely straightforward. It was mostly on the end-user paradigm from using the Word software (green screen) to a web-based application.

Find a way to manage licenses wisely. Negotiate it as best as you can with your provider because it is very expensive.

We evaluated SAP and Oracle EBS.

Evaluate the known issues, implement the most stable tool releases, and keep your ASUs/ESUs up-to-date.

We create use cases for clients after completing deployment, development, and unit testing; the end users are given access to the solution for testing before the final handover. We typically prepare these use cases in Word or Excel format.

I have experience with various modules in JD Edwards EnterpriseOne, including finance, sales order management, procurement, manufacturing, and transportation. I'm familiar with the master tables for each module and have even developed a custom transformation model for a client. This involved creating functional specifications and building the model from scratch to meet their business needs.

Regarding supply chain management, it dramatically enhances distribution operations by streamlining processes from procurement to sales order completion. It includes understanding the entire cycle, such as entering sales orders, submitting them for end processes like shipment confirmation and invoicing, and closing orders after sales updates. Similarly, in procurement, the critical step of voucher matching ensures transaction accuracy and efficiency.

The financial management features are convenient and helpful in JD Edwards EnterpriseOne.

Implementing JD Edwards EnterpriseOne can have its challenges. For example, we faced issues like timeout exceptions in a recent integration project while pulling data from third-party systems. It required careful consideration of interface options for integration with external systems. We decided to use Orchestration, an advanced tool in JD Edwards, to overcome these challenges and ensure smooth connectivity with external systems. Challenges like these are part of the implementation process but can be effectively managed with the right tools and approach. Another area that needs enhancement is the pricing structure, making it more competitive. Additionally, focusing on more automation features would be beneficial. JD Edwards is already great for integration projects, but further improvements in these areas would make it even more appealing to clients starting ERP projects from scratch.

I have thirteen years of experience with JD Edwards EnterpriseOne. 

It's very stable and flexible across different modules like finance, document management, order management, transportation, inventory, and manufacturing.

It is a scalable solution. I would rate the product an eight out of ten.

After the development and testing phase, we move the project status to a specific phase for deployment, such as "work in progress" or another designated status based on project setup. Then, a deployment consultant takes over to handle the deployment process.

Overall, I would rate the solution a seven out of ten.