ERPClimb logoERPClimb

SAP MM / P2P Supplier and Business Partner Interview Questions

In SAP MM / P2P rounds, supplier and business partner questions are where configuration knowledge meets day-to-day behaviour — what a setting does, and what breaks in a live system when it is wrong.

Foundational and intermediate coverage of supplier master data in SAP MM/P2P, covering the classic vendor master model, the mandatory Business Partner (BP) approach in S/4HANA, the relationship between BP and vendor records, and the configuration needed to keep both synchronized in real projects.

This page carries 28 reviewed SAP MM / P2P supplier and business partner interview questions, each with a complete written answer and no sign-in required. The set breaks down into 4 foundational, 11 mid-level and 13 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

Rehearse these out loud rather than reading them. If you can explain each answer in your own words, including one realistic way it goes wrong on a project, you are covering what a normal SAP MM / P2P round on supplier and business partner expects.

28 Supplier and Business Partner questions with answers

easySupplier and Business Partner

1. 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?

The reconciliation account links the vendor subledger to the correct GL control account in FI, ensuring every AP posting automatically rolls up to the right balance sheet account without direct postings to the GL. It is maintained once per company code segment on the BP vendor role. Allowing manual override at document level would break subledger-to-GL reconciliation and violate the standard prohibition on posting directly to reconciliation accounts.
easySupplier and Business Partner

2. 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?

S/4HANA enforces the Business Partner as the single leading object for vendors and customers; CVI (Customer/Vendor Integration) synchronizes BP with the classic vendor/customer master. If CVI mapping is incomplete or inconsistent, purchasing, invoice verification, and FI postings fail because the system cannot resolve the BP-vendor link, causing PO creation errors and blocked hypercare transactions.
easySupplier and Business Partner

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

In S/4HANA Public Cloud, supplier master data is maintained exclusively through the Business Partner model using Fiori apps like Manage Business Partner (Supplier role) or via the Business Partner API/OData services for integration with upstream systems such as Ariba, MDG, or a central master data hub. Classic MM transactions like XK01/MK01 are not available; CVI runs in the background automatically. Bulk creation is done via Migrate Your Data apps or API-based mass upload, not LSMW.
easySupplier and Business Partner

4. When converting ECC vendor masters to Business Partners during an S/4HANA transformation, what is the correct direction of data synchronization and why does SAP enforce it?

In S/4HANA, Business Partner is the leading object; vendor master data is derived from BP via the Customer/Vendor Integration (CVI) synchronization. You create or maintain the BP first, and CVI automatically generates the linked vendor (and FI vendor) records in the background tables. Direct creation of vendor master via classic transactions like XK01 is blocked or redirected in S/4HANA to enforce this BP-centric model, ensuring FI and MM data consistency.
mediumSupplier and Business Partner

5. 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?

Account group configuration for suppliers is driven through BP roles (FLVN00/FLVN01) mapped to vendor account groups; each account group defines number range assignment (internal/external), field status (required/optional/suppressed) per screen, and whether the vendor is one-time, standard, or intercompany. In S/4HANA, BP is the leading object, so account group also determines which BP roles are mandatory and how the vendor view (Purchasing/Company code) is synchronized via CVI.
mediumSupplier and Business Partner

6. 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?

Likely the business partner was created with only the FI vendor role (or general BP role) but not extended with the purchasing organization-level vendor role/account group mapping, so purchasing views (purchasing data, plant data) are missing. Resolve by using BP transaction to extend the vendor role for the required purchasing organization, ensuring the BP account group's number range and role configuration link correctly to vendor account group in customizing (BP role category). Also verify the purchasing org is assigned to the plant's company code.
mediumSupplier and Business Partner

7. 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?

Check the vendor master's partner determination for the purchasing organization: partner functions such as ordering address (OA), goods supplier (GS), invoicing party (PI), and payee (PY) may point to different partner numbers than the main vendor. If PI or PY partner functions were not maintained or were defaulted incorrectly during vendor creation, invoices and payments route to the wrong party. Correct the partner function assignment in the vendor master (or BP relationship in S/4HANA), verify the partner determination procedure linked to the account group, and reissue or correct open documents referencing the wrong partner.
mediumSupplier and Business Partner

