You can archive change records for the following changes to user master records:
--> Authorization changes and changes to other user characteristics
--> Changes to user passwords
Object Definition
The archiving object US_USER is used to archive password change records from table USRH04.
The object US_PASS archives records of changes to user master records other than password
changes.
For example, authorization changes are recorded in a user master record. These recordings are
stored in the USRH02 table.
Technical Information
Unless you are archiving very many 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
Dependencies
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.
Archiving Criterion and Retention Requirements
SAP recommends a retention period 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.
Log
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.
Creating an Archive File
Choose Tools --> Administration --> User maintenance. Then choose Users --> Environment -->
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.
Executing the Deletion Program
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.
How to Earn Rs.25000 every month in internet without Investment?
Archiving User Change Records
Labels:
Archiving
Subscribe to:
Post Comments (Atom)
topics
-
▼
2009
(764)
-
▼
August
(65)
- Applying Security Constraints to a Security Role
- Mapping Users and Groups
- Architecture of Security Roles
- Determining Change Documents
- Transferring Users from New Systems
- Licence Data Tab Page in SU01
- Personalization Tab Page in Su01
- Groups Tab Page in SU01
- Authorization Profile SAP_NEW
- Authorization Profile SAP_ALL
- Profiles Tab Page in SU01
- SNC Tab Page in SU01
- Determining Roles, Profiles, Authorizations, and A...
- User Information System
- Assigning Users
- Assigning Roles to Users in User Maintenance
- User Maintenance with Active Central User Administ...
- Assign a Standard Role to a User
- Roles Tab Page in SU01
- Logon Data Tab Page in SU01
- Creating and Maintaining User Master Records
- The SAPOSCOL service in Windows has been deleted s...
- How to find derived roles under the master roles
- How to Reset Different Buffers in Sap
- How to find an Operation mode Switch
- How to check if CUA is used
- How to install an add-on using a SAINT transaction...
- How do you rollback a transport in R/3 Enterprise?
- How to stop Active Background Jobs?
- SAP Application Server States
- Memory Pipes
- Using the ICM Monitor
- Creating a Connection to a Reference System
- Control Object Types
- Displaying a Job Log
- Storage Requests: Detail View
- Monitoring Storage of Print Lists
- Checking Space Usage in TemSe
- Location for Storing Spool Data
- Storage Methods for Spool Objects in TemSe
- Archiving IDocs
- Archiving Profile Change Records
- Archiving Authorization Change Records
- Archiving User Change Records
- Archiving User and Authorization Changes
- Role Maintenance
- Configuring the SAP Front End
- Mapping Windows Users to SAP Users for Kerberos SSO
- Single Sign-On with Microsoft Kerberos SSP
- Configuring SNC: Using CPIC from AS ABAP
- Configuring SNC: SAProuter à SAProuter
- Configuring SNC: SAP GUI à AS ABAP
- Configuring SNC: Printing
- Checking the Status of Background Processing
- Importing a Queue
- Checking Logs
- Rules for the Queue
- Defining a Queue Based on a Target Support Package
- Defining a Queue Based on Multiple Software Compon...
- Defining a Queue Based on a Software Component
- Deleting the Queue
- Defining the Support Package Queue
- Support Package Manager Settings
- Loading Support Packages from the Front End
- Loading Support Packages from SAP Support Portal o...
-
▼
August
(65)
No comments:
Post a Comment