UE - Meldungen im Umfeld Benutzer und Berechtigungen

The following messages are stored in message class UE: Meldungen im Umfeld Benutzer und Berechtigungen.
It is part of development package SUSR in software component BC-SEC-USR-ADM. This development package consists of objects that can be grouped under "ABAP User Administration".
Message Nr
Message Text
000&1 is currently in use; if problems occur, contact user &2
001Error when preparing the search help (F4 input help)
002Cannot search with selected search pattern for field &1
003There are too many entries in the check table for field &1
005Function module &1 does not exist in system &2
009Action was canceled by user
010No profile found for search pattern &
011"Continue": Continue the selection
012"Cancel": Return to the selection screen and revise the criteria
013No user found for search pattern &
014No user group found for search pattern &
015No role found for search pattern &
016No object found for search pattern &
017No authorization found for search pattern &
018No area menu found for search pattern &
019No output device found for search pattern &
020Profile & is part of role &, which still contains other profiles
021You are not authorized to display users of group &1 in system &2
022No alias found for search pattern &
023No reference user found for search pattern &
025No valid input found for field &
026You are not authorized to display users in system &1
027No output device found for search pattern &
030Function is not supported in target system &
040User &1 has no system assignments
050Object &2 was assigned to user &1 (key -> long text)
051Assignment of object &2 to user &1 deleted (key -> long text)
052Assignment of application object &2 to user &1 changed
053All application references to user &1 deleted
060&1&2 &3&4
061&1 &2 &3 &4
091User renamed; password deactivated
100Test message for user &
111There is already an entry with this key
112Select an authorization object for this function
129Object &1 exists in package &2
130Object &1 exists in package &2 with the original language &3
131Object &1 is in namespace &2
132Object &1 has not yet been exported (unrestricted changes are possible)
133Object &1 has already been exported (only restricted changes possible)
134Object &1 does not have an object directory entry
135Permissible activities not maintained for field ACTVT for object &1
136&1 already exists in object &2.
137Object name &1 does not match package &2
139Object &1 is unchanged; saving is not necessary
140Create or adjust object documentation in language &1
141Create the object documentation after saving the object
142Create or adjust the object documentation
143There is no object documentation in original language &1
150Invalid authorization field name (&1 is more than 10 character long)
151No authorization field with the name &1 exists
200Authorization object names are not part of the namespace concept
202Object &1 has already been delivered; only restricted changes possible
203Object &1 has already been delivered; deletion is not permitted
205Object &1 is in the customer namespace; ENTER -> Continue
206Object &1 is in SAP namespace; creating it is classified as modification
207Object &1 belongs to SAP; extending field changes are possible
208Object &1 belongs to SAP; header data changes are possible
209Object &1 belongs to SAP; deletion is not permitted
210Object class &1 is in the SAP namespace; change here is a modification
211Object class &1 is in customer namespace; creation here not meaningful
212Object &1 cannot be edited in this system
213Only restricted editing of object &1 is possible in this system
214&1 is not permitted as an object name
215Namespace check for &1 failed
216Namespace check for &1 failed; cannot change
217&1 not suitable as namespace for authorization objects
218Namespace &1 is not registered in this system
219Object &1 cannot be saved in package &2
220Save object &1 in a package in namespace &2
221Object &1 belongs to &2; changes are modifications
222Object &1 belongs to &2; supplementary field changes are possible
230Object &1 is not used in authorizations and roles
231Object &1 is not used in authorization default values (&2)
240Object &1 saved
241Save aborted
242Object saved incorrectly
298Select exactly one authorization field for this function.
299Navigation from this field is not supported
300Authorization field &1 is used in &2 objects.
301Authorization field &1 is not used in any objects.
302&2 applications contain the authorization field &1 in SU22 data.
303&2 applications contain the authorization field &1 in SU24 data.
304&2 roles contain the authorization field &1.
305Authorization field &1 is unchanged. You do not need to save.
306Authorization field &1 saved.
307Authorization field data contains errors. Cannot save.
308Authorization field &1 contains warnings but can be saved.
309Data element for authorization field &1 changed from &2 to &3.
310Authorization field name &1 (length &2) can contain max. 10 characters.
311Authorization field &1 is not fully defined (&2 missing).
312Output length &1 for authorization field is too big (maximum 40 char).
313Output length &1 for authorization field is unsuitable (at least 1 char).
314Output length &1 reduced to permitted value &2.
315New output length &1 is not permitted.
316New output length &1 exceeds the permitted value (maximum 40 characters).
317Output length changed to permitted value &1.
318Assignment of value help for field value maint. changed from &1 to &2
320Data type &1 cannot be used for authorization fields.
321Use of data type &1 is restricted for authorization fields.
322Exit module &1 does not actively exist.
323Exit module &1 is not suitable as a maintenance exit.
324Check table &1 does not actively exist.
325Table &1 is not suitable as a check table.
330Authorization field &1 deleted.
331&1 is locked by user &2
332Object & is not suitable as search help
400Intervals are not supported
401No authorization value was specified
412Parameter error: SEC_AREA is required
500The combination: object &1 for authorization &2 does not exist
800Application &1 is locked due to zero downtime maintenance
Privacy Policy