Skip to Content

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


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./wp-content/uploads/2016/08/0104_1015303.jpg


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.









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





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







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.





You must be Logged on to comment or reply to a post.
  • Thank you Michael for this useful and detail post. I am going to carry out the same conversion in our system and I will give you and community feedback/ extra info if found.

      • Thank you, Michael!

        We have copied BUP001 to a new Role and mapped that Role to a new Account Group with a separate number range.  The BP will not flow to KNA1 to utilize as a partner function.

        The error we are getting is language key is missing.  I added Data Set BUA011 to BUP001 View to add language but I still receive the error. In the new Account Group, I have marked all the fields as optional.

        I also added Data Set CVIC08 to create the Sales View to utilize for partner function adds, but the view does not appear.

        Business Partner Error.png

        Thank you for any guidance you can offer.

        Business Partner Error.png
      • Hi Michael,

        I found in Note 928616 the fields that I must set as required in the field groupings and this corrected the error.  I did not have them set as required.  I had filled the fields but the fields apparently must be set to required.

        Thank you!

        • Hi Heidi,

          I'm glad your problem got solved, yes you're right, it's mandatory to maintain some of the basic information like country code, language key etc. before you start the actual synchronization job.

          Have a nice day!

  • Hi Micheal,

    As mentioned above have completed all the customization and  have run the synchronization cockpit as well without any errors for both the customers vendors and contact person. Also as per the note 2210486 , have checked both KNA1/CVI_CUST_LINk , LFA1 /CVI_VEND_LINK, KNVK/CVI_CUST_CT_LINK/CVI_VEND_CT_LINK with equal number of entries present in both the tables and there also no customization errors as per the report "CVI_FS_CHECK_CUSTOMIZING" either in business setting, customer or vendor .  In spite of all these i am getting the same  error in the report " R_S4_PRE_TRANSITION_CHECKS " 

    Overall SAP S/4HANA pre-transition check result: highest return code 12 !!"

    Message No. BL001 :- the same error as above. Can you help.


    • Hi Sai,

      Sorry I was struggling to get used to the new SCN site.

      It depends on your scenario, in our case we don't have BP user in our ERP system before the conversion, so we only did one-way synchronization, vendor/customer to BP user.

      Is it possible you have some "invalid" data in our source system for vendor/customer? We did have few invalid data entries and we have to manually delete them at the database level.

      Also, is it possible you missed any vendor/customer group? If you can please post the full error log or screenshot.


  • Hi Michael,

    Have done the customization as mentioned above and completed the synchronization cockpit as well without any errors for both the customer and vendors. As per the SAP Note 2210486 the tables KNAL/CV_CUST_LINK, LFA1/CVI_VEND_LINK , KNVK/CVI_CUST_CT_LINK/CVI_VEND_CT_LINK also have equal no of entries , but still getting the same message Overall SAP S/4 Hana pre-transition check results : highest return code 12 .                                                                                                                                                        We did one way synchronization. So, is it necessary to  do two way synchronization to  remove the errors while executing R_S4_PRE_TRANSITION_CHECKS.                                                               Thanks Sai

  • Hi Michael,

    While running the program R_S4_PRE_TRANSITION_CHECKS, I am getting following error,
    "Overall SAP S/4HANA Pre-Transition check result: highest return code 12 !!

    "Some of the customers are not having contact person mapping kindly refer note 2210486."

    And while running the report CVI_FS_CHECK_CUSTOMIZING, its giving message -"No Customising errors", all the required fields are showing activated.

    So can you please help on this error, what exactly is the issue if you can let me know it would be great.


      • Hello Michael,


        Your document has been very helpful in my CVI activity.

        I have done all the mapping as per the document you have shared but I am stuck with the error in the screenshot.All settings pertaining to contact person have been done.


        Please can you help me resolve the error attached.You kind help will be appreciated.

        Warm Regards.

  • Hello Michael,

    Thanks for this useful post. It helped me to solve the issue of CVI.

    Appreciate your efforts to share such a helpful information.


  • Note that SAP standard tax categories are found in OSS Note 775919.  Any additional tax categories that you enter yourself are considered system modifications.

  • Hello Micheal Hu.

    First time Iam doing a S/4 HANA project. We need to convert customers in ECC to BP. This concept of BP goes above my head.

    For eg. Tax category in ECC is a four digit number which means it is a tax condition type and for each countries we define tax category in ECC and assign it to customer and material master.

    Now I could not understand what is this three digit tax category CN1/CN5. what is its functional relevance . we never define three digit tax category in customer master in ECC. so how does system know CN1/Cn5 are missing during sync of customers to BP ?





    Hi Micheal,

    Thank you for this article and the previous one, helped us a lot in terms of maintaining couple of missing items and also in the directions of confirming our steps were in right direction. However we are stuck with the error during synchronization, which is as below.

    and also the error "Business partner ##1 does not exist".

    this is what we got when we executed MDS_PPO2 tcode.

    and the Consistency check is showing the error, which says CVI CONT MAP with the code 12.

    It would be of great help if you can provide your inputs or pointers in this direction.