ERP Event Logs: A Canonical Form for KPI Time-Series Extraction and Characterization

summary

The gist

ERP event logs provide a canonical form for KPI extraction over relational ERP systems by collapsing schema heterogeneity into a flat structure from which KPIs become reusable operations Pruning…

In short

The paper proposes using event logs from ERP systems as a universal, flat structure for extracting Key Performance Indicators (KPIs). By mapping complex, varied database schemas into this canonical log format, researchers can define standardized KPIs like volumes and durations. This approach allows for uniform KPI extraction across different customer systems and enables direct comparison of processes like order-to-cash and procure-to-pay.

Key concepts

Event Log
A standardized record capturing every start (case) and step (activity) in an end-to-end business process. It collapses the messy, different database structures from various ERP systems into one simple, flat structure suitable for analysis.
KPI Families
Three types of KPIs derived from the event log: volumes (how much work flows), durations (how long work takes), and rates (how often things deviate). These standardized metrics allow for consistent measurement of process health across different business operations.
Extraction Leverage
The main benefit is not new data, but efficiency. By performing the complex extraction once into the common event log structure, subsequent KPI calculations become simple operations on that single structure rather than requiring costly, schema-specific joins for every metric.

Terminology used across episodes

This episode discusses

The paper

ERP Event Logs: A Canonical Form for KPI Time-Series Extraction and Characterization · Read on arXiv

SAP SE

Transcript

Introduction to the show: ident: Computer Science. The day in computer science: software, systems and theory on arXiv.

Tom: We're looking at the paper: "ERP Event Logs".

Jane: Here's the gist of the paper. ERP event logs provide a canonical form for KPI extraction over relational ERP systems by collapsing schema heterogeneity into a flat structure from which KPIs become reusable operations Pruning redundant reasoning tokens The paper shows that an event log, a canonical (case, activity, timestamp) representation derived from the same tables, collapses this heterogeneity into one flat structure.

Tom: Using standardized event logs built from hundreds of SAP S/4HANA customers under a shared activity ontology, they define three families of process-derived KPIs (volumes, durations, and rates) and extract them uniformly across customer systems for two common end-to-end organizational processes—order-to-cash and procure-to-pay.

Jane: They normalize rates and screen series for minimum coverage to support comparison across customers of very different sizes.

Tom: How the training signal is built The event log records each document that marks the start of an end-to-end process execution as a case, and each processing step as an (activity, timestamp) pair belonging to that case.

Title and authors: Tom: So we’re looking at "ERP Event Logs: A Canonical Form for KPI Time-Series Extraction and Characterization" by Sherri Hadian, Adrian Rebmann, Atacan Korkmaz, Gregor Berg, and Ulf Brackmann. These are the folks who built this framework.

Jane: They are taking something that is spread across hundreds of normalized relational tables in enterprise resource planning systems and trying to find a way to extract key performance indicators from it uniformly.

Lu: The title tells you exactly what they’re doing: creating a canonical form, which is this event log structure with case, activity, and timestamp, to solve the problem of bespoke joins for every metric.

Meng: So why does this matter practically? I’m wondering if this just means we have one more complex layer of data transformation instead of a simpler one.

Lalam: It means they build standardized event logs using a shared activity ontology from hundreds of SAP S/4HANA customers, which allows them to define three families of process derived KPIs: volumes, durations, and rates <ref:2610.09903#pg1,from hundreds of SAP S/4HANA customers>.

Tom: Right, so they are not just looking at raw data points; they are defining these specific kinds of metrics—volumes for how much work flows through a process, durations for how long it takes that work to do something, and rates for how often things go wrong.

Jane: And they extract these uniformly across two major end-to-end processes: order-to-cash and procure-to-pay. That's a big scope because those are huge parts of any business workflow.

Lu: They normalize the rates and screen series for minimum coverage to make sure you can actually compare results across customers who might be very different in size or complexity.

Meng: If you can compare the same type of metric, like lead time, between a small customer’s process and a massive one’s, that gives me some confidence in the comparison part.

Lalam: Exactly. Because order-to-cash and procure-to-pay reduce to the same common structure, their signals become directly comparable without needing to reconcile two totally unrelated join paths.