8. 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?

The account group controls the vendor's number range and field status, including whether purchasing organization data can be created, but the actual authorization to maintain info records depends on the purchasing organization assignment made when extending the BP's purchasing role. If a supplier is extended to a purchasing org without the correct account group field status enabling purchasing data, buyers cannot create or update info records, leading to inconsistent pricing data and fragmented vendor records across purchasing orgs.
mediumSupplier and Business Partner

9. 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?

Confirm the BP account group configuration determines which BP roles (Business Partner General, FI Vendor, Purchasing/Supplier) are automatically derived or available for extension; if a supplier was created under an account group not linked to the purchasing role, the vendor purchasing data (LFM1) never gets created, blocking PO/info-record maintenance, and similarly missing FI role blocks vendor company code data for invoicing. Fix by extending the BP with the missing role via BP transaction, ensuring the account group-to-role mapping and number range assignment are corrected for future creations, and mass-extend affected suppliers.
mediumSupplier and Business Partner

10. 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 Public Cloud, custom CVI configuration is not possible, so cleansing must happen before load using SAP Migration Cockpit staging tables or Fiori apps. Run duplicate and tax-ID checks in the legacy system, standardize bank data per country schema, and use the predelivered BP grouping/number ranges. Any exceptions requiring custom mapping must be handled through data cleansing tools upstream, not system configuration, since Public Cloud restricts CVI customization.
mediumSupplier and Business Partner

11. A services vendor under evaluation has purchase orders spanning multiple cost centers and account assignment categories (K for standard cost center, mixed limit items for unplanned services). Finance asks whether this affects supplier evaluation scoring for price and delivery performance. How would you assess and address this?

Supplier evaluation scoring (price, quality, delivery) is generally aggregated at vendor/material or vendor/purchasing-org level and is largely independent of account assignment category, since scoring criteria draw from PO price history, GR timeliness, and quality notifications rather than cost object splits. However, if limit items lack GR/SES-based delivery data, delivery performance scoring may be skewed or incomplete for those lines. I'd verify which PO items feed into evaluation criteria, exclude non-representative limit items if needed, and confirm cost center variety doesn't distort price comparison baselines across dissimilar service categories.
mediumSupplier and Business Partner

12. How would you configure supplier evaluation criteria and scoring to integrate with output-triggered communication for supplier scorecards in SAP MM?

Configure evaluation criteria and sub-criteria weightings in the vendor evaluation customizing (main criteria like price, quality, delivery, service), then link scoring to purchasing organization-specific settings. Output of scorecards typically uses NAST-based condition records or, in S/4HANA, BRFplus/Adobe Form output determination tied to a message type. You'd set up a partner function for evaluation recipients and schedule output via a job or manual trigger from the vendor evaluation transaction, ensuring FI-AP master data (vendor account group) is consistent for output address determination.
mediumSupplier and Business Partner

13. 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?

The purchasing value key stores default purchasing conditions such as reminder levels, order acknowledgment requirements, minimum order value and tolerance limits, and it defaults into purchasing documents when a vendor is used. When onboarding is standardized through vendor account groups or, in S/4HANA, business partner roles with vendor grouping, the purchasing value key should be assigned consistently as part of the onboarding template so buyers do not need to manually configure tolerances per vendor, reducing inconsistent enforcement of acknowledgment or reminder policies across purchasing organizations.
mediumSupplier and Business Partner

14. Your organization uses MDG to govern vendor master data feeding into SAP for invoice posting. Auditors flag a case where a vendor was created twice with slightly different bank details, resulting in duplicate payments. What audit controls would you recommend to prevent recurrence?

I would recommend MDG duplicate-check rules on vendor name/address/tax ID before activation, mandatory dual control for bank detail changes, sensitive field change reports (vendor master change documents) reviewed periodically, and automated duplicate invoice checks in LIV using vendor plus invoice reference plus amount. Combined with periodic vendor master audits and segregation of duties between vendor creation and payment run execution, these controls close the gap end to end.
mediumSupplier and Business Partner

