Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SEC-USR-ADM (Application Component) User and Authorization Management⤷
SUSR (Package) ABAP User Administration 
Attribute
| Message class |  |
01 | |
| Short Description |  |
General Basis, e.g. user and authorization maintenance | |
| Message Number |  |
394 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20130531 |
Message Text
Help Document
Diagnosis
The CUA definition is inconsistent, because
- the ALE model is inconsistent.
For the ALE model, Central User Administration requires a uniquely defined central system (only a central system). All child systems must also be included in a CUA only once (no duplicated systems).
- Some child systems were deleted from the ALE model, while they are still in the CUA model
- The central system of the ALE model does not match the central system of the CUA model
- The CUA model exists, but the ALE model does not
System Response
Procedure
To resolve the inconsistency of the ALE model, you can either change or create the ALE model in transaction BD64 or save the CUA view in transaction SCUA, so that the ALE model is regenerated in accordance with it. If you perform the adjustment in transaction SCUA, you can either save the CUA model immediately or first change and then save it. If you want to remove some child systems from the CUA, you should first remove these in the CUA model on the initial screen of the transaction SCUA by choosing Delete, both in the central and relevant child systems.
Procedure for System Administration
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in |
