Have You Outgrown Your JDE Reporting?

3 signs your business needs more than reports and dashboards.

Hosted by John Brooks, one of the first employees at JD Edwards Europe and 30 years in JDE reporting and analytics.

Your JD Edwards reporting tool was the right call when you bought it. JDE was the system, the reports came out of the system, and that was the job.

Answer yes to any of these and it's worth 30 minutes of your time:

• Your business now runs on more than just JD Edwards, and no single report covers all of it
• Getting to an answer still involves an extract and some gymnastics in a spreadsheet
• It takes days between spotting a problem in a report and doing something about it

Join John as he walks through the three reasons JDE customers reach this point, what he's seen teams try in response, and why the reports that still work for you can stay exactly where they are.

What you'll take away

• Why business processes that run across systems are the point at which single-system reporting stops working
• What happens when one tool can't serve finance, analysts and management at once, and what fills the gap
• Why knowing what happened is no longer the hard part, and what closing the gap between problem and action actually requires
• A clear line between what your current reporting should keep doing and what it was never built to do

Who should attend

Finance directors, finance managers, controllers and FP&A who work with JD Edwards, plus the reporting and BI people who build for them. Any reporting or BI tool, on-premise or cloud.

Your host

John Brooks was one of the first employees at JD Edwards Europe in the early 1990s and has spent 30 years in JDE reporting and analytics with customers across North America, the UK and Europe. He has seen most reporting projects in this space succeed, fail, and get quietly replaced by a spreadsheet.