JD Edwards EnterpriseOne Reviews

• Warehouse management
• Advanced pricing
• Sales order management
• Inventory
• Procurement and subcontracting
• Bulk stock management
• Fulfillment management
• Advanced stock evaluation
• Environmental accounting and reporting

Order processing time has been reduced by 30% (KPI metric). There are many such instances that were shared by various clients in my consulting career.

I would like to see improvements in:

• Change in grade & potency on volume control (BOM) while issuing a work order
• Work order approval process
• Transportation module rate schedule flexibility
• PO receipt reversal using the EDI process
• Purchase order approval process
• Landed cost rule hierarchy definition
• Account codes that can have legacy description for reporting
• Sourcing processes with more flexibility and direct relationships with the purchase cycle
• Self-requisition process approval setup to be made available for the purchase cycle

My experience in JD Edwards has been for about 17 years. I worked with almost all the versions of JD Edwards: WorldSoft, OneWorld XE, and EnterpriseOne.

We had stability issues, but Oracle support resolved them.

I did not encounter any issues with scalability.

As a consultant, I have been involved with many successful JD Edwards implementations. The changes were for the better.

The setup was complex for the most part. In a few cases, it was simple.

The ROI is good.

In pre-sales, we used to appraise our clients on the strengths and weaknesses of the product.

It’s a good ERP system that gives users ease-of-use, the flexibility to integrate with other systems, and the ability to meet most of the KPIs.

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.

• Easy maintenance
• Fast development
• Very complete modules
• Multi-platform
• Multi-languages
• Multi-currency
• Completely configurable
• Integration with mobile applications
• Web services
• and more.

File management is easy to obtain. We do not need to spend user time to sort the information.

Gives us better work-floor management and easy integration with scanners, dispatch, etc.

EnterpriseOne has been the product that allows us to focus on our products and not on our ERP, and this means a lot.

Project management and CRM. Oracle has another solution for these areas. These functional areas of ERP are not on top of the market. You will need to purchase a specific solution.

I have used EnterpriseOne for eight years.

I did not encounter any issues with stability when the system is updated by people who do understand the road-map and the product. With EnterpriseOne, you need to have good developers to keep up the performance of the system. All companies need adjustments and developments, but they must be performed taking as a reference 'the future' of the products, retrofits, updates, etc. Then you can be updated every two years and not getting stacked into a version.

We have not really had any scalability issues.

Oracle has improved a lot. This was a pending subject I when I raised my first service request to Oracle and it took months to get an answer. Nowadays, I am getting a web conference, call, or an email after sending my request. My last issue was solved within two weeks (a tricky one). This is an 4/5 to me.

To be a great competitor, you need to be surrounded by the best employees, best products, best service and best technology and, from my point of view, Oracle is doing this very well.

EnterpriseOne can be multi-platform. That means you can have two servers on Linux, one on Windows and the last one could be an AS400. This complexity cannot be provided for by another product. My initial setup was complex, but the architecture was very complex, too. After that, I have had multiple easy setups. The best way to achieve this is to choose only one OS for your servers; otherwise it could be a nightmare.

This is a product for medium to large companies. It is not cheap, but it is not expensive. You must be able to analyze the price of maintenance, consultancy, times to develop a solution, etc. The first invoice is not the most important. This is a long time relationship (Company+ERP).

• Navision
• SAP
• OpenBravo

Ask for demo's, because maybe my vision is not your vision. The best way to know the product is to ask for small demo's.

Robust supply chain model: This greatly reduces the need for customization via code changes.

It incorporates industry specific standards thereby inculcating a process oriented work culture.

The report development tools needs more GUI interfaces and it needs to be more user centric. There is another view reporting tool that works on these guidelines.

I have been using EnterpriseOne for 18 years.

We have not had much issue with stability.

We have not had any scalability issues.

I rate technical support 4/5.

We were using something else. We switched to meet business demands.

Licensing is a bit complex, especially after it was acquired by Oracle.

We looked at SAP.

It’s a good and configurable product. Need to ensure that the business hires the right resources to implement it.

