Jeroen Zuijderwijk
Read all my blogsArchiving basics:
Customizing options
For this blog archiving object CRM_ACT_ON (for Activities) is used. Other archiving objects have similar set-up options. Taking a look at the archiving object specific customizing, the following settings are made in the “Technical Settings” and “Check and Delete”. Also the “Residence Times Transaction Types” needs to be specified.
Technical settings
In technical settings, make sure the default variants for test and live mode are available. First of all, select the logical file name (if it’s not yet defined, look at Cross-Client File Names/Paths and discuss this with a SAP Basis consultant). Default variants are not available, so these need to be created before they can be used in the archiving job. Leave the other settings as they are.
Check and Delete
Now for the settings in Check and Delete. Notice there is a checkbox “Check Active” which indicates inclusion of the archiving object in the cross-archiving object archiving runs. Further on the use of this checkbox will be made clear. Then there are numbers to be filled for “Number of Calls Preselection Module”, “Package Size Preselection Module”, “Package Size Check Module”and “Resubmission Interval in Days”. The first 2 fields indicate how many objects are selected in total during 1 cross archiving object archiving run. E.g. in case of 5 calls to the preselection module with a package size of the preselection module of 100.000, results in an archiving run covering 500.000 objects. Playing around with these package size allows determination of the optimal package size. The fourth field, the resubmission interval ensures the same objects are not checked every day. The preselection run checks whether a document can be archived. This means it has no follow up documents, it is in a final status (so completed or canceled) and it’s been in the system longer than the specified residence time. The variant for the check job also needs to be created at this point.
Residence Times Transaction Types
For each transaction type, a residence type can be specified. Entering a residence time for a transaction type, ensures a transaction resides the system at least a certain amount of time.
Let’s start archiving
Alternative job planning
The deletion of all objects can be performed using report RSARCHD. The archiving object for which documents can be deleted entered into a variant and also the number of parallel deletion processes can be defined.. The delete job will only delete documents from the database if they are included in an archive file (so the write step completed successfully). This ensures you can still retrieve your data from the archive files in case it’s necessary. The archive files can be deleted from the file system once the data is no longer needed. Be aware that archiving data from your SAP CRM system doesn’t remove the information from your reporting environment. To comply with GDPR you may need to scramble or delete some of the data from that system as well.