Mastering SAP S/4HANA: The Ultimate 7-Step Guide to BP and CVI Configuration

If you have spent any time in the traditional SAP ERP environment, you are likely intimately familiar with the distinct silos of Transaction Codes like XD01 and XK01. For decades, Vendor and Customer masters lived in separate worlds, often resulting in data redundancy and a fragmented view of a single business entity. In SAP S/4HANA, the “old way” is gone.

The transition to the Business Partner (BP) model is a strategic pivot toward enterprise scalability. In this modern architecture, the Business Partner acts as the Leading Object. Through Customer-Vendor Integration (CVI), the BP API triggers an “Outbound” synchronization to the legacy Customer and Vendor master tables. This ensures that while the system uses a unified entry point, backward compatibility with finance and logistics modules is maintained via a sophisticated data buffer. While CVI configuration is often viewed as a “black box,” it can be mastered in seven logical steps.

1. The Shift: Why Business Partner (BP) is the New Standard

The traditional ERP master data model was built for a simpler time, but it carries three core limitations that stifle modern digital transformation:

2. Customer/Vendor Integration (CVI)

CVI assigns Customer and Vendor master data object to SAP Business Partner object and vice versa as shown in the below diagram.

A Business Partner is always created when a Customer or Vendor is created.

2. Phase 0: Pre-requisite Check

Before you touch CVI settings, your foundational organizational structure must be robust. As a senior consultant, I recommend verifying these “Big Four” before starting:

Link to each post is given below

3. How to Configure BP (Business Partners) and CVI (Customer-Vendor Integration) in 7 Steps

Step 1: Architecting Your Account Groups

Account Groups define the structural identity of your business entities. They determine field control, number range behavior, and how Customer/Vendor masters behave during CVI synchronization. A well‑designed Account Group strategy ensures clean BP → Customer/Vendor mapping without inconsistencies.

1.1 Define Account Groups For Customers

Customer Account Groups determine how Customer master data behaves during BP → Customer synchronization. They define field control, number ranges, and reconciliation logic.

Follow the below path:

We have defined Account Group “CUST” for our customers.

1.2 Define Account Groups For Vendors

Vendor Account Groups define how Vendor master data behaves during BP → Vendor synchronization. They control field selection, number ranges, and reconciliation accounts.

Follow the below path:

We have defined Account Group “SUPL” for our vendors.

Step 2: Establishing Number Ranges

Number ranges define the identity structure of your master data. In S/4HANA, consistent number ranges across BP, Customer, and Vendor objects dramatically reduce CVI errors and simplify UAT. Most high‑integrity implementations use a unified range (e.g., ZP) to maintain consistency.

2.1 Create Number Ranges for Customer Accounts

Follow the below path to create Customer number ranges:

Configure the Customer number ranges as shown below:

2.2 Create Number Ranges for Vendor Accounts

Follow the below path to create Vendor number ranges:

Configure the Vendor number ranges as shown below:

Step 3: Linking Ranges to Account Groups

Assigning number ranges to Account Groups is the technical bridge between BP and legacy Customer/Vendor masters. Without correct assignments, CVI will throw “Number range not defined” errors during BP synchronization.

3.1 Assign Number Ranges to Customer Account Groups

Follow the below path to assign number ranges to Customer Account Groups:

Assign number range “ZP” to Customer Account Group “CUST”.

3.2 Assign Number Ranges to Vendor Account Groups

Assign number range “ZP” to Vendor Account Group “SUPL”.

Step 4: Define Number Range for Business Partners

The Business Partner object requires its own number range, independent of Customer and Vendor ranges. However, aligning all three ranges (BP, Customer, Vendor) is one of the strongest best practices in S/4HANA. It eliminates confusion, simplifies UAT, and ensures predictable CVI synchronization.

Use Transaction BUCF to define the BP number range. Create a range that mirrors the Customer/Vendor number range (e.g., ZP) to maintain consistency across all master data objects.

Below is the number range created for BP, matching the ranges used for Account Groups CUST and SUPL:

Step 5: The Critical Link – Grouping & Assignment

This step determines how BP numbers are generated and how they synchronize with Customer/Vendor numbers. BP Grouping controls internal vs external number assignment and is directly tied to CVI behavior.

The recommended approach for most S/4HANA implementations is:

✔ Use External Standard Grouping
✔ Assign the same number range used for Customer/Vendor (e.g., ZP)

5.1 Troubleshooting SAP S/4HANA BP Synchronization Errors

During BP Grouping configuration, you may encounter the runtime dump DYNP_TOO_MANY_RADIOBUTTONS_ON.

a) Reason for the Error

b) Resolution

Step 6: Directional Synchronization (CVI Settings)

This is the heart of CVI configuration. Here you define how the Business Partner object synchronizes with legacy Customer (KNA1) and Vendor (LFA1) tables. Every time a BP is saved, CVI triggers an “Outbound” synchronization to update Customer/Vendor masters.

6.1 Number Assignment for Direction BP to Customer

6.2 Number Assignment for Direction BP to Vendor

Step 7: Now Create Our First BP Vendor & First BP Customer

All BP & CVI configuration is now complete. This step validates your configuration by creating your first BP Vendor and BP Customer and ensuring CVI synchronization works flawlessly.

7.1 Creation of First BP Vendor

Start Transaction BP.

7.1.1 Creation of Role “000000 – Business Partner (General)”

Input the name of the BP Vendor you want to create and click on Create Organization.

Fill out address and communication details such as language, postal code, and region.

7.1.2 Creation of Role “FLVN00 – FI Vendor”

Select the role FLVN00 – FI Vendor from the dropdown. This role contains financial fields such as reconciliation accounts, payment terms, and company code assignments.

