Unit 4: Master Data in Procurement
Purchasing documents are mostly filled from master data. This unit covers the three key master data objects of procurement – business partner (supplier), material master and purchasing info record – plus purchasing conditions and the valuation logic that links Materials Management to Financial Accounting.
Lesson 1 · Maintaining Business Partner Master Data
After this lesson you can
- Explain the business partner concept, categories, roles and customer/vendor integration
- Describe the data levels of a supplier and the reconciliation account
- Use partner roles and one-time (CpD) suppliers
Key concepts
Master data is long-lived data stored centrally and shared by several applications, which avoids redundant entry. In procurement the most important objects are the supplier (business partner), the material master and the purchasing info record. When a document is created, data flows from them into the document:
| Master record | Data copied into purchasing documents |
|---|---|
| Material master | Order unit, short text, PO text, material group |
| Supplier (business partner) | Address, payment terms, currency, Incoterms |
| Purchasing info record | Supplier-specific price/conditions, planned delivery time, tolerances |
In SAP S/4HANA suppliers and customers are maintained as business partners (BP) using transaction BP or the Fiori app Manage Business Partner Master Data. In SAP ERP vendors and customers were separate objects (XK01/MK01, XD01); these transactions are redirected to BP in S/4HANA.
| BP element | Explanation |
|---|---|
| BP category | Person, organization or group. Determines which fields are available (e.g. first/last name vs. company name). Fixed at creation – cannot be changed later. |
| BP role | Business context in which the BP acts. For procurement: FLVN01 Supplier (purchasing data) and FLVN00 FI Vendor (company code data). For sales: Customer / FI Customer. |
| BP grouping | Controls number range (internal or external numbering) and, through CVI, is mapped to the vendor account group. |
Data levels of a supplier
| Data area | Org level | Examples |
|---|---|---|
| General data | Client | Name, address, communication, bank details, control data, contact persons |
| Company code data (FI Vendor role) | Company code | Reconciliation account, payment terms and methods for automatic payment, correspondence, withholding tax |
| Purchasing data (Supplier role) | Purchasing organization (optionally plant / supplier subrange) | Order currency, Incoterms, partner functions, GR-based IV, ERS indicator, minimum order value, other controls |
Customer/vendor integration (CVI)
Accounts payable still uses vendor accounts technically (subledger), so each BP that acts as supplier must have a synchronized vendor record. CVI does this in the background: when you create or change the BP, the corresponding vendor fields are created or updated automatically. In Customizing you assign BP groupings to vendor account groups and configure synchronization control.
SPRO › Cross-Application Components › Master Data Synchronization › Customer/Vendor Integration › Business Partner Settings › Settings for Vendor Integration › Field Assignment for Vendor Integration › Assign Keys › Define Number Assignment for Direction BP to Vendor
Reconciliation account
Each supplier has a number that is also its subledger account number; per supplier the open liabilities are tracked. In the company code data you must enter a reconciliation account – a G/L account that collects the liabilities of many suppliers in the general ledger (e.g. "Payables domestic"). When an invoice is posted to the supplier, the system automatically posts to this G/L account in parallel.
Partner roles (partner functions)
The supplier fulfils several roles in one process: ordering address, goods supplier, invoicing party and payee. These can be different business partners – e.g. orders go to supplier A, goods come from subsidiary S, invoices come from headquarters C. Such deviating partners are defined in the purchasing data and proposed in documents.
| Partner function (English key) | Meaning |
|---|---|
VN | Vendor (supplier) – the PO recipient |
OA | Ordering address |
GS | Goods supplier |
PI | Invoicing party |
One-time suppliers (CpD)
No PO or invoice is possible without a supplier master record. For suppliers used once or rarely, a collective one-time account (CpD – Conto pro Diverse) is created with a special BP grouping. It holds only non-specific data (language, currency, reconciliation account); name, address and bank details are entered in each document.
The BP approach is mandatory in all SAP S/4HANA releases: XK01/MK01 etc. jump to BP. CVI must be set up before conversion from SAP ECC. Newer releases also provide mass maintenance and data-quality apps for BP via SAP Master Data Governance.
- BP represents supplier and customer (not MRP areas or storage locations).
- Supplier org levels: client (general), company code (FI vendor), purchasing organization (supplier) – not storage location or purchasing group.
- BP category cannot be changed after creation.
- Reconciliation account is in the company code data.
- CpD: name/address are entered in the document.
Lesson 2 · Maintaining Material Master Data
After this lesson you can
- Explain views and organizational levels of the material master
- Create and extend a material master record; explain material type and industry sector
- Work with valuation data: price control, valuation area, valuation class
Key concepts
The material master is the single central source of material data for all logistics areas (purchasing, inventory management, MRP, invoice verification, sales, accounting). Data is grouped into views per department, e.g. Basic Data, Purchasing, MRP 1–4, Plant data/storage, Accounting, Costing, Sales, Quality Management, Warehouse Management. Next to the main data screens there are additional data screens (alternative units of measure, descriptions in other languages, consumption values).
| Org level | Examples of data |
|---|---|
| Client | Material number, short text, base unit of measure, material group, PO text, material type, industry sector |
| Plant (or valuation area) | Purchasing group, order unit (variable), MRP data, shelf-life data, price control, valuation price, valuation class |
| Storage location | Storage bin, storage-location-specific MRP |
| Sales org / distribution channel | Sales data |
| Warehouse number / storage type | Warehouse management data |
When maintaining a material you first see two dialog boxes: choose the views, then the organizational levels. The default can be preset (Defaults › Views / Org levels).
Material type and industry sector
| Control element | What it controls |
|---|---|
Material type (e.g. ROH raw material, HALB semifinished, FERT finished, HAWA trading goods, NLAG non-stock, DIEN service) | Number assignment (internal/external) and number ranges; which views can be maintained; allowed procurement type (in-house/external/both); together with the plant whether stock is managed by quantity and/or value; allowed valuation classes (via account category reference); field selection. |
| Industry sector (e.g. mechanical engineering, retail) | Which screens appear and their sequence, which industry-specific fields are shown. Cannot be changed after creation. |
Extending a material
Adding a new view or a new organizational level (e.g. a second plant) is an extension and is done with the create transaction (MM01), not with change (MM02). Change only modifies views/levels that already exist. Every creation or change is logged in change documents (display via MM04).
- MM01: enter material number (if external numbering), industry sector, material type.
- Select views (Basic Data, Purchasing, Accounting, Plant data/Storage …).
- Enter org levels (plant, storage location, valuation area).
- Fill the data screens and save. Use MM02 to change and MM03 to display; Fiori: Manage Product Master Data.
Material valuation
Stock value = stock quantity × valuation price. Valuated goods movements update both the material master (quantity, value, possibly price) and the G/L accounts, which makes valuation the bridge between MM and FI. It is governed by Customizing and by the Accounting view of the material.
The valuation area is the level at which material is valuated: plant (SAP recommendation, mandatory for PP/Costing) or company code. This is a fundamental setting that is very hard to change later.
SPRO › Enterprise Structure › Definition › Logistics – General › Define Valuation Level
Price control
Standard price (S) | Moving average price (V) | |
|---|---|---|
| GR valuation | Always at standard price | At PO price (other movements at current MAP) |
| Price difference at GR/IR | Posted to price difference account (PRD); stock value unchanged | Posted to stock account (if enough stock coverage) – price changes; remainder to PRD |
| Price in material master | Constant until a new standard price is released | Recalculated: total value / total quantity |
| Typical use | Own produced materials (semi-/finished goods) | Purchased materials (raw materials, trading goods) |
Example: current price 20, GR of 10 pcs at PO price 25. With V: stock +250, GR/IR −250. With S: stock +200, price difference +50, GR/IR −250.
Valuation class
The valuation class (Accounting 1 view) groups materials for account determination: it decides which stock G/L account is posted, so you do not need a separate account per material. Which valuation classes are allowed depends on the material type (via the account category reference); one valuation class can be allowed for several material types.
SPRO › Materials Management › Valuation and Account Assignment › Account Determination › Account Determination Without Wizard › Define Valuation Classes
SAP S/4HANA supports a material number of up to 40 characters (activated in Customizing). Material Ledger is mandatory, with actual costing optional, and valuation tables are part of the Universal Journal (ACDOCA). The Fiori app Manage Product Master Data is the successor of MM01–MM03 for many users.
- Material type controls number assignment, views, procurement type, quantity/value update, valuation class choice – not short text length or allowed suppliers.
- Industry sector cannot be changed after creation.
- Adding a view = extension with MM01, not MM02.
- Purchasing group, price control and valuation class are plant (valuation area)-level data; PO text and base unit are client-level.
- Valuation class → stock account; it does not control the price control procedure.
Lesson 3 · Maintaining Purchasing Info Record
After this lesson you can
- Maintain info records manually and automatically
- Explain conditions, condition types, the calculation schema and price determination
Key concepts
The purchasing info record is purchasing master data that stores what you know about a supplier–material (or supplier–material group) combination. Its contents are proposed into POs and help buyers compare sources.
- Current and future prices and conditions (gross price, discounts, freight, scales)
- Delivery data: planned delivery time, over-/underdelivery tolerances, minimum quantity
- Supplier-specific data: supplier material number, supplier subrange
- Number of the last PO (last document)
- Texts: info record memo (internal, copied to the PO item, not printed) and purchase order text (copied and printed)
| Info category | Used for |
|---|---|
| Standard | Normal procurement |
| Subcontracting | Price of the processing service in subcontracting |
| Consignment | Price for withdrawals from consignment stock (prerequisite for consignment) |
| Pipeline | Pipeline materials (e.g. electricity, water) withdrawn directly |
Org levels: general data at client level; purchasing data per purchasing organization, optionally per purchasing organization + plant.
Maintenance options
- Manual: ME11 (create), ME12 (change), ME13 (display); Fiori Manage Purchasing Info Records.
- Automatic via the Info update indicator in a purchasing document:
Source document Effect on info record Quotation Conditions and document/item number transferred PO, contract release order, scheduling agreement Document and item number stored as "last document" Contract If no info record exists yet for supplier/material/org level, one is created with the contract conditions; an existing one is not updated
Purchasing conditions
Conditions are agreements on prices, surcharges, discounts and freight. They can be held in quotations, info records, outline agreements and POs, and as general conditions (e.g. per supplier). From them the system calculates:
| Price | Definition |
|---|---|
| Gross price | Price before discounts and surcharges (e.g. condition type PB00) |
| Net price | Gross price ± discounts and surcharges |
| Effective price | Net price − cash discount + delivery costs, neutral provisions and non-deductible taxes |
Time dependency: conditions in info records, contracts and general conditions are time-dependent (validity periods, scales possible). Conditions in POs are always time-independent (valid as long as the document). For quotations and scheduling agreements the document type's "time-dependent conditions" indicator decides. Header conditions apply to all items, item conditions only to their item.
Condition technique
- Condition type – represents one price element; defines calculation type (fixed amount, percentage, quantity-dependent) and scale basis (quantity, value, weight).
- Access sequence – search strategy listing in which order condition tables are read (specific to general).
- Calculation schema (pricing procedure, e.g.
RM0000) – sequence of condition types, subtotals (net/effective price), reference levels for percentages, manual-change permissions, requirements. Different schemas can be determined per purchasing organization and supplier (schema groups).
SPRO › Materials Management › Purchasing › Conditions › Define Price Determination Process › Define Condition Types / Define Access Sequences / Define Calculation Schema / Define Schema Determination
Price determination in a PO
The system searches from specific to general: info record for supplier/material at purchasing organization + plant, then at purchasing organization level. Valid conditions in the info record take priority; if none are valid, the price from the last purchasing document stored in the info record is proposed. If nothing is found, the buyer enters the price manually. The valuation price of the material master is never proposed as PO price.
In SAP S/4HANA the pricing results of purchasing documents are stored in table PRCD_ELEMENTS (replacing the ERP table KONV). The Fiori app Manage Purchasing Info Records supports mass change and creation from the PO.
- Info record = master data; org levels client, purchasing organization, plant.
- Info record memo: not printed; PO text: printed.
- Contract creates an info record only if none exists.
- PO conditions are time-independent; info record/contract conditions time-dependent.
- Price determination order: info record (POrg+plant) → info record (POrg) → last document → manual; never the valuation price.
Lesson 4 · Analyzing Material Valuation
After this lesson you can
- Explain material, invoice and accounting documents and how they are linked
- Trace FI postings and price updates for GR and IR with standard and moving average price
Documents
| Document | Created by | Identified by | Content |
|---|---|---|---|
| Material document | Every goods movement | Number + material document year | Header: posting date, user. Items: material, quantity, movement type, plant, storage location. Cannot be changed – cancel/reverse and repost. |
| Accounting document (from GR) | Valuated goods movements only | Company code + number + fiscal year | Header: dates, period, currency. Items: G/L accounts and amounts. Company code derived from plant. |
| Invoice document (MM) | Logistics invoice verification | Number + year | Invoicing party, posting date, creator; items with amounts per quantity |
| Accounting document (from IR) | Every posted invoice | Company code + number + fiscal year | Supplier, GR/IR, tax, differences |
A movement is valuation-relevant only if FI is affected. A GR of raw material to stock increases current assets; a transfer between storage locations of the same plant changes nothing in FI, so only a material document is created.
Scenario: standard price (S)
Illustrative figures: standard price 2.00; GR of 100 pcs at PO price 2.40; invoice for 100 pcs at 2.20.
| Step | Stock (BSX) | GR/IR (WRX) | Price diff. (PRD) | Supplier | Material price |
|---|---|---|---|---|---|
| GR | +200 (qty × standard) | −240 (qty × PO price) | +40 (expense) | – | 2.00 unchanged |
| IR | – | +240 (cleared at PO price) | −20 (income) | −220 (invoice price) | 2.00 unchanged |
Scenario: moving average price (V)
Illustrative figures: opening stock 1,000 pcs, value 2,000 (MAP 2.00); same GR and IR.
| Step | Stock (BSX) | GR/IR (WRX) | Supplier | Total qty / value | MAP |
|---|---|---|---|---|---|
| GR | +240 (PO price) | −240 | – | 1,100 / 2,240 | ≈ 2.04 |
| IR | −20 (difference to stock) | +240 | −220 | 1,100 / 2,220 | ≈ 2.02 |
If, at invoice time, less stock is on hand than the invoiced quantity (some has been consumed), only the proportional part of the difference goes to the stock account; the rest goes to the price-difference account (PRD).
Configuration (IMG)
SPRO › Materials Management › Valuation and Account Assignment › Account Determination › Account Determination Without Wizard › Configure Automatic Postings
(Transaction OBYC; key transaction keys: BSX stock, WRX GR/IR, PRD price differences, GBB offsetting entries for inventory postings.) Display documents with MB03 (material document), MIR4 (invoice), FB03 (accounting document); show price/stock values with MM03 Accounting view or MMBE.
In SAP S/4HANA every valuated movement is written to the Universal Journal ACDOCA, and the Material Ledger is always active, so inventory values can be held in up to three currencies. Price differences remain visible per material in the Material Ledger.
- Transfer within one plant: no FI posting.
- S price: GR at standard price, difference to
PRD, stock value unchanged at IR. - V price: GR at PO price, MAP = total value / total quantity; IR difference to stock if stock coverage exists.
- GR/IR is always posted at PO price at GR and cleared at PO price at IR; supplier is posted at invoice price.
- Material and accounting documents are separate but linked; company code derived from plant.
Unit summary & exam focus
Business partner, material master and info record supply most data in purchasing documents. Conditions are evaluated via the condition technique to determine prices, and the material's price control decides how GR and IR are valuated and where price differences end up.
T-codes in this unit
| T-code | Purpose |
|---|---|
| BP | Maintain business partner (supplier/customer) |
| XK01 | Create vendor (redirected to BP in S/4HANA) |
| MK01 | Create vendor, purchasing (redirected to BP) |
| XD01 | Create customer (redirected to BP) |
| MM01 | Create / extend material |
| MM02 | Change material |
| MM03 | Display material |
| MM04 | Display material change documents |
| ME11 | Create purchasing info record |
| ME12 | Change purchasing info record |
| ME13 | Display purchasing info record |
| OBYC | Automatic account determination (MM) |
| MB03 | Display material document |
| MIR4 | Display invoice document |
| FB03 | Display accounting document |
| MMBE | Stock overview |
Self-check questions
- Which organizational levels are relevant for a BP in the roles Supplier and FI Vendor?
Answer
Client (general data), company code (FI vendor) and purchasing organization (supplier) – not storage location or purchasing group. - True or false: to add the Purchasing view to an existing material you use the change transaction.
Answer
False – adding a view or org level is an extension, done with the create transaction (MM01). - Name three things the material type controls.
Answer
Number assignment/number range, which views can be maintained, allowed procurement type, quantity/value updating (with plant), allowed valuation classes. - Which org levels exist in a purchasing info record?
Answer
Client (general data), purchasing organization, and optionally plant. - In which order does the system look for a PO price?
Answer
Valid conditions in the info record for POrg + plant, then POrg; if no valid conditions, the price of the last PO in the info record; otherwise manual entry. The valuation price is never proposed. - What does the valuation class determine?
Answer
Which stock G/L account is posted; it allows many materials to share one stock account. - Material with S price 20; GR of 10 pcs at PO price 25. Which accounts are posted?
Answer
Stock +200 (BSX), price difference +50 (PRD), GR/IR −250 (WRX). The standard price stays 20. - Does an internal transfer within one plant create an accounting document?
Answer
No; only a material document is created because FI is not affected.