SAP ABAP Message Class SRAL (Read Access Log Message Class)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SEC-RAL (Application Component) Read Access Logging
⤷
SREAD_ACCESS_LOG_CORE (Package) Read Access Logging: Core Framework
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SEC-RAL (Application Component) Read Access Logging⤷
SREAD_ACCESS_LOG_CORE (Package) Read Access Logging: Core Framework 
Attributes
| Message class |  |
SRAL |
| Short Description |  |
Read Access Log Message Class |
| Changed On |  |
20141121 |
| Last Changed At |  |
124018 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
WS Configuration for type '&1', name '&2', operation '&3' is not locked | The short text describes the object sufficiently | |
| 2 | 001 |
WS Configuration for type '&1',name '&2',operation '&3' cannot be locked | The short text describes the object sufficiently | |
| 3 | 002 |
WS Configuration for type '&1',name '&2',operation '&3' is terminated | The short text describes the object sufficiently | |
| 4 | 003 |
Field '&1,&2,&3,&4' is not contained in field list | The short text describes the object sufficiently | |
| 5 | 004 |
ABAP data type '&1' is not supported | The short text describes the object sufficiently | |
| 6 | 005 |
Data reference for ABAP data type '&1' could not be created | The short text describes the object sufficiently | |
| 7 | 006 |
Error during rules processing. See previous exception. | The short text describes the object sufficiently | |
| 8 | 007 |
Error when saving WS Configuration: Type '&1',name '&2', operation '&3' | The short text describes the object sufficiently | |
| 9 | 008 |
Log Group '&1' does not exist in configuration '&2' | The short text describes the object sufficiently | |
| 10 | 009 |
Condition '&1' does not exist in configuration '&2' | The short text describes the object sufficiently | |
| 11 | 010 |
WS Configuration for type '&1', name '&2', operation '&3' does not exist | The short text describes the object sufficiently | |
| 12 | 011 |
Select Option ID '&1' for config. '&2' in conditon '&3' does not exist | The short text describes the object sufficiently | |
| 13 | 012 |
Expression ID '&1' for config. '&2' in condition '&3' does not exist | The short text describes the object sufficiently | |
| 14 | 013 |
Condition ID '&1' for config. '&2' does not exist | The short text describes the object sufficiently | |
| 15 | 014 |
Sel.Opt. '&1' for config. '&2' in sel.option '&3' in does not exist | The short text describes the object sufficiently | |
| 16 | 015 |
Only ranges for the same field can be used in one select option | The short text describes the object sufficiently | |
| 17 | 016 |
Select Option '&1' in expression '&2' in condition '&3' does not exist | The short text describes the object sufficiently | |
| 18 | 017 |
Log Group '&1' in configuration '&2' cannot be saved | The short text describes the object sufficiently | |
| 19 | 018 |
Log Group Fields in Log Group '&1' in operation '&2' cannot be saved | The short text describes the object sufficiently | |
| 20 | 019 |
Log Field '&1' does not exist in Log Group '&2' in configuration '&3' | The short text describes the object sufficiently | |
| 21 | 020 |
Log Field '&1' already exists in Log Group '&2' in configuration '&3' | The short text describes the object sufficiently | |
| 22 | 021 |
Condition '&1' does not exist in Log Group '&2' in configuration '&3' | The short text describes the object sufficiently | |
| 23 | 022 |
Condition '&1' already assigned to Log Group '&2' in configuration '&3' | The short text describes the object sufficiently | |
| 24 | 023 |
Failed to convert data to raw (&1&2&3&4) | The short text describes the object sufficiently | |
| 25 | 024 |
Data type '&1' is not supported | The short text describes the object sufficiently | |
| 26 | 025 |
Failed to convert raw to data (&1&2&3&4) | The short text describes the object sufficiently | |
| 27 | 026 |
Search '&1' saved | The short text describes the object sufficiently | |
| 28 | 027 |
Search '&1' could not be saved | The short text describes the object sufficiently | |
| 29 | 028 |
Saved Search '&1' deleted | The short text describes the object sufficiently | |
| 30 | 029 |
Saved Search '&1' could not be deleted | The short text describes the object sufficiently | |
| 31 | 030 |
Low Value '&1' has to be less than High Value '&2' | The short text describes the object sufficiently | |
| 32 | 031 |
Unsupported channel type '&1' | The short text describes the object sufficiently | |
| 33 | 032 |
Failed to set log environment for channel type '&1' | The short text describes the object sufficiently | |
| 34 | 033 |
Failed to get SHM write access object for current work process: ID='&1' | The short text describes the object sufficiently | |
| 35 | 034 |
Failed to perform operation '&1' on SHM access | The short text describes the object sufficiently | |
| 36 | 035 |
Failed to convert data to string | The short text describes the object sufficiently | |
| 37 | 037 |
WS Config. for type '&1', name '&2', operation '&3' is locked by '&4' | The short text describes the object sufficiently | |
| 38 | 038 |
Failed to access table '&1': operation '&2', connection '&3' | The short text describes the object sufficiently | |
| 39 | 040 |
Failed to build field list for object type '&1' object '&2' | The short text describes the object sufficiently | |
| 40 | 041 |
Field '&3' in msg type '&2', dir. '&1' is not part of the WS operation | The short text describes the object sufficiently | |
| 41 | 042 |
Fieldlist is empty | The short text describes the object sufficiently | |
| 42 | 043 |
Activation of WS Config. for type '&1', name '&2', operation '&3' failed | The short text describes the object sufficiently | |
| 43 | 044 |
Deactivation of WS Config. for type '&1',name '&2',operation '&3' failed | The short text describes the object sufficiently | |
| 44 | 045 |
Log Group '&1' already exists in configuration '&2' | The short text describes the object sufficiently | |
| 45 | 046 |
Condition '&1' already exists in configuration '&2' | The short text describes the object sufficiently | |
| 46 | 047 |
Enter another expression name. '&1' already exists in condition '&2'. | The short text describes the object sufficiently | |
| 47 | 048 |
Option '&1' in select option is not supported | The short text describes the object sufficiently | |
| 48 | 049 |
Log Group '&1' cannot be removed. Unassign all conditions first | Space: object requires documentation | |
| 49 | 050 |
Data type '&1' requested, but actually found type '&2' | The short text describes the object sufficiently | |
| 50 | 051 |
Field ID '&1' in configuration '&2' for channel '&3' does not exist | The short text describes the object sufficiently | |
| 51 | 052 |
Field ID '&1' for channel '&2' cannot be saved | The short text describes the object sufficiently | |
| 52 | 053 |
Configuration with ID '&1' for channel '&2' does not exist | The short text describes the object sufficiently | |
| 53 | 054 |
Configuration instance already terminated | The short text describes the object sufficiently | |
| 54 | 055 |
Error when activating WS config: Type '&1',name '&2', operation '&3' | The short text describes the object sufficiently | |
| 55 | 056 |
Configuration instance already locked by another user | The short text describes the object sufficiently | |
| 56 | 057 |
Log fields of log group '&1' in configuration '&2' cannot be saved | The short text describes the object sufficiently | |
| 57 | 058 |
Group '&1' must not consist of response and fault fields simultaneously | The short text describes the object sufficiently | |
| 58 | 059 |
Condition &1 must not consist of response and fault fields simultaneously | The short text describes the object sufficiently | |
| 59 | 060 |
Configuration with ID '&1' must be locked | The short text describes the object sufficiently | |
| 60 | 061 |
Assign. of Group &1 to Cond. &2 must not contain resp. and fault fields | The short text describes the object sufficiently | |
| 61 | 062 |
Building element structure list failed for configuration with ID '&1' | The short text describes the object sufficiently | |
| 62 | 063 |
No configuration exists for Web Dynpro Recording '&1' | The short text describes the object sufficiently | |
| 63 | 064 |
Log Domain '&1' in business area '&2' does not exist | The short text describes the object sufficiently | |
| 64 | 065 |
Building element structure with fieldID '&1' failed | The short text describes the object sufficiently | |
| 65 | 066 |
Log Domain '&1' in business area '&2' is locked by '&3' | The short text describes the object sufficiently | |
| 66 | 067 |
You are not authorized to perform this operation | The short text describes the object sufficiently | |
| 67 | 068 |
Could not read new value for period | The short text describes the object sufficiently | |
| 68 | 069 |
User exclusion list could not be created | The short text describes the object sufficiently | |
| 69 | 070 |
User exclusion list could not be deleted | The short text describes the object sufficiently | |
| 70 | 071 |
User could not be added to user exclusion list | The short text describes the object sufficiently | |
| 71 | 072 |
User could not be deleted from user exclusion list | The short text describes the object sufficiently | |
| 72 | 073 |
User exclusion list entries could not be read | The short text describes the object sufficiently | |
| 73 | 074 |
User exclusion list '&1' does not exist | The short text describes the object sufficiently | |
| 74 | 075 |
User '&1' exists already in blacklist '&2' | The short text describes the object sufficiently | |
| 75 | 076 |
Invalid user exclusion list name | The short text describes the object sufficiently | |
| 76 | 077 |
Log Domain business area '&1' must not contain the symbol '/' | The short text describes the object sufficiently | |
| 77 | 078 |
Log Domain Name '&1' must not contain the symbol '/' | The short text describes the object sufficiently | |
| 78 | 079 |
Specify all required fields | The short text describes the object sufficiently | |
| 79 | 080 |
Username '&1' is not valid | The short text describes the object sufficiently | |
| 80 | 081 |
Log Group '&1' is not consistent. Select Logging Type for all fields | The short text describes the object sufficiently | |
| 81 | 082 |
Configuration '&1' is not consistent. Create at least one Log Group | The short text describes the object sufficiently | |
| 82 | 083 |
Only characters '&1' are permitted in text '&2' | The short text describes the object sufficiently | |
| 83 | 084 |
Failed to save assignments of Log Group '&1' in Configuration '&2' | The short text describes the object sufficiently | |
| 84 | 085 |
Web Service Consumer configuration '&1' cannot contain response fields | The short text describes the object sufficiently | |
| 85 | 086 |
Condition '&1' is still assigned in Log Group '&2' | The short text describes the object sufficiently | |
| 86 | 087 |
User exclusion list '&1' is locked by '&2' | The short text describes the object sufficiently | |
| 87 | 088 |
User exclusion list is not locked | The short text describes the object sufficiently | |
| 88 | 089 |
Configuration was saved | The short text describes the object sufficiently | |
| 89 | 090 |
Configuration values could not be saved: &1 | The short text describes the object sufficiently | |
| 90 | 091 |
Error while writing RAL data | The short text describes the object sufficiently | |
| 91 | 092 |
New value has not been applied | The short text describes the object sufficiently | |
| 92 | 093 |
Web Dynpro Configuration for Recording '&1' does not exist | The short text describes the object sufficiently | |
| 93 | 094 |
Web Dynpro Configuration for Recording '&1' is locked by '&2' | The short text describes the object sufficiently | |
| 94 | 095 |
Web Dynpro Configuration for Recording '&1' cannot be locked | The short text describes the object sufficiently | |
| 95 | 096 |
Assign a condition to Log Group '&1' or set 'Without Condition' | The short text describes the object sufficiently | |
| 96 | 097 |
Assign field(s) to Log Group '&1' | The short text describes the object sufficiently | |
| 97 | 098 |
User exclusion list '&1' already exists | The short text describes the object sufficiently | |
| 98 | 099 |
Configuration ID '&1', Channel ID '&2' has been activated | The short text describes the object sufficiently | |
| 99 | 100 |
Configuration ID '&1', Channel ID '&2' has been deactivated | The short text describes the object sufficiently | |
| 100 | 101 |
Cannot save WD config. for recording '&1', appl. '&2', appl. config. '&3' | The short text describes the object sufficiently | |
| 101 | 102 |
Activation of configuration ID '&1' for channel ID '&2' failed | The short text describes the object sufficiently | |
| 102 | 103 |
Logging Purpose with ID '&1' already exists. Choose a different ID | The short text describes the object sufficiently | |
| 103 | 104 |
Web Service operation '&1' cannot be configured as it is asynchronous | The short text describes the object sufficiently | |
| 104 | 105 |
Log Group '&1' must not consist of system fields only. Add channel fields | The short text describes the object sufficiently | |
| 105 | 106 |
Inactive Configuration already exists for Object '&1' | The short text describes the object sufficiently | |
| 106 | 107 |
Active Configuration already exists for Object '&1' | The short text describes the object sufficiently | |
| 107 | 108 |
Error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 108 | 109 |
Configuration ID '&1', Channel ID '&2' has been saved | The short text describes the object sufficiently | |
| 109 | 110 |
Configuration ID '&1', Channel ID '&2' has been deleted | The short text describes the object sufficiently | |
| 110 | 111 |
User exclusion list has been saved | The short text describes the object sufficiently | |
| 111 | 112 |
User '&1' has been added to user exclusion list | The short text describes the object sufficiently | |
| 112 | 113 |
User '&1' has been removed from user exclusion list | The short text describes the object sufficiently | |
| 113 | 114 |
RAL has been activated in client '&1' | The short text describes the object sufficiently | |
| 114 | 115 |
RAL has been deactivated in client '&1' | The short text describes the object sufficiently | |
| 115 | 116 |
RAL error log level has been changed to &1 | The short text describes the object sufficiently | |
| 116 | 117 |
RAL performance trace level has been changed to &1 | The short text describes the object sufficiently | |
| 117 | 118 |
RAL log retention period has been changed to &1 | The short text describes the object sufficiently | |
| 118 | 119 |
Create at least one Expression for Condition &1 | The short text describes the object sufficiently | |
| 119 | 120 |
Add at least one field to the Expression &1 | The short text describes the object sufficiently | |
| 120 | 121 |
New Configuration value has been saved: &1 | The short text describes the object sufficiently | |
| 121 | 122 |
New Logging Purpose '&1' has been created | The short text describes the object sufficiently | |
| 122 | 123 |
Logging Purpose '&1' has been deleted | The short text describes the object sufficiently | |
| 123 | 124 |
New Log Domain '&1' has been created | The short text describes the object sufficiently | |
| 124 | 125 |
Log Domain '&1' has been deleted | The short text describes the object sufficiently | |
| 125 | 126 |
Log Domain '&1' has been saved | The short text describes the object sufficiently | |
| 126 | 127 |
For RFC '&1' field path '&2' cannot be found in runtime parameter list | The short text describes the object sufficiently | |
| 127 | 128 |
For RFC '&1' parameter with name '&2' has no runtime value provided | The short text describes the object sufficiently | |
| 128 | 129 |
For RFC '&1' path '&2' does not correspond to parameter structure | The short text describes the object sufficiently | |
| 129 | 130 |
bgRFC Unit ID &1 not found in RAL cache | The short text describes the object sufficiently | |
| 130 | 131 |
RFC config. for location '&1', func. module '&2' is locked by '&3' | The short text describes the object sufficiently | |
| 131 | 132 |
RFC config. for location '&1', func. module '&2' cannot be locked | The short text describes the object sufficiently | |
| 132 | 133 |
Could not write to bgRFC RAL cache | The short text describes the object sufficiently | |
| 133 | 134 |
RFC channel log data transformation error | The short text describes the object sufficiently | |
| 134 | 135 |
Invalid RFC location '&1' | Space: object requires documentation | |
| 135 | 136 |
Error when activating RFC config: location '&1',name '&2' | The short text describes the object sufficiently | |
| 136 | 137 |
Error when saving RFC Configuration: Function Module Name '&1' | The short text describes the object sufficiently | |
| 137 | 138 |
RFC Config. for function module name '&1' is locked by '&2' | The short text describes the object sufficiently | |
| 138 | 139 |
RFC Config. for function module name '&1' cannot be locked | The short text describes the object sufficiently | |
| 139 | 140 |
Enter a Function Module name | The short text describes the object sufficiently | |
| 140 | 141 |
Check Function Module name '&1' | The short text describes the object sufficiently | |
| 141 | 142 |
System Error during function call | The short text describes the object sufficiently | |
| 142 | 143 |
Enter a distinct Function Module name | The short text describes the object sufficiently | |
| 143 | 144 |
Purpose '&1' is locked by '&2' | The short text describes the object sufficiently | |
| 144 | 145 |
New Purpose &1 has been created | The short text describes the object sufficiently | |
| 145 | 146 |
Purpose '&1' has been deleted | The short text describes the object sufficiently | |
| 146 | 147 |
Purpose &1 does not exist | The short text describes the object sufficiently | |
| 147 | 148 |
Error getting RFC metadata | The short text describes the object sufficiently | |
| 148 | 149 |
Invalid RFC name '&1' | The short text describes the object sufficiently | |
| 149 | 150 |
Invalid monitor type '&1' | The short text describes the object sufficiently | |
| 150 | 151 |
ABAP data type '&1' in field '&2' is not supported in conditions | The short text describes the object sufficiently | |
| 151 | 152 |
check if RFC is set for Function Module '&1' | The short text describes the object sufficiently | |
| 152 | 153 |
Field '&1' is not contained in field list. | The short text describes the object sufficiently | |
| 153 | 154 |
'Exporting' Fields are not allowed for Client RFC Configurations | The short text describes the object sufficiently | |
| 154 | 155 |
Select at least one user | The short text describes the object sufficiently | |
| 155 | 156 |
Read access logging not connected to an archive | The short text describes the object sufficiently | |
| 156 | 157 |
Purpose '&1' has been changed | The short text describes the object sufficiently | |
| 157 | 158 |
Error opening archive files. Error code = '&1' | The short text describes the object sufficiently | |
| 158 | 159 |
Select an archive file | The short text describes the object sufficiently | |
| 159 | 160 |
Error reading archive file. Error code = '&1' | The short text describes the object sufficiently | |
| 160 | 161 |
Search criteria '&1' no supported for selected persistency source. | The short text describes the object sufficiently | |
| 161 | 162 |
Error reading archive index. | The short text describes the object sufficiently | |
| 162 | 163 |
No archive infostructure found | The short text describes the object sufficiently | |
| 163 | 164 |
Search name not availble in archive index | The short text describes the object sufficiently | |
| 164 | 165 |
Enabling in Client is locked by '&1' | The short text describes the object sufficiently | |
| 165 | 166 |
Enabling in Client cannot be locked | The short text describes the object sufficiently | |
| 166 | 167 |
Configuration for Function Module '&1' and Location '&2' already exists | The short text describes the object sufficiently | |
| 167 | 168 |
Enabling in Client must be locked | The short text describes the object sufficiently | |
| 168 | 169 |
Index based search not possible. No index found. | The short text describes the object sufficiently | |
| 169 | 170 |
Field '&1' in configuration '&2' does not exist | The short text describes the object sufficiently | |
| 170 | 171 |
Error getting datatype information for &1 | The short text describes the object sufficiently | |
| 171 | 172 |
No ABAP Type for datatype &1 found | The short text describes the object sufficiently | |
| 172 | 173 |
Log Context '&1' does not exist in configuration '&2' | The short text describes the object sufficiently | |
| 173 | 174 |
Log Context '&1' in configuration '&2' cannot be saved | The short text describes the object sufficiently | |
| 174 | 175 |
Fields of Log Context '&1' in configuration '&2' cannot be saved | The short text describes the object sufficiently | |
| 175 | 176 |
Field '&1' does not exist in Log Context '&2' in configuration '&3' | The short text describes the object sufficiently | |
| 176 | 177 |
Field '&1' already exists in Log Context '&2' in configuration '&3' | The short text describes the object sufficiently | |
| 177 | 178 |
Log Context '&1' already exists in configuration '&2' | The short text describes the object sufficiently | |
| 178 | 179 |
Only one log context element in configuration '&1' is allowed | The short text describes the object sufficiently | |
| 179 | 180 |
Only one field in log context '&1' in configuration '&2' is allowed | The short text describes the object sufficiently | |
| 180 | 181 |
Log Domain '&1'does not fulfill required pattern: softwarecomponent/name | The short text describes the object sufficiently | |
| 181 | 182 |
Field '&1' is not supported and cannot be assigned to '&2' | The short text describes the object sufficiently | |
| 182 | 183 |
Log Domain '&1' cannot be deleted, it is still used in Log Group(s) | The short text describes the object sufficiently | |
| 183 | 184 |
Logging Purpose '&1' cannot be deleted, it is still used in Log Group(s) | The short text describes the object sufficiently | |
| 184 | 185 |
Enter a name | The short text describes the object sufficiently | |
| 185 | 186 |
Select a Saved Search | The short text describes the object sufficiently | |
| 186 | 187 |
Log Domain already exists | The short text describes the object sufficiently | |
| 187 | 188 |
Enter a name | The short text describes the object sufficiently | |
| 188 | 189 |
Cannot save Dynpro config. for recording '&1', main program '&2' | The short text describes the object sufficiently | |
| 189 | 190 |
Dynpro Configuration for Recording '&1' does not exist | The short text describes the object sufficiently | |
| 190 | 191 |
Dynpro Configuration for Recording '&1' is locked by '&2' | The short text describes the object sufficiently | |
| 191 | 192 |
Dynpro Configuration for Recording '&1' cannot be locked | The short text describes the object sufficiently | |
| 192 | 193 |
Configuration '&1' is not consistent. Create one or no log context | The short text describes the object sufficiently | |
| 193 | 194 |
Configuration '&1' is not consistent.Log context must be logged with val. | The short text describes the object sufficiently | |
| 194 | 195 |
Dynpro path invalid at pos &1. Reason: &2 | The short text describes the object sufficiently | |
| 195 | 196 |
Disable recording '&1' for channel '&2' first | The short text describes the object sufficiently | |
| 196 | 197 |
Recording '&1' for channel '&2' already exists. Choose a different name | The short text describes the object sufficiently | |
| 197 | 198 |
System Field '&1' cannot be defined as Log Context | The short text describes the object sufficiently | |
| 198 | 199 |
Path '&1' has invalid format | The short text describes the object sufficiently | |
| 199 | 200 |
Path '&1' does not end with current program name '&2' | The short text describes the object sufficiently | |
| 200 | 201 |
Path '&1' does not end with current dynpro '&2' | The short text describes the object sufficiently | |
| 201 | 202 |
Path '&1' does not contain the program | The short text describes the object sufficiently | |
| 202 | 203 |
Path '&1' does not contain the dynpro | The short text describes the object sufficiently | |
| 203 | 204 |
Path '&1' does not contain the container | The short text describes the object sufficiently | |
| 204 | 205 |
Select a valid field direction Type for field '&1' | The short text describes the object sufficiently | |
| 205 | 206 |
Field direction not supported for channel '&1' | The short text describes the object sufficiently | |
| 206 | 207 |
Assign Field to Log Context '&1' | The short text describes the object sufficiently | |
| 207 | 208 |
No configurable Fields available in '&/1', only Response and/or Faults | The short text describes the object sufficiently | |
| 208 | 209 |
Objects are inserted into transport request &1 (description: &2) | The short text describes the object sufficiently | |
| 209 | 210 |
&1 object entries for transport could not be created | The short text describes the object sufficiently | |
| 210 | 211 |
Transport mode '&1' is invalid | The short text describes the object sufficiently | |
| 211 | 212 |
New transport &1 (description: &2) created | The short text describes the object sufficiently | |
| 212 | 213 |
Objects cannot be inserted into transport request '&1' | The short text describes the object sufficiently | |
| 213 | 214 |
Transport request '&1' is invalid. Objects cannot be inserted | The short text describes the object sufficiently | |
| 214 | 215 |
No changes are allowed in this system client | The short text describes the object sufficiently | |
| 215 | 216 |
Field'&1' in LG'&2' is a password field. Only 'Without Value' is allowed | The short text describes the object sufficiently | |
| 216 | 217 |
Password field '&1' is not supported in conditions | The short text describes the object sufficiently | |
| 217 | 218 |
Password field '&1' is not supported in log context | The short text describes the object sufficiently | |
| 218 | 219 |
Purpose '&1' has been saved | The short text describes the object sufficiently | |
| 219 | 220 |
Recording '&1' for channel '&2' has been saved | The short text describes the object sufficiently | |
| 220 | 221 |
Recording '&1' for channel '&2' has been deleted | The short text describes the object sufficiently | |
| 221 | 222 |
Recording '&1' for channel '&2' has been enabled | The short text describes the object sufficiently | |
| 222 | 223 |
Recording '&1' for channel '&2' has been disabled | The short text describes the object sufficiently | |
| 223 | 224 |
Select at least one log domain | The short text describes the object sufficiently | |
| 224 | 225 |
Select at least one configuration | The short text describes the object sufficiently | |
| 225 | 226 |
Select at least one logging purpose | The short text describes the object sufficiently | |
| 226 | 227 |
Select at least one recording | The short text describes the object sufficiently | |
| 227 | 228 |
Changed objects are inserted into task &1 of request &2(description:&3) | The short text describes the object sufficiently | |
| 228 | 229 |
Field '&1' has been added to recording '&2' | The short text describes the object sufficiently | |
| 229 | 230 |
Field '&1' has been removed from recording '&2' | The short text describes the object sufficiently | |
| 230 | 231 |
Changes are automat. recorded. Only activate consistent configuration(s). | The short text describes the object sufficiently | |
| 231 | 232 |
Set at least one active Condition assigned to Log Group '&1' | The short text describes the object sufficiently | |
| 232 | 233 |
Path must not be initial | The short text describes the object sufficiently | |
| 233 | 234 |
Dynpro Path '&1' must not end with a contain | The short text describes the object sufficiently | |
| 234 | 235 |
Invalid dynpro length '&1' in path '&2' | The short text describes the object sufficiently | |
| 235 | 236 |
Column '&1' has been added to recording '&2' | The short text describes the object sufficiently | |
| 236 | 237 |
Column '&1' has been removed from recording '&2' | The short text describes the object sufficiently | |
| 237 | 238 |
Field '&1' is not contained in recording '&2' | The short text describes the object sufficiently | |
| 238 | 239 |
Column '&1' is not contained in recording '&2' | The short text describes the object sufficiently | |
| 239 | 240 |
Recording '&1' already contains column '&2'. Column information updated. | The short text describes the object sufficiently | |
| 240 | 241 |
Recording '&1' already contains field '&2'. Field information updated. | The short text describes the object sufficiently | |
| 241 | 242 |
Configuration entries for transport could not be created | The short text describes the object sufficiently | |
| 242 | 243 |
User exclusion list entries for transport could not be created | The short text describes the object sufficiently | |
| 243 | 244 |
"Enabling in client" entry for transport could not be created | The short text describes the object sufficiently | |
| 244 | 245 |
Recording entry for transport could not be created | The short text describes the object sufficiently | |
| 245 | 246 |
Channel Web Dynpro is currently not supported | The short text describes the object sufficiently | |
| 246 | 247 |
Import from memory ID '&1' failed | The short text describes the object sufficiently | |
| 247 | 248 |
Export to memory Id '&1' failed | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141121 | SAP |
| SAP Release Created in |
