JD Edwards EnterpriseOne Reviews

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

My role for this product, JD Edwards EnterpriseOne, is as a technical developer. I use almost all of the technical tools, including JDeveloper, which is a tool that we use for development, specifically web services development using Java programming. At the moment, JDeveloper is a product within Oracle that is integrated with our JD Edwards EnterpriseOne product for developing business services.

We all use JD Edwards EnterpriseOnes' core technical products, including the Universal Batch Engine, which we use for report development. Another tool is used for interactive application development.

And the name-giving tools and business functions that we create based on the needs. So those are the types of business functions that we create with JD name-giving tool programming, and you can see the functions that we use in C+, C++ for Java, and JD Edwards name-giving tool programming languages. When it comes to databases, I have experience in both executing and writing SQL.

I like all of the progress Oracle has made with JD Edwards EnterpriseOne. They have introduced a new tool, Orchestrator, in the most recent version or the most recent separated version of JD Edwards EnterpriseOne. It is a replica or a replacement for the development of business services, in my opinion. We use the Orchestrator tool to develop the orchestration processes, which we then use for data migration from the Legacy system to JD Edwards EnterpriseOne, and vice versa if you're using that tool.

I like the terminologist, which I would say is a must-have feature that was missing when I was using OneWorld. Prior to JD Edwards EnterpriseOne, there was OneWorld, and there were no requesting tokens, holding tokens, or resuming the object for myself. Unless I give them permission, no one else can check it out and start working on it to write code. As a result, that is an enhancement to the OneWorld in JD Edwards EnterpriseOne.

I have worked with various types of objects. I have worked with almost all types of objects. I was given an excellent opportunity to work on a wide range of JD Edwards EnterpriseOne objects.

The 1V reporting is straightforward and simple to use. Creating 1V reports does not require any technical knowledge. This is quite interesting, and I know how to work on it; it is not a part of improvement, and I am aware of it. Aside from that, I haven't worked on any JD Edwards EnterpriseOne E1 pages.

I'm really looking forward to some opportunities to get some work done on it so that I can learn JD Edwards EnterpriseOne E1 pages and gain some experience.

They have all of the good models, such as finance, supply chain, recruitment, HRMS, accounts receivable, and payable.

Despite the fact that it is an old technology, we still have good projects and good work. It's an excellent technological product that any client should consider.

Oracle has introduced Orchestrator as a new technical tool in the most recent upgraded version.

I didn't get much experience working on this Orchestrator, but I did watch some tutorials and do some exercises on my own. And, to be honest, I don't have such an environment for orchestration development. That is something I need to look into, study, and have peace of mind about. Aside from that, there are some technical tools introduced by Oracle that I have not worked on. I have a lot of 1V reporting. 1V reporting is a type of interactive reporting tool that Oracle has introduced in JD Edwards EnterpriseOne.

In a nutshell, Orchestrator is the primary technical tool on which I would like to focus my efforts.

The tools we use for data transformation from Legacy to JD Edwards EnterpriseOne are inbound and outbound from JD Edwards EnterpriseOne. Most of us as technical people believe that the suite processors or EDI processors introduced by JD Edwards EnterpriseOne and Oracle are more reliable when compared to the most advanced tools for business development orchestration, such as JDeveloper. Because the objective of using it is the same, it's for data transformation.

We believe that the older features or tools provided by Oracle are more reliable than the new ones. If you ask me, I would prefer to stick with the older tools that we use for data transformation because they are more reliable.

The implementation phase is critical. If that is done correctly, it will be a 10 out of 10.
That is a very important part, as it is the first stage when you buy this product. If the product has been successfully implemented, you will receive a score of 10 out of 10. The implementation procedure could be simplified. Then there's customization, product customization, as well as customization for your business environment. That can be counted separately, not all at once.

I have been working with JD Edwards EnterpriseOne for more than ten years.

We are using the latest version.

We have not deployed it using the cloud, because the project that I have been working with does not yet use the cloud.

JD Edwards EnterpriseOne is a stable, and reliable product.

My current project is a US project, and I can tell you that we have a team of about 250 people. 250 people, but not all of them in JD Edwards EnterpriseOne. We have nearly 50 people in different teams at JD Edwards EnterpriseOne.

There are many more in this project. I'm not sure if there are any other projects that are using this product. But there are several projects, but I'm only going to tell you about my current project.

JD EnterpriseOne's product is simple to use and understand. When it comes to ERP technology, there are many models, all of them, that have been widely used in the United States, first and foremost, and it is developed are with the needs of the US clients in mind.

Oracle does offer technical support. They do provide technical assistance. Oracle is a company that offers technical support.

We do obtain licenses from Oracle. For example, I work for a client who provides us with access to Oracle support and licenses. And whenever we get stuck somewhere, whether it's a problem with a JD Edwards EnterpriseOne product, a technical problem, a functional problem, or anything else, we just write a query on the Oracle support portal. There is an Oracle support portal where we can submit our questions, and they respond within two to three working days.

We've been writing them, our queries, directly to Oracle support, and they do respond, and they respond as quickly as they can.

I was not involved in the deployment process. I do work on product development. I'm the head of JDeveloper.

Deployment of the product is handled by a different department known as the CNC department. CNC consultants are more aware of it. 

We have separate teams, for the product deployment. 

There are some maintenance activities that our CNC team has been doing for a long time. I'll give you an example, of maintenance activities. The client may be using a specific product version, and there may be some ESUs or stars, which we, or a CNC consultant, may apply to that product upon function approval.

