Remove Inactive Versions of Data Elements and Tables 
When you invoke the transaction S_AUT01 Configuration of Audit Trail (Logging), inactive or data elements or tables may be displayed on the Variances System <=> Own Settings screen. It is possible that you are not able to change the inactive objects and that changes are only allowed in the case of active objects.
The data elements are inactive because the changes you made in the Data Dictionary have not been activated. This may be due to the following reasons:
A user has made changes that are not yet supposed to be active.
Activation is scheduled as a background job.
Changes were saved during the configuration of the logging in transaction S_AUT01. Activation using the Mass Activation function has not yet been carried out however.
The following section describes how to proceed to remove the inactive versions:
Check which changes have been made. You can get information on this by using transaction SE11 (Dictionary) to compare the inactive version with the active one. Check which user made the changes and clarify what was done and why.
If you made the changes, check whether activation has been scheduled as a background job. If so, wait until the latter has run.
If you made the changes and you want them to be adopted, you must activate the inactive objects. To do this, you can either use transaction SE11 (Dictionary) or run the Mass Activation program RADMASG0_C3 with transaction SE38. On the initial screen of the Mass Activation function, you can directly enter the desired objects by choosing the Direct Objects button. The Direct Objects dialog box then appears. Here you can enter the data elements or tables. Alternatively, you can enter a Transport Order on the initial screen for Mass Activation.
Note
When logging settings are transported to another system, only the active version is transported in each case. If you have released the transport to the target system prior to activating the changes in the source system, the changes will not be adopted in the target system.
A warning message then appears in the export log.
Re-transport the relevant objects to the target system after successfully activating them in the source system.