Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Hi All,

With my recent experience in S/4 HANA in place upgrade,I would like to explain one of the pre-checks to move to S/4 HANA i,e CVI Integration.Only customers with CVI in place can move to SAP S/4 HANA 1709.

Key Points:

  • All customers and Vendors have to converted in to BP . The vendors and customers you do not want to be converted to BP, you should mark them for deletion and archive.

  • All the configuration for BP pre-checks have to configured in ECC system .

  • CVI integration do not require any outage and can be done during weekends.

  • Make sure all the email id of customers/vendors are properly maintained as the business partner validates if the email id has a valid characters.

Below are the activities to be performed:

Activate Business Function CA_BP_SOA . To activate CA_BP_SOA you need to activate its prerequisite CA_SUPPLIER_SOA .

After you activate the business function execute the program

CVI_FS_CHECK_CUSTOMIZING, you will get an list of steps to be performed.

As per above,we need to activate synchronization for Vendor-->BP and Customer-->BP and the PPO requests.

PATH: SPRO/Cross-Application Components/Master Data Synchronization

The preparatory help gives you the sequence to be followed for activation.

Activate PPO:

For pre-checks activate CVI_01 and CVI_02. After the successful conversion activate the CVI_03 and CVI_04.

next step:Make a note of Queue names from table MDSV_CTRL_OPT





Go to T-code -SMQR and click on Register


Similarly register for rest of  the Queues.

Maintain Synchronization objects

After the successful conversion of Customer/vendor to BP, activate the BP-->Customer and BP-->Vendor.

Activate Function modules:

Till this point we have just activated the pre-requisites for CVI.

Now start Customer and vendor integration settings:

Similarly maintain it for customers also.

Define Role category of Vendor and Customer

Click on New Entry and add as per below.

If you select Vendor-Based, all the vendors will be converted in to BP.

Define BP Role for Direction vendor to BP

Z001 and Z002 are vendor groups assigned to BP role FLVN00

Now define the number range for business partners.

Define the number ranges for business partners as External during conversion. Once the conversion is successfully done, change them to internal.

It is recommended to create number ranges with similar names of your vendor group number range.

This is set to external because, during CVI the program will try to allocate the same number of vendor/customer to Business partner.

Define the BP grouping and assign the number range.

I have defined the BP grouping with similar names of Vendor grouping, for easy mappings.

Assign the BP group to Vendor group

During conversion define the direction from vendor to BP

It is recommended to select option Same no as the vendor numbers and BP numbers will be same with this selection.

Similarly assign it for customer groups also.

Re-run the program: CVI_FS_CHECK_CUSTOMIZING

From Above all the customizing looks good.

Though the above shows CVI03 and CVI04 not activated, this is done just to maintain clarity for the sake of conversion. After conversion you have to activate all the CVI’s as in HANA transaction code BP will be single point of entry for creating vendor. Hence the direction BP àt customer/vendor has to be activated.

Because I encountered many issues during synchronization, I recommend below configuration below you run MDS_LOAD_COCKPIT.

Error: 1 in cockpit

Geocoder SAP0: Country Specification is incomplete (Customizing)

Use SAP note 553073 – to solve the above error

Adjust the tables





Click on maintain

Click on Adjustment

you have to copy from standard client 100

Select All


Click Adjust and save.

Similarly perform the same for remaining tables mentioned.


Tax Number XX1 not does not exist

Update table V_TFKTAXNUMTYPE with the missing tax number by copying the standard tax numbers.


Error-3: Assert Condition violated

This is because of missing industry code in business partners.

We copy all the industry codes of vendor to Business partner configuration.


Double Click on Industry Number Systems and click on create.

User table T016 as base to copy the industry codes from vendor.




There should not be any industry code in the non-mapped entries for table.

You can execute the program in update mode, it maps to business partners. I did I manually as per below.


Click on Define Incoming Industries and map 1:1

Error-4: Email ID not valid

Because there are spaces and for some @ is missing errors come up. Correct the same in vendor master data and re-run as below



The job is scheduled and you can check the status in monitor tab.

3rd TAB gives list of all the errors.

Once you adjust vendor master and correct the email ID, click on individual synchronization. If there are similar errors you can use Mass synchronization

Finally execute program:CVI_UPGRADE_CHECK_RESOLVE

This will give you the list of vendors and Customers that are not converted.

I strongly recommend you to go through 2210486,2344034 and 956054.


Error5: Form of Address 005 not designated for Organizations

Please maintain the data as per below screenshot for this.


Error6: XXDEFAULT not maintained in address type


Go to SAP Business Partner-->Business Partner-->Basic Setting-->Address Determination-->Define Transaction and define the business transactions.

and then  in the next step Define the address type.

Error 6: Missing link in the CVI table for the same number objects


Please follow the instruction of note 2373665  and create a new program ZCVI_VEND_LINK_CREATE

Execute the above program to fix the inconsistencies in CVI link table and Customer/Vendor master tables.

Verify CVI_VEND_LINK with LFA1



Praful Jain.
Labels in this area