The paper's summary: Tom: So what’s the actual mechanism they used? They record every document that marks the start of an end-to-end process execution as a case, and every processing step as an activity and a timestamp pair belonging to that case.

Jane: They use this fixed mapping of source records to a canonical activity from a shared vocabulary to resolve the different labels customers might use for the same thing.

Lu: Crucially, they put both kinds of information—the document start and the step details—under one time resolved representation, which recovers series that the state tables had overwritten from history.

Meng: That sounds like they are fixing a known problem where historical data gets messy because newer information overwrites older states.

Lalam: Right, so they are recovering those old series using this single event log structure. It’s not just recording new stuff; it’s reconstructing the process history correctly.

Tom: And then every KPI is then a uniform operation over this one structure, which is why it becomes reusable after that initial mapping effort.

Jane: So, they are essentially creating a standardized language for describing process events so that you can extract these three families of KPIs—volumes, durations, and rates—consistently across different ERP systems.

Lu: They define volume as a count of an activity per period to capture demand and throughput, duration as the timestamp difference between two activities in one case to capture lead times, and rate as a count normalized by a population to capture exceptions.

Meng: I like the distinction between those three families because it gives you different types of operational questions you can ask about the process health.

Lalam: And they are showing how this works for order-to-cash and procure-to-pay, allowing for direct cross process comparison of sales and procurement side signals, including lead times and order arrivals.

The paper's improvements: Tom: Now, the paper points out that the gain isn't just about having more expressive power in relational algebra; it’s about extraction leverage—paying that extraction cost once and reusing KPI operators over one common structure instead of needing a new schema specific join every time.

Jane: That means they are prioritizing the operational efficiency of analysis over just having a theoretically powerful database query language.

Lu: The improvement is that this shared representation yields reusable, comparable, and model ready KPI time series where the ontology aligns semantics and the common schema reuses KPI operators.

Meng: From my side, if it means I don't have to write custom ETL logic for every new dashboard metric against every customer system, that’s a huge win for deployment complexity.

Lalam: It means the ontology aligns the meaning of things across different systems, so when you use a KPI operator once, it works reliably everywhere.

Tom: The paper also characterized the heterogeneity of these processes using simple process descriptors derived directly from this canonical form—like how much work flows through a business process or how long that work takes.

Jane: They are showing how you can characterize the differences between hundreds of customers based on their actual execution patterns, not just what their database schema looks like.

Lu: This allows for direct comparison of sales and procurement side signals, which is something raw ERP would require reconciling two unrelated join paths to do.

Meng: So they are moving the complexity from runtime query time to a one-time mapping phase, which is exactly what we need when shipping models at scale.

Conclusion: Tom: So wrapping up, the core contribution of "ERP Event Logs: A Canonical Form for KPI Time-Series Extraction and Characterization" is framing the event log as this common representation for KPI extraction over relational ERP systems.

Jane: The value is really in that extraction leverage—once mapped, process derived KPIs reduce to reusable operations over one structure, which helps you define three families of KPIs: volumes, durations, and rates.

Lu: They characterized the heterogeneity across hundreds of customers and showed cross process comparability for order-to-cash and procure-to-pay signals.

Meng: I think the most important thing is that this system makes KPI analysis more scalable because it moves the heavy lifting to a one time mapping phase rather than on every query.

Lalam: And they also characterized forecastability patterns across both processes, showing that volume series are the most forecastable family, and forecastability decreases from volumes through durations to rates.

Tom: So the big picture is this: you get a common structure that lets you define uniform KPI families and compare different customer processes easily. This paper really shows how to make KPI extraction more standardized across diverse enterprise systems.

Jane: It sets up a nice foundation for building models that can handle heterogeneity, which is something we all struggle with in real-world data environments.

Lu: The future work would naturally be about testing these forecastability patterns rigorously and seeing if this representation holds up when you introduce even more complex process steps.

Meng: From an engineering standpoint, the challenge for deployment will be making that initial mapping robust enough to handle schema changes in those customer systems without breaking everything.

Lalam: So in summary, "ERP Event Logs: A Canonical Form for KPI Time-Series Extraction and Characterization" gives us a way to treat complex ERP data as a flat structure ready for standardized KPI operations.

More episodes

← Home