In SAP, updates to the database are not always executed immediately. Instead, the system uses an update task mechanism to ensure data consistency, improve performance, and provide rollback control. These updates can run in two modes: Synchronous (V1), where critical updates are executed immediately to ensure data integrity, and Asynchronous (V2), where less critical updates are processed later to reduce system load and improve performance.
1. Synchronous Update (V1 Update)
- The update request is processed immediately after the dialog step is completed.
- The program waits until the update is finished before continuing.
- Used when the update is critical for business consistency.
✅ Examples:
- Posting an accounting document in FI
- Creating a Sales Order in SD
- Material stock update in MM
👉 Business transaction cannot continue unless the update is successful.
2. Asynchronous Update (V2 Update)
-
The update request is placed in the update queue, but it is executed later, not immediately.
-
The program does not wait for the update to finish.
-
Used for secondary / non-critical updates like statistics or logs.
✅ Examples:
- Updating LIS (Logistics Information System) tables
- Updating change history tables (logs, statistics, reporting data)
👉 Business transaction continues immediately, even if update fails.
Feature | Synchronous Update (V1) | Asynchronous Update (V2) |
---|---|---|
Timing | Immediate | Later (queued) |
Program waits? | Yes | No |
Criticality | Mission-critical updates | Non-critical updates |
Examples | FI posting, Sales Order, Stock update | Statistics update, Logs |
Failure impact | Transaction rolls back | No rollback (only logs/statistics missing) |
Technical Note
- Both V1 and V2 updates are processed by Update Work Processes (UPD/UP2).
- You can check update processing in transaction SM13.
- V1 updates are serialized, V2 are parallel and less time-critical.