As with any ERP, regular checkups ensure that your system is running optimally. And, as you know, when regular checkups are not performed, chances are you’re going to run into instability and integrity issues.
At Spinnaker Support, we love squeezing out every last drop of ROI we can — and we like to think we’ve perfected the art of optimizing JD Edwards software. Over the years, we’ve developed a process that we use to support JD Edwards users, a comprehensive checklist and scheduled cadence for making JD Edwards’ systems run faster, more effectively, and more stably. As our JDE community seems to be receiving less support than ever before, we’ve decided to share some of these insights for the first time, in the hopes of helping you optimize your instance of the software we all love so much.
Have you ever asked yourself how often you need to perform full vs. update packages? Or how often? We’ve worked with customers that have never built a full package before — and when they have a critical fix that needs to be updated, it becomes a nightmare to get that “build of record” completed.
Check your security setup frequently to avoid vulnerabilities caused by segregations of duties. Internal breaches of your data are not fun and, as we all know, can be catastrophic.
Have you ever booked an order based on item availability, only to learn it was out of stock? If you haven’t conducted a cycle count lately, it’s time to add one to the top of your list. Doing so will correct the available inventory in the system (Inventory Adjustments), so that you’ll know well in advance if you’re running low on any items.
Have you ever come into the office and noticed that all of your inventory was priced incorrectly? There are features in JD Edwards that let you set expiration dates for inventory, and if those aren’t maintained, they can cause huge headaches. So double check that those dates have been entered — and that they’re correct.
Do you run any of the JDE Integrity Reports? These are critical to ensuring that your AP balances to the GL, that your Bill of Materials (BOM) is correct, and so forth. They’re functions that follow JD Edwards’ standards. Run them in Proof mode to understand if there are issues or, if necessary, run them in Final mode to correct them.
When it comes to keeping an ERP, like JD Edwards, humming, these suggestions are just the tip of the iceberg. And if it feels like it takes a village to keep up with regular checkups, remember we’re on your team and here to help — as much or as little as you need us to. For even more tips and tricks check out this infographic.