BP ConversionGuide

PUBLIC
2022-03-18
Business Partner Conversion Activities

© 2022 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Business Partner Conversion Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Business Partner Approach (Customer/Supplier Integration). . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Master Data Consistency Check for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4 Prepare Customizing and Mapping Tables for Business Partner Conversion. . . . . . . . . . . . . . . . 7

4.1 Number Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2 SEPA Mandate for Vendors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
4.3 Customer and Vendor Table Checks Prior to Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5 Convert Customer/Supplier Data Into Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
6.1 CVI_COCKPIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.2 CVI_MIGRATION_PRECHK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3 CVI_CUSTOMIZING_RESOLVE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
6.4 CVI_LEDH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.5 MDS_LOAD_COCKPIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
6.6 MDS_PPO2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.7 Address Checks for One-Time Accounts (CPD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2 PUBLIC Content
Document History
The following table provides an overview of the most important document changes.
Version Date Description
3.6 2022-03-28 ● Updated sections 6.1, 6.2 and 6.4

with functional changes.
3.5 2021-09-27 ● Added subsection Managing Num

ber Ranges in CVI Synchronization
in section 4.1.
● Updated section 5 with functional
changes.
● Updated section 6.1 with functional
changes.
● Added section 6.4
3.4 2021-03-29 ● Added sections 4.2 and 4.3

● Updated section 5 with a note
● Updated sections 6.1 and 6.2 with
functional changes
3.3 2020-05-01 ● Added section 6.1

● Updated section 5 with new steps
3.2 2019-08-13 ● Updated section 6.2 with correct

IMG paths
● Updated section 6.2 with func
tional changes
3.1 2019-05-03 ● Updated section 6.1 with redirec

tion feature
● Updated section 5 with SAP Note
2780288
3.0 2019-03-15 ● Added sections 3 and 6.1 for Mas

ter Data Consistency Check
● Updated section 5 Prerequisites
2.0 2017-04-07 Updated sections 4 and 5.1
1.0 2017-01-31 Preliminary Version

Document History PUBLIC 3
1 Business Partner Conversion Activities
This guide provides an end to end guidance on business partner conversion activities. This guide is part of
2265093 Business Partner Approach.
You can use the standard centralized guided Cockpit, that would have seamless integration to all the required
process components, in the intended sequence. This would enable customer/consultant community to
perform CVI Synchronization in a hassle-free manner, assisted by a cognitive Cockpit, and get a holistic view of
end-to-end conversion process.
For an ECC system, the CVI Cockpit can be launched via transaction code CVI_COCKPIT [page 21]

4 PUBLIC Business Partner Conversion Activities
2 Business Partner Approach (Customer/
Supplier Integration)
This section introduces the Business Partner Approach that is primarily relevant to customers who are
migrating from SAP ERP to SAP S/4HANA.
 Note
The recognized term is CVI (Customer/Vendor Integration), but for this release we will refer to Customer/
Supplier Integration or when necessary, the abbreviation CVI.
Only customers with Customer/Supplier Integration in place can move to SAP S/4HANA. SAP Business Suite
customers can move from different start releases to SAP S/4HANA. To ensure a successful conversion, all
customers and suppliers must be converted to BP (Business Partners) in the system. This is also true for the
business partners that are already in use. When the customer/supplier transformation process is triggered, the
system posts all required fields into the business partner. The Business Partner is the leading object while
creating customer or supplier master data.
Supplier and Customer Master Data are widely used within SAP ERP, and customizing settings have to be
maintained correctly so that data can be completely converted without additional settings. You can process
both Customer/Supplier master records from business partner maintenance, as well as maintain data from
customer/supplier processing to the business partner.
To ensure a successful upgrade all customers/suppliers must be converted to a Business Partner and all
contacts that relate to customer or supplier must be converted to a Business Partner including customers,
suppliers, and assigned contacts with the deletion flag. See 2265093 for more information.
 Note
Retail customers who are migrating to SAP S/4HANA, see 2310884 .

Business Partner Approach (Customer/Supplier Integration) PUBLIC 5
3 Master Data Consistency Check for
Business Partner
Context
While migrating to SAP S/4HANA, you need to convert your customer and vendor master data to business
partner. TheCVI_MIGRATION_PRECHK report performs the necessary business checks for customer and
vendor master data if you are intending to migrate to SAP S/4HANA.
 Note
This report covers only the most important master data functional checks with respect to business partner
conversion. The list of checks is not as extensive as the checks that are taken place in MDS_LOAD_COCKPIT
during the actual conversion.
Procedure
1. Execute CVI_MIGRATION_PRECHK [page 26] report to perform master data consistency check.
2. You can check the output Master Data Consistency Check - Results to see the errors.
3. Make necessary corrections to your current master data to ensure smooth conversion to business partner.

6 PUBLIC Master Data Consistency Check for Business Partner
4 Prepare Customizing and Mapping Tables
for Business Partner Conversion
Context
Before the conversion to S/4HANA, ensure that the following settings are maintained correctly in the relevant
Customizing and that the mapping tables are maintained.
Procedure
1. Use report CVI_CUSTOMIZING_RESOLVE [page 30] to perform the necessary checks per client, to find
out missing customizing entries, and solution to create/correct these entries for each client.
Manual Customizing in Transaction SPRO:
2. Synchronization Object BP is active (PPO Active equals true)
Customizing Path Cross-Application Components Master Data
Synchronization Synchronization Control
Synchronization Control Activate PPO Requests for
Platform Objects in the Dialog
3. Active Synchronization between Customer/Supplier and BP is active

○ Source Object Customer and Target Object BP must be active (Act.Ind equal true)
○ Source Object Supplier and Target Object BP must be active (Act.Ind equal true)
Synchronization Synchronization Control
Synchronization Control Activate Synchronization
Options
4. Active Creation of Postprocessing Orders for component AP-MD
a. Activate the Business Process CVI_01, Customer Business Partner

b. Activate the Business Process CVI_02, Supplier Business Partner

Prepare Customizing and Mapping Tables for Business Partner Conversion PUBLIC 7
Customizing Path Cross-Application Components General Application
Functions Postprocessing Office Business
Processes Activate Creation of Postprocessing
Orders
After the successful synchronization of data, you can also activate the Postprocess Orders for CVI_03
and CVI_04 for direction Business Partner Customer /Supplier .
5. Customer/Supplier number range and numeric numbers

○ If the Customer/Supplier number range is already disjoint, we recommend that as a mirror image of
the customer/supplier number range the business partner number range should be defined.
○ If Customer/Supplier number range is not disjoint, we recommend that you maintain the business
partner number range in such a way that the most numbers from customer/supplier can be reused.
○ Customer/Supplier numeric numbers should be taken over to business partner
 Recommendation
To allow the customer/supplier numeric numbers to be taken over to the business partner, the
numeric intervals of the business partner number ranges must be set to external.
After the successful synchronization of data, the numeric intervals of the business partner must be
changed back to internal. Additionally, the customer/supplier numeric number range must be set to
external to allow identical numbers for customer/supplier and business partner.
Access and check the customer number range transaction by under the following customizing path:
Customizing Path Logistics - General Business Partner Customers
Control Define and Assign Customer Number
Ranges
Access and check the supplier number range transaction under the following customizing path:
Customizing Path Logistics - General Supplier Customers Control
Define Number Ranges for Supplier Master Records
Access the business partner number range transaction under the following customizing path:
Customizing Path Cross-Application Components SAP BusinessPartner
Business Partner Basic Settings Number Ranges
and Groupings Define Number Ranges/Define
Groupings and Assign Number Ranges
SAP recommends that you allocate for new business partners identical numbers when assigning numbers
to customer/supplier and business partners. However, this is not possible in every case, for example, if SAP

8 PUBLIC Prepare Customizing and Mapping Tables for Business Partner Conversion
business partners already existed in the system prior to conversion and the number ranges overlap. For
more information and an example, see Number Assignments.
Access the number range transaction under the following customizing path and the set the indicator Same
Numbers:
Synchronization Customer/Supplier Integration
Business Partner Settings Settings for Customer
Integration Field Assignment for Customer Integration
Assign Keys Define Number Assignment for Direction
BP to Customer/Supplier
6. Business Add-Ins(BAdIs)
You can implement customer-specific mappings like Form of Address from Customer/Supplier to Business
Partner using the available BAdIs. Here it would also be possible to create a Business Partner in a different
category, for example, person instead of organization. In this case, you have to deactivate the
enhancement CVI_MAP_TITLE_DIRECT and activate the enhancement implementation
CVI_MAP_BP_CATEGORY in the IMG. The implementation is already available.
Business Partner Settings Business Add-Ins (BAdIs)
○ BAdI: Data Assignment BP Customer/Supplier/
Contact Person
○ BAdI: Data Assignment of Bank Details BP
Customer/Supplier
○ BAdI: Data Assignment of Payment Cards BP
Customer
○ BAdI: Data Assignment of Form of Address from
Customer/Supplier to BP
○ BAdI: Defaults for Creating Data from BP to
Customer/Supplier
7. BP roles are assigned to account groups

Customizing Path For customer: Cross-Application Components
Master Data Synchronization Customer/Supplier
Integration Business Partner Settings Settings for
Customer Integration Define BP Role for Direction
Customer to BP
For supplier: Cross-Application Components Master
Data Synchronization Customer/Supplier Integration
Business Partner Settings Settings for Supplier
Integration Define BP Role for Direction Supplier to
BP
8. For every account group BP Grouping must be available
Customizing Path For customer: Cross-Application Components
Master Data Synchronization Customer/Supplier
Integration Business Partner Settings Settings for
Customer Integration Field Assignment for Customer
Integration Assign Keys Define Number Assignment
for Direction Customer to BP
For supplier: Cross-Application Components Master
Data Synchronization Customer/Supplier Integration
Integration Field Assignment for Supplier Integration
Assign Keys Define Number Assignment for Direction
Supplier to BP
9. For Customer Value Mapping

Assign Attributes Contact Person
○ Activate Assignment of Contact Persons

○ Assign Department Numbers for Contact Person
○ Assign Functions of Contact Person
○ Assign Authority of Contact Person
○ Assign Authority of Contact Person
Cross-Application Components Master Data
Assign Attributes
○ Assign Marital Statuses
○ Assign Legal Form to Legal Status
○ Assign Payment Cards
○ Assign Industries
10. For Supplier Value Mapping
Integration Field Assignment for Supplier Integration
Assign Attributes Assign Industries
11. For Checking Direction from Customer to BP
Integration Define BP Role for Direction Customer to
BP
12. For Checking Direction from Supplier to BP

Integration Define BP Role for Direction Supplier to
BP
13. For Checking Direction from BP to Customer/Supplier

○ You must ensure that the entries that you have maintained in Assign Department Numbers for
Contact Person (during precheck) are available in Customizing for Business Partner under Cross-
Application Components SAP Business Partner Business Partner Relationships Contact Person
○ Define Departments
○ Define Functions
○ Define Powers of Attorney
○ Define VIP Entries
○ You must ensure that the entries that you have maintained in Assign Marital Statuses (during
precheck) are available in Customizing for Business Partner under Cross-Application Components
SAP Business Partner Business Partner Persons Marital Statuses Maintain Marital Status
○ You must ensure that the entries that you have maintained in Assign Legal Form to Legal Status
(during precheck) are available in Customizing for Business Partner under Cross-Application
Components SAP Business Partner Business Partner Maintain Legal Forms
○ You must ensure that the entries that you have maintained in Assign Payment Cards (during
precheck) are available in Customizing for Business Partner under Cross-Application Components
Payment Cards Maintain Payment Card Type
○ You must ensure that the entries that you have maintained in Assign Industries (during precheck) are
available in Customizing for Business Partner under Cross-Application Components SAP
Business Partner Organizations Maintain Industry Systems and Industries
Mapping Tables
14. The CVI pre-check logic compares all KNA1/LFA1 entries with the entries in the CVI_CUST_LINK and
CVI_VEND_LINK mapping tables. For contacts that relate to existing KNA1/LFA1 entries, the pre-check
logic compares all KNVK entries that have assigned Customers (field KUNNR) and Suppliers (field LIFNR)
with the entries in the CVI_CUST_CT_LINK and CVI_VEND_CT_LINK mapping tables.
4.1 Number Assignment
SAP recommends that you keep the customer/supplier number the same when converting to Business Partner
(BP). When the same number is used for a different customer and supplier, you must then give one of them a
different BP number. If you assign identical numbers, this avoids confusion at the application level (when two
different numbers appear for the business partner within a transaction). To use identical numbers, you need
some background information on the customer/supplier and business partner number range. The business

partner in table BUT000, the customer in table KNA1 and the supplier in table LFA1 have independent number
ranges.
For the sake of simplification we are focusing in this example on the business partner and customer. You create
each business partner in a particular business partner group. The account group defines the number range of
the customer master record. Both groups determine the number range in which a business partner and a
customer are created. The link between the three objects has to be configured in the Customer/Supplier
Integration (known as CVI). Before you can assign identical numbers you have to make sure that the number
ranges fit into each other.
The following example shows existing business partners created with internal numbers and customer created
with internal numbers with overlapping number range 01.
BP Groupings
Grouping Short Name Description Number range External
0001 Int.No.Assgnmnt Internal Number As 01 -

signment
Intervals Business Partner
NR From No. To Number Nr Status Ext
01 0000000001 0999999999 5000 -
Account Groups
Group Name Number Range
DEBI Customer (general) 01
Intervals Customer
NR From No To Number Nr Status Ext
01 0000100000 0000199999 100010 -
Since only To Number can be changed for an internal number range you have to do the following:
1. Change the To Number for the business partner interval to 0000099999, for example.
2. Create a new range 02 and mark for external.
01 0000000001 0000099999 5000 -
02 0000100000 0000199999 - x
3. Change the BP Groupings Number Range to 02.

BP Groupings
0001 Int.No.Assgnmnt Internal Number As 02 X

signment
During the transformation the new business partners are now created out of the customer with the same
numbers.
After the initial load you should change the number range again in such a way that new identical numbers are
created for business partner and customers by defining a new range for business partner and customer.
1. Create a new intervals business partner range 03.
01 0000000001 0000099999 5000 -
02 0000100000 0000199999 - x
03 0000200000 0000300000 - -
2. Change the BP groupings number range to 03
BP Groupings
0001 Int.No.Assgnmnt Internal Number As 03 -

signment
3. Change the account groups range to 02
Group Name Number Range
DEBI Customer (general) 02
Managing Number Ranges in CVI Synchronization
While managing number ranges, the following requirements are considered:
● Mapping multiple customer/vendor account groups with rather smaller number of records into one
collective Business Partner grouping
● Applying the same number for the customer/vendor records and their assigned Business Partners

Following is an example:
Customer/Vendor Customer/Vendor BP Number Same Number

Account Group Number Range BP Grouping Range
Z001 1000 - 1999 -> ZBP1 1000 - 9999 x
Z002 2000 - 2999 -> ZBP1 1000 - 9999 x
Z005 5000 - 6999 -> ZBP1 1000 - 9999 x
For numbers to be the same, the customer/vendor account group number range and its mapped BP grouping
number range must be the same. When there are multiple account groups with different number ranges it is
quite cumbersome to synchronize every account group separately, adjust number ranges per run in the MDS
Load Cockpit. Therefore, a simplification is introduced to manage number ranges in CVI synchronization when
the customer/vendor account group number is within the number range as that of the mapped business
partner grouping. The simplification does not enforce customer/vendor account group number range to be
exactly the same number range as that of the mapped business partner grouping. This is implemented in the
mapping directions: Customer to Business Partner and Vendor to Business partner.
4.2 SEPA Mandate for Vendors
SEPA mandates cannot be created directly for vendors as it is possible for only customers. In some cases, it is
necessary though to use mandates also for vendors. You can use the synchronization program
RFKREDEB_SYNC to create SEPA mandates for vendors. This program creates in a first run, a customer using
the address data and bank details of the vendor in scope. Customer and Vendor objects get linked via the
tables LFA1-KUNNR/KNA1-LIFNR. The customer can be used to create mandates which are then also
available for the vendor. Additionally, customer/vendor pairs which are used for mandate purposes get saved in
database table TRFKREDEB_SYNC. Any subsequent runs of the program RFKREDEB_SYNC maintains the
address data and bank details of the customer/vendor pairs in table TRFKREDEB_SYNC in synchronization.
Software Update Manager Checks
Before conversion to SAP S/4HANA, you can perform Software Update Manager (SUM) checks. The SUM
checks if customer/vendor pairs in table TRFKREDEB_SYNC are assigned to the same business partner and the
KNA1-LIFNR/LFA1-KUNNR link exists. If the SUM checks fail, there will be error messages displayed and you
will need to fix the inconsistencies.
For all customer/vendor pairs in TRFKREDEB_SYNC table, SUM checks for the following:
● A customer and vendor are mapped to the same business partner. If they are not mapped to the same
business partner, there will be error messages displayed.
● A customer is assigned as a mapped/linked customer to a vendor in the table TRFKREDEB_SYNC.
○ If the customer is assigned to a business partner and the customer/vendor pairs are mapped to the
same business partner, there will be no error messages displayed in this case.

○ If the customer is not assigned to a business partner, but the mapped customer and vendor details are
in synchronization and vendor is already assigned to a business partner. Then, error messages are
displayed and you need to correct them. You need to map the same vendor business partner to the
customer.
● A vendor has a mapped/linked customer in table TRFKREDEB_SYNC.
○ If the vendor is already assigned to a business partner and the customer/vendor pairs are mapped to
the same business partner, there will be no error messages displayed in this case.
○ If the vendor is not assigned to a business partner, but the mapped customer and vendor details are in
synchronization and customer is already assigned to a business partner. Then, error messages are
displayed and you need to correct them. You need to map the same customer business partner to the
vendor.
Procedure
Following are the steps for creating SEPA mandate for vendor:
1. Goto transaction SE11 and enter the view name MDSV_CTRL_OPT_A and display the contents.
2. In the Active Synchronization Options, you must select Customer->BP and Vendor->BP options.
3. Goto transaction xk01 and create the vendor with mandatory details along with bank details.
This will create a vendor with a business partner.
4. Execute the report RFKREDEB_SYNC.
This report will create a mapped customer for the given vendor and update the table TRFKREDEB_SYNC
with vendor and mapped customer information.
5. Check the contents in table TRFKREDEB_SYNC.
The customer and vendor links LFA1-KUNNR and KNA1-LIFNR must exist.
Following are the steps to view the errors:
1. Execute the report /SDF/RC_START_CHECK using the transaction SE38.

2. Select the Target SAP S/4 HANA Version from the drop-down list.
3. From the simplification list, select the ID SI2: MasterData_BP. Click on Check Consistency Details button.
4. Expand the Check item "SI2: MasterData_BP”.
Errors for SEPA Mandate checks are listed.
Following are the steps to fix the errors:
1. Goto transaction SE11 and enter the view name MDSV_CTRL_OPT_A and display the contents.
2. In the Active Synchronization Options, you must select:
○ All the synchronization options - in case of customer and vendor not mapped to same business
partner
○ Customer->BP and Vendor->BP - in case of customer and vendor not mapped to a business partner
○ Customer->BP - in case of customer not mapped to same business partner
○ Vendor->BP - in case of vendor not mapped to same business partner
3. If the customer is not mapped to the business partner, run the MDS_LOAD_COCKPIT for Customer → BP
with the customer number. This will map same vendor business partner to the customer.
If the vendor is not mapped to the business partner, run the MDS_LOAD_COCKPIT for Vendor → BP with the
vendor number. This will map same customer business partner to the vendor.

 Note
In SAP S/4HANA, SEPA mandate for suppliers (vendors) are maintained by adding additional role of
customer to the same business partner.
If you have already activated CVI in ECC and synchronization is active for Customer → BP and Vendor → BP
directions and there are different business partners created for vendors and the linked customers, then
there is no option but to archive such business partners of customers and to create additional customer
role for vendor business partners in order to have SEPA functionality for the vendor business partners.
Before the upgrade, execute RFKREDEB_SYNC synchronization program or execute MDS_LOAD_COCKPIT to

ensure that vendor and linked customer are synchronized to the same business partner.
In case error persists, perform the following steps:
1. Create additional customer role for the business partner of that vendor.
2. Archive the business partner of customer.
4.3 Customer and Vendor Table Checks Prior to Conversion
The historic customer and vendor links in customer BD001 (Business Partner: Assignment Customer –
Partner) and vendor BC001 (Business Partner: Assign Vendor – Partner) database tables are not migrated to
the new tables CVI_CUST_LINK (Assignment Between Customer and Business Partner) and CVI_VEND_LINK
(Assignment Between Vendor and Business Partner). Therefore, in SAP S/4HANA, you will need to check both
the tables BD001 and CVI_CUST_LINK/BC001 and CVI_VEND_LINK to verify if a customer/vendor is assigned
to a business partner.
During migration from ERP to SAP S/4HANA, a new simplification check is introduced to check for unmigrated
entries in the customer/vendor BD001 and BC001 tables and display errors. If unmigrated entries exist in these
tables, then you must execute the reports CVI_MIGRATE_CUST_LINK and CVI_MIGRATE_VEND_LINK prior to
conversion. These reports will ensure that all customer and vendor links are available in CVI_CUST_LINK and
CVI_VEND_LINK tables. Then you must ensure that BD001 and BC001 tables are empty prior to Software
Update Manager (SUM) upgrade.
Procedure
Following are the steps to view the errors:
1. Execute the report /SDF/RC_START_CHECK using the transaction SE38.

2. Select the Target SAP S/4 HANA Version from the drop-down list and choose Execute.
3. From the simplification list, select the ID SI28: MasterData_BP. Click on Check Consistency Details button.
4. Expand the Check item "SI28: MasterData_BP”.
Errors are listed.

Following are the steps to fix the errors:
1. Goto transaction SE38 and execute the reports CVI_MIGRATE_CUST_LINKS and

CVI_MIGRATE_VEND_LINKS.
All customer and vendor links will now be available in CVI_CUST_LINK and CVI_VEND_LINK tables.

5 Convert Customer/Supplier Data Into
Business Partner
Prerequisites
● You have checked master data consistency as described in Master Data Consistency Check for Business
Partner [page 6] and made necessary corrections.
● You have checked and adapted the customizing, and created the Customer/Supplier Integration (known as
CVI) and contact person mapping as described in Prepare Customizing and Mapping Tables for Business
Partner Conversion [page 7].
Context
Carry out the conversion process in the sequence below and repeat it if necessary.
 Note
The total conversion time depends on different factors, such as:
● BP/CVI/Precheck know-how
● Customer/Supplier/BP number ranges
● BP Customizing consistency including field attributes
● Customer/Supplier/Business Partner data consistency
● Customer/Supplier Enhancements (Extensions)
● Data volume
Procedure
1. Call up the transaction MDS_LOAD_COCKPIT [page 35]. The non-synchronized customer/supplier data
automatically get downloaded to your temp folder. You can use the Read File button in
MDS_LOAD_COCKPIT [page 35] to upload the data for synchronization.
There is a default BAdI implementation (CVI_CUSTOM_MAPPER) called up in the direction Customer/

Supplier to Business partner, to bypass the following checks.
You can segregate the suppression of checks based on records marked for deletion and records not
marked for deletion by indicating against the relevant columns.
○ Tax Jurisdiction
○ Email
○ Bank

Convert Customer/Supplier Data Into Business Partner PUBLIC 19
○ Tax Numbers
○ Region & Postal Code
○ Geocode
 Note
For Contact Persons (Customer/Vendor), you can bypass Email, Region & Postal Code checks only.
 Note
You can activate the field check suppression using the Customizing activity Activate Field Check
Suppression under Cross-Application Components Master Data Synchronization Customer/
Vendor Integration . The CVI_CUSTOM_MAPPER BAdI is called for the activated field checks for
suppression.
For one-time customers and one-time vendors, the address checks also can be skipped. For One-Time
Accounts (CPD and so on), there is a default internal BAdI implementation (CVI_CPD_SKIP_ADDR_CHCK)
to bypass the following address checks. For more information, see Address Checks for One-Time Accounts
(CPD) [page 38]
○ Address Checks for all C/V One-Time Accounts (CPD etc.)
 Note
This check is applicable for Contact Persons (Customer/Vendor) with One-Time Accounts.
See 2336018 , 2345087 , 2780288 , 2955243 , 2949716 , 2955857 and 2955121 for more
information on these checks.
2. Adjust the customizing if there are errors.
If there is a missing BP event (such as a missing function module), deactivate the event using transaction
BUS7.
 Note
If the system determines inconsistencies in data between the CVI Link tables (CVI_CUST_LINK,
CVI_VEND_LINK, and CVI_CUST_CT_LINK ) and the Business Partner tables, for example, BUT000,
or vice versa, you should search for an SAP Note with the key word BP_ CVI.
For example, if a customer and a supplier exists with the same number representing the same legal
entity the migration fails with the message BP already exists. SAP Note 954816 explains how
you can solve this problem.
3. After conversion, reset the system settings to original state:

a. Deactivate the BAdI (CVI_CUSTOM_MAPPER) to revert the settings for suppressed checks such as Tax
Jurisdiction Code check, Postal Code check, Address Regional check and so on.

20 PUBLIC Convert Customer/Supplier Data Into Business Partner
6 Appendix
6.1 CVI_COCKPIT
The CVI (Customer Vendor Integration) Cockpit is an SAP standard guided Cockpit, meant to ease the overall
complexity of the Business Partner/CVI conversion processes, that would have seamless integration to all the
individual process components. The CVI Cockpit can be launched via transaction code CVI_COCKPIT.
The following is the structure of the CVI Cockpit:
● Overall CVI Cockpit

○ Current Client Status and Cross-Client Sync Status
○ Read Me
○ Note Checker
○ CVI Library
○ Preparation
○ Master Data Consistency
○ Check Customizing
○ Suppress Checks
○ Legal Entity Pre-checks
○ CVI Load
○ Pre Load Activities
○ Activation/Deactivation of Interfaces
○ Block Maintenance Transactions
○ Further Information
○ Real Load Activities
○ Load Tool
○ Post Processing
○ Completeness Check
○ Post Load Activities
○ Activation/Deactivation of Interfaces
○ Release Maintenance Transactions
○ Upgrade Preparation
○ Post Processing
○ Upgrade Prechecks

Appendix PUBLIC 21
Features
The CVI Cockpit mainly comprises of three levels.
● Overall CVI Cockpit

○ Cross-Client Sync Status – The overall status based on the number of unsynchronized records in each
of the clients. The Cross-Client Sync can have only two valid statuses - Red or Green, indicating Ready
and Not Ready respectively. Red indicates that there are unsynchronized records in one of the clients,
and green indicates there are no unsynchronized records in any of the clients.
○ Current Client Status
○ Four Stages under the cockpit
○ Individual tasks under each Stage
 Note
All the stages of CVI Cockpit excludes customers, vendors and associated contact persons which
are assigned to retail sites.
The CVI Cockpit Current Client Status, the four Stages and their respective Tasks have a status associated
to them.
All the Tasks of the CVI Cockpit requires manual maintenance of statuses. There are three statuses - Red,
Green and Yellow.
Upon the first launch of the CVI Cockpit, all the statuses are defaulted (greyed out).
Based on the status of the Tasks, the status of the Stages is automatically determined.
○ Stage status is Red, if one or more of its Tasks are set to red
○ Stage status is Green, only if all its Tasks are set to green
○ Stage status is Yellow, if one or more of its Tasks are set to yellow
The CVI Cockpit Current Client Status can have only two valid statuses- Red and Green, indicating Ready
and Not Ready respectively.
The CVI Cockpit Current Client Status becomes Green (Ready), only upon meeting BOTH the below
conditions:
○ All the Stages are Green (confirmed)
○ There should be no unsynchronized customer or vendor or customer contact person or vendor
contact person records (to BP) in the system
In case, either or all the above conditions are not met, the CVI Cockpit Current Client Status stays Red.
 Note
The CVI Cockpit Current Client/Cross-Client Synchronization Status (Count of Unsynchronized

Customers, Vendors, Customer Contact Persons, Vendor Contact Persons) excludes customer, vendors
and contact persons belonging to retail sites.
Next Steps
This button will provide you information on the activities after Customer/ Vendor to BP synchronization. It is
only enabled when the CVI Cockpit Current Client Status is Green. Otherwise, it remains disabled.

22 PUBLIC Appendix
Authorization
You must have the required authorization to execute the tasks in CVI Cockpit.
An authorization profile for T-Code: CVI_COCKPIT in the SU22 provides the list of authorization objects
corresponding to the executable tasks.
It is recommended to enhance the user authorization profile based on the SU22 recommendation.
Activities
For total count on unsynchronized customer, vendor, customer contact person or vendor contact person
records for current client or cross-client sync, click on Real-Time Status button.
The positioning of all the Stages and its related Tasks are already done in a logical sequence. For Stages, the
sequence is Left to right. For Tasks, the sequence is Top to Bottom.
 Note
There are some tasks in each stage that are executable anytime independent of the sequence.
General Functions of Task

Across the CVI Cockpit, there are 2 types of Tasks - Executable and Non-executable.
The non-executable Tasks are active both in Display and Edit Mode.
Click on Edit to activate the Tasks. Click on Execute button to launch individual Tasks. Click on the Information
button to know more about respective Tasks.
Tasks Executable at Any Time

Some of the tasks under each stage are active for execution at any time as they are independent of the
preceding or succeeding stage status. You need not click Edit to activate the Execute option for such tasks as
they are executable at any time. Such tasks do not require the previous stage to be Green and the current stage
to be in edit mode.
Once you have executed a Task, go to Task Status and select one of the below Status:
01 Initial
02 Needs Resolution
03 In Process
04 Skip Step (Project Decision)
05 OK
06 Ok with Reservation
07 Resolved
Status 01 will indicate the Task status as Grey. Status 02 will indicate Task status as Red. Status 03 will indicate
Task status as Yellow. Status 04, 05, 06, 07 will indicate Task status as Green.

Appendix PUBLIC 23
Precaution: You may achieve Task status as Green, even with 04 - 'Skip Step (Project Decision)' and 06 - 'OK
with Reservation'. In such cases, please ensure completion of the concerned task before proceeding to next
stage, in order to attain system consistency.
Enter a mandatory comment in the Comment field. Last Executed By field indicates the last person who
handled the Task.
Click on the Change Log button to get the change history of all the Tasks in the current stage.
 Note
This is common to all the Tasks across all the stages.
Click on Edit to activate the Execute option of all the Tasks in respective Stages.
 Note
Some of the tasks under each stage are active for execution at any time as they are independent of the
preceding or succeeding stage status to be Green. You need not click Edit to activate the Execute option for
such executable tasks
Stage Name: Read Me

This is the first Stage of CVI Cockpit. You can access the collective notes (TCI), which contains all the
prerequisite notes for a CVI conversion project.
Stage Name: Preparation

This is the second Stage of CVI Cockpit. This stage contains the tasks which perform necessary master data
and customizing checks with respect to Business Partner Synchronization
The following tasks of this stage are executable at any time:
● Master Data Consistency

● Check Customizing
● Legal Entity Pre-checks
Stage Name: CVI Load

This is the third stage of CVI_COCKPIT. This stage is divided into three sections - Pre-Load Activities, Real Load
Activities, and Post Load Activities. These tasks contain activities that help in converting customer/ vendor data
to BP Data.
● Post Processing
● Completeness Check
Stage Name: Upgrade Preparation

This is the fourth and the last Stage of CVI Cockpit. The tasks inside this stage gives reprocessing capabilities
and enlists a quantification of the remaining inconsistencies, thereby enabling you to check the consistency of
the BPs created.
● Post Processing

24 PUBLIC Appendix
● Pre-upgrade Customizing Checks
Cockpit Screen Behavior
Please note the below screen behaviors while making changes to the stages and tasks of CVI Cockpit program.
Auto-save option is not supported

In the middle of the task, if you exit the CVI Cockpit program, then the task will not get automatically saved.
Also, if you set the task status and do not press Enter, then the change log will not be saved, and the task status
will not be saved.
Backward Navigation
If you try to edit a confirmed stage, it will reset the all the tasks of sub-sequent stages.
1. All subsequent stages and it tasks will reset.

2. The status of the current stage retains all the task statuses. And the status of the current stage will be
redetermined based on the modified task status.
Forward Navigation
If you want to edit sub-sequent stages, the edit option for the stages will be available based on below actions-
1. If all the task statuses of the current stage are set to Green, then edit option is enabled in the immediate
next stage. Edit option remains disabled in all other sub-sequent stages.
2. If any task status of the current stage is not set to Green, then edit option is disabled in the immediate next
stage and remains disabled in other sub-sequent stages.
Out of Scope
The current version of CVI Cockpit specifically takes care of BP Synchronization for Customer and Vendor
Master Data only. The following data sets are currently out of executable scope:
1. HCM/Employee Objects
2. CRM Integration Scenarios
3. MDG Capabilities

Appendix PUBLIC 25
6.2 CVI_MIGRATION_PRECHK
Prevalidation: Master Data Consistency Check
Purpose
This report performs the necessary business checks for customer and vendor master data if you are intending
to migrate to SAP S/4HANA. This report gives an upfront overview of master data consistency that is required
for conversion to business partner master data. You can run this report to check the following business
scenarios:
● Tax Code
● Postal Code
● Email
● Bank Data
● Tax Jurisdiction
● Industry
● Transportation Zones
● Address
● Number Range
 Note
When you execute this report for customer/vendor contact persons, only the business checks Postal Code,
Email and Address are applicable for checking.
Also, you can run this report to check the following optional business scenario:
● Tax ID
 Note
The Tax ID business check is available for VAT numbers of countries based in European Union (EU) only.
 Note
If you have selected Records Marked for Deletion in the Customizing Activate Field Check Suppression for
any of the above business scenarios, then the check is skipped for that business scenario for the
corresponding customer, vendor, and contact person records that are marked for deletion.
Prerequisites
● To correct the master data consistency errors using the Edit feature, you need the following authorizations.
With these authorizations, you are also able to use the Mass Populate feature.

26 PUBLIC Appendix
○ Authorization object C_PRECHK_M and the activity 02 assigned.
○ Authorization object B_MASSMAIN, activity MASSOBJTYP and values XD99 (customer) or XK99 (vendor)
assigned.
● The Run ID is generated based on a customizable number range, which is part of standard content delivery.
Note that this content is available in client 000. You should ensure that this content is available in the
required clients via client copy.
● To correct the address errors using the Address Changes feature, you need DQM 4.1 add-on installed.
 Note
MDC report is also compatible with DQM 4.0 SP10 for address validations based on the configured
Postal Address directories. However, microservice capabilities are only supported with DQM 4.1
version.
● To run the optional business check for tax ID (EU only), you need to setup an RFC connection to the VAT
Information Exchange System (VIES) portal. For the RFC connection setup, refer 2866929 and see the
attachment "2866929 Online Validation - Implementation Instructions v2.4.pdf".
Selection
Select the parameters for the checks that report needs to perform. Then, execute the report.
● General Selection – You can choose the master data type; Customer or Vendor or Customer Contact Person
or Vendor Contact Person. You can also enter a customer or vendor number and specify its account group
and/or organization details such as company code, sales organization/purchasing organization. Note that
account group can undergo changes for a given customer or vendor, which may result inconsistent output.
The organization details selection vary depending on the selected master data type. If you select Customer
or Customer Contact Person, then the Sales Organization selection criteria is enabled. If you select Vendor,
then Purchasing Organization selection criteria is enabled. If you select Customer or Vendor or Customer
Contact Person, then Company Code selection criteria is enabled.
● Business Checks – Choose the relevant checks that you want to carry out during migration precheck. You
can also choose all checks using Select All check box. By default, all the scenarios are selected.
 Note
If you have selected the master data type as Customer Contact Person or Vendor Contact Person in the
General Selection, then only the Address, Postal Code and Email business checks are enabled for
selection.
● Optional Business Checks – Choose the Tax ID (EU only) check to carry out tax ID validation during
migration precheck.
● Technical Details
○ Server Group – You can choose the predefined server group to be used for parallel processing, from the
value help. This is a mandatory field.
○ Description – Enter a description for the run. This is a mandatory field.

Appendix PUBLIC 27
Output
The report generates an output containing the status of each check that it performs. The Run History section
displays the details of the run with a link to the output Master Data Consistency Check - Results.
Run History
● Status
○ Green - Indicates that the last action is completed.
○ Yellow - The action is still in progress.
○ Red - Status is undetermined.
○ Cross (Red) - Indicates that the run is terminated. You can check the job log (transaction SM37) for
more details.
○ Grey - Indicates that it is an obsolete Run ID and no further actions are supported. The old run ID
becomes obsolete. In this case, you need to create a new run ID with the required selection criteria.
● Variants - Double click to view all the variants that are considered for the corresponding run.
● Rerun - You can repeat a run with the same selection criteria.
● Run ID - Indicates the unique identifier that is created for each run. Click Run ID to view the detailed output
Master Data Consistency Check - Results of the corresponding run.
● Click on Object ID in the detailed description view. This redirects you to XK02 transaction for vendor and
XD02 transaction for customer. For customer/vendor contact persons, this redirects you to MAP2
transaction for vendor contact person and VAP2 transaction for customer contact person.
● Description - Displays the description that you have previously entered for each run.
● You can use Refresh button to view the latest status of each run.
Master Data Consistency Check - Results
You can view a detailed list of errors, based on the business checks and optional business checks selected for
the run. The header area displays the metadata and the number of remaining error records pending after each
correction for the following:
● Run ID
● Description
● Object Type
● Total Customer/Vendor Processed or Total Customer/Vendor Contact Person Processed
● Total Error Count Identified
● Unresolved Error Count
● Optional Check Error Count (This is displayed for the optional business checks only)
Some important parameters on the results screen are explained below:
● Object ID - Indicates the customer or vendor ID or customer contact person or vendor contact person ID.
This redirects you to the corresponding maintenance transactions for vendor (XK02) and customer
(XD02). For customer/vendor contact persons, this redirects you to the corresponding maintenance
transactions for vendor contact person (MAP2) and customer contact person (VAP2).
● Table Key - You can identify which record needs be updated based on the table key.
● The following columns are displayed only when DQM add-on is installed. Also, you need to be editing the
address checks:
○ Address Check Status - Displays the status of the address checks. The different statuses are:

28 PUBLIC Appendix
○ C - Validated address
○ D - Invalid address
○ Blank - Address not validated
○ Formatted Address - For address records with address check status as C, click the icon to view the
validated address data for the address fields.
○ Proposed Address - Indicates that the validated address is accepted or rejected.
○ X indicates that the proposed address is without any ambiguity and is accepted.
○ Blank indicates ambiguous address and is rejected.
● DB Value - Displays the current data in the database.
● Correction Status - Displays the resolution status of the error.
● Message - Displays the correction information.
 Note
Your proposed values are stored in draft persistence to ensure minimal risk of data loss.
Activities
1. Enter the relevant parameters and execute the report.

2. Double click Variants to view the selection criteria that was considered for the corresponding run.
3. Choose Run ID to view the detailed output Master Data Consistency Check - Result of the corresponding
run.
1. Click Object ID. This redirects you to XK02 transaction for vendor and XD02 transaction for customer.
For customer/vendor contact persons, this redirects you to the corresponding maintenance
transactions for vendor contact person (MAP2) and customer contact person (VAP2).
2. By default, errors pertaining to all the business checks are listed. Choose Edit button to view errors
corresponding to each business check.
 Note
For the master data type Customer Contact Person or Vendor Contact Person, only the errors
pertaining to Address, Postal Code and Email business checks are listed.
3. Choose the business check that you want to correct errors for.
 Note
You cannot edit a master data record (for correction) if it is already being edited as part of another
Run ID or by another user. Also, Number Range errors and some of the Tax Code errors cannot be
edited.
4. Click Edit button. This enables you to correct errors by entering a new value under New Value column.
 Note
For the master data type Customer Contact Person or Vendor Contact Person, you can correct the
Address, Postal Code and Email errors only.

Appendix PUBLIC 29
5. Click Check button. This checks if the new value is acceptable by the system and displays
corresponding information under Message column.
6. When you edit Address Checks, you can use the Address Changes feature. This provides options to
either Fix Ambiguous Address or Reject Address Proposal based on address proposals from DQM.
○ Fix Ambiguous Address - Select an address record and choose Fix Ambiguous Address. A single
validated address or multiple address suggestions are displayed. You can review the changes in the
address and Accept Validated Address or Use Original Address.
When you accept the validated address, it is displayed in the New Value column, the address check
status is set to C, and the proposed address is set to X. When you retain the original address, the
address check status is set to D and proposed address is set to blank.
○ Reject Address Proposal - If you want to change the address data proposed by DQM (with address
check status as C and proposed address as X), choose Reject Address Proposal. The New Value
column is enabled for editing, address check status is set to D, and proposed address is set to
blank.
7. Save your entries. You can save a record only after correcting all errors pertaining to it. See application
logs using transaction SLG1 for more details.
However, the corrections will be committed to database only when all errors pertaining to an object are
validated using the Check button and there is no error returned while saving the object via standard
API.
8. You can correct similar errors that have a common solution. To do this, choose a row with the error and
click Mass Populate button.
9. You can see the application log using transaction SLG1 with parameters CVI_PRECHK as object and
Customer/Vendor as sub object.
6.3 CVI_CUSTOMIZING_RESOLVE
Use
You can use this program to perform the necessary checks per client. It also provides Customizing resolution
program, where you can find out missing customizing entries and the solution to create/correct these entries
for each client.
Features
Selection
Choose the required check and execute.
Output
The program generates an output containing the status of each check that it performs. If the status is green,
this indicates that check is successful. If the status is red, you must follow the steps mentioned in this
document to resolve the errors.

30 PUBLIC Appendix
Activities
Run each check to view its message logs.
General Settings
1. In this section, you can find the missing customizing entries, and inconsistencies for the following areas:
○ Synchronization Direction
○ Connection to PPO
○ Registered Function Modules
○ Tax Classification
○ Address Number Range Validity Check
○ Select Industry System
2. Choose Customizing button to navigate to the relevant Customizing activity and add missing data.
3. For Tax Classification errors might occur due to entries that are missing in Customizing tables (but present
in Customer/Vendor master tables). To solve this inconsistency, choose Display <-> Change button to
enter required data and Save your changes.
4. For Select Industry System, you can choose Standard Industry indicator using the Display <-> Change
button.
Customer -> BP Checks
The system checks for missing entries in the direction from Customer to Business Partner.
○ Setting for Business Partner Roles
○ Setting for Business Partner Groupings
○ Customer Account Group -> Role
○ Customer Account Group -> Grouping
○ Missing Legal Status to Legal Form
○ Missing Payment Cards
○ Missing Industry Keys - Incoming
3. To correct inconsistencies, choose Display <-> Change button to enter required data and Save your
changes.
Contact Person
1. You receive the error logs if you have not maintained the mapping of different attributes between customer
and Business Partner. You must perform value mapping from the drop down provided for each of the
following sections:
○ Missing Activation
○ Missing Department Numbers
○ Missing Functions
○ Missing Authority
○ Missing VIP Indicator
○ Missing Marital Status
2. Save your changes.
Vendor -> BP Checks

Appendix PUBLIC 31
The system checks for missing entries in the direction from Vendor to Business Partner.
○ Vendor Account Group -> Role
○ Vendor Account Group -> Grouping
○ Missing Industry Keys - Incoming
3. To correct inconsistencies, choose Display <-> Change button to enter required data and Save your
changes.
BP -> Customer Checks
The system checks for missing entries in the direction from Business Partner to Customer.
○ Missing Legal Status to Legal Form
○ Missing Payment Cards
○ Missing Industry Keys - Outgoing
Contact Person
1. You receive the error logs if you have not maintained the mapping of different attributes between customer
and Business Partner. You must perform value mapping from the drop down provided for each of the
following sections:
○ Missing Department Numbers
○ Missing Functions
○ Missing Authority
○ Missing VIP Indicator
○ Missing Marital Status
BP -> Vendor Checks
The system checks for missing entries in the direction from Business Partner to Vendor.
1. In this section, you can find missing customizing entries and inconsistencies for the following areas:
○ Missing Industry Keys - Outgoing
2. Click Customizing button to navigate to the relevant Customizing activity and add missing data.
3. To correct inconsistencies, choose Display <->Change button to enter required data and Save your
changes.

32 PUBLIC Appendix
6.4 CVI_LEDH
Purpose
This report lists customer and vendor records that cross-reference each other forming a legal entity pair but
are not mapped to a business partner.
During the synchronization process in MDS Load Cockpit (MDS_LOAD_COCKPIT), there may be errors for the
customer and vendor legal entity pair due to inconsistencies in the address, bank details and tax data between
them.
This report allows you to select the customer or vendor to be the leading entity for address, tax details and
bank data. The MDS Load Cockpit uses the leading entity information from this report to synchronize the legal
entity customer and vendor pair to business partner. This will harmonize the data and avoid errors for legal
entity pairs.
Prerequisites
● To view and edit the report, you need the authorization object CVI_LEDH and all the activities assigned.
● The CVI_MAP_LEGAL_ENTITY BAdI implementation must be active to merge customer and vendor
records to the same business partner (same legal entity).
Selection
Select the leading parameters for the address, bank details and tax data in this report and save the data. Then,
execute the MDS Load Cockpit (MDS_LOAD_COCKPIT) report to harmonize the data.
Output
● Status - Indicates status of the customer and vendor pair synchronization, the statuses are as follows:
○ Leading Entities Missing: The leading entity (customer/vendor) for data merge is not selected for the
unequal address, bank details or tax data.
○ Customer and Vendor → BP Synchronization Pending: The leading entity for data merge is updated for
the unequal address, bank details, tax data. But, the MDS Load Cockpit (MDS_LOAD_COCKPIT) is not
executed, therefore synchronization in the direction Customer/Vendor → Business Partner is pending.
○ Customer → BP Synchronization Pending: The leading entity for data merge is updated for the unequal
address, bank details, tax data. The MDS Load Cockpit (MDS_LOAD_COCKPIT) is executed in the
direction Vendor → Business Partner, but synchronization in the direction Customer → Business
Partner is pending.
○ Vendor → BP Synchronization Pending: The leading entity for data merge is updated for the unequal
address, bank details, tax data. The MDS Load Cockpit (MDS_LOAD_COCKPIT) is executed in the

Appendix PUBLIC 33
direction Customer -> Business Partner, but synchronization in the direction Vendor → Business
Partner is pending.
● Customer - Customer number with cross-referenced vendor. When you click the customer number, it
redirects you to the corresponding transaction for customer (XD03) in display mode.
● Vendor - Vendor number with cross-referenced customer. When you click the vendor number, it redirects
you to the corresponding transaction for vendor (XK03) in display mode.
● Address - Indicates status of the address check between the customer and vendor pair, whether it is same
or not. Following are the status icons:
○ Green - Indicates that the customer and vendor addresses are identical as the address data is the
same.
○ Red - Indicates that the customer and vendor addresses are non-identical as there are differences in
the address data.
○ When you click the status icon in Address, it displays the customer and vendor address fields. In case
of unequal address, it highlights the customer and vendor address fields that are not identical. You also
have an option to choose between multiple addresses (standard address, international address) to
view the corresponding address fields.
● Leading Address - You can choose the leading entity to be either the Customer or Vendor address data for
the merge. This field is editable only when the address data is not the same i.e. the Address status icon is
red. When the address data is the same, this field is non-editable, and the value is set to Not Applicable.
● Tax - Indicates status of the tax data check between the customer and vendor pair, whether it is same or
not. Following are the status icons:
○ Green - Indicates that the customer and vendor tax data are identical.
○ Red - Indicates that the customer and vendor tax data are non-identical as there are differences in the
tax data.
○ Grey - Indicates that there is no customer and vendor tax data.
○ When you click the status icon in Tax, it displays the customer and vendor tax fields. In case of unequal
tax data, it highlights the customer and vendor tax fields that are not identical. You also have an option
to choose between multiple tax data to view the corresponding tax data fields.
● Leading Tax - You can choose the leading entity to be either the Customer or Vendor tax data for the merge.
This field is editable only when the tax data is not the same i.e. the Tax status icon is red. When the tax data
is the same, this field is non-editable, and the value is set to Not Applicable.
● Bank - Indicates status of the bank details check between the customer and vendor pair, whether it is same
or not. Following are the status icons:
○ Green - Indicates that the customer and vendor bank details are identical.
○ Red - Indicates that the customer and vendor bank details are non-identical as there are differences in
the bank details.
○ Grey – Indicates that there is no customer and vendor bank data.
○ When you click the status icon in Bank, it displays the customer and vendor bank fields. In case of
unequal bank details, it highlights the customer and vendor bank fields that are not identical. You also
have an option to choose between multiple banks to view the corresponding bank fields.
● Leading Bank - You can choose the leading entity to be either the Customer or Vendor bank data for the
merge. This field is editable only when the bank details is not the same i.e. the Bank status icon is red.
When the bank details are the same, this field is non-editable, and the value is set to Not Applicable.
● Source - Indicates the source from where the customer and vendor records are obtained. The source can
be either Standard (SAP delivered) or Custom (BAdI CVI_LE_DATA_HARMONIZATION).

34 PUBLIC Appendix
For customer and vendor records that are not linked to each other but belong to the same legal entity
(same address, bank details and tax data), you can implement the BAdI CVI_LE_DATA_HARMONIZATION
to obtain the customer and vendor records and synchronize them to the same BP.
 Note
If the same customer and vendor records are obtained using the standard and custom logic (BAdI), the
standard logic will take precedence.
 Note
New entries which are not saved will be highlighted in the report.
Activities
1. Select Customer or Vendor as the leading entity in Leading Address, Leading Tax, Leading Bank for the
unequal address, tax data and bank details.
2. Save the report.
6.5 MDS_LOAD_COCKPIT
Use
You can use this report for the following purposes:
● Synchronize the customer/supplier data into SAP business partner during conversion from to S4/HANA
● Create or update a corresponding SAP business partner for the customer and supplier data for general
data, addresses, role data, bank details and so on
Prerequisites
Perform the checks, maintain the relevant Customizing entries, create the Customer/Supplier Integration
(known as CVI) and contact person mapping as described in Prepare Customizing and Mapping Tables for
Business Partner Conversion.
Features
Selection

Appendix PUBLIC 35
Following are the fields on the entry screen of the report:
● Synchronization process – You can select the Source Object/Target Object.

● Customizing Synchronization – This section lists the customized synchronization options.
● Processing – In this tab, you can specify various control parameters such as Block Size, Queue Name,
Server Group and so on. Note that you need to enter values in this section only if you want to change the
default values. Preferably use a smaller Block size (<50) for better performance.
● Monitor – The Monitor tab displays the logs after execution. You can select the entry and click Call PPO
button. To see the status of the background jobs, select the entry, click Queue button and choose Queue
Monitor.
● Selection Criteria for Source Object:
○ Synchronization Scope – You can select a relevant entry from the drop down list.
○ Range of source object – In the table, you can specify the Field Name, Incl/Excl , Option, and Upper/
Lower Limit criteria for the data records you want to synchronize.
○ Read File - You can upload customer/supplier data for synchronization. For more information, see
2399368
Output
After synchronizing the data from the source object to the target object, the report displays the results in the
Monitor tab.
Activities
1. Call up transaction MDS_LOAD_COCKPIT. The Synchronization Cockpit screen appears.

2. Enter the relevant selection criteria.
3. Click Start Synchronization button or press F8 to execute the report.
4. Select the Monitor tab to view the results.
5. Select the error entry and click Call PPO button. It navigates to MDS_PPO2 transaction screen which
displays the corresponding error details.
 Note
Refer to MDS_ PPO2 documentation for further steps. Also you can directly call up transaction
MDS_PPO2 and enter the selection criteria to view error details.
More Information
Preparing Synchronization Runs

36 PUBLIC Appendix
6.6 MDS_PPO2
Use
You can use this report for the following purposes:
● View the error state of Business Partner, Customer and Supplier synchronization
● Set the error log statuses to Completed after resolving the error
Prerequisites
Run the MDS_LOAD_COCKPIT program.
Features
Selection
You can choose a variant at Variant Name or enter the relevant selection criteria in Selection Options.
Output
The reports displays synchronization errors and redirects you to the corresponding transactions to resolve the
data errors. The report automatically synchronizes the data based on your synchronization selection.
Activities
1. Call up transaction MDS_PPO2. The Initial Screen appears.
 Note
You can directly reach the corresponding error details page in MDS_PPO2 by selecting the error
message on Monitor tab after running MDS_LOAD_COCKPIT program.
2. Enter the selection criteria and select Execute.

3. On the Overview screen, double-click the Business Partner or Customer/Supplier number to view the
corresponding error messages.
4. If it is a data error,
1. Scroll down and select your source object tab.
2. Choose Display or Change option. It opens the corresponding transaction page so that you can view or
edit the data.
3. Save the changes. The data automatically get synchronized to the target object.
5. If it is a Customizing error,

Appendix PUBLIC 37
1. Manually navigate to the corresponding Customizing table/activity and resolve the error.
2. Start synchronization. You have two synchronization options:
○ Individual Synchronization - Synchronizes the selected source and target objects
○ Mass Synchronization - Synchronizes all source and target objects based on the selected error
code
6. Once the errors are resolved, come back to MDS_PPO2, and manually set the error status by using
Complete button.
7. After resolving synchronization errors, to know if any other errors have occurred, re-execute the MDS_PPO2
report using the date on which you corrected synchronization errors, as the selection criteria.
6.7 Address Checks for One-Time Accounts (CPD)
During maintenance of customer and vendor master data records, address data is not mandatory for
customers/vendors of account groups of type CPD or equivalent account groups having One-time Account
(OTA) flag set. Customers may or may not maintain any address data. Hence, during save of such customers/
vendors, no error is thrown even if there are any inconsistencies in the address data. While migrating to S/
4HANA, the address fields are always mandatory. Hence, customers performing a CVI implementation,
encounter errors for One-Time Accounts (CPD) during consistency check, synchronization process and SUM
phases.
You can enable skip address checks for OTAs (CPD etc.) with the help of the new flag Address Checks for all
C/V One-Time Accounts (CPD etc.) in SPRO Customizing Cross-Application Components Master Data
Synchronization Customer/Vendor Integration Activate Field Check Suppression .
 Note
The flag is activated by default in order to ensure that address checks are not performed during the
migration.
When the Address Checks for all C/V One-Time Accounts (CPD etc.) field is activated, it bypasses the address
data consistency checks in the following phases of CVI:
● Readiness Check API - Address errors are not added to the count of inconsistencies.
● Master data consistency check - Address errors are not displayed in the detailed report even if the address
checks checkbox is enabled in the report.
● Synchronization (MDS_LOAD_COCKPIT): Address errors are suppressed and such customer/vendor
records are synchronized to business partner without the errors being captured in the PPO.
 Note
There is a default internal BAdI implementation CVI_CPD_SKIP_ADDR_CHCK to bypass the address

checks.
● SUM phase: Address errors are suppressed and such customer/vendor records are synchronized to
business partner without the errors being captured in the PPO.

38 PUBLIC Appendix
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Important Disclaimers and Legal Information PUBLIC 39
www.sap.com/contactsap
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

BP ConversionGuide

Uploaded by

Copyright:

Available Formats

BP ConversionGuide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BP ConversionGuide

Uploaded by

Copyright:

Available Formats

PUBLIC

Business Partner Conversion Activities

THE BEST RUN

1 Business Partner Conversion Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Business Partner Approach (Customer/Supplier Integration). . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Master Data Consistency Check for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 Prepare Customizing and Mapping Tables for Business Partner Conversion. . . . . . . . . . . . . . . . 7

5 Convert Customer/Supplier Data Into Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Business Partner Conversion Activities

Version Date Description

3.6 2022-03-28 ● Updated sections 6.1, 6.2 and 6.4

3.5 2021-09-27 ● Added subsection Managing Num­

3.4 2021-03-29 ● Added sections 4.2 and 4.3

3.3 2020-05-01 ● Added section 6.1

3.2 2019-08-13 ● Updated section 6.2 with correct

3.1 2019-05-03 ● Updated section 6.1 with redirec­

3.0 2019-03-15 ● Added sections 3 and 6.1 for Mas­

2.0 2017-04-07 Updated sections 4 and 5.1

1.0 2017-01-31 Preliminary Version

Business Partner Conversion Activities

Business Partner Conversion Activities

Retail customers who are migrating to SAP S/4HANA, see 2310884 .

Business Partner Conversion Activities

Business Partner Conversion Activities

Customizing Path Cross-Application Components Master Data

Synchronization Synchronization Control

Synchronization Control Activate PPO Requests for

Platform Objects in the Dialog

3. Active Synchronization between Customer/Supplier and BP is active

Customizing Path Cross-Application Components Master Data

Synchronization Synchronization Control

Synchronization Control Activate Synchronization

4. Active Creation of Postprocessing Orders for component AP-MD

a. Activate the Business Process CVI_01, Customer Business Partner

Business Partner Conversion Activities

Functions Postprocessing Office Business

Processes Activate Creation of Postprocessing

5. Customer/Supplier number range and numeric numbers

Customizing Path Logistics - General Business Partner Customers

Control Define and Assign Customer Number

Customizing Path Logistics - General Supplier Customers Control

Define Number Ranges for Supplier Master Records

Customizing Path Cross-Application Components SAP BusinessPartner

Business Partner Basic Settings Number Ranges

and Groupings Define Number Ranges/Define

Groupings and Assign Number Ranges

Business Partner Conversion Activities

Customizing Path Cross-Application Components Master Data

Synchronization Customer/Supplier Integration

Business Partner Settings Settings for Customer

Integration Field Assignment for Customer Integration

Assign Keys Define Number Assignment for Direction

Customizing Path Cross-Application Components Master Data

Synchronization Customer/Supplier Integration

Business Partner Settings Business Add-Ins (BAdIs)

○ BAdI: Data Assignment BP Customer/Supplier/

○ BAdI: Data Assignment of Bank Details BP

○ BAdI: Data Assignment of Payment Cards BP

7. BP roles are assigned to account groups

Business Partner Conversion Activities

3.5 2021-09-27 ● Added subsection Managing Num

3.1 2019-05-03 ● Updated section 6.1 with redirec

3.0 2019-03-15 ● Added sections 3 and 6.1 for Mas

0001 Int.No.Assgnmnt Internal Number As 01 -

0001 Int.No.Assgnmnt Internal Number As 02 X