Diagnosis
You have attempted to delete an authorization field that is still inuse. This happens, for example, if you indicate the characteristic as'Not authorization relevant' in the maintenance of the InfoObjects.

System Response
The action was terminated and the authorization is just as active as itwas before.

Procedure
To be able to delete an authorization field it must no longer appear inauthorization objects. As authorization objects themselves are used inauthorizations and user profiles, changes must also be made in these.
Proceed as follows:
Determine those authorization objects that use the authorization field.You use the transaction 'Maintenance of the authorization objects'(RSSM) for this. On the initial screen do not select any objects andhit the pushbutton 'Auth.fields hierarchy'. You will then get a treedisplay of all authorization fields as well as the used authorizationobjects, authorizations and profiles. By opening a subtree in thisgraphical display the mutual dependencies can be recognized.
Of course you can also determine the individual dependencies using thecorresponding maintenance transactions: All authorizations forauthorization objects with the transaction SU03 and user profiles withtransaction SU02.
Delete the dependent authorizations in the user profiles with thetransaction SU02.
Delete the dependent authorizations with transaction SU03.
Delete the dependent authorization objects with transaction RSSM.
You can now delete the authorization fields or switch the InfoObject to'non-authorization-relevant'.