7.1.3 Creation of Role “FLVN01 – Supplier (Purchasing)”

Switch to the role FLVN01 – Supplier (Purchasing). This role contains purchasing‑related fields such as order currency, payment terms, and purchasing organization data.

Once all mandatory fields are filled, save the BP. The system will automatically create the corresponding Vendor master (LFA1) through CVI synchronization.

7.2 BP for Embedded & Decentralized EWM

We must create a BP with plant assignment to declare it as the Default Party Entitled to Dispose in Embedded EWM.

Now we will declare our BP as “Default Party Entitled to Dispose” for plant PA10 / EWM WM PA11.

7.3 Creation of First BP Customer

Now that BP Vendor creation is complete, we proceed with creating the BP Customer. This step validates Customer‑side CVI synchronization and ensures that BP roles, number ranges, and field mappings are correctly aligned for Customer master creation.

Start Transaction BP.

Input the name of the BP Customer you want to create and click on Create Organization.

7.3.1 Creation of Role “000000 – Business Partner (General)”

Customer Name is PA01CUST01 – “Houston Direct Auto”.

Select Material Group “BP03”.

First create the General Role “000000 – Business Partner (General)”.

Input address details such as street number, postal code, city, region, etc., as shown in the screenshot above.

7.3.2 Creation of Role “FLCU00 – FI Customer”

Switch to the role FLCU00 – FI Customer. This role contains financial fields such as reconciliation accounts, payment terms, dunning data, and company code assignments.

7.3.3 Creation of Role “FLCU01 – Customer (Sales & Distribution)”

Switch to the role FLCU01 – Customer (Sales & Distribution). This role contains sales‑related fields such as Sales Organization, Distribution Channel, Division, shipping conditions, partner functions, and delivery‑related data.

Once saved, the system automatically creates the Customer master (KNA1) through CVI synchronization, completing the BP → Customer integration.

Input reconciliation account 21100000 (pick from the downloaded GL Account master).

You can also create GL 21100000 manually.

7.1.3 Creation of Role “FLVN01 – Supplier”

Select role FLVN01 – Supplier from the dropdown.

This creates the Vendor in Purchasing Organization PA10.

We have successfully created our first vendor PA01VEN01.

7.2 BP as “Default Party Entitled to Dispose” for Embedded & Decentralized S/4HANA

We must create a BP with plant assignment to declare it as the Default Party Entitled to Dispose in Embedded EWM.

Now declare BP as Default Party Entitled to Dispose for plant PA10 / EWM WM PA11.

7.3 Creation of First BP Customer

Start Transaction BP.

Enter Customer Name PA01CUST01 – Houston Direct Auto and click Create Organization.

7.3.1 Creation of Role “000000 – Business Partner (General)”

Enter address details such as street number, postal code, city, region, etc.

7.3.2 Creation of Role “FLCU01 – Customer (Sales & Distribution)”

Choose role FLCU01 – Customer and enter:

Sales Org: PA10 – IC Car Sales Organi
Distribution Channel: PA – Car Dealers
Division: DC – Diesel Car

Order Tab: Cust.Pric.Procedure = IC – IC CarCust PriceP

Shipping Tab:

• Delivery Priority: 2 – Normal
• Delivering Plant: PA10 – PPIC C
• Shipping Conditions: P1 – Standard

Billing Tab:

• Tax Classification: 1 – Liable for Taxes
• Acct Assmt Grp Cust: 01 – Domestic Revenue

Save the entries.

7.3.3 Creation of Role “FLCU00 – FI Customer”

Enter reconciliation account 112100000 – PPIN‑Receivables Domestic.

7.4 Creation of BP Vendor for Vendor Consignment

For Vendor Consignment, the BP Vendor must have specific fields maintained in role FLVN01.

7.5 Creation of BP Customer & Supplier for STO with Delivery Scenario

For STO with delivery scenario:

• Supplying Plant must be created as Supplier in Receiving Plant’s Purchasing Organization.
• Receiving Plant must be created as Customer in Supplying Plant’s Sales Org & Distribution Channel.

7.5.1 Creation of BP Supplier for STO with Delivery Scenario

Create plant PA10 as Supplier PA10_PLANT in Receiving Plant’s Purchasing Org.

7.5.2 Creation of BP Customer for STO with Delivery Scenario

Plant PA20 is Customer.

7.6 Creation of BP Customer & Supplier for Inter‑Company STO with Delivery & Billing

Receiving Plant PP10 belongs to a different Company Code.

• Supplying Plant must be Supplier in Receiving Plant’s Purchasing Org.
• Receiving Plant must be Customer in Supplying Plant’s Sales Org & Distribution Channel.

7.6.1 Creation of BP Supplier for Inter‑Company STO

Create plant PA10 as Supplier PA10_PLANT in Purchasing Org PP10.

Enter Schema Group Supplier = 02 – SPL Sch.Grp IC STO Dlv Billing.

Conclusion: Mastering BP & CVI in SAP S/4HANA

Business Partner and Customer‑Vendor Integration (CVI) form the backbone of master data in SAP S/4HANA. When configured correctly, they eliminate redundancy, ensure consistency across Finance and Logistics, and provide a unified, scalable master data model for the entire enterprise.

By following the structured 7‑step approach in this guide — from Account Groups and Number Ranges to BP Grouping, CVI Mapping, and advanced STO/Inter‑Company STO scenarios — you ensure a clean, error‑free BP/CVI setup aligned with SAP best practices and real‑world project requirements.

Your system is now ready for advanced BP roles, industry‑specific extensions, and future S/4HANA innovations.

FAQ : CVI – Customer Vendor Integration

Image Courtesy: Flat vector created by Freepik