Purpose
This report performs these two functions:

• It determines the number of data records for a key version, and sets the
key version to "can be deleted" if it is no longer used.

• It encrypts the payment card data of an old key version using the
current key.

Integration
The report processes data from various application tables.
The entire dataset is divided into sections of about the same size by athree-digit number ("subarea"). You can use this number for parallelprocessing.
If you want to delete an old key version using the Administration ofKey Versions (SSFVA) transaction, you must first set the keyversion to "can be deleted" using this report.

Prerequisites
You activated the business function PCA_KEYV (Periodic KeyReplacement for Payment Card Encryption).
You set the Key Replacement Active indicator in Customizing forCross-Application Components under Payment Cards -> BasicSettings -> Make Security Settings for Payment Cards.
You created a key version for SSF application PAYCRV (transactionAdmin. of Key Versions for PAYCRV - CCSECA).
The secondary index is activated automatically when you activate thebusiness function PCA_KEYV.

Selection
Enter a version number and the maximum runtime for the report.

Output
The report displays an application log.
If you run the report in the background, the system stores theapplication log on the database.

Example
You have a large number of data records in the system and schedule tenparallel jobs as listed below:


• Job 1: subareas 000 to 099


• Job 2: subareas 100 to 199


• Job 3: subareas 200 to 299


• Job 4: subareas 300 to 399


• Job 5: subareas 400 to 499


• Job 6: subareas 500 to 599


• Job 7: subareas 600 to 699


• Job 8: subareas 700 to 799


• Job 9: subareas 800 to 899


• Job 10: subareas 900 to 999

You have the jobs run at night for three hours. The next day, you checkhow many data records remain.