SU2X - Nachrichten zur Berechtigungsvorschlagswertepflege
The following messages are stored in message class SU2X: Nachrichten zur Berechtigungsvorschlagswertepflege.
It is part of development package S_PROFGEN in software component BC-SEC-AUT-PFC. This development package consists of objects that can be grouped under "ABAP Role Administration (Profile Generator)".
It is part of development package S_PROFGEN in software component BC-SEC-AUT-PFC. This development package consists of objects that can be grouped under "ABAP Role Administration (Profile Generator)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Internal error while saving |
| 002 | Action was canceled by user |
| 003 | Saving not necessary (data is unchanged) |
| 004 | There is no data for your selection |
| 005 | System or client is locked against changes; action is not possible |
| 006 | Table TBRG is locked by user &1; action is not possible |
| 007 | General error in lock management |
| 008 | &1 data for &2 (&3) saved |
| 009 | &1 data for &2 (&3) unchanged |
| 010 | Default variant &1 was saved |
| 011 | Default variant &1 was deleted |
| 012 | There is already a default variant with the name &1 |
| 013 | Object &1 is already being used. |
| 014 | Cannot delete default values while &1 exists |
| 015 | Authorization default value maintenance restricted due to system setting |
| 016 | Selected application type not permitted for this function |
| 017 | Text change for application &1 (&2) was saved |
| 018 | Status change is not possible in display mode |
| 019 | Authorization default values are missing for object &1 |
| 020 | Select exactly one entry for processing |
| 021 | Select at least one valid row for processing |
| 022 | Group definition for authorization object &1 deleted |
| 023 | Group definition saved for authorization object &1 |
| 024 | Group definition already exists for authorization object &1 |
| 025 | You need to specify the reference field for group maintenance |
| 026 | Reference field &1 is not contained in object &2 |
| 027 | Group definition for authorization object &1 does not exist |
| 028 | Package assignment for group &1 adjusted in accordance with TADIR |
| 029 | Inconsistent authorization default: Object &1, field &2 |
| 030 | You do not have sufficient authorization to perform this action |
| 031 | Navigation not supported for &1 |
| 032 | Default authorization values are incomplete |
| 033 | Please select which default data to load from. |
| 034 | Could not delete entry &1 |
| 035 | Could not save entry &1 |
| 036 | Object & cannot be deleted because it still has users. |
| 040 | Deletion only possible in SU22 individual maintenance |
| 041 | Application &1 still exists in system; deletion not permitted |
| 049 | There is no short description for authorization field &1. |
| 050 | You have no authorization for field &1 (action: &2). |
| 051 | &1 fields are not displayed due to insufficient authorizations. |
| 052 | You are not authorized to view the complete selection list. |
| 053 | No display authorization for default values for application &1. |
| 054 | No change authorization for default values for application &1. |
| 055 | Default values loaded for application &1 (work area &2). |
| 056 | Object list: Status '&2' was added to object '&1' automatically |
| 057 | Object list: Maintenance status of object &1 was defined automatically |
| 058 | Object &1 does not exist; editing status set to 'No Default' |
| 059 | Object &1 does not exist; set the maintenance status to "No default" |
| 060 | Object list: Maintenance status for object &1 defined automatically |
| 061 | Invalid default values for object &1 detected in &2 |
| 062 | Default status for object '&1' adapted in accordance with SU22_EXIT. |
| 063 | Object list: Object &1 does not exist. |
| 064 | Field list: Field &1 is not part of object &2. |
| 065 | Cannot be saved. See the SU22_EXIT error. |
| 096 | File does not contain &1 for &2; no update |
| 097 | Simulation: &1 for &2 were changed |
| 098 | &1 changes for &2 already included; no update required |
| 099 | Invalid parameter combination in API call |
| 100 | Scenario &1: Authorization check for object &2 failed |
| 101 | Simulation: Variant &1 created. |
| 102 | There is no system documentation for scenario &1 |
| 103 | The documentation for scenario &1 is only possible via an external note |
| 104 | Scenario &1 not yet stored as active version |
| 105 | &1 saved |
| 106 | Database change failed |
| 107 | No change required |
| 108 | Rows were marked for update |
| 109 | &1 rows marked for update |
| 110 | Scenario &1 is locked by user &2 |
| 111 | Scenario &1 is locked by another user |
| 112 | Error in lock management |
| 113 | Transportable entries were added to request |
| 114 | You can only select one row for this function |
| 115 | Scenario &1 is already being procssed and therefore cannot be deleted |
| 116 | Transportable entries were added to request |
| 117 | Variant &1 created. |
| 120 | Changed data must be saved before using this function |
| 121 | &1 scenarios adjusted |
| 122 | Entry required in field &1 |
| 123 | Specify a valid value for &1 |
| 124 | If possible, specify an SAP Note that describes the scenario |
| 125 | Scenario documentation must be maintained (&1) |
| 200 | Consistency check, undocumented error code &1 |
| 201 | Object &1 is not assigned to a valid object class |
| 202 | Object &1 exists in the default data, but does not have an object class |
| 203 | Object &1 exists in the check indicator, but not in SU21 |
| 204 | Object &1 exists in the default values, but is not defined in SU21 |
| 205 | Object definition &1 does not contain any authorization fields |
| 206 | Default for inconsistent authorization object |
| 207 | Object is used consistently in &1 applications |
| 208 | There are no default values for this object |
| 209 | Default for object &1 does not contain any defined authorization fields |
| 210 | Field list of default for object & is incomplete |
| 211 | Default values do not match organizational level &1 |
| 212 | Non-organiz. level field contains typical organizational level value &1 |
| 213 | Organizational level field &1 is not used the default values |
| 214 | Organizational level field &1 is not defined as an authorization field |
| 215 | Organizational level field &1 is not consistently defined in SU20 |
| 216 | Organizational level field & is not used in authorization objects |
| 217 | Organizational level is used in default values of & applications |
| 218 | Object &1 - Error in ACTVT authorization default values |
| 219 | Object &1 - No activities maintained for field ACTVT |
| 220 | Unknown fixed values in authorization default values of object & |
| 221 | Security-critical default value for object &1 |
| 222 | Object has errors and cannot be transported |
| 223 | Edit the SAP_NEW data; object is relevant for SAP_NEW |
| 224 | Missing default values for object &1 have been added |
| 225 | &2 data contains invalid default values for object &1 |
| 226 | Invalid default values for object &1 removed from &2. |
| 227 | Field list of default for object &1 corrected/supplemented. |
| 230 | &1 - incorrect org. level value (object &2, field &3) &4 |
| 231 | Invalid field value &1 (object &2, field &3) &4 |
| 232 | Multi-line default contains &1 (object &2, field &3) &4 |
| 233 | Default values missing for &1 object &2 &3 |
| 234 | Unknown default value &1 for &2 &3 &4. |
| 235 | Incomplete default for &1 object &2 field &3 &4 |
| 236 | Invalid default for &1 object &2 field &3 &4 |
| 238 | &1 - Check flag &2 is invalid - Object &3 does not exist (&4) |
| 239 | Invalid default for object &1 (&2) - Object classes &3 &4 missing |
| 240 | Invalid default for object &1 (&2) - Obsolete object classes &3 &4 |
| 241 | &1 - invalid check flag 'No Check' for object &2 &3 |
| 242 | Unknown check flag value &1 for &2 &3 &4. |
| 243 | Object &1 already exists in the default values for (&2) |
| 244 | Identical default values for object &1 have been compressed (&2) |
| 245 | Identical default values for object &1 are not allowed (&2) |
| 250 | Start authorization default for object &1 for &2 &3 |
| 251 | Invalid check flag &1 for object &2 for &3 &4 |
| 252 | Invalid start authorization default for object &1 for &2 &3 |
| 253 | Required object &1 missing for &2 &3 |
| 254 | Superfluous check flag for object &1 in &2 &3 |
| 300 | Leading application &1 must be deleted first. |
| 301 | Leading application &1 must also be deleted. |
| 302 | &1 &2 cannot be removed from the object list |
| 303 | Removed object &1 is in trace data of application |
| 304 | Object &1 removed from object list |
| 497 | Start of regeneration of profile SAP_ALL |
| 507 | SAP_ALL profile regenerated in client &1 by user &2 |
| 508 | Error when generating SAP_ALL: client &1, user &2, error &3 |
| 509 | Profile SAP_ALL was added in full to client & |
| 516 | SAP_ALL profile: start of processing in client &1 |
| 533 | SAP_ALL profile regenerated in all clients |
| 600 | Select using either check indicators or default status |
| 601 | Select an application type |
| 602 | Leading application &1 (&2) does not exist |
| 603 | No SU22 header data exists yet for the default data for &1 (&2) |
| 604 | &1 for &2 ( &3 ) is locked by user &4. |
| 605 | &1 for &2 ( &3 ) is locked by another user. |
| 606 | Save the newly added objects. |
| 610 | Maintain the successor transaction in transaction SU22 (see long text). |