Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 36 ยท SAP Architecture and Navigation

SAP Master Data vs Transaction Data: Materials, Vendors, Customers, Documents

Learn the difference between master data (materials, vendors, customers, G/L accounts) and transaction data (documents), organizational views, document numbers and data quality.

All SAP data falls into two big groups. Master data describes the things a business deals with and changes rarely: materials, customers, vendors, accounts. Transaction data records events that happen, such as a purchase order, a goods receipt or an invoice, and grows with every business day. A transaction always refers to master data. Mixing the two up is the most common beginner confusion, and poor master data is the most common cause of later errors.

Master data

Master data is created once and reused by thousands of transactions.

Master data Describes Key data Typical t-code (classic)
Material master A product, part, service or packaging Material number, description, unit of measure, plant data, price MM01 / MM02 / MM03
Vendor master A supplier Name, address, payment terms, bank, reconciliation account XK01, MK01, FK01
Customer master A buyer Name, address, payment terms, sales area data XD01, VD01, FD01
Business partner (S/4HANA) Customer, vendor and others in one model Roles, addresses, banking BP
G/L account master An account in the ledger Account number, type, currency, field status FS00
Cost center A unit that incurs cost Cost center number, responsible person, hierarchy KS01
Bill of materials (BOM) The components of a product Parts and quantities CS01
Employee master A person Personal data, pay, organization PA30

Views of a master record

A master record is split into views (or screens) because different departments need different information. The material master has basic data, purchasing, sales, MRP (planning), storage, accounting and costing views. Each view stores data at a defined organizational level:

  • Basic data: client level (the same for the whole company).
  • Plant data (MRP, purchasing): per plant.
  • Sales data: per sales organization and distribution channel.
  • Accounting data: per valuation area (usually the plant).
flowchart TD
    M["Material master BOLT-01"] --> B["Basic data<br/>client level"]
    M --> P["Purchasing + MRP<br/>per plant"]
    M --> S["Sales<br/>per sales org + channel"]
    M --> A["Accounting<br/>per plant: price, valuation"]

One material, several views at different organizational levels.

This is why you cannot order a material in plant 1020 if its purchasing view was only created for plant 1010. The message "material not maintained for plant" is a master data gap, not a program bug.

Transaction data

Transaction data is created by business events and usually appears as a document:

  • Purchase requisition, purchase order, goods receipt, invoice
  • Sales order, delivery, billing document
  • Accounting document (the ledger entry produced by most events)
  • Production order, maintenance order

Each document has a header (date, company code, document type, who created it) and items (lines with material, quantity, amount). Documents get a document number from a number range, for example 4500000123 for a purchase order. Posted accounting documents cannot be changed in important fields; they are reversed and re-entered, which keeps the audit trail intact.

Property Master data Transaction data
Changes Rarely Every day
Volume Thousands Millions
Owner A responsible department The process that created it
Example Vendor "Acme Ltd" Invoice 5105000789 from Acme Ltd

How they work together

When you create a purchase order, you enter the vendor number and material number. SAP reads the master data and copies defaults: the vendor's payment terms, the material's unit and plant data, the price from the info record. These defaults flow into the document, so entering one number gives you dozens of correct fields. That is the benefit of good master data: fewer manual entries, fewer errors.

Python Stand-in: a document copies defaults from master data

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Data quality and governance

Because master data is reused everywhere, errors multiply. Companies therefore set up master data governance:

  • Duplicates: the same supplier entered twice leads to double payments. Check before creating.
  • Mandatory fields and validation rules, set by field status and field groups.
  • Approval workflows for sensitive changes such as bank details of a vendor.
  • Change documents: SAP stores who changed which field and when; display them in the master data transaction under Environment > Change documents.
  • Blocking and deletion flags instead of physical deletion, so history stays readable.
Python Stand-in: duplicate vendor detector

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Customizing data: the third category

There is a third group often called customizing or configuration data: settings that define how processes behave (document types, number ranges, payment terms, tax codes). It is entered in SPRO and moves between systems by transport, as you saw in the landscape lesson. Master data and transaction data normally do not travel by transport; they are entered or loaded in each system.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which of these is master data?

    A vendor record is master data; the other three are transaction data (documents).
  2. 2. Why does the material master have several views?

    Views separate basic, purchasing, sales and accounting data by department and level.
  3. 3. How do you normally correct a posted accounting document?

    Posted documents are reversed to keep the audit trail.
  4. 4. What is stored in customizing data?

    Customizing defines how the system behaves and is transported between systems.

Summary

  • Master data (materials, vendors, customers, accounts) changes rarely and is referenced by all transactions.
  • Transaction data (documents) records business events with a header and items.
  • Master records have views stored at different organizational levels.
  • Clean master data prevents duplicates and errors; use governance, change documents and blocking flags.
  • Customizing data defines behavior and is transported between systems.

Next: The SAP module map