SD_O2Cbeginner
Customer and Business Partner
Covers the customer master and Business Partner (BP) model in SAP SD, including data structure, the ECC-to-S/4HANA transition from XD/VD transactions to the BP-centric approach, account groups, partner functions, integration with FI (customer account) and CRM/cloud scenarios, and troubleshooting master data issues that affect order-to-cash processing.
Overview
Covers the customer master and Business Partner (BP) model in SAP SD, including data structure, the ECC-to-S/4HANA transition from XD/VD transactions to the BP-centric approach, account groups, partner functions, integration with FI (customer account) and CRM/cloud scenarios, and troubleshooting master data issues that affect order-to-cash processing.
Lessons in this topic
- SD Customer and Business Partner Part 1: Customer Master Data StructureHow customer master data is organized for order-to-cash: general data, company code data and sales area data, what each level controls in sales, delivery, billing and accounting, and how account groups and partner functions shape the customer.
- SD Customer and Business Partner Part 2: Business Partner Model and CVI ConfigurationHow S/4HANA replaces direct customer maintenance with the Business Partner: BP categories, roles, groupings and number ranges, and the Customer Vendor Integration (CVI) settings that synchronize BP data to customer and vendor tables — including number assignment and role-category mapping.
- SD Customer and Business Partner Part 3: Partner Functions and Partner DeterminationHow sales documents find their partners: partner functions (sold-to, ship-to, bill-to, payer and others), partner determination procedures for customer master, sales document header and item, delivery and billing, permitted functions per account group, and the source of each partner in the document.
- SD Customer and Business Partner Part 5: BP Governance — Migration Strategy, MDG and Multi-System ConsolidationArchitect's view of the Business Partner as the enterprise master data object: ownership and data standards, duplicate prevention, migration strategy (greenfield load vs brownfield conversion), SAP MDG for central governance, replication to other systems, and consolidating customers from several ERPs.
- SD Customer and Business Partner Part 4: CVI Architecture and Synchronization TroubleshootingHow CVI works under the hood and how to fix it when it fails: synchronization direction, link tables, the MDS load cockpit for mass synchronization, post-processing office for failed records, typical errors (number range, mandatory fields, role mapping, tax numbers) and the brownfield conversion prerequisites.
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?
- 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?
- 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?
- A customer complains that invoices are being sent to the wrong company entity even though the sold-to party is correct. How would you investigate and resolve this using partner function configuration?
- Your organization uses SAP MDG to govern customer master creation, but sales teams complain that newly approved customers cannot be used in sales orders for two days after MDG approval. How would you investigate and resolve this?
Related topics
SD_O2C
Pricing, Shipping, Billing, Revenue and Credit
SD_O2C
Sales Documents and End-to-End Order-to-Cash
SD_O2C
SD Foundation, Enterprise Structure and Master Data
SD_O2C
Advanced SD Scenarios, Integration and Production Support
SD_O2C
S/4HANA SD Transformation, Migration, Public Cloud and Architecture
SD_O2C
Enterprise Structure