JD Edwards EnterpriseOne Reviews

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.

JD Edwards EnterpriseOne is an ERP solution for our customer's business processes comprising of manufacturing, financials, procurement, inventory, et cetera.

JD Edwards EnterpriseOne has improved within all the solutions and there have been a lot of investments by Oracle in these solutions. Most of the functionalities, and business requirements, are available for the system in the solution and there have been enhancements to the processes, UI, and tools, which have been done on a regular basis.

The inbuilt BI user experience and enhanced UI analytics, are very good. These are key features I love about the solution. It is more user-friendly with functionalities continually updating and there's less technical dependency. Rather than hiring a technical person to explain everything or doing the development for you, anyone can do it on their own without any technical help, such as the end-users.

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

JD Edwards EnterpriseOne is highly stable.

JD Edwards EnterpriseOne is best suited for small and medium business enterprises. There are multiple features in the solution that customers look for and this is why it has been a good solution for the past 30 to 35 years in the market.

JD Edwards EnterpriseOne is a scalable solution.

If there's any problem, such as a bug in the system, you have the solution on the knowledge garden, on the Oracle website.

I am an engineer for the last 18 years and I have not seen any other solution from the market that is better. I have seen some comparable solutions, that might be on par with the JD Edwards EnterpriseOne. However, JD Edwards EnterpriseOne is being rated as the tier one ERP in the industry for SMBs.

The initial setup of JD Edwards EnterpriseOne is straightforward. However, it could improve.

I rate the setup of JD Edwards EnterpriseOne a three out of five.

The maintenance of JD Edwards EnterpriseOne is very low. There can be support after the implementation, but I've seen a lot of customers using the solution without the support. They are able to maintain the solution on their own.

My advice to others is JD Edwards EnterpriseOne is excellent. It has multiple features and business processes of the industry, especially the manufacturing industry, out of the box. There are fewer customizations required. It can meet, 90 to 95 percent of the standard business processes' out-of-box functionality. It is a very good solution from a business point of view.

I rate JD Edwards EnterpriseOne a nine 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.

Our parent company is heavily into engineering, manufacturing, and life sciences. Most of our customers using JD Edwards EnterpriseOne is a mixture of manufacturing and life sciences. They are heavy on most of the modules, such as sales, distribution, manufacturing, and finance.

This solution can be deployed on the cloud or on-premise.

The most valuable features of JD Edwards EnterpriseOne are the flexibility of the configuration, it is highly configurable. It is not rigid as other solutions, such as SAP. They have recently added a custom workflow approach and approval workflows.

Treasury management is typically used in forex, loans, trade management and property management is not available. The solution could improve if they added them. 

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

The stability of JD Edwards EnterpriseOne on-premise could have some latency at times, but not always. When it comes to bulk data it might be a problem from the customer side when they don't have adequate provision for RAM or hardware.

The latency could be 5 to 10 percent of customers who are large companies, and data volume is a lot, that's the only issue that I have seen. JD Edwards EnterpriseOne has improved because of the additional tools for reporting, when we're reporting, the issue has been resolved. Otherwise, typical the PDF where we used to do a lot of customization for reports is now very good.

The support from Oracle is quite good. In the last two or three years, the entire focus from Oracle is towards the cloud. Though a good level of support is available, they are more focused on the cloud, while a little bit less attention to all the other solutions, such as on-premise applications. For example, EBS or JD Edwards EnterpriseOne. Since it was an acquired solution from Oracle, some distance or gap has been formed.

JD Edwards EnterpriseOne's initial setup is very easy. We have created some migration tools for master and transactional data in an automated way.

JD Edwards EnterpriseOne has a lot of value for the money. The implementation cost and license cost are quite reasonable compared to other solutions, such as Oracle EBS or SAP.

My advice to others is they should know the way the world has changed post-pandemic. They should think about cloud solutions so they aren't dependent on hosting it on their premise. Somebody has to be in person available to support this solution.

I rate JD Edwards EnterpriseOne a nine out of ten.

I've been working as a JD Edwards consultant for four companies we did projects for all four in the food markets. With all four of them, two times it was an implementation project, and two times it was management and book fixing and that kind of thing.

For me, it always was production and logistics.

The strongest functionality of JD Edwards is the ability to model, in the production that it is, model the production process. If I were to model the bill of materials and production routing, then that's one of the strongest parts of JD Edwards.

The initial setup is not difficult.

The solution can scale.

The stability is good.

There's a large amount of online documentation that makes troubleshooting easy.

It's all in the way that end-users are able to make reports. The more that's flexible, the better it is. In JD Edwards, it's the reports that you get standard. Then the user has to deal with that and if he's not satisfied with it, well, then that's tough luck, so to say. The reporting has to be flexible or it will turn the end-user off.

