Archiving User Change Records (BC-ADM-SEC)

The archiving object US_USER is used to archive password change records from table USH04. The object US_PASS archives records of changes to user master records other than password changes. In this way, for example, changes in the authorizations in a user master record are recorded. These recordings are stored in the USH02 table.

Unless you are archiving a large number of change records, an archiving run should have no significant effect on the performance of your system. The user change records require the following memory space (uncompressed):

• US_PASS password change records: 300 bytes
• US_USER user change records: 100 bytes

When you archive user change records, it does not have any effect on other archivable data. There are no particular dependencies or relationships between user change records and other archivable data.

You can use the archiving objects US_PASS and US_USER within the framework of Information Lifecycle Management. To be able to do this, you must activate the related business functions. The system then shows the ILM Actions group box. Using these actions, you can, for example, run archiving during which the system evaluates the retention periods entered in Information Retention Manager. You can also create snapshots (copies) of data, and you can delete data that does not meet your criteria.

We recommend a storage duration of 10 years for all user and authorization change records.

Change records are archived according to the date that you specify. All records older than the date specified are archived. Old archives are not automatically deleted.

The log files generated by archiving and deleting records are stored in the SAP spool system. The archiving log records the number of change records archived. The delete log lists the change records that were deleted after the archiving session.

Choose Tools   → Administration   → User Maintenance.Then choose Users,followed byEnvironment → Archive and Read, and then the required archiving function.

The archiving function calls the standard archiving interface, where the correct archiving object is already specified.

You need only specify (or create) an appropriate report variant, specify the start time and printing specifications for the background processing of the report, and schedule the report with Create job.

See also the documentation on the archiving procedure in general. You will find this documentation in the first section of this document.

You must explicitly delete archived records after an archiving session has been successfully completed. Be sure to check the archiving log to be sure that the archiving session has been completed successfully. Also, be sure that you specify the same date for the deletion program. Otherwise, too many or too few change records will be deleted.