MM / P2Pbeginner

MM Supplier and Business Partner Part 1: Supplier Master Data in the Business Partner Model

Key takeaway

In S/4HANA, suppliers are maintained as business partners. Learn the BP concept (one partner, many roles), supplier roles for accounting and purchasing, the data levels — general, company code, purchasing organization — and what each level controls in procurement and payments.

What this complete series covers

Learn Supplier and Business Partner in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for: Best for SAP consultants, developers, and learners who want a practical understanding of Supplier and Business Partner.
Prerequisites: Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome: By the end, you should be able to explain Supplier and Business Partner clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: MM Supplier and Business Partner Part 1: Supplier Master Data in the Business Partner Model
Introduces why supplier master data is central to procurement, contrasts the classic vendor master with the Business Partner (BP) model, and explains the views and organizational l
Part 2: MM Supplier and Business Partner Part 2: Configuring BP to Supplier Synchronization (CVI)
Explains the configuration behind Business Partner to vendor synchronization in S/4HANA, including BP roles for suppliers, number range alignment, grouping, and the direction setti
Part 3: MM Supplier and Business Partner Part 3: Vendor Account Groups and BP Role Mapping
Learn how vendor account groups, number ranges, and Business Partner roles (FLVN00, FLVN01) are configured together so supplier master creation stays consistent across FI and MM views in S/4HANA.
Part 4: MM Supplier and Business Partner Part 4: Architecting the BP Model Across ECC, S/4HANA and Cloud Landscapes
An architect-level view of how to design, govern and operate the Business Partner (BP) as the single master data object for suppliers across hybrid ECC and S/4HANA landscapes, cove
Part 5: MM Supplier and Business Partner Part 5: Troubleshooting BP and Supplier Synchronization Failures
Diagnose and resolve real-world Business Partner to vendor synchronization errors in S/4HANA, including mass maintenance conflicts, extension issues across company codes and purcha

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ In S/4HANA, suppliers are created and changed with transaction BP; XK01/MK01 are replaced.
✅ One business partner can hold several roles: supplier (purchasing), supplier (financial accounting), customer, etc.
✅ Data levels: general (name, address, tax, bank), company code (reconciliation account, payment terms, payment methods), purchasing org (order currency, incoterms, GR-based IV, partner functions).
✅ Customer-vendor integration (CVI) keeps the classic vendor tables (LFA1, LFB1, LFM1) in sync.
⚠️ Missing purchasing org data means the supplier can't be used in POs for that purchasing org.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Supplier master data in the BP model
Part 2: Configuring BP to supplier synchronization (CVI)
Part 3: Vendor account groups and BP role mapping
Part 4: Architecting the BP model across landscapes
Part 5: Troubleshooting BP and supplier synchronization

━━━━━━━━━━━━━━━━━━━━
▶ 1. BUSINESS PARTNER CONCEPT

One partner, many roles; organization or person.
BP grouping controls number range and (via mapping) the vendor account group.

━━━━━━━━━━━━━━━━━━━━
▶ 2. GENERAL DATA

Name, address, communication, tax numbers, bank details.

━━━━━━━━━━━━━━━━━━━━
▶ 3. COMPANY CODE DATA (FLVN00)

Reconciliation account, payment terms, payment methods, withholding tax.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PURCHASING ORGANIZATION DATA (FLVN01)

Order currency, incoterms, payment terms, GR-based IV, partner functions, purchasing value key.

━━━━━━━━━━━━━━━━━━━━
▶ 5. S/4HANA SPECIFICS

BP transaction, CVI synchronization, Fiori apps for suppliers.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create a BP with supplier roles for company code 1000 and purchasing org 1000.
Create a PO for the supplier.
Post an invoice and check payment terms.

✅ CHECKPOINT: the supplier works in purchasing and accounting with the expected defaults.

Code example

ABAP Code

===== STEP 1: create =====BP → create organization → grouping (e.g. supplier external numbering) → role FLVN00 (company code 1000) → role FLVN01 (POrg 1000) ===== STEP 2: data per level =====General: name, address, tax number, bankCompany code: recon account 160000, payment terms Z030, payment methods T/CPurchasing org: order currency EUR, incoterms FCA, GR-based IV X, purchasing value key ===== STEP 3: tables =====BUT000 (BP) ↔ LFA1 / LFB1 / LFM1 (vendor) via CVI

Real project scenario

During an S/4HANA greenfield implementation, buyers could not select new suppliers in POs. Master data teams had created BPs with the financial role only. Adding the FLVN01 purchasing role with purchasing org data and a role checklist per supplier type fixed onboarding.

Common mistakes

Creating only one role.
Missing purchasing org data.
Duplicate BPs for same supplier.
Wrong reconciliation account.
Bank data without verification.

Best practices

Use role checklists per supplier type.
Check duplicates before creation.
Verify bank data (dual control).
Govern BP groupings.
Train on BP transaction.

Interview angle

Questions: "How are suppliers maintained in S/4HANA?", "Which data levels exist?", "What is CVI?"
Strong answer: BP with supplier roles, general/company code/purchasing org data, BP grouping, CVI syncing vendor tables, BP transaction replacing XK01.

Practice this lesson

Quick check

1. Which transaction is used to create suppliers in S/4HANA?

2. New suppliers can be paid but cannot be used in purchase orders. What is missing?

3. Where is the supplier's reconciliation account maintained?

Interview questions

1. In S/4HANA Public Cloud procurement, how are business partners (suppliers) typically created and integrated, given that classic supplier master maintenance transactions are restricted?

Answer it in your own words first, then compare.

2. In an S/4HANA greenfield implementation, buyers cannot select newly created suppliers in POs although finance can post invoices. What do you check?