How to Capture SAP Changes the Moment They Happen

Most SAP data workflows run on a schedule. They wake up, read from SAP, and work out what changed. That works, but there is always a window where you are acting on stale data.

There is another way. SAP can push the change to you the moment it happens. A customer gets created, an order gets saved, a journal gets posted, and your workflow runs within seconds. This post explains how the DVW Flow Tool captures SAP changes, the event-driven version of change data capture, at the application layer. No database triggers, no log-mining, no replication layer.

Watch SAP trigger a Flow Tool workflow the instant a record changes. Also available on YouTube.

Three ways to get changes out of SAP

Not every workload needs the same latency. The DVW Flow Tool covers the full range with three mechanisms, all at the application layer.

1. Event-driven extract flows. SAP pushes to the Flow Tool the moment a business event fires, using SAP's own Business Transaction Events framework. The matching extract flow runs within seconds. No polling, no nightly batch. This is the mode for the changes you cannot wait for: a new customer that needs sanctions screening, an order that should update a downstream system, a posting that should refresh a dashboard.

2. Change-document delta. For master data and transactional changes where a scheduled delta is enough, the Flow Tool reads SAP change documents and extracts only what changed since the last run. Minutes to hours, on your own cadence.

3. Timestamp and BW request-ID windows. For tables without change-document coverage, and for BW delta, the Flow Tool tracks timestamp and request-ID watermarks to pull only new and changed records. Any schedule.

How event-driven capture works

Step 1. Hook into the SAP events that matter, from a financial posting to a sales order to a goods movement, using standard SAP extension points such as a business transaction event or a user exit.

Step 2. When the event fires, SAP calls your flow by name on the Flow Tool Server. The flow reads the related records from SAP, transforms them, and writes them to your chosen destination.

Step 3. The handler returns immediately, so the flow runs asynchronously and never slows down the user who hit save.

Why the application layer matters

Most change data capture tooling works underneath SAP, at the database: log-mining, database triggers, or a dedicated replication layer. That works, but it comes with baggage. It bypasses SAP's application logic, it needs its own infrastructure, and the database sees rows, not business events.

Capturing changes at the application layer changes all three. Every read fires after SAP's own authorization checks, so the capture respects your SAP security model. There is no extra layer to install, own and operate between SAP and your platform. And you capture the business event, not the row change: a single invoice posting touches many rows across several tables, but the event fires once, with full business context.

What this is not

Event-driven capture is near-real-time, not sub-second replication. If you need genuine sub-second SAP-to-warehouse replication, that is a replication workload and a different class of tool. Most analytics and automation workloads do not need it. They need the change within seconds or on a reliable schedule, delivered prepared and ready to use, and that is what the Flow Tool does.

Event-driven capture is available on SAP ECC and SAP S/4HANA, on-premise and Private Edition / RISE, and runs on the DVW Flow Tool Server.

See it on your own SAP data

The DVW Flow Tool reads, transforms, and delivers SAP data to 20+ analytics platforms and cloud services. Change capture is one part of it.

Explore the DVW Flow Tool Watch Demos Start Free Trial