I find the following features to be most valuable:

• Technical and functional flexibility.
• Ability to change when the client needs to grow.

The improvements, I could summarize in one word: Increased control. This is true for the following areas

• Inventory
• Costs
• Finance
• Plant Maintenance
• Fixed assets
• Legal documents

In addition, its flexibility has enabled us to change its original configuration to better our business.

I would like to see the following:

• Improvement to the procedure for installing and updating the JD Edwards application.
• Classification of documents of installation of ESUs, by:
  
  • Those with special instructions.
  • Creation of tables.
  • Special instructions for "Locations".

I have used it for 22 years.

There were stability issues, and part of the job, is to offer a stable platform. We followed the following process stages:

• Evaluated.
• Tested.
• Scaled to Oracle, when required.
• Evaluated options.
• Implement in production.

There are always scalability issues. But, as a JD Edwards technician, I support the hardware sales, and I am responsible for performing Dimensioning (or "Platform Sizing") platform.

Technical support are A1; the best.

I am a specialist and use an appropriate solution according to the needs of the business.

Setup can be complex. I have worked with complicated products such as JD Edwards, considering their variety of options to configure and variety of providers involved. The secret is to have the proper documentation and support from the manufacturer and of course, constancy.

This product is like every other application, in this business area. So, in each instance, the important thing is to do the following:

• Determine the scope of the need.
• Functionality of the application.
• What the application offers to grow?
• How can I adjust its price per budget.

For example, limiting the ability to grow the application with the business, will lead to implementing a new application in the future. (This will cost more).

I have evaluated many other products, which offer the same functionality but they really had a high (price / benefit) relationship.

This application is multi-platform so select the one where your systems personnel, has more experience.

You must commit, to all departments of the company in the implementation.

It should be placed in the same area for all the consultants and their staff.

Remember, this is a project that requires:

• Document Reach.
• Commit resources.
• Follow-up of commitments.

The most valuable feature is the scope of functionality that JD Edwards covers. You could start small with something like financials and HR payroll, and you can expand it to be used for asset maintenance, distribution, manufacturing. It also comes with a development tool set so that you can add onto it fairly easily.

It's quite cost-effective in comparison with other ERPs. The rest of them are all expensive.

They could enhance the reporting tools. We've been looking for a joint venture billing solution, which is actually on the road map, so it's coming.

It's very stable. It's been around for 30 years or so. EnterpriseOne came out in the mid-90s, so that makes it over 20 years old, but they continually add new features and functionality all the time.

It's also very good. It runs on different platforms, so you can pick and choose which hardware system you would like for whatever scale of company you are. I used to work for a very large oil company that ran it for about 15,000 people. I know that there's companies larger than that, as well.

I personally haven't used it recently, but folks on my team have, and the answer is always, "It depends." If it's a fairly straightforward answer, they're very good at pointing you to wherever the technical documentation is so that you can look it up yourself again next time. If it's complex, or there's some debate on whether the item is a bug or functioning as designed, it does take quite some time to get through that, and from a customer perspective, sometimes you have to be pretty persistent.

A lot of it is the partnership. Lots of vendors are willing to sell you a product, but then aren't there when something goes wrong. It really needs to be a relationship for the long term when you're looking for the solution, as well as meeting all of the functional requirements that you have.

I would rate it a 9, because it's the best in the ERPs, as far as I'm concerned, but it's never perfect, so it will never be a 10.

Definitely give JD Edwards a chance, and make sure you talk to other JD Edwards customers before you make your decision.

The programming language is the most valuable feature for me. I'm all about flexibility so that I can respond to what my users need. The fact that we have the capabilities to do our own customizations is huge. The programming language is certainly understandable and manageable for someone at my level. I'm not a programmer all the time but I make mods to the software to support the needs of the business. The interface for making the mods and things like that is straightforward enough and it works. That's very handy.

We're a very small company, so having one product that can run basically almost every aspect of our business is very valuable. There's one thing to manage, one conference to attend. We run everything. We don't have very many third-party apps bolted on.