15. A procurement lead wants to introduce a formal supplier evaluation process for service vendors, tying evaluation scores into future release strategy or sourcing decisions. What are the key design elements and limitations you would flag?

Design should use Supplier Evaluation (in S/4HANA, via Supplier Evaluation app/MM-SRV integration or classic LB01/LB02 in ECC) capturing criteria like price, quality, delivery/service timeliness, and compliance, scored periodically and stored against the vendor. Scores can inform sourcing decisions manually (e.g., quota arrangement adjustments) but are not natively wired into PO release strategy characteristics, so any automated linkage requires custom logic or manual governance. Flag that evaluation data quality depends on consistent GR/service confirmation and invoice timeliness data feeding the criteria.
hardSupplier and Business Partner

16. 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?

Enforce single-direction or clearly governed bidirectional sync rules between Ariba supplier records and BP/CVI, with CVI customizing ensuring vendor and BP are always created/updated together, not independently. Implement number range and matching logic (tax ID, DUNS) to prevent duplicate creation, and restrict direct vendor creation in FI/MM outside the governed integration flow. Regularly run CVI consistency checks and reconcile Ariba supplier IDs against SAP BP numbers before output documents trigger.
hardSupplier and Business Partner

17. 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?

Design BP account groups aligned to supplier categories, then use field status groups per role (e.g., FLVN1 for purchasing data) to control which fields procurement vs finance can maintain. Use BP role-based authorization concepts, workflow-based approval for critical fields (payment terms, bank data), and periodic data quality reports. Segregate sensitive fields (bank details) requiring dual control, and leverage change document monitoring for audit.
hardSupplier and Business Partner

18. 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?

Investigate whether CVI synchronization mapping (BP role to vendor account group) is configured consistently across regions, since template rollouts often diverge in customizing between initial pilot and later waves. Check MDG's matching/duplicate-check rules for tax number or name/address fuzzy matching gaps causing false negatives. Review the direction of synchronization (BP-to-vendor vs vendor-to-BP) and confirm number range assignments aren't overlapping across regions feeding the same MDG hub.
hardSupplier and Business Partner

19. 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?

Check whether MDG is the system of record and whether those vendor BPs are locked for direct changes outside MDG replication (BD staging or change requests). Migration Cockpit writes directly via BAPIs, which can conflict with MDG governance locks or trigger duplicate change request workflows. Validate the migration object's field mapping against MDG-required fields, review the staging tables (LTMC) for structure mismatches, and coordinate with MDG team to either exclude MDG-governed records from Cockpit load or replicate post-MDG.
hardSupplier and Business Partner

20. 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?

First check the integration monitoring dashboard for replication error logs to isolate whether failures correlate with specific vendor/BP records. Cross-reference the failing BP IDs against the MDG change request history to identify incomplete or pending governance approvals. Common root cause is BPs replicated to the connected system before MDG fully activates all roles (vendor, FI); fix by re-triggering MDG distribution and re-running the failed PO replication once BP is fully synchronized.
hardSupplier and Business Partner

21. 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?

In S/4HANA, Business Partner is the leading object and vendor master is only maintained via CVI-synchronized BP; you cannot bypass BP/CVI to keep legacy vendor-only records. The guidance is to design BP roles and number ranges so each vendor is represented once as BP with appropriate purchasing/company code views, not duplicate BP records per company code. Ignoring this risks broken CVI synchronization, duplicate vendor masters, failed Ariba supplier sync (which expects a single BP-driven vendor per supplier), and reconciliation issues in FI-AP.
hardSupplier and Business Partner

22. 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?

In S/4HANA, vendor master data is fundamentally BP-based, with CVI synchronizing BP and vendor roles; Ariba supplier integration (via Ariba Network or SAP Ariba Supplier Lifecycle and Performance) replicates supplier records that must land as BPs, not classic vendor-only records, since standalone vendor tables aren't the master data model anymore. If CVI isn't enforced from day one, supplier records can be created inconsistently, causing duplicate BPs, broken vendor role assignment, or failed PO/invoice postings referencing incomplete vendor master data.
hardSupplier and Business Partner

