Solution : https://service.sap.com/sap/support/notes/766703 (SAP Service marketplace login required)
Summary :
The SAP Note provides details on implementing and managing credit card encryption in the R/3 system. It outlines the usage of SAPCryptolib for encrypting payment card numbers, available from Release 46C with specific Support Packages and Kernel patches. Activation procedures are described in Note 633462. The encryption secures payment data against direct database access or simple reports but not against source code manipulation or unauthorized debugging. Notably, encrypted data impacts system performance and memory. During upgrades, especially from non-Unicode to Unicode systems, encryption keys must be carefully managed to avoid data loss.
Key words :
encrypted payment card numbers consume, encryption prevents direct database accesses, archive encrypted payment card data, function encrypts payment card numbers, display individual payment card numbers, authorization object f_bkpf_buk activity c4, include increased memory consumption, individual payment card number, transferred payment card number, decrypt payment card numbers
Related Notes :
| 1319517 | Unicode Collection Note |
| 1034482 | FAQ: Credit card encryption in CRM |
| 1029819 | Encryption of payment cards in SD and customer master |
| 894022 | NAE: Credit Card Masking |
| 813198 | Action 'C4' is missing for the VBAK_AAT authorization object |
| 812658 | Credit card information incomplete |
| 791178 | Credit card encryption in AR backend |
| 662340 | |
| 633462 | Encrypting credit card data |