I'm not sure if there are any missing features. The last thing we worked with was Orchestrator and that was something that could be of great value. Orchestrator will prove to be the solution for many problems. At the moment, there isn't something that I would say that we're all waiting for it. On the other hand, they should make more noise on the Orchestrator, as there are not many people who know what it is and what it can do, and what it can mean for new implementations, or old ones.

I've used the solution for the past five or six years.

The solution is quite stable. 

The product can scale. If you are too big or too small for the solution, if you are something like Coca-Cola worldwide, you would not use JD Edwards solely for all activities. They're too big. If you are a company of, let's say 10 employees, then you're too small. However, otherwise, if you choose right, it's very easy to set it up and it's scalable. If you are going from, let's say 200 to 500 employees, no problem. If you have two sites and you're growing to five production sites, also no problem.

The solution is part of the Oracle family and I always used the information that I could find in Oracle Metalink. For JD Edwards it's also there this. The support information that you can find on the Oracle sites, the support sites, it's huge. If I have a problem, then in 80% of the cases, I can find a solution somewhere on the support side of Oracle before I have to lock a service request with the Oracle support unit. There's a lot of information that you can find on your own. Therefore, the support is quite good.

At this moment, I'm on my second project for Oracle E-Business Suite and then the project module.

The implementation process is pretty simple. I can relate it to the E-Business Suite, as I've also a long-term experience in E-Business Suite. JD Edwards is more simple than the E-Business Suite to set up and make work. On the other hand, if you have a very large operation and your operation is multi-language and multicurrency, then the E-Business Suite is better as it has more opportunities to set it up for multicurrency and multi-language. That said, in daily practice, JD Edwards is reasonably easy to set it up.

In terms of maintenance, for the application management team, for a normal instance of JD Edwards, then you could expect something like, let's say 500 users. Then there would be one or two application managers that are managing an application of that size - and perhaps one database manager.

The ROI is not my business. I can't speak to if we have seen any.

I barely know what the license costs are. They are in the range of $1,000 per end-user per year or something like that. A lot of the bigger ERP solutions, like E-Business Suite or SAP, are all the same or similar in terms of pricing. 

We are a system integrator.

I'd advise new users if you are using JD Edwards or if you are using Oracle E-Business Suite, just go on with it and stay using it for a long time. It will be supported until, the last I heard, 2030, by Oracle and perhaps even longer. However, if you are thinking about implementing an ERP solution that's new, from the scratch, I would consider one of the cloud solutions. Then you could look to an Oracle Cloud product or you can look to Salesforce - whatever suits your business. I would go for the cloud products and not for the, well, let's say old school, on-premise products.

I would rate the solution at an eight out of ten.

It is a good product for managing the business. We can manage supply chain and distribution, manufacturing, finance, etc.

I'm a consultant. I work for different clients, and I have worked on different versions, such as XP, 8.12, 9.1, and 9.2.

The good thing about it is that it is very customizable. We can modify it the way we want.

With the new versions, it has become very user-friendly. We have integration with mobiles, and we have cloud-based solutions. There are a lot of things that can be done by front-end users without technical knowledge. They can create reports without having to do any coding, and it's very good now.

If they can research and make the installation part easier or more user-friendly, it would be nice.

I have been using this solution for about 10 years. 

It is very stable.

It is very scalable. The client I'm currently working with has about a thousand users, but I've worked with other clients with a lot more users, such as about 5,000 or so, across different geographies.

There is currently no plan to increase its usage.

It is pretty good, but when we contact Oracle support, we have to first do our homework. They need several things before they look into any issues. 

Oracle provides support for standard things. They support the standard or vanilla product. If we have a lot of customizations, it gets tricky. We are responsible for the things we change, and they are mostly responsible for the standard part. So, the more customizations we have, the trickier it gets.

I used a product from Oracle as a CRM tool, but I haven't used any other ERP. I've only been using JD Edwards.

It is not very straightforward. You need a very technical person to do that or assist you. The installation is okay, but when you're implementing, you have to do adjustments to make it work for your business. So, it does require a little bit of technical expertise. You might need help from Oracle as well. 

The installation takes a few days, but the implementation can take a few months.

In terms of maintenance, in the current team that I'm working with, there are about 25 to 30 people for IT support for 1,000 users.

I find it really good. I have limited exposure to the product, and from my point of view, it is very customizable. It is very good because we can modify the way we want. It is stable as long as we are following Oracle guidelines.

I would definitely recommend it to others. I love it. With the new versions, it has become very good. 

I would rate it a nine out of 10.

We use this solution for the financial model. We use it for accounts receivable, with payments, accounting, fixed assets, inventory, and purchasing.

We are a quite large B2B company. The solution is deployed on-premise.

I think it is strong in sales, inventory, and pricing.

