SAP Knowledge Base Article - Public

3395592 - Error: “There is no assignment mapping defined for payment card type” While Migrating the Customer Master Data


Using the Migrate Your Data app, upon migrating the Customer Data into the system, you see the below error:

There is no assignment mapping defined for payment card type '' 

Message no. CVI_MAPPING032 

A payment card type is to be assigned for which no entry to be assigned has been made in Customizing.
System Response
The assignment cannot be carried out.

Define a suitable assignment for the payment card type '' in the IMG activity Assign Payment Cards.



Reproducing the Issue

  1. Go to Migrate Your Data app
  2. Select your migration project
  3. Scroll down to Migration object: Customer
  4. Select the row for your .xml file
  5. Press start transfer and complete the migration activity
  6. System throws the error


This is due to the incorrect Payment Data which is present in migration file. In Payment Card Data only Digital Token is maintained and none of the card information is maintained. Hence, Payment Card Type becomes initial/empty and Business Partner to Customer synchronization fails and Customer data does not get created.


Pass the entire Payment Card information in the migration file. In case you do not want to create Payment Card information for Customers, do not pass any information (not even Customer number) in the Payment Data sheet of the migration file. Additionally if you face the same issue with existing Business Partner during re-execution of migration, then delete the corrupt Payment Card Data using the app Maintain Business Partner.

All migration objects mark only mandatory fields if they are technically required. All other cases depend on the business background and need to be handled within the processing logic, that is, within the API. If incomplete data is passed to the API it must return with an error message.

Once the initial data is migrated, the missing data could be reloaded with object Customer - Extend existing record by new org levels. The structures in the original object and the extend object should be identical except the additional field RUN_ID which is the counter to separate the enhancements.


Payment Card, CVI_MAPPING032, Payment Data, Assign Payment Cards, assignment mapping, migration, Customer, Payment Card Type , KBA , LO-MD-BP , Business Partners , Problem


SAP S/4HANA Cloud all versions