Business Partner in SAP S/4HANA

"No number range assigned to grouping"

Cause: The BP grouping has no number range, or the range does not match the customer account group range.

Fix: Maintain the grouping and its number range (SPRO → Cross-Application Components → SAP Business Partner), and align internal/external assignment with the customer account group.

Sales area data missing on the BP

Cause: Role FLCU01 (SD Customer) has not been assigned, or the sales area was never extended.

Fix: Open the BP, add role FLCU01, then maintain the sales area data. Without FLCU01 there is no KNVV record and the BP cannot be used in a sales order.

Duplicate business partners created during migration

Cause: Customers and vendors representing the same legal entity were converted separately, or the run was executed twice.

Fix: Run BUPA_CHECK_MIGRATION to identify duplicates and merge them. Fix the grouping/mapping before rerunning.

Contact persons not linked after migration

Cause: Old KNVK contact records did not convert into BP relationships.

Fix: Create the relationship manually (BUPA_REL) with role BUP001, or re-run the contact-person mapping step.

CVI synchronisation errors on save

Cause: A field mandatory for BP is empty in the customer master (industry, search term, tax data).

Fix: Fix the underlying data in the customer master, then re-trigger synchronisation. Always clean data before conversion, not after.

Credit master not visible after migration

Cause: Classic credit data (KNKK) was not migrated into FSCM credit segments.

Fix: Assign role UKM000 and migrate credit master data; maintain the credit segment in UKM_BP.

What is Business Partner in SAP S/4HANA?

Business Partner (BP) is the single, central object used to represent customers, vendors, contact persons, and prospects in SAP S/4HANA. Instead of maintaining separate customer and vendor masters with different transactions, you create one Business Partner and assign it roles (for example FLCU00 for FI Customer and FLCU01 for SD Customer). BP is not optional in S/4HANA — it is the mandatory entry point for creating and changing customer and vendor master data, and it writes through to the classic tables (KNA1, KNB1, KNVV) via CVI synchronisation.

Why is XD01 not working in S/4HANA?

In SAP S/4HANA, the classic customer master transactions XD01/XD02/XD03 (and XK01, VD01, FD01) are no longer the way to create master data. The Business Partner transaction BP replaces them. Depending on the release and configuration the old transactions may be blocked, display-only, or redirect you to BP. This is a deliberate SAP simplification: one object, one transaction, many roles. If someone still recommends XD01 as the way to create a customer in S/4HANA, their knowledge predates the simplification.

What is the difference between FLCU00 and FLCU01?

They are two different BP roles for the same customer. FLCU00 (FI Customer) holds the company-code data — reconciliation account, payment terms, dunning — and populates KNB1. FLCU01 (SD Customer) holds the sales-area data — sales organisation, distribution channel, division, shipping conditions, customer pricing procedure — and populates KNVV. A sold-to party used in sales orders typically needs both roles. If sales area data is missing on a BP, the usual cause is that FLCU01 was never assigned.

What is CVI (Customer Vendor Integration)?

CVI is the synchronisation layer that keeps Business Partner data and the classic customer/vendor master tables in sync. When you save a BP with role FLCU00 or FLCU01, CVI writes the corresponding KNA1/KNB1/KNVV records so that existing programs, reports, and custom code continue to work. CVI is also the mechanism used during migration: it converts existing ECC customers and vendors into Business Partners, using a mapping between customer account groups and BP groupings.

What is a BP grouping and why does it matter?

A BP grouping determines the number range for the Business Partner — whether the number is assigned internally by the system or entered externally, and from which range. During migration, each customer account group is mapped to a BP grouping (for example Sold-to 0001 to a Z001 grouping) so converted customers keep a predictable numbering scheme. Most number-range errors during BP creation or migration trace back to grouping configuration.

Do KNA1 and KNVV still exist in S/4HANA?

Yes. KNA1, KNB1, and KNVV still exist and are still populated — but through CVI synchronisation when a Business Partner is saved, not through direct creation in XD01. You can still read from them in reports and custom code. The important discipline is that BUT000 and the BP framework are now the leading source of truth, and master data must be created and changed through the BP transaction.

How do you migrate existing ECC customers to Business Partner?

At a high level: activate the CVI business function in ECC (SFW5), configure the mapping from customer account groups to BP groupings (CVI_GROUPING_SETUP), map customer fields to BP fields (CVI_MAP_CUST_VEND) and fix gaps, test-convert a representative sample (CVI_CHECK_CUSTOMER), then run the mass conversion (CVI_MASS_MIGRATION / program BPUSMCS01) in test mode before productive mode. After migration, validate with BUPA_CHECK_MIGRATION and confirm roles, sales area data, and credit master are correct. The single biggest risk is poor customer master data quality — clean the data in ECC before converting, never after.