MM / P2Pintermediate

MM Supplier and Business Partner Part 3: Vendor Account Groups and BP Role Mapping

Key takeaway

Design account groups and groupings: what the vendor account group still controls (number range, field status, one-time vendors, partner schemas), mapping to BP groupings, role assignment by supplier type (goods, services, one-time, intercompany), and field control for mandatory data.

Explanation

📌 KEY POINTS
✅ The vendor account group still controls number range, field status (vendor side) and special types like one-time vendors.
✅ BP grouping determines the BP number range and maps to the account group.
✅ Roles are assigned per supplier type: goods/services suppliers need both financial and purchasing roles; some only financial.
✅ Field control on BP side (field groupings per role) enforces mandatory data.
⚠️ Too many account groups/groupings complicate governance without business benefit.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured synchronization. Now account groups and roles.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ACCOUNT GROUPS

Number range, field status, one-time account flag, partner function schema.

━━━━━━━━━━━━━━━━━━━━
▶ 2. BP GROUPINGS

Number range for BP; mapped to account group.
Typical: external suppliers, intercompany, one-time, employees.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ROLE ASSIGNMENT

FLVN00 (company code) + FLVN01 (purchasing) for trading suppliers.
Financial-only suppliers (e.g. authorities).

━━━━━━━━━━━━━━━━━━━━
▶ 4. FIELD CONTROL

BP field groupings per role/grouping; vendor field status aligned.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PARTNER FUNCTIONS

Ordering address, invoicing party, goods supplier.

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

Define groupings for supplier types.
Map to account groups.
Define mandatory fields.
Test creation per type.

✅ CHECKPOINT: each supplier type can be created with correct numbers, roles and mandatory data.

Code example

ABAP Code

===== STEP 1: design example =====BP grouping SUPL (external suppliers, internal numbers 3000000–3999999) → account group KREDBP grouping ICSP (intercompany suppliers) → account group ICSP (trading partner mandatory)BP grouping ONET (one-time) → account group CPD (one-time flag) ===== STEP 2: roles per type =====Trading supplier: FLVN00 + FLVN01 | authority/tax office: FLVN00 only ===== STEP 3: field control =====Mandatory: tax number (country-based), bank (for payment method T), purchasing: order currency

Real project scenario

During a merger, two legacy systems had 25 vendor account groups with overlapping meanings. The template consolidated them into five BP groupings mapped to five account groups with clear rules (external, intercompany, one-time, employee, authorities), simplifying governance and reporting.

Common mistakes

Too many groupings.
Intercompany suppliers without trading partner.
One-time vendors misused for regular suppliers.
Missing mandatory tax/bank fields.
Roles assigned inconsistently.

Best practices

Keep groupings few and meaningful.
Enforce trading partner for intercompany.
Restrict one-time vendor use.
Define mandatory fields per type.
Document role rules.

Interview angle

Questions: "What does the vendor account group control in S/4HANA?", "How are BP groupings mapped?", "Which roles does a supplier need?"
Strong answer: account group controls number range/field status/one-time; grouping ↔ account group; roles per supplier type; field control; partner functions.

Practice this lesson

Quick check

1. What does the vendor account group still control in S/4HANA?

2. Which supplier type should require a trading partner?

3. How is the vendor account group determined when a supplier BP is created?

Interview questions

1. How does the purchasing value key in the vendor master interact with account group and business partner role design, and why does this matter when standardizing vendor onboarding?

Answer it in your own words first, then compare.

2. How do vendor account group settings and Business Partner role assignments influence which purchasing organizations can maintain purchasing info records for a supplier, and what governance issue results if these are misaligned?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.