In a recent trip to a hardware store, my son asked me why there are so many different types of screwdrivers – regular, Phillips, hex, etc. This led to a discussion around the fact that different jobs require different tools, and even though you may be able to use a regular screwdriver on a Phillips head screw, the job would be harder and would take longer to complete. He compared this to a time when he tried to do his math homework with a crayon instead of a pencil. He completed the homework, but his teacher could not understand half of it.
What does that have to do with JD Edwards and analytics? Well….
JD Edwards, like many other ERP tools, is great at what it is designed to do: it gives companies of all sizes – across many industries – an integrated set of applications that spans all aspects of the business, including sales, resource planning, supply chain, financials, and others. But analyzing the data generated in JDE can be pricy, inconvenient, and it may take a long time. This deficit is actually the result of one of JDE’s greatest strengths: its flexible architecture that allows organizations to customize their deployments for their business needs. This flexibility means reporting and analytics solutions must be customized as well, and that’s where the price and time come in.
The traditional resolution for this problem is to build a data warehouse that allows for the integration of multiple sources into a dimensional model geared towards analytics and reporting. This solution, however, has its own implications. The process that populates the data warehouse (extract, transform and load or ETL for short) can take several hours to complete, making it impossible for the business to have access to near real-time data. Also, data warehouses can take months, if not years to deploy, requiring heavy IT involvement and continuous maintenance, driving the total cost of ownership (TCO) up.
By now you may be thinking “But I also heard of analytics tools that can connect directly to my JDE database without a data warehouse. What about those?” Good thought! But it is flawed. ERP database schemas are designed for fast insert and update of records as opposed to analysis and reporting. This causes performance issues when you need to go through multiple tables and joins – potentially waiting minutes, if not hours – just to find out how many products you sold last week. Additionally, this type of querying can put an extreme amount of stress on your JDE database, slowing down the processes that are required to keep your business running.
As a result, most organizations end up spending more money and time than anticipated to puzzle together a high-maintenance solution with multiple tools just to generate even the most basic reports.
So… what is the solution? Click here for a webinar that addresses these issues using a solution co-developed with our partner Incorta’s groundbreaking analytics to solve all the issues found in legacy operational reporting and traditional enterprise business intelligence tools and see a demonstration of Ranzal’s new, Incorta-powered templates for analyzing JDE data, all of which are available out-of-the-box.
This webinar offers great understanding of a quick-deployment solution that will address your organization’s specific needs and customizations while eliminating the cost and frustration associated with months and years of development time – using the power of Incorta and Edgewater Ranzal’s years of experience with deploying reporting solutions for JDE organizations.