Skip to content
IT Canvass
SAP fundamentals · Lesson

Transaction data

Quick answer

Transaction data grows continuously and dominates database size.

Key takeaways

  • 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.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Which statement is true of Transaction data?

    • A. Each transaction is typically stored as documents, a header and item structure, in dedicated tables.
    • B. SAP Integration Suite is SAP’s cloud integration platform (iPaaS) on BTP, bundling Cloud Integration (CPI)…
    • C. These HANA examples show data modeling and SQL on the in-memory database, a calculation/CDS view and…
    Show answer

    A. Each transaction is typically stored as documents, a header and item structure, in dedicated tables.

    Covered in the “What transaction data is” section of this lesson.

  2. Which of these also applies to Transaction data?

    • A. Over-granting backend authorizations.
    • B. Guessing instead of using the reference tools.
    • C. SAP follows a document principle: every business event creates a document with a unique number, a header…
    Show answer

    C. SAP follows a document principle: every business event creates a document with a unique number, a header…

    Covered in the “Documents and the document principle” section of this lesson.

  3. Which part of the Learn SAP curriculum covers Transaction data?

    • A. SAP fundamentals
    • B. SAP ABAP development
    • C. SAP administration
    Show answer

    A. SAP fundamentals

    This lesson sits in the SAP fundamentals section of the Learn SAP course.

Frequently asked questions

What does the term Transaction data refer to in SAP?

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.

What is another point to note about Transaction data?

Transaction data grows continuously and dominates database size.

What else is worth knowing about Transaction data?

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.

What tends to go wrong with Transaction data?

Confusing documents with master data. Ignoring the header/item structure when reading tables. Underestimating data growth from transactions.
CallWhatsAppEnquire