Those ESUs will sort when there is consolidation or when there is a package that includes some of the additional functionality for any particular object that is not present in the version that the client has been using. In that case, we identify the ESUs and stars to which we must apply in specific objects. Accordingly, we accept those functions and approvals. We, as technical personnel, reviewed them, the code that ESU and the stars requested, and upon function approval, the CMC consultants applied on those objects, the list of objects wherever it is required. This is the type of maintenance that CNC workers perform on a regular basis.

In terms of price, it is not on the high end. When compared to the SAP product, it is significantly less expensive.

If you buy the product and then get support from Oracle directly, they will charge you.

It is conditional. If you buy some additional licenses from them to use products, I believe they will give you access to that when you buy a product. That is present, of course, but if you require something additional from them, an addition to the product, there are some sub-products there you will require in the future, so they will charge for that or any valid services for some years or some time period, but those charges are also very minimal.

Oracle is my company's partner, and JD is an Oracle product. It's a partner to my company, and it's a client partner, but they have a license to a product version, and they also have Oracle support. There is an Oracle support portal; we ask a question, the client asks a question, and the client asks another question. We have had discussions with Oracle about this product. If you purchase this product, you will receive Oracle support for the initial days.

When you buy JD Edwards products, the first step that you will need is JD Edwards implementation. For each model that you purchase, you will require the services of some functional experts. When you purchase it as a product, you will be purchasing some models from them. You will require a financial model as well as supply chain models. For each model, you will undoubtedly require supply chain, finance, and consulting. They will be responsible for the product's implementation.

I would definitely recommend this solution because I have had a great experience working with this product as a developer.

I would rate JD Edwards EnterpriseOne an eight out of ten.

Every single module has some particular value depending on who the type of user is. For example, the Address Book is a master data feature. It offers a lot of different types of credits and collections. It allows you to hone in on the credit holds, allows you to be specific if you need some customer statements, or provides reminder letters. It allows you different cross-language functionality, which we need across the different countries that we're in. It allows you to have different payment terms. It has this Address Book by line of business, so that if you had multiple business units, you could hone in on each credit and collection based upon each business unit specific, while using the same, single customer.

The product is pretty spot on. The nicest feature that I love about Address Book, and just JD Edwards in general, is that it always gives you an inquiry screen before you actually add an order entry, and it always allows you. But before you delete something, it always questions you, "Are you sure you really want to do this?" No matter what version you're in, it always asks you that -- tried and true.

There's a lot of patches and bugs that come along when you're doing your upgrade that were not found or hidden during the user-acceptance testing. So now there's a lot of base lines that have to be applied, so that's rather disappointing.

We've been on JD Edwards for a while now. It was on our previous platform, and it was used by most of our regions, so this was decided back in 2008.

We've had no issues with deployment.

I just went live with an upgrade, so it's not stable. We have tons of disconnects. We just went up on the Oracle Cloud, and it has horrendous stability, with internet browser issues, compatibility issues, and we're trying to determine if it is on the network side of my local network or is it on the Oracle side.

We're still investigating whether it will scale. We've only been live for six weeks, so it's a critical product that's being highly reviewed. But we're taking it one step at a time.

If it's critical and we keep raising it, as long as there's a ticket, technical support will respond to us. Even if we go to the top of Oracle, they still need a ticket. Then they'll double-check your work, and so they really want it to be specific before they'll actually proceed with anything else.

The initial setup is complex because you're going up on the cloud. Coming from where we were before to where we are now took us about two-and-a-half years.

I'd encourage others to use it, but I've been using JD Edwards for a very long time. Others would choose an SAP product over this because they over a full-blown solution. If your data isn't aligned and you don't have all the garbage taken out, you're going to end up with the same bad system you had before you implemented it.

This is a stable and solid product. 

We've lost the second and third layer of support to a company that specializes in JD Edwards, so they do all the changes for us. 

I've been using this solution for 12 years. 

We have some small issues but the stability is fine. 

The scalability is good. 

We have a monthly SOA meeting. Tech support is always busy with tickets, incidents, changes and service requests.

The initial setup is somewhere between straightforward and complex. It was not straightforward, but it was done a while ago and would likely be simpler these days. We used a third party for our implementation 12 years ago. We now have 600 users. 

We've seen a return on our investment. 

The licensing costs are reasonable. 

I recommend this solution and rate it 10 out of 10. 

EnterpriseOne's integration could be improved.

I've been using EnterpriseOne for more than twenty years.

EnterpriseOne is stable and can be customized according to customer requirements. 

EnterpriseOne is scalable for large enterprises.

EnterpriseOne is cost-effective for large enterprises.

I wouldn't recommend EnterpriseOne for small enterprises because the cost-benefit doesn't work out. But for large enterprises, it's a very good and cost-effective solution that's competitive with other products like SAP. I would rate EnterpriseOne nine out of ten.

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.

Our primary use case is for accounting, budgeting, project costs, and all cost-related financial purposes.

I have found their budgeting and financial inquiries are easy to work with. It is easy to inquire about any account in our company. They are good with financial and accounting platforms.

From my perspective sometimes it is glitchy.  We have to close the application and restart the computer. It does not submit the inquiry as requested. 

I have been working with JD Edwards EnterpriseOne for the past nine months.

I have found the stability matches our current expectations.

We are having a few issues with scalability bringing other individuals into the same purchase order. This is something that needs to be improved.

It is straightforward. I learned it in a week to ten days and I am doing the purchasing orders as well.

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