SRAL - Read Access Log Message Class
The following messages are stored in message class SRAL: Read Access Log Message Class.
It is part of development package SREAD_ACCESS_LOG_CORE in software component BC-SEC-RAL. This development package consists of objects that can be grouped under "Read Access Logging: Core Framework".
It is part of development package SREAD_ACCESS_LOG_CORE in software component BC-SEC-RAL. This development package consists of objects that can be grouped under "Read Access Logging: Core Framework".
Message Nr ▲ | Message Text |
|---|---|
| 000 | WS Configuration for type '&1', name '&2', operation '&3' is not locked |
| 001 | WS Configuration for type '&1',name '&2',operation '&3' cannot be locked |
| 002 | WS Configuration for type '&1',name '&2',operation '&3' is terminated |
| 003 | Field '&1,&2,&3,&4' is not contained in field list |
| 004 | ABAP data type '&1' is not supported |
| 005 | Data reference for ABAP data type '&1' could not be created |
| 006 | Error during rules processing. See previous exception. |
| 007 | Error when saving WS Configuration: Type '&1',name '&2', operation '&3' |
| 008 | Log Group '&1' does not exist in configuration '&2' |
| 009 | Condition '&1' does not exist in configuration '&2' |
| 010 | WS Configuration for type '&1', name '&2', operation '&3' does not exist |
| 011 | Select Option '&1' for config. '&2' in condition '&3' does not exist |
| 012 | Expression ID '&1' for config. '&2' in condition '&3' does not exist |
| 013 | Condition ID '&1' for config. '&2' does not exist |
| 014 | Sel.Opt. '&1' for config. '&2' in sel.option '&3' in does not exist |
| 015 | Only ranges for the same field can be used in one select option |
| 016 | Select Option '&1' in expression '&2' in condition '&3' does not exist |
| 017 | Log Group '&1' in configuration '&2' cannot be saved |
| 018 | Log Group Fields in Log Group '&1' in operation '&2' cannot be saved |
| 019 | Log Field '&1' does not exist in Log Group '&2' in configuration '&3' |
| 020 | Log Field '&1' already exists in Log Group '&2' in configuration '&3' |
| 021 | Condition '&1' does not exist in Log Group '&2' in configuration '&3' |
| 022 | Condition '&1' already assigned to Log Group '&2' in configuration '&3' |
| 023 | Failed to convert data to raw (&1&2&3&4) |
| 024 | Data type '&1' is not supported |
| 025 | Failed to convert raw to data (&1&2&3&4) |
| 026 | Search '&1' saved |
| 027 | Search '&1' could not be saved |
| 028 | Saved Search '&1' deleted |
| 029 | Saved Search '&1' could not be deleted |
| 030 | Low Value '&1' has to be less than High Value '&2' |
| 031 | Unsupported channel ID '&1' |
| 032 | Failed to set log environment for channel type '&1' |
| 033 | Failed to get SHM write access object for current work process: ID='&1' |
| 034 | Failed to perform operation '&1' on SHM access |
| 035 | Failed to convert data to string |
| 036 | No Channel ID provided |
| 037 | WS Config. for type '&1', name '&2', operation '&3' is locked by '&4' |
| 038 | Failed to access table '&1': operation '&2', connection '&3' &4 |
| 039 | Unexpected channel id &1 (expected &2) |
| 040 | Failed to build field list for object type '&1' object '&2' |
| 041 | Field '&3' in msg type '&2', dir. '&1' is not part of the WS operation |
| 042 | Fieldlist is empty |
| 043 | Activation of WS Config. for type '&1', name '&2', operation '&3' failed |
| 044 | Deactivation of WS Config. for type '&1',name '&2',operation '&3' failed |
| 045 | Log Group '&1' already exists in configuration '&2' |
| 046 | Condition '&1' already exists in configuration '&2' |
| 047 | Enter another expression name. '&1' already exists in condition '&2'. |
| 048 | Option '&1' in select option is not supported |
| 049 | Log Group '&1' cannot be removed. Unassign all conditions first |
| 050 | Data type '&1' requested, but actually found type '&2' |
| 051 | Field '&1' in configuration '&2' for channel '&3' does not exist |
| 052 | Field '&1' for channel '&2' cannot be saved |
| 053 | Configuration with ID '&1' for channel '&2' does not exist |
| 054 | Configuration instance already terminated |
| 055 | Error when activating WS config: Type '&1',name '&2', operation '&3' |
| 056 | Configuration instance already locked by another user |
| 057 | Log fields of log group '&1' in configuration '&2' cannot be saved |
| 058 | Group '&1' must not consist of response and fault fields simultaneously |
| 059 | Condition &1 must not consist of response and fault fields simultaneously |
| 060 | Configuration '&1' must be locked |
| 061 | Assign. of Group &1 to Cond. &2 must not contain resp. and fault fields |
| 062 | Building element structure list failed for configuration with ID '&1' |
| 063 | No configuration exists for Web Dynpro Recording '&1' |
| 064 | Log Domain '&1' in business area '&2' does not exist |
| 065 | Building element structure with fieldID '&1' failed |
| 066 | Log Domain '&1' in business area '&2' is locked by '&3' |
| 067 | You are not authorized to perform this operation |
| 068 | Could not read new value for period |
| 069 | User exclusion list could not be created |
| 070 | User exclusion list could not be deleted |
| 071 | User could not be added to user exclusion list |
| 072 | User could not be deleted from user exclusion list |
| 073 | User exclusion list entries could not be read |
| 074 | User exclusion list '&1' does not exist |
| 075 | User '&1' exists already in exclude list '&2' |
| 076 | Invalid user exclusion list name |
| 077 | Log Domain business area '&1' must not contain the symbol '/' |
| 078 | Log Domain Name '&1' must not contain the symbol '/' |
| 079 | Specify all required fields |
| 080 | Username '&1' is not valid |
| 081 | Log Group '&1' is not consistent. Select Logging Type for all fields |
| 082 | Configuration '&1' is not consistent. Create at least one Log Group |
| 083 | Only characters '&1' are permitted in text '&2' |
| 084 | Failed to save assignments of Log Group '&1' in Configuration '&2' |
| 085 | Web Service Consumer configuration '&1' cannot contain response fields |
| 086 | Condition '&1' is still assigned in Log Group '&2' |
| 087 | User exclusion list '&1' is locked by '&2' |
| 088 | User exclusion list is not locked |
| 089 | Configuration was saved |
| 090 | Configuration values could not be saved: &1 |
| 091 | Error while writing RAL data |
| 092 | New value has not been applied |
| 093 | Web Dynpro Configuration for Recording '&1' does not exist |
| 094 | Web Dynpro Configuration for Recording '&1' is locked by '&2' |
| 095 | Web Dynpro Configuration for Recording '&1' cannot be locked |
| 096 | Assign a condition to Log Group '&1' or set 'Without Condition' |
| 097 | Assign field(s) to Log Group '&1' |
| 098 | User exclusion list '&1' already exists |
| 099 | Configuration ID '&1', Channel ID '&2' has been activated |
| 100 | Configuration ID '&1', Channel ID '&2' has been deactivated |
| 101 | Cannot save WD config. for recording '&1', appl. '&2', appl. config. '&3' |
| 102 | Activation of configuration '&1' for channel ID '&2' failed |
| 103 | Logging Purpose with ID '&1' already exists. Choose a different ID |
| 104 | Web Service operation '&1' cannot be configured as it is asynchronous |
| 105 | Log Group '&1' must not consist of system fields only. Add channel fields |
| 106 | Inactive Configuration already exists for Object '&1' |
| 107 | Active Configuration already exists for Object '&1' |
| 108 | Error: &1 &2 &3 &4 |
| 109 | Configuration '&1' (Channel ID = '&2') has been saved |
| 110 | Configuration '&1' for channel '&2' has been deleted |
| 111 | User exclusion list has been saved |
| 112 | User '&1' has been added to user exclusion list |
| 113 | User '&1' has been removed from user exclusion list |
| 114 | RAL has been activated in client '&1' |
| 115 | RAL has been deactivated in client '&1' |
| 116 | RAL error log level has been changed to &1 |
| 117 | RAL performance trace level has been changed to &1 |
| 118 | RAL log retention period has been changed to &1 |
| 119 | Create at least one Expression for Condition &1 |
| 120 | Add at least one field to the Expression &1 |
| 121 | New Configuration value has been saved: &1 |
| 122 | New Logging Purpose '&1' has been created |
| 123 | Logging Purpose '&1' has been deleted |
| 124 | New Log Domain '&1' has been created |
| 125 | Log Domain '&1' has been deleted |
| 126 | Log Domain '&1' has been saved |
| 127 | For RFC '&1' field path '&2' cannot be found in runtime parameter list |
| 128 | For RFC '&1' parameter with name '&2' has no runtime value provided |
| 129 | For RFC '&1' path '&2' does not correspond to parameter structure |
| 130 | bgRFC Unit ID &1 not found in RAL cache |
| 131 | RFC config. for role '&1', func. module '&2' is locked by '&3' |
| 132 | RFC config. for role '&1', func. module '&2' cannot be locked |
| 133 | Could not write to bgRFC RAL cache |
| 134 | RFC channel log data transformation error |
| 135 | Invalid RFC role '&1' |
| 136 | Error when activating RFC config: role '&1',name '&2' |
| 137 | Error when saving RFC Configuration: Function Module Name '&1' |
| 138 | RFC Config. for function module name '&1' is locked by '&2' |
| 139 | RFC Config. for function module name '&1' cannot be locked |
| 140 | Enter a Function Module name |
| 141 | Check Function Module name '&1' |
| 142 | System Error during function call |
| 143 | Enter a distinct Function Module name |
| 144 | Purpose '&1' is locked by '&2' |
| 145 | New Purpose &1 has been created |
| 146 | Purpose '&1' has been deleted |
| 147 | Purpose &1 does not exist |
| 148 | Error getting RFC metadata |
| 149 | Invalid RFC name '&1' |
| 150 | Invalid monitor type '&1' |
| 151 | ABAP data type '&1' in field '&2' is not supported in conditions |
| 152 | check if RFC is set for Function Module '&1' |
| 153 | Field '&1' is not contained in field list. |
| 154 | 'Exporting' Fields are not allowed for Client RFC Configurations |
| 155 | Select at least one user |
| 156 | Read access logging not connected to an archive |
| 157 | Purpose '&1' has been changed |
| 158 | Error opening archive files. Error code = '&1' |
| 159 | Select an archive file |
| 160 | Error reading archive file. Error code = '&1' |
| 161 | Search criteria '&1' no supported for selected persistency source. |
| 162 | Error reading archive index. |
| 163 | No archive infostructure found |
| 164 | Search name not availble in archive index |
| 165 | Enabling in Client is locked by '&1' |
| 166 | Enabling in Client cannot be locked |
| 167 | Configuration for Function Module '&1' and role '&2' already exists |
| 168 | Enabling in Client must be locked |
| 169 | Index based search not possible. No index found. |
| 170 | Field '&1' in configuration '&2' does not exist |
| 171 | Error getting datatype information for &1 |
| 172 | No ABAP Type for datatype &1 found |
| 173 | Log Context '&1' does not exist in configuration '&2' |
| 174 | Log Context '&1' in configuration '&2' cannot be saved |
| 175 | Fields of Log Context '&1' in configuration '&2' cannot be saved |
| 176 | Field '&1' does not exist in Log Context '&2' in configuration '&3' |
| 177 | Field '&1' already exists in Log Context '&2' in configuration '&3' |
| 178 | Log Context '&1' already exists in configuration '&2' |
| 179 | Only one log context element in configuration '&1' is allowed |
| 180 | Only one field in log context '&1' in configuration '&2' is allowed |
| 181 | Log Domain '&1'does not fulfill required pattern: softwarecomponent/name |
| 182 | Field '&1' cannot be assigned to '&2'. Data type information is missing |
| 183 | Log Domain '&1' cannot be deleted, it is still used in Log Group(s) |
| 184 | Logging Purpose '&1' cannot be deleted, it is still used in Log Group(s) |
| 185 | Enter a name |
| 186 | Select a Saved Search |
| 187 | Log Domain already exists |
| 188 | Enter a name |
| 189 | Cannot save Dynpro config. for recording '&1', main program '&2' |
| 190 | Dynpro Configuration for Recording '&1' does not exist |
| 191 | Dynpro Configuration for Recording '&1' is locked by '&2' |
| 192 | Dynpro Configuration for Recording '&1' cannot be locked |
| 193 | Configuration '&1' is not consistent. Create one or no log context |
| 194 | Configuration '&1' is not consistent.Log context must be logged with val. |
| 195 | Dynpro path invalid at pos &1. Reason: &2 |
| 196 | Disable recording '&1' for channel '&2' first |
| 197 | Recording '&1' for channel '&2' already exists. Choose a different name |
| 198 | System Field '&1' cannot be defined as Log Context |
| 199 | Path '&1' has invalid format |
| 200 | Path '&1' does not end with current program name '&2' |
| 201 | Path '&1' does not end with current dynpro '&2' |
| 202 | Path '&1' does not contain the program |
| 203 | Path '&1' does not contain the dynpro |
| 204 | Path '&1' does not contain the container |
| 205 | Select a valid field type for field '&1' |
| 206 | Field type configuration is not supported for channel '&1' |
| 207 | Assign Field to Log Context '&1' |
| 208 | No configurable Fields available in '&/1', only Response and/or Faults |
| 209 | Objects are inserted into transport request &1 (description: &2) |
| 210 | &1 object entries for transport could not be created |
| 211 | Transport mode '&1' is invalid |
| 212 | New transport &1 (description: &2) created |
| 213 | Objects cannot be inserted into transport request '&1' |
| 214 | Transport request '&1' is invalid. Objects cannot be inserted |
| 215 | No changes are allowed in this system client |
| 216 | Field'&1' in LG'&2' is a password field. Only 'Without Value' is allowed |
| 217 | Password field '&1' is not supported in conditions |
| 218 | Password field '&1' is not supported in log context |
| 219 | Purpose '&1' has been saved |
| 220 | Recording '&1' for channel '&2' has been saved |
| 221 | Recording '&1' for channel '&2' has been deleted |
| 222 | Recording '&1' for channel '&2' has been enabled |
| 223 | Recording '&1' for channel '&2' has been disabled |
| 224 | Select at least one log domain |
| 225 | Select at least one configuration |
| 226 | Select at least one logging purpose |
| 227 | Select at least one recording |
| 228 | Changed objects are inserted into task &1 of request &2(description:&3) |
| 229 | Field '&1' has been added to recording '&2' |
| 230 | Field '&1' has been removed from recording '&2' |
| 231 | Changes are automat. recorded. Only activate consistent configuration(s). |
| 232 | Set at least one active Condition assigned to Log Group '&1' |
| 233 | Path must not be initial |
| 234 | Dynpro Path '&1' must not end with a contain |
| 235 | Invalid dynpro length '&1' in path '&2' |
| 236 | Column '&1' has been added to recording '&2' |
| 237 | Column '&1' has been removed from recording '&2' |
| 238 | Field '&1' is not contained in recording '&2' |
| 239 | Column '&1' is not contained in recording '&2' |
| 240 | Recording '&1' already contains column '&2'. Column information updated. |
| 241 | Recording '&1' already contains field '&2'. Field information updated. |
| 242 | Configuration entries for transport could not be created |
| 243 | User exclusion list entries for transport could not be created |
| 244 | "Enabling in client" entry for transport could not be created |
| 245 | Recording entry for transport could not be created |
| 246 | Channel Web Dynpro is currently not supported |
| 247 | Import from memory ID '&1' failed |
| 248 | Export to memory Id '&1' failed |
| 249 | Configuration '&1' for channel '&2' already locked by user '&3' |
| 250 | Configuration '&1' for channel '&2' cannot be locked |
| 251 | Field '&1' in Log Group '&2' should be assigned to a Log Domain |
| 252 | Configuration ID '&1', Channel ID '&2' could not be saved |
| 253 | Failed to create object key definition for channel &1 |
| 254 | Failed to convert data to raw |
| 255 | Failed to convert raw data |
| 256 | Read Access Logging: Exception occured |
| 257 | Validity period must be between 1 and 24 |
| 258 | Change selected field type '&1' of field '&2' to a supported value |
| 259 | Remove field '&1' from log group '&2' as it is invalid |
| 260 | Change logging type '&1' of field '&2' to a supported value |
| 261 | Exclude logging of initial value is not allowed for field '&1'. |
| 262 | Change field type of system field '&1' from '&2' to '&3' |
| 263 | Enter at least one ID for export |
| 264 | At least one recording is still enabled |
| 265 | At least one configuration is inactive or does not exist |
| 266 | At least one Log Group does not have a Purpose |
| 267 | At least one recording has no data |
| 268 | At least one Log Group is inconsistent |
| 269 | At least one Log Group Condition has no fields assigned |
| 270 | Imported file is inconsistent. Check objects in source system |
| 271 | Transport temporarily not possible. RFC configurations are locked by '&1' |
| 272 | Field '&1' can't be removed. It is configured in '&2', channel '&3' |
| 273 | Error creating data for type &1 length &2 decimals &3 |
| 274 | At least one search criteria must be specified |
| 275 | Remove field '&1' from log context '&2' as it doesn't exist in fieldlist |
| 276 | Remove expression '&1'. Contained field '&2' doesn't exist in fieldlist |
| 277 | Remove field '&1' from log group '&2' as it doesn't exist in fieldlist |
| 278 | Object &1 &2 does not exist |
| 279 | Configuration '&1' is inconsistent. Application Component '&2' is invalid |
| 280 | Field'&1' in LG'&2': 'Exclude if initial' is not allowed for passwords. |
| 281 | |
| 282 | Enable at least one relevant starting program or transaction |
| 283 | Data type information is missing |
| 284 | Invalid terminal id. Expected 32 hex digits (0-9,A-F) |
| 285 | Negative values are not permitted |
| 286 | Trace Configuration for username '&1' is locked by '&2' |
| 287 | Trace Configuration for terminal id '&1' is locked by '&2' |
| 288 | User '&1' does not exist |
| 289 | Trace Configuration already exists |
| 290 | Trace Configuration does not exist |
| 291 | Log group '&1' uses same purpose '&2' as group '&3'. This is not allowed |
| 292 | '&1' is enabled as starting application, which is not available anymore |
| 293 | Program '&1' must be enabled as it is used in Log Groups |
| 294 | Program '&1' should not be enabled as it is not used in log groups |
| 295 | Assert failed: &1 |
| 296 | Purpose &1 was imported |
| 297 | Log Domain &1 was imported |
| 298 | Recording &1 was imported |
| 299 | Configuration &1 was imported |
| 300 | Import for Channel &1. File contains data of different Channels |
| 301 | Field '&1' in Log Group '&2' cannot be logged because it is excluded |
| 302 | Field '&1' in Log Context '&2' cannot be logged because it is excluded |
| 303 | Generic Path '&1' occurs more than once in Log Group '&2' |
| 304 | Field '&1' is already covered by generic path '&2' in Log Group '&3' |
| 305 | Generic Path '&1' occurs more than once in Log Context '&2' |
| 306 | Field '&1' is already covered by generic path '&2' in Log Context '&3' |
| 307 | Remove field '&1' from cond. '&2' and expr.'&3' as it is excluded |
| 308 | Resolve inconsistency for field with generic path '&1' in expr. '&2' |
| 309 | Generic logging has been activated for dynpro applications |
| 310 | Generic logging has been deactivated for dynpro applications |
| 311 | No changes allowed. Upgrade is running |
| 312 | Error in dynamic field config: &1 &2 &3 &4 |
| 313 | Template Configuration &1 cannot be deleted |
| 314 | Template Configuration &1 cannot be activated |
| 315 | Template Configuration &1 cannot be deactivated |
| 316 | Recording '&1' for channel '&2' does not exist |
| 317 | Template Recording &1 for channel &2 cannot be deleted |
| 318 | Template Recording &1 for channel &2 cannot be cleared |
| 319 | SAP Template: Log Purpose '&1' is not allowed to be exported |
| 320 | SAP Template: Log Domain '&1' of area '&2' is not allowed to be exported |
| 321 | SAP Template: Recording '&1' is not allowed to be exported |
| 322 | Object is not in customer namespace. |
| 323 | Template Log Domain &1/&2 cannot be deleted |
| 324 | Template Log Purpose &1 cannot be deleted |
| 325 | Select only one configuration |
| 326 | Configuration does inherit from any SAP-Template |
| 330 | Object not in allowlist. Activation will not be possible! |
| 331 | Channel does not support creation of new RAL configurations |
| 332 | Log Output |
| 333 | Business Area |
| 334 | Domain |
| 335 | Log Domain |
| 336 | Log Domain '&1' in business area '&2' for scope '&3' does not exist |