Supplier and Business Partner

Lessons in this topic

• MM Supplier and Business Partner Part 1: Supplier Master Data in the Business Partner ModelIn 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.
• MM Supplier and Business Partner Part 2: Configuring BP to Supplier Synchronization (CVI)Configure customer-vendor integration for suppliers: activation of synchronization, BP roles and role categories, BP groupings mapped to vendor account groups, number assignment (same or different numbers), field mappings, and the synchronization cockpit and post-processing for conversions.
• MM Supplier and Business Partner Part 3: Vendor Account Groups and BP Role MappingDesign 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.
• MM Supplier and Business Partner Part 4: Architecting the BP Model Across ECC, S/4HANA and Cloud LandscapesArchitect supplier master data across landscapes: conversion vs new implementation implications, central governance with MDG, distribution to connected systems (Ariba, other ERPs), supplier lifecycle (onboarding, qualification, blocking), duplicates and harmonization, and data privacy.
• MM Supplier and Business Partner Part 5: Troubleshooting BP and Supplier Synchronization FailuresDiagnose BP-supplier problems: synchronization errors during conversion or daily maintenance, missing roles or org data, number range conflicts, suppliers blocked for posting or purchasing, integration replication failures, and a structured analysis path with the relevant tools.

Interview questions covered

• As solution architect, what controls must be enforced around Business Partner/CVI synchronization when integrating S/4HANA with Ariba to prevent duplicate or inconsistent vendor master records during output-driven PO/invoice cycles?
• In an S/4HANA implementation with Business Partner as the mandatory supplier creation approach, how would you govern field selection differences between procurement and finance teams while maintaining data quality?
• During a global template rollout integrating S/4HANA with Ariba, vendor master records created via CVI in one region are causing duplicate business partners with mismatched roles when synchronized through MDG. What is your root-cause analysis approach?
• In the Business Partner model, what is the purpose of the reconciliation account entered on the company code segment of a supplier BP, and why must postings never override it manually at document level?
• When configuring supplier account groups in the Business Partner model, what design decisions govern how BP roles, number ranges, and field status link to vendor master data creation?
• During a large-scale migration using SAP Migration Cockpit (LTMC/LTMOM), the vendor master migration object is failing for a subset of records with MDG-managed vendors, but succeeds for non-MDG vendors. What is your troubleshooting approach?
• A plant is being set up for a new manufacturing facility, and business partner roles for suppliers need to be aligned with account groups. Purchasing users report they cannot maintain purchasing data for a newly created BP because the vendor role wasn't extended properly. What is likely wrong, and how do you resolve it?
• During hypercare after go-live, PO replication from Central Procurement to a connected S/4HANA system is failing intermittently, and business partner master data discrepancies are suspected as the root cause via MDG. How would you diagnose and resolve this?
• During cutover to S/4HANA, why must all vendor and customer master records be converted to Business Partners using CVI, and what is the impact if this step is skipped or done incorrectly?
• During a Fit-to-Standard workshop for a P2P migration to S/4HANA with Ariba integration, the client insists on retaining separate vendor master records per company code rather than adopting the Business Partner/CVI model with centralized synchronization. What is the correct governance guidance, and what is the risk of ignoring it?
• A purchase order is issued to a vendor, but invoices from that vendor are being routed to the wrong payee, and goods are being shipped to an incorrect address despite the vendor master appearing complete. How would you investigate and resolve this using partner function configuration?
• For an S/4HANA Public Cloud implementation integrating with SAP Ariba, why must suppliers be represented as Business Partners (BP) with the Customer/Vendor Integration (CVI) synchronization active, and what governance risk arises if this isn't enforced from day one?
• A global template configures one purchasing value key on the vendor master with standard reminder levels and an order acknowledgment requirement applied to all purchasing organizations sharing that vendor. Post-rollout, one purchasing organization reports false expediting alerts because its vendors never confirm POs, while another purchasing organization needs stricter tolerance days for the same vendor. As architect, how do you resolve this without manually maintaining vendor-specific value keys for thousands of vendors?
• In S/4HANA Public Cloud procurement, how are business partners (suppliers) typically created and integrated, given that classic supplier master maintenance transactions are restricted?
• During a P2P migration to S/4HANA for a multinational client, Business Partner/CVI conversion succeeds for most vendors, but vendors in countries requiring specific localization data (e.g., tax registration formats) are failing CVI sync when MDG pushes updates, causing downstream FI posting blocks. How would you root-cause and resolve this at architect level?
• 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?
• During a large-scale supplier Business Partner conversion using MDG as the governance layer, several thousand vendors fail CVI synchronization with errors related to duplicate tax numbers and inconsistent address data across company codes. As the lead architect, how would you approach root-causing and resolving this at scale?
• During a merger, two legacy systems used different vendor account groups mapped inconsistently to Business Partner roles: some suppliers were created with only the FI Vendor (FLVN00) role and lack the Purchasing role, while others have Purchasing but no FI role activated. Procurement users report they cannot maintain purchasing views, and AP reports certain suppliers cannot be used on invoices. How do you diagnose and resolve this at the account group and BP role level?
• A client migrating to S/4HANA Public Cloud has thousands of ECC vendor masters with duplicate tax IDs and inconsistent bank data. How would you approach the Business Partner supplier conversion in this constrained, standard-config environment?
• In a global rollout with multiple purchasing organizations sharing the same vendor, why do partner functions in the vendor master matter, and how should they be governed?

Related topics

Interview questions on this topic

• SAP MM / P2P Supplier and Business Partner interview questions
• SAP MM / P2P interview questions