Sie sind auf Seite 1von 26

S/4HANA System Conversion Pre-check

setting up Customer Vendor Integration


Hi everyone, in this post I’m going to talk about setting up CVI in SAP ERP system, as it’s mandatory for
S/4HANA system conversion.

Before we start I want to make it clear that I’m not an expert in the topic of CVI configuration but when I
encountered this problem, I can’t find a detailed configuration guide for the necessary steps I should take, and
my goal was pass the per-check and perform a system conversion successfully, so let’s begin the topic.

So the basic configuration of CVI consists of three major steps:

1. Basic Configuration of CVI

2. Customer Integration Configuration

3. Vendor Integration Configuration


4. Dealing with Errors

1. Basic Configuration of CVI

Use SE38 to run report CVI_FS_CHECK_CUSTOMIZING, this will give us a glance of the current system
configuration about CVI.
Activate Postprocessing Office

Use transaction SPRO to activate the Postprocessing Office, its under the following path:

Cross-Application Components/General Application Functions/Postprocessing Office/Business


Processes/Activate Creation of Postprocessing Orders
Synchronization Control

Cross-Application Components/Master Data Synchronization/Synchronization Control

Use transaction SM30 to check view MDSV_CTRL_OPT for queue names for the following objects:

Source Object Target Object Queue Name


BP CUSTOMER MDS_BUPA_CUST
BP VENDOR MDS_BUPA_VEND
CUSTOMER BP MDS_CUST_BUPA
VENDOR BP MDS_VEND_BUPA
Now back to synchronization control preparation, click on queue processing to register the RFC queues with a
* mark at the end of every queue name.
The final results should looks like this

Synchronization Objects

Cross-Application Components/Master Data Synchronization/Synchronization Control/Synchronization


Control
Activate PPO Requests for Platform Objects in the Dialog
Activate Synchronization Options
Check / Activate Function Modules

Cross-Application Components/SAP Business Partner/Data Distribution/Activate Function Modules


2. Customer Integration Configuration

Check/Define Number Range for Customer Accounts

Accounts Receivable and Accounts Payable/Customer Accounts/Master Data/Preparations for Creating


Customer Master Data
Check/Define Assign Number Ranges to Customer Account Groups

This’s very important, based on the information in this view, we can generally decide which customer account
group should be included during the configuration of CI later on. If the “Number Range” column is empty, we
can assume that customer account group is not activated in the system.
Define BP Roles

SAP Business Partner/Business Partner/Basic Settings/Business Partner Roles

For each entry of the following BP Roles in BP Role Categories, add “BPUS” and “CHAN” with “Transaction
Allowed” Modification Indicator.

FLCU00

FLCU01

FLVN00

FLVN01
Define BP Role for Direction Customer to BP

Cross-Application Components/Master Data Synchronization/Customer/Vendor Integration/Business Partner


Settings/Settings for Customer Integration

The group information was mentioned earlier in section “Check/Define Assign Number Ranges to Customer
Account Groups”

Define Number Assignment for Direction Customer to BP

You may choose the group accordingly.


Define Groupings and Assign Number Ranges

Cross-Application Components/Master Data Synchronization/Customer/Vendor Integration/Business Partner


Settings/Settings for Customer Integration/Field Assignment for Customer Integration/Assign Keys
Finishing up configurations

Cross-Application Components/Master Data Synchronization/Customer/Vendor Integration/Business Partner


Settings/Settings for Customer Integration/Field Assignment for Customer Integration/Assign Attributes

Perform all the necessary configuration in this section. Nothing too much to talk about this step cause it only
involves select component from CVI then mapping it to BP.
As an example of one of the configuration
Run the Synchronize by using Synchronization Cockpit

Transaction MDS_LOAD_COCKPIT
Check the status, if everything was ok, you should be able to see a green icon in the status field. Otherwise it’ll
tell you what was wrong with the configuration, we’ll deal some of the error later on.
3. Vendor Integration Configuration

So basically it was the same procedure as Customer Integration, I’ll list the configuration steps here and skip
the picture

Check/Define Number Ranges for Vendor Accounts

Check/Assign Number Ranges to Vendor Account Groups

Define BP Role for Direction Vendor to BP

Define Number Assignment for Direction Vendor to BP

Run the Synchronize by using Synchronization Cockpit

Transaction MDS_LOAD_COCKPIT
If you’re not sure which vendor group was activated in the system, you can ask your functional specialist or
you can check the group one by one by using transaction MKVZ, if that group is empty, then you can excluded
it.

4. Dealing with Errors

Error “Tax Number categories xxx does not exist”

First, let’s maintain the Tax Number categories CN1 and CN5, to do so, use
transaction SM30 to maintain view V_TFKTAXNUMTYPE, copy an existing entry.
Now go to SPRO to Maintain Tax Number Categories, choose create new entries

Cross-Application Components/SAP Business Partner/Business Partner/Tax


Numbers
Error “address xxx not designated for organizations“

Cross-Application Components/SAP Business Partner/Business Partner/Forms of


Address
Finally, we can run the pre-check R_S4_PRE_TRANSITION_CHECKS in client 000 to
check if CVI problem was resolved.

check here

If you’re still facing error, please run ABAP report from SAP Note 2210486, this’ll give you a detailed
information about which customer or vendor that’s not synchronized correctly, then you can do some
investigation. My experience is that sometimes you may forgot some individual groups or accounts, there’s
also a possibility that you have some “invalid” master data in your system that you may need to manually
correct/delete from the system (double check it before delete any data in production system).

One last thing to mention, it was just a one-way synchronization, meaning only
Customer/Vendor to BP user, if you wish to configure two-way synchronization,
please check the relevant configuration instructions, but basically it’s the same
procedure.
That’s all for this topic, let me know if there’s anything else I can help or correct
me if I made any mistake here.

Regards,

Michael