You can use the report RSDELCUA to delete all or part of an existing Central User Administration model. It also allows you to clean up invalid parts of old CUA models in the system.
Selection
- The checkbox for Test Mode is selected by default, to help prevent unintentional deletions.
- Deleting Individual Child Systems from the Current CUA Landscape
- You can use this option to delete one or more child systems from the current CUA landscape.
- The option to Delete the Entire CUA is only available in a CUA central system.
- Additional selection options, described in point A, are only available with this option. You can use these to decide how to handle users that do not have a system assignment for the CUA central client itself.
- Delete Invalid Content in CUA Tables
- All table content for which the model does not match the current, active model is deleted.
- (point A) The five options in the box How Should Users Without System Assignments for the CUA Central System Be Handled? are only available when deleting the entire CUA and also only in the CUA central system. They were introduced to replace the old behavior [see subpoint a)], which was prone to errors, and which globally locked these users.
- Also Lock Users Globally (previous behavior – not recommended)
- Also Lock Users Locally
- The local locking of a user has the advantage that this lock is not transferred when distributing/transferring the user to or from child systems.
- Make Users Valid Locally
- This option allows you to keep the existing [globally set] attributes for these users in the local CUA central client after the deletion of the CUA.
- Authorizations are not assigned to these users in this step, meaning that, although they would be able to log on to the central client afterwards, they would have no rights.
- Delete Users
- The result of this option is the closest to returning the client to its status before its role as the CUA central system.
- Do Not Make Any Changes (for a case where you plan to reactivate the CUA soon after the deletion)
- This option is preset under the assumption that what is usually required is only a temporary deactivation of the CUA, for example, to perform maintenance tasks and to ensure that no changes are made to the users during this time.
The deletion of the entire CUA and the deletion of individual child systems deletes the CUA model and the ALE distribution model in the affected child systems. If there are no problems during the RFC call of the functions required to do so, no manual postprocessing is required in transaction BD64 (Change Distribution Model).
The report writes change documents for the CUA landscape (change document object: USER_CUA) both in the CUA central system and in the child systems to be deleted. The report only records which child systems were deleted from the landscape in the CUA central system, however.
