Transaction data
Transaction data records the individual business events that happen every day, orders, deliveries, invoices, goods movements, postings. It is created constantly, references master data, and is what flows through SAP’s end-to-end processes.
Transaction data grows continuously and dominates database size.
- Where master data is the stable reference (a customer, a material), transaction data is the event that uses it: a sales order for…
- SAP follows a document principle: every business event creates a document with a unique number, a header (who, when, overall data)…
- When a transaction is posted, it triggers updates across modules, a goods receipt updates inventory and posts to finance.
- Watch out: Confusing documents with master data.
What transaction data is
Where master data is the stable reference (a customer, a material), transaction data is the event that uses it: a sales order for that customer, a goods receipt for that material. Each transaction is typically stored as documents, a header and item structure, in dedicated tables.
Documents and the document principle
SAP follows a document principle: every business event creates a document with a unique number, a header (who, when, overall data) and items (the lines). A sales order lives in VBAK (header) and VBAP (items); a financial document in BKPF (header) and BSEG (items). This consistent structure appears everywhere.
Transaction data drives integration
When a transaction is posted, it triggers updates across modules, a goods receipt updates inventory and posts to finance. Transaction data is therefore the mechanism through which SAP’s integration actually happens.
Volume and archiving
Transaction data grows continuously and dominates database size. Managing its volume, through archiving and, in S/4HANA, a simplified data model, is an important operational concern.
Common pitfalls
- Confusing documents with master data.
- Ignoring the header/item structure when reading tables.
- Underestimating data growth from transactions.