Something that could be included is a supply chain management system. That's what we're looking for.

I have been using this solution for 25 years.

Stability is good.

Scalability is good. We can do a lot without any problems. We have about 600 people using this solution.

Setup is simple. For deployment, we used eight people to run the software.

We used both consultants and resellers for deployment.

The licensing costs are on a yearly basis, and there are no additional costs.

I would rate this solution 10 out of 10.

We are using the latest version. 

We use the solution for operational requirements, including procurement, inventory and management. As we are advocates of contraction, we cover almost everything within the system. 

We found that the system was unable to address many of our concerns, especially when it comes to project management. We actually found it to be quite hard to use and to lack user-friendliness, which is the reason we decided to move. 

While the overall function for providing coverage is good, the way the system works turned out to be a bit difficult. Efficiency was an issue, as well as user-friendliness. Something which would take five minutes in a standard ERP, takes 10 with the solution. The method of handling the entire transactions should be greatly simplified.

When it comes to scalability, a much larger team is needed to handle the system than would otherwise be the case with an SAP solution. 

The solution is really expensive. 

If used properly, one can see a return on his investment. If not, it will cost a person a lot of money. It's that simple. 

I have worked with technical support and it actually involves two types of consultants, one technical and the other functional. The technical requirements, such as coding, which comprise the backend, should have more people involved for delivering what is needed.

We have been using JD Edwards EnterpriseOne in excess of four to five years. 

The solution is stable.

When it comes to scalability, a much larger team is needed to handle the system than would otherwise be the case with an SAP solution.

The solution is used extensively in our organization. 

I have worked with technical support and it actually involves two types of consultants, one technical and the other functional. The technical requirements, such as coding, which comprise the backend, should have more people involved for delivering what is needed. 

We have plans to move to another solution. 

Much cost-consuming staff is needed for deployment and maintenance. 

If used properly, one can see a return on his investment. If not, it will cost a person a lot of money. It's that simple.

The solution is really expensive.

When it comes to scalability, a much larger team is needed to handle the system than would otherwise be the case with an SAP solution.

The deployment is handled through a third party; in which we have a team of consultants. They handle everything, from the setup, to the implementation, to the training. 

My advice to others is that they use what is available in the system and not attempt to exceed its capacity. 

I rate JD Edwards EnterpriseOne as a five out of ten. 

I help implement it, set it up, and support it. It is really good for clients who use it for financials, supply chain, payroll, human resources, and manufacturing, so almost everything.

I use multiple versions of it, such as 9.0, 9.1, and 9.2, because I support many customers. In terms of deployment, the customers have all kinds of deployments such as traditional data centers, public cloud, and private cloud.

It brings operational efficiency by integrating different processes within the organization into one system. It also brings best practices of the industry into your processes. You can configure the processes within the software in a way that they align with the best practices that exist in the industry.

It is highly configurable. You have a choice in terms of how you want to run it. You can run it in your own data center, in a private cloud, or in a public cloud. The choice is really up to the customer.

They have been improving it every day, but it could have more automation. 

I have been working with this solution for 19 years. 

It is pretty stable now. There were earlier releases that weren't as stable, but it is becoming more and more stable every day.

It can scale if architected well. It is highly configurable, and it is dependent on how a customer chooses to set it up. It is built to scale for 5,000 users. It is not really a limit, but 5,000 or less is where it performs well.

Their technical support is good.

Our clients have used legacy systems, homegrown systems, and other ERP solutions.

It is complex. In terms of deployment, you can get it all up and running within a month, but its implementation is a long process. It depends on the size of the organization and the number of processes they're trying to implement. So, implementations can take anywhere from six months to two years, depending on how big the organization is.

The number of staff required for deployment and maintenance depends on the implementation. In terms of their roles, there are system admin and developers. Then there are application consultants or business analysts. They are the people who have expertise in a particular domain such as financials, supply chain, or manufacturing. So, it depends on the different processes that you are going to set up in JD Edwards. You could have an organization that is only implementing financials, and in that case, you only need one financial SME, but if you have an organization that is going to implement financials, manufacturing, and supply chain, you're going to need SMEs for these areas.

It depends on the number of users and the modules that you want to buy. It is licensed on a perpetual license basis. You buy the license costs upfront, and then there is maintenance for support that you pay every year, which is typically about 20%.

The expense also depends on an organization's IT strategy, such as whether they're going to support the system internally or whether they're going to get an external vendor like my company to help support it.

Make sure that you have the right strategy on whether you're going to support it internally or you're going to hire an external vendor for it. It needs a specialized skill set; it is not something that anyone can just support.

I would rate it an eight out of 10. This is based on what I've heard from my customers and people who use other solutions. I haven't worked with too many other products to give a fair comparison.

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.