ERP analytics: from report factory to decision engine

Every ERP analytics program starts the same way: a go-live, then a request for "just a few more reports," then a hundred more. Nobody assigns an owner to the data quality behind those reports, because assigning an owner feels like a delay and building the report feels like progress.

The pattern shows up early and it shows up late. Early, it looks like duplicate vendor records and three different definitions of "active employee." Late, it's an executive asking why the AI agent gave a different headcount than last week's dashboard, and nobody in the room can answer.

Under the marketing, Workday, Oracle and SAP run close to the same architecture: source systems, a blending or preparation layer, a semantic layer that defines what the numbers mean, and a delivery layer for reports and dashboards. There's now a fifth layer that reads the modeled data and acts on it directly.

The vendors differ in how they package the blending and preparation work.

The clearest guidance on Prism implementation is also the least glamorous: build governance first. Define security roles, access controls, ownership and publishing workflows before you expand usage, because Prism's value scales with the governance model underneath it.

The same discipline applies outside Workday. A recurring finding in Oracle Fusion Data Intelligence implementations is that success comes down to sequencing. Don't start until clean, complete data is available in the source system. And don't force the tool on people who don't yet feel the reporting pain it solves.

Within about 18 months of each other, all three major ERP vendors converged on the same idea: zero-copy access to external data platforms instead of moving everything into one place.

The shared lesson: the platform that wins governs its data well enough that copying it becomes unnecessary.

Most ERP analytics programs skip the semantic layer. Gartner's March 2026 top predictions say that by 2030, universal semantic layers will be treated as critical infrastructure, alongside data platforms and cybersecurity, specifically to keep AI systems from inheriting and amplifying "multiple versions of the truth."

Inside Oracle's ecosystem the confusion has a specific name: OTBI versus BI Publisher versus OAC versus FDI. They're four tools with different jobs, and more often than not they get picked without a plan.

Employee-level BI adoption was around 19% in 1998, 22% in 2009 and 35% in 2019, per Gartner, then back down to 25% in a 2022 BARC and Eckerson Group study. One explanation: analytics tools are built for analysts, and analysts are roughly a quarter of any workforce, so a tool built for that quarter caps out around that quarter.

The predictable side effect is shadow IT. As of a 2023 update, roughly 60% of U.S. businesses were still running meaningful parts of their operation through Excel.

Migrations put the sprawl in a single number, because every legacy report has to be triaged at once. On one real program, 400 legacy reports came into scope for rationalization. Ninety were rebuilt because someone could show a real, current use. The rest were consolidated, replaced by self-service or simply retired.

Most mature programs need both, sequenced correctly. The in-suite side and the dedicated platform stand on the same foundation: governance plus the semantic layer.

Prosci's own research puts a hard number on this. Projects with extremely effective sponsors are 79% likely to meet their objectives. With extremely ineffective sponsors, that drops to 27%. Microsoft's internal BI platform is a documented case: after adopting the Prosci ADKAR model for its reporting rollout, Microsoft reported a 450% increase in adoption.

Weak sponsorship shows up as a symptom long before anyone calls it the root cause. The symptom is a decision backlog: questions raised in a steering meeting that never get formally closed. Every decision that sits open past 60 days starts acting like debt, accruing interest in the form of rework and rebuilt trust.

Every major ERP vendor now ships an AI layer that sits directly on top of the governed data foundation. Workday positions Prism explicitly as the governed data foundation feeding Workday Illuminate agents. Oracle's answer is AI Agent Studio for Fusion Applications, a no-cost development platform for building and orchestrating agents. SAP's Joule is moving the same direction inside SAP Analytics Cloud.

The guidance that holds up across all three ecosystems is the same: start with one or two high-value use cases, prove the return, and only then expand.