## 12.2.9  Migration of Payment Card Data on SAP Business Partner
The following section is relevant for you only if you use the SAP business partner.
For the SAP business partner in S/4HANA systems to support encrypted storage of payment card data, a one-time data migration is required.
Before this migration, the system manages the payment card data in the database tables listed below (among others). In both tables, the payment card number is in plain text.
| Database Table   | Use                                                                           |
|------------------|-------------------------------------------------------------------------------|
| CCARD            | Data of payment card                                                          |
| BUT0CC           | Relationship between SAP business partner and payment card usingCCINSandCCNUM |
You migrate the data of database table CCARD completely to the database tables PCA\_SECURITY\_*. On the SAP Easy Access screen, choose Cross-Application Components Security of Payment Card Data
Encryption of Payment Cards Migration of Credit Cards . The encrypted value of the credit card number is stored during this process in the table PCA\_SECURITY\_RAW. The relationship to the credit card is reflected in table CCARD by the field CARD\_GUID, and the fields CCNUM and CCINS are initialized. The system considers only those entries in table CCARD that are still used in table BUT0CC.
## Database Tables
| Database Table   | Use                                                                         |
|------------------|-----------------------------------------------------------------------------|
| PCA_SECURITY_*   | Data of payment card                                                        |
| BUT0CC           | Relationship between SAP business partner and payment cards using CARD_GUID |
When migrating using the above program, you cannot spread the conversion over time. That means you have to completely convert the data in one run. The actual encryption can either take place directly during the migration, or you can encrypt the data later using program PCA\_MASS\_CRYPTING.
You are required to run the migration program even if you have not yet stored any payment card data in the business partner data (for instance, at the time of installation), but you want to store encrypted data in the future.
You cannot work with the system during the migration or after a partially successful migration, since it is not possible to predict how the executing programs will react. However, severe inconsistencies are to be expected.
To execute the migration program, you need an access code that SAP provides upon request. To request this code, enter a customer message under component AD-MD-BP. Refer to this security guide or to SAP Note 1032588.
For security reasons, the system stores a backup copy of the table entries in table CCARD\_COPY. After you have ensured that the system works correctly after the migration, you can delete the backup copy using program RCC\_MIGRATION\_DEL\_COPY.
If you are using Contract Accounts Receivable and Payable (FI-CA), and are using the business partner shadow table there to improve the performance of mass runs, also see the explanations in the Security Guide for Contract Accounts Receivable and Payable in the section Payment Card Industry Data Security Standard [page 125].