There's also a time-savings element, and a frustration with the data interface. I've been in the industry for a long time and came before JD Edwards from a situation where we had a number of so-called best-of-breed. Then as IT, you're constantly moving data back and forth and that lends its own set of complications and problems and disconnects. JD Edwards has mitigated a lot of that.

I have found a couple of bugs in my career, but more often it's just a missing functionality or inconsistent interface. I think their Transportation Management module, that's one of the bolt-ons that we have, is very limited. That would probably be my main complaint. We had to buy another solution to address that.

I'm part of the TechSig and I thought it was kind of funny that the top thing on our TechSig list is to bypass the OK button because every time you run a report, it comes up to the "do you want to change your printer?" screen and a user must click OK. It is one of those silly things and it's just an extra click, but it's unnecessary. Yet, it's been there for 20 years probably! That's just a small example.

We implemented it in 2001.

We've had no real issues with deployment.

I would have to say no, definitely no major issues with stability.

As far as scalability goes, we're a very small company, but we were able to implement the portions of the program that we needed. Other than that okay button for the printing, we're able to bypass features that we don't need because we're not a big company. And because of the way it's designed with processing options and version and things like that, we can tailor it for our business needs. As we've grown, we've added new functionalities and we've done a few mods. 

So it's been growing with us. I think we have a long ways to go. We're still a small company and we were probably the smallest customer at the time when we implemented. We're probably not anymore, but we're still very small as far as the arena, so we have a long ways to go before we outgrow it.

At the time, JD Edwards had completely rewritten their software, and I understand that now. I hadn't been exposed to it before. It was very cohesive at the time, I thought, for software. Sometimes you use software and you can almost tell, "oh, this module was bolted on and re-patched, but it clearly was written by a different group with a different focus." Whereas, JD Edwards at the time was all written fairly together with a new vision. I would say that the implementation was pretty good.

It's definitely fulfilled most of our business needs. The flexibility is really number one up there. I have only worked a little bit with other ERP systems, such as SAP, and JD Edwards surpasses that.

When you're comparing JD Edwards to any other tool, look at the flexibility. Look at the capabilities to change it, for it to grow with you as a company, for it to support business needs that you don't need now, but you're going to need in the future. That's very important.

The most valuable feature for us is its robustness, especially coming from the system we had before because it can do so many more things. For example, we can drill down into the data a lot more. That's a huge advantage for us.

I'm coming out of the Canadian office, and the overall system is hosted out of our US office, which is considerably larger. The Canadian office is a small operation, but we have a system that a company of our size should not be able to afford. We're getting a lot more toys, bells, whistles and stuff like that that we would not otherwise be able to afford. It's helped us tremendously that JD Edwards allows remote access from a location away from where it's hosted.

It's got a steep learning curve. There's a lot of terminology, a lot of extra setup stuff that seems a little complicated and a little bit of extra work that doesn't always seem very necessary. For somebody who understands it a little better, they're going to know why all that extra work was there, but I'm not.

There seemed to be screen after screen of data and attributes. I guess they all have a purpose, but we haven't found what that is because we don't necessarily mine the data or back any of it out. We just don't feel like it's worth the effort right now.

It's rock solid. We've had no issues with instability.

It's been able to scale for our needs and we've had no issues with scaling.

We were previously using Microsoft Dynamics GP and it was not as robust. It was a great place to put data into but a little hard to get data out of. It's much easier to get data out with JD Edwards.

The initial setup took about six to eight months, so it was accelerated. It was essentially all my time for about six or eight months, but it came in on time, on budget, etc., so obviously a lot of thanks to our US office for all their help in getting it done. They've used it for many, many years, so it was just adding a new branch into the software and getting us up to speed. It could have been complex, but because our US office was already using it, it was much simpler.

It's forced us to adhere to business processes, where we were a little loose with our previous ERP. It's a little bit more rigid, and in my opinion, that's not a bad thing. It might seem scary at first, but it's not so bad. Not a lot of other advice to give, but it was a good project for us and it's helped our business. It's great from that perspective.