23. 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?

The purchasing value key sits on the vendor master (purchasing data), not per purchasing organization, so one key cannot satisfy conflicting org-level requirements for the same vendor. Resolution is to define multiple purchasing value keys aligned to regional or business-rule segments, and drive assignment during vendor onboarding via mass maintenance or LSMW based on the region attribute rather than one-off manual edits. For truly org-specific tolerance or acknowledgment needs, override at the purchasing info record level instead of forcing a vendor-master-wide change, preserving the global default while allowing local exceptions.
hardSupplier and Business Partner

24. 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?

Investigate whether MDG's country-specific validation rules (BP address/tax number format) differ from the legacy vendor master data patterns, since CVI enforces BP number ranges and role assignments that must satisfy localization checks before FI can post. Check BP role BUP003/FLVN00-equivalent role sync, tax number category mapping per country, and whether MDG replication model includes country-specific extension fields. Resolution typically requires country-specific MDG validation rules aligned to CVI mapping tables (e.g., FSTAX categories), plus a phased data cleanse before final CVI activation, run country-by-country rather than globally.
hardSupplier and Business Partner

25. 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?

I would first isolate failures by category using the CVI conversion error logs, separating true data-quality issues (duplicate tax IDs, conflicting addresses) from configuration issues (missing number range mapping, BP grouping). For data-quality errors, I would engage MDG's duplicate check and data quality rules before re-triggering conversion rather than forcing overrides. I would also validate that address versioning per company code is correctly mapped to BP address usages, and run conversions in batches with reconciliation reports rather than a single mass run to control blast radius.
hardSupplier and Business Partner

26. 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?

Partner functions like ordering address, invoice presenting party, and goods supplier allow one vendor master to represent different roles across the procurement process, which is critical when a single legal vendor has separate ship-from locations or invoicing entities used by multiple purchasing organizations. Governance requires defining default partner roles at the purchasing organization level in the vendor master and ensuring consistent maintenance so purchase orders correctly derive ordering address and invoice recipient without manual override at transaction time, avoiding payment or delivery misdirection.
hardSupplier and Business Partner

27. When designing number range strategy for supplier master (Business Partner/vendor) records across multiple company codes in a global template, what governance decisions must be made and why?

You must decide whether to use a single global number range group (internal or external) shared across all company codes via one BP account group, or segment ranges by region/entity for traceability, ensuring number ranges assigned to BP grouping align consistently with the vendor account group used for company-code-specific and purchasing-org data extension. Internal ranges avoid duplicate-key errors but reduce meaningful numbering; external ranges support legacy migration but risk gaps/duplicates if not centrally governed. Number range assignment is maintained in BP grouping configuration, not directly in classic vendor account group transactions.
hardSupplier and Business Partner

28. In a global template rollout spanning multiple company codes and countries, how would you design a governance process for field selection on vendor account groups to balance central control with country-specific statutory and tax requirements?

Establish a tiered governance model: define a global template account group field selection baseline with core mandatory fields (name, address, tax classification), then use account group field status combined with company-code-level screen layout supplements for statutory fields like withholding tax type or local tax IDs. Route local exceptions through a change control board so deviations are documented, tested in a sandbox, and approved before transport. Maintain a central field-status matrix per account group and country to prevent conflicting or duplicate configuration, and use regression testing before each rollout wave to confirm no unintended global impact.

Related lesson

Configuring Business Partner to Supplier (Vendor) Synchronization

Related topics

Invoice VerificationValuationAutomatic Account DeterminationService ProcurementSource DeterminationS/4HANA MM Transformation, Ariba, Migration, Public Cloud and ArchitectureMaterial MasterPurchase OrderRelease StrategyFlexible WorkflowPhysical InventoryGoods Receipt and Goods Issue

Next practice step

Practice with Interview AITake a mock test