Customer and Business Partner

Lessons in this topic

• Business Partner Model and Customer Vendor Integration (CVI) in S/4HANAExplains how S/4HANA replaces direct customer master maintenance with the Business Partner model, how CVI synchronizes BP with customer and vendor master data, and what this means for configuration and troubleshooting.
• Partner Functions and Partner Determination Procedures in Sales DocumentsLearn how partner functions (Sold-to, Ship-to, Bill-to, Payer) are defined, grouped into partner determination procedures, and assigned to account groups and sales document types so the correct business partners flow automatically into every sales transaction.
• Customer Vendor Integration (CVI) Architecture and Synchronization TroubleshootingUnderstand how Customer Vendor Integration synchronizes classic customer and vendor master records with the Business Partner model in S/4HANA, why synchronization can break, and how to diagnose and resolve mismatches in a production support context.
• Customer Master Data Fundamentals: Structure, Account Groups and Partner FunctionsIntroduces why customer master data is foundational to SD, how it is structured across general, company code, and sales area data, and how account groups and partner functions drive document behavior.
• Enterprise Governance for Business Partner: Migration Strategy, MDG Integration and Multi-System ConsolidationArchitect-level guidance on designing and governing Business Partner as the single master data object across a multi-system, multi-country S/4HANA landscape, covering migration approach, MDG-driven governance, data quality controls and long-term operating model.

Interview questions covered

• A customer complains that invoices are being sent to the wrong bill-to party after a partner function change was made at the customer master level. The change was intended to apply only to new orders. What is likely happening, and how should partner function changes be managed?
• After a merger, a customer hierarchy spans nodes assigned to different credit control areas and company codes. Once hierarchy-based rebate accrual postings go live, finance reports rebate accruals hitting incorrect reconciliation accounts for certain subsidiary nodes. As the architect, how would you diagnose whether the customer hierarchy structure itself is driving this FI account determination issue?
• During a merger, two legacy companies each maintain the same customer under different account groups in different sales areas, and now both need to be consolidated into one BP with a shared sales area structure. What is your approach to resolving the account group conflict and consolidating the sales areas?
• What is sales area data on the customer master, and why is it maintained separately from the general and company code data?
• In a Business Partner-centric S/4HANA landscape, how should number ranges for customer account groups be designed to avoid conflicts between internal and external numbering, and what happens if the BP number range overlaps with an existing account group range?
• Multiple regional teams independently maintain customer master records, resulting in duplicate customers and inconsistent sales area data. What governance approach would you recommend using MDG or Business Partner controls?
• A regional sales manager wants to view all customers assigned to their sales area in a Fiori app, but the app shows fewer customers than expected. What sales area assignment issues would you check first?
• Sales orders in a specific sales office are inconsistently picking the wrong ship-to partner despite correct customer master partner determination. How would you diagnose and resolve this in an MDG-integrated landscape?
• What is the purpose of a customer account group in SAP SD, and how does it influence credit management setup for a customer master record?
• A business unit wants to onboard a new customer that will order under two different sales areas sharing the same account group. What master data governance considerations must you address?
• A global rollout project reports that partner determination on customer-sales area data is inconsistent across regions, causing wrong ship-to or bill-to defaults on sales orders created via an MDG-driven mass upload. How would you troubleshoot this?
• In an S/4HANA Business Partner landscape, how does the customer account group configuration interact with material sales view data to determine which fields are mandatory or relevant when creating a sales order?
• Your organization is migrating from classic customer master maintenance to Business Partner-based customer creation. A consultant proposes reusing the existing account group directly as the BP grouping. What issues should you anticipate and how should the design be validated?
• A Fiori-based mass update adds a new sales area to a group of customers under existing MDG governance, but ship-to partner functions default incorrectly for orders created in the new sales area while the sold-to and bill-to remain correct. How would you diagnose the root cause?
• During a Business Partner migration, material sales views for a set of materials are not appearing correctly on sales orders for certain customer account groups, though the materials exist in the Sales Org/Distribution Channel combination. How would you investigate the integration between Material Sales Views and Customer Account Group settings?
• What is a customer hierarchy in SD, and what business purpose does it serve?
• A regional finance team reports that a newly created customer via Fiori Manage Customer Master Data app cannot be used in a sales order because the required sales area is missing. Walk through how you would diagnose and resolve this.
• When extending a customer to a new sales area in a global rollout governed by MDG, what enterprise structure and partner determination considerations must be validated before the extension is approved?
• What is the purpose of the customer account group in SAP SD, and how does it control customer master data maintenance?
• A newly onboarded customer's sales order keeps failing with 'sales area data incomplete' even though the customer master appears fully maintained. As the architect, how would you diagnose and resolve a systemic account group misconfiguration causing this?

Related topics