Before uploading customer or supplier data, verify the Business Partner and Customer/Vendor Integration foundation. A perfectly formatted migration template cannot compensate for a missing role, incompatible number range or incorrect mapping between a Business Partner grouping and a customer or supplier account group.
The Galal Academy lesson demonstrates this foundation in an SAP S/4HANA 2022 environment. SAP documentation may call CVI “Customer/Supplier Integration” in newer releases. Exact configuration paths and delivered roles can differ, so use the system's own message long text and release documentation as the final reference.
Understand the three layers
A Business Partner holds general identity and address data. Customer and supplier roles extend that partner with application-specific data. In the demonstration, a customer is built from a general Business Partner role, a Financial Accounting customer role, and a Sales and Distribution customer role. The exact roles required depend on the process you are migrating.
CVI is the integration framework that keeps Business Partner and customer or supplier master data aligned. SAP states that the Business Partner is the leading object in SAP S/4HANA and that customer and supplier records must be converted for a system conversion. This does not mean every error is a “CVI error”; some are ordinary source-data or organizational-validation failures.
Prerequisite checklist
Confirm these items before blaming the spreadsheet:
- required Business Partner roles exist and are permitted for the target scenario;
- BP groupings and their number ranges are defined;
- customer and supplier account groups and number ranges are defined;
- BP groupings are mapped to the correct customer or supplier account groups;
- internal or external numbering is consistent across the mapping;
- company code, sales area and purchasing organization assignments required by the chosen roles exist;
- reconciliation accounts, payment terms and other mandatory target values are valid;
- country-specific tax and address checks reflect the approved test or production design.
Do not disable a validation just to get a file through. A test-system exception demonstrated for fictional data is not automatically suitable for production.
Use the message to classify the failure
| Symptom | Evidence to collect | Next check |
|---|---|---|
| Number cannot be assigned | BP grouping, account group, internal/external flag, attempted number | Compare both number-range definitions and mapping |
| Customer or supplier role fails | Role, company code or sales-area/purchasing data, full long text | Check required organizational assignments and mandatory fields |
| Duplicate or existing instance | Source key, migration-project history, previously migrated BP number | Determine whether the row was already staged or migrated |
| Invalid tax or address data | Country, tax category, entered value, validation message | Correct source data or approved localization setup |
| Generic synchronization failure | Application log, BP/customer/supplier identifiers, preceding errors | Resolve the earliest specific error before rerunning |
Illustrative diagnosis
Suppose fictional source customer C-104 is assigned to BP grouping ZC01 with external numbering, while the mapped customer account group expects internal numbering. The upload may fail even though the name, address and company-code fields are complete. The corrective action is not to keep changing the customer number in Excel. First align the approved numbering design and CVI mapping, then regenerate or correct the source record and simulate again.
Rerun with control
After fixing the cause, rerun the smallest supported scope and verify the created Business Partner number, customer or supplier role, company-code data and sales or purchasing data. Keep the original error, corrective action and evidence of the successful result in the migration log.
Common mistakes
- Assuming BP, customer and supplier are unrelated masters in SAP S/4HANA.
- Copying a grouping without checking its number range.
- Correcting the spreadsheet when the missing item is configuration.
- Granting or changing broad permissions instead of resolving a functional setup issue.
- Rerunning after a generic message without reading the earliest detailed log entry.
Continue learning
Continue with the customer and supplier Migration Cockpit demonstration, a member lesson that applies the prerequisite setup to migration files.
FAQ
Does every Business Partner need both customer and supplier roles? No. Extend only the roles required by the business relationship and migration scope.
Can the same BP be both customer and supplier? The model supports multiple roles, but the target design, mappings and data governance must be deliberate.
Where should I verify the concept? See SAP Help on the Business Partner approach and Customer/Supplier Integration.
Watch the Business Partner and CVI setup lesson — free lesson
COMMUNITY DISCUSSION
Questions and practical insights
Ask about the process, share what worked, or help another SAP learner.