SAP ABAP Message Class RSDA (BW Archiving: Messages)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSDA (Package) BW Data Archiving and Near-line Storage. Core Functions
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSDA (Package) BW Data Archiving and Near-line Storage. Core Functions
Attributes
Message class | RSDA | |
Short Description | BW Archiving: Messages | |
Changed On | 20140121 | |
Last Changed At | 101748 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | General error in BW archiving (-> see long text) | Space: object requires documentation | |
2 | 002 | General error in Nearline Service (-> long text) | Space: object requires documentation | |
3 | 003 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
4 | 004 | &1 = &2 | The short text describes the object sufficiently | |
5 | 005 | &1[&2]-&3 = &4 | The short text describes the object sufficiently | |
6 | 006 | in program, include, rows = &1, &2, &3 | The short text describes the object sufficiently | |
7 | 007 | Write program for data archiving process &1 was terminated | The short text describes the object sufficiently | |
8 | 008 | Delete program for data archiving process &1 was terminated | The short text describes the object sufficiently | |
9 | 009 | Reload program for data archiving process &1 was terminated | The short text describes the object sufficiently | |
10 | 010 | Processing of data archiving process &1 canceled | The short text describes the object sufficiently | |
11 | 011 | Deletion program for near-line requests terminated | The short text describes the object sufficiently | |
12 | 012 | Near-line service does not currently support this functionality | The short text describes the object sufficiently | |
13 | 013 | Could not copy &1 archiving requests to NLS | Space: object requires documentation | |
14 | 014 | NLS copy program for archiving requests was terminated | The short text describes the object sufficiently | |
15 | 015 | Data archiving process &1 can be deleted | The short text describes the object sufficiently | |
16 | 016 | Data archiving process &1 deleted | The short text describes the object sufficiently | |
17 | 017 | Could not delete data archiving process &1 | The short text describes the object sufficiently | |
18 | 018 | No active data archiving processes to be deleted | The short text describes the object sufficiently | |
19 | 019 | Error while accessing relocated data (Archive or Near-line Storage) | Space: object requires documentation | |
20 | 020 | Near-line connection &1 does not exist | The short text describes the object sufficiently | |
21 | 021 | Near-line connection &1 to original BW system disconnected | The short text describes the object sufficiently | |
22 | 030 | HANA revision does not support archiving of Inventory InfoProviders | Space: object requires documentation | |
23 | 031 | Archiving not supported for non HANA-optimized Inventory InfoProviders | Space: object requires documentation | |
24 | 032 | New ref-point handling is not active for Inventory InfoProvider &1 | Space: object requires documentation | |
25 | 100 | *--------------------------- Modeling -----------------------------* | The short text describes the object sufficiently | |
26 | 101 | The data archiving process &1 is not available | The short text describes the object sufficiently | |
27 | 102 | Data archiving process &1 is not available in version &2 | The short text describes the object sufficiently | |
28 | 103 | No DDIC objects can be generated from version &1 | The short text describes the object sufficiently | |
29 | 104 | Version &1 cannot be activated | The short text describes the object sufficiently | |
30 | 105 | Check of the data archiving process &1 returns no errors | The short text describes the object sufficiently | |
31 | 106 | InfoObject &1 is not an absolute time characteristic in InfoProvider &2 | The short text describes the object sufficiently | |
32 | 107 | Error when writing the DAP &1 to the database (table &2) | The short text describes the object sufficiently | |
33 | 108 | A data archiving process cannot be created for TLOGO object type &1 | The short text describes the object sufficiently | |
34 | 109 | Cannot create data archiving process for &2 | Space: object requires documentation | |
35 | 110 | There is already an archiving object from BW 3.X for InfoProvider &2 | The short text describes the object sufficiently | |
36 | 111 | Object &2 of object type &1 is not supported | The short text describes the object sufficiently | |
37 | 112 | InfoObject &1 is not a permitted characteristic in InfoProvider &2 | The short text describes the object sufficiently | |
38 | 113 | InfoObject &1 is not permitted as a partitioning characteristic | The short text describes the object sufficiently | |
39 | 114 | Request-based archiving requires &2 as a partitioning characteristic | The short text describes the object sufficiently | |
40 | 115 | The data archiving process for InfoProvider &1 was not locked | The short text describes the object sufficiently | |
41 | 116 | No partitioning is possible for archiving with free selections | The short text describes the object sufficiently | |
42 | 117 | Table / view &1 (type &2) of data archiving process &3 saved | The short text describes the object sufficiently | |
43 | 118 | Time slice archiving requires a time characteristic to be specified | The short text describes the object sufficiently | |
44 | 119 | Object version '&1' cannot be saved, only version 'N' | The short text describes the object sufficiently | |
45 | 120 | Data archiving process '&1' cannot be executed | Space: object requires documentation | |
46 | 121 | Near-lin object &1 will be deleted | The short text describes the object sufficiently | |
47 | 122 | No partitioning characteristic specified | The short text describes the object sufficiently | |
48 | 123 | Partitioning characteristic &1 is not key char. of InfoProvider &2 | The short text describes the object sufficiently | |
49 | 124 | Data archiving process &1 locked by user &2 | The short text describes the object sufficiently | |
50 | 125 | All runtime objects of data archiving procses &1 deleted | The short text describes the object sufficiently | |
51 | 126 | Runtime objects restored from active version | The short text describes the object sufficiently | |
52 | 127 | Data archiving process &1 is consistent | The short text describes the object sufficiently | |
53 | 128 | Data archiving process &1 check returned errors | The short text describes the object sufficiently | |
54 | 129 | User &1 has authorization to archive InfoProvider &2 | The short text describes the object sufficiently | |
55 | 130 | User &1 does not have authorization to archive InfoProvider &2 | The short text describes the object sufficiently | |
56 | 131 | User &1 does not have authorization to reload InfoProvider &2 | The short text describes the object sufficiently | |
57 | 132 | Error in authorization check for request &1 (see other messages) | The short text describes the object sufficiently | |
58 | 133 | Error in authorization check for InfoProvider &1 | The short text describes the object sufficiently | |
59 | 134 | New archiving request created for data archiving process &1 | The short text describes the object sufficiently | |
60 | 135 | Processing is in production mode | The short text describes the object sufficiently | |
61 | 136 | Processing is in test mode | The short text describes the object sufficiently | |
62 | 137 | Lock for creating an archiving request successfully set | The short text describes the object sufficiently | |
63 | 138 | Lock for creating archiving request currently not possible | The short text describes the object sufficiently | |
64 | 139 | User &1 is authorized to reload into InfoProvider &2 | The short text describes the object sufficiently | |
65 | 140 | Exception &1 occurred in line &2 of include &3 (program &4) | The short text describes the object sufficiently | |
66 | 141 | All | The short text describes the object sufficiently | |
67 | 142 | Nothing | The short text describes the object sufficiently | |
68 | 143 | &1 | The short text describes the object sufficiently | |
69 | 144 | &1 | The short text describes the object sufficiently | |
70 | 145 | &1 &2 '&3' | The short text describes the object sufficiently | |
71 | 146 | &1 &2 '&3' '&4' | The short text describes the object sufficiently | |
72 | 147 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
73 | 148 | The data area to be archived is not yet fully compressed | Space: object requires documentation | |
74 | 149 | Not all requests have been rolled up to subsequent data marts | Space: object requires documentation | |
75 | 150 | Not all requests have been rolled up to subsequent aggregates | Space: object requires documentation | |
76 | 151 | Error in program generation (program class &1, ID &2) | The short text describes the object sufficiently | |
77 | 152 | Archived data were deleted from data archiving process '&1' | Space: object requires documentation | |
78 | 153 | Partitioning characteristic '&1' is not part of semantic key | The short text describes the object sufficiently | |
79 | 154 | '&1' was assigned as semantic partitioning characteristic | The short text describes the object sufficiently | |
80 | 155 | InfoProvider '&1' does not contain a suitable time slice characteristic | Space: object requires documentation | |
81 | 156 | InfoObject '&1' may not be removed from InfoProvider '&2' | Space: object requires documentation | |
82 | 157 | Not all requests have been rolled up to subsequent data marts | Space: object requires documentation | |
83 | 158 | InfoProvider &1 cannot be archived | Space: object requires documentation | |
84 | 161 | Processing successfully completed after reaching target status '&1' | The short text describes the object sufficiently | |
85 | 165 | User &1 is not authorized to delete archive data | Space: object requires documentation | |
86 | 166 | User &1 is authorized to delete archive data from InfoProvider &2 | The short text describes the object sufficiently | |
87 | 171 | Error deleting request &1 from InfoCube &2 | The short text describes the object sufficiently | |
88 | 179 | Invalid change of type for time slice characteristic '&1' of DAP '&2' | Space: object requires documentation | |
89 | 180 | Invalid structure change | The short text describes the object sufficiently | |
90 | 181 | Field '&1': Data type changed from '&2' to '&3' | The short text describes the object sufficiently | |
91 | 182 | Field '&1': Length shortened from &2 to &3 for data type '&4' | The short text describes the object sufficiently | |
92 | 183 | Field '&1': Length shortened from &2 to &3 for type change to '&4' | The short text describes the object sufficiently | |
93 | 184 | Field '&1': Length changed from &2 to &3 for data type '&4' | The short text describes the object sufficiently | |
94 | 185 | Field '&1': Length changed from &2 to &3 for type change to '&4' | The short text describes the object sufficiently | |
95 | 186 | Field '&1': Value range reduced from &2 to &3 whole number places | The short text describes the object sufficiently | |
96 | 187 | Field '&1': Accuracy reduced from &2 to &3 decimal places | The short text describes the object sufficiently | |
97 | 188 | Field '&1': Data type '&2' not supported | The short text describes the object sufficiently | |
98 | 189 | Invalid type def. for field '&1': type '&2', length &3, decimal places &4 | The short text describes the object sufficiently | |
99 | 190 | Data archiving process '&1' still contains data and is deactivated | The short text describes the object sufficiently | |
100 | 191 | Could not deactivate data archiving process '&1' | The short text describes the object sufficiently | |
101 | 192 | Data archiving process '&1' is deactivated | The short text describes the object sufficiently | |
102 | 193 | Specify a data archiving process | The short text describes the object sufficiently | |
103 | 194 | Data archiving process &1 does not contain a near-line connection | Space: object requires documentation | |
104 | 195 | Selection was not restricted | Space: object requires documentation | |
105 | 196 | Selection saved | The short text describes the object sufficiently | |
106 | 197 | Unable to save selection | The short text describes the object sufficiently | |
107 | 200 | *----------------------------- Runtime -------------------------------* | The short text describes the object sufficiently | |
108 | 201 | InfoProvider '&1' is of type '&2' and is not a nearline provider | The short text describes the object sufficiently | |
109 | 202 | &1 of &2 data records are in a locked area | Space: object requires documentation | |
110 | 203 | Data record is in area of archiving request &1(&2) | Space: object requires documentation | |
111 | 204 | Requested action &1 was refused in its entirety | Space: object requires documentation | |
112 | 205 | Request &1 could not be locked | The short text describes the object sufficiently | |
113 | 206 | The archiving run &1 is not assigned to an archiving request | The short text describes the object sufficiently | |
114 | 207 | Cannot yet delete data for archiving request &1 | The short text describes the object sufficiently | |
115 | 208 | Archiving request &1 still has open reload request &2 | Space: object requires documentation | |
116 | 209 | Archiving request &1 cannot be reloaded in status &2 | The short text describes the object sufficiently | |
117 | 210 | Data archiving process &1 is not active and cannot be executed | The short text describes the object sufficiently | |
118 | 211 | The user terminated editing of the process variant | The short text describes the object sufficiently | |
119 | 212 | This function has not yet been implemented | The short text describes the object sufficiently | |
120 | 213 | The status transfer from '&1' to '&2' is not permitted | The short text describes the object sufficiently | |
121 | 214 | Requests for data archiving process &1 locked by user &2 | The short text describes the object sufficiently | |
122 | 215 | Request &3 for data archiving process &1 locked by user &2 | The short text describes the object sufficiently | |
123 | 216 | Data packages for request &1 locked by user &2 | The short text describes the object sufficiently | |
124 | 217 | Data package &3 for request &1 locked by user &2 | The short text describes the object sufficiently | |
125 | 218 | Requests for near-line object &1 locked by user &2 | The short text describes the object sufficiently | |
126 | 219 | Request &3 for near-line object &1 locked by user &2 | The short text describes the object sufficiently | |
127 | 220 | Request &1 does not exist | The short text describes the object sufficiently | |
128 | 221 | Request &1 has invalid type '&2' | The short text describes the object sufficiently | |
129 | 222 | Lock set for request &2 in mode &1 | The short text describes the object sufficiently | |
130 | 223 | Lock deleted for request &2 in mode &1 | The short text describes the object sufficiently | |
131 | 224 | Request &1 created successfully | The short text describes the object sufficiently | |
132 | 225 | Selection conditions of request &1 are: | The short text describes the object sufficiently | |
133 | 226 | Selected area already completely archived | The short text describes the object sufficiently | |
134 | 227 | Deletion conditions for selected deletion are: | The short text describes the object sufficiently | |
135 | 228 | Simulation of selective deletion returns different number of data records | Space: object requires documentation | |
136 | 229 | Error deleting data from InfoProvider '&1' in deletion mode '&2' | The short text describes the object sufficiently | |
137 | 230 | Overlapping check with archived data areas for InfoProvider &1 | The short text describes the object sufficiently | |
138 | 231 | Check not necessary as no data has been archived for &1 | The short text describes the object sufficiently | |
139 | 232 | No check for data archiving process with free selections | The short text describes the object sufficiently | |
140 | 233 | TLOGO type '&1' is not permitted for checking method '&2' | The short text describes the object sufficiently | |
141 | 234 | Can only check activation queue (activation) or change log (rollback) | The short text describes the object sufficiently | |
142 | 235 | Archived data area: | The short text describes the object sufficiently | |
143 | 236 | &1 &2 | The short text describes the object sufficiently | |
144 | 237 | No overlap with archived data areas found | The short text describes the object sufficiently | |
145 | 238 | &1 data records locked by archiving request &2 | The short text describes the object sufficiently | |
146 | 239 | Data record &1 locked by archiving request &2 | The short text describes the object sufficiently | |
147 | 240 | Lock released for request &1 for reloading from archive | The short text describes the object sufficiently | |
148 | 241 | Data already completely copied; current request status is '&1' | The short text describes the object sufficiently | |
149 | 242 | Archivation run &1 for archivation request &2 was set to invalid | The short text describes the object sufficiently | |
150 | 243 | Existence check for archived data in InfoProvider &1 failed | The short text describes the object sufficiently | |
151 | 244 | No requests of type '&2' that can be continued found for DAP '&1' | The short text describes the object sufficiently | |
152 | 245 | No restrictions were defined | Space: object requires documentation | |
153 | 246 | Archiving/reload request &1 not yet completed | The short text describes the object sufficiently | |
154 | 247 | Data area to be archived is empty | The short text describes the object sufficiently | |
155 | 248 | Inconsistency with archiving pointers in request status management | Space: object requires documentation | |
156 | 249 | Enter a partition | Space: object requires documentation | |
157 | 250 | No time restrictions defined | Space: object requires documentation | |
158 | 251 | Status transition from '&2' to '&3' performed for request &1 | The short text describes the object sufficiently | |
159 | 252 | Query result inconsistent; interim deletion performed | Space: object requires documentation | |
160 | 260 | Consistency check of InfoProvider &2 and near-line object &3 in DAP &1 | The short text describes the object sufficiently | |
161 | 261 | Structures &1 and &2 are consistent | The short text describes the object sufficiently | |
162 | 262 | Component for InfoObject &2 missing in near-line structure &1 | The short text describes the object sufficiently | |
163 | 263 | Type of component &1 for InfoObject &2 is not consistent | The short text describes the object sufficiently | |
164 | 264 | Length of component &1 for InfoObject &2 is not consistent | The short text describes the object sufficiently | |
165 | 265 | Decimal places in component &1 for InfoObject &2 are not consistent | The short text describes the object sufficiently | |
166 | 266 | InfoProvider &2 and near-line object &3 are inconsistent in DAP &1 | Space: object requires documentation | |
167 | 270 | Verification of data package &2 in request &2 successfully finished: | The short text describes the object sufficiently | |
168 | 271 | Deviation in data package &2 between write and verification phases: | The short text describes the object sufficiently | |
169 | 272 | Write phase: &1 data records copied into &2 data objects | The short text describes the object sufficiently | |
170 | 273 | Verification pahse: &1 data records read into &2 data objects | The short text describes the object sufficiently | |
171 | 274 | Verification of data package &2 in request &1 failed | The short text describes the object sufficiently | |
172 | 275 | Number of archived records does not equal the number of reloaded records | Space: object requires documentation | |
173 | 279 | ------------------------------------------------------------------------- | The short text describes the object sufficiently | |
174 | 280 | ************************************************************************* | The short text describes the object sufficiently | |
175 | 281 | Start of copy phase for request &1 | The short text describes the object sufficiently | |
176 | 282 | Copy phase completed successfully for request &1 | The short text describes the object sufficiently | |
177 | 283 | Start of verifcation phase for request &1 | The short text describes the object sufficiently | |
178 | 284 | Continuation/repeat of verification phase for request &1 | The short text describes the object sufficiently | |
179 | 285 | Verification phase for request &1 completed successfully | The short text describes the object sufficiently | |
180 | 286 | Start of selective delete phase for request &1 | The short text describes the object sufficiently | |
181 | 287 | Near-line request &1 activated successfully | The short text describes the object sufficiently | |
182 | 288 | Repetition of selective delete phase for request &1 | The short text describes the object sufficiently | |
183 | 289 | Selective delete phase for request &1 completed successfully | The short text describes the object sufficiently | |
184 | 290 | Request &1 successfully confirmed and completed | The short text describes the object sufficiently | |
185 | 291 | Reader for InfoProvider '&1' successfully opened | The short text describes the object sufficiently | |
186 | 292 | Reader for InfoProvider '&1' successfully closed | The short text describes the object sufficiently | |
187 | 293 | Writer for archiving request &1 successfully opened | The short text describes the object sufficiently | |
188 | 294 | Writer for archiving request &1 successfully closed | The short text describes the object sufficiently | |
189 | 295 | Writer for ADK archiving session &1 successfully opened | Space: object requires documentation | |
190 | 296 | Writer for ADK archiving session &1 successfully closed | Space: object requires documentation | |
191 | 297 | Writer for near-line request &1 successfully opened | The short text describes the object sufficiently | |
192 | 298 | Writer for near-line request &1 successfully closed | The short text describes the object sufficiently | |
193 | 299 | Reader for archiving request &1 successfully opened | The short text describes the object sufficiently | |
194 | 300 | Reader for archiving request &1 closed successfully | The short text describes the object sufficiently | |
195 | 301 | Reader for ADK archiving session &1 opened successfully | The short text describes the object sufficiently | |
196 | 302 | Reader for ADK archiving session &1 successfully closed | The short text describes the object sufficiently | |
197 | 303 | Reader for near-line request &1 opened successfully | The short text describes the object sufficiently | |
198 | 304 | Reader for near-line request &1 closed successfully | The short text describes the object sufficiently | |
199 | 305 | Writer for InfoProvider '&1' successfully opened | The short text describes the object sufficiently | |
200 | 306 | Writer for InfoProvider '&1' successfully closed | The short text describes the object sufficiently | |
201 | 307 | All &1 data packages verified | The short text describes the object sufficiently | |
202 | 308 | &1 of total of &2 data packages verified | The short text describes the object sufficiently | |
203 | 309 | &1 data packages verified, write phase not yet completed | The short text describes the object sufficiently | |
204 | 310 | Start of common selective delete phase for multiple requests | The short text describes the object sufficiently | |
205 | 311 | Selective delete phase closed successfully | The short text describes the object sufficiently | |
206 | 312 | &1 data records copied in volumes of &2 KB | The short text describes the object sufficiently | |
207 | 313 | &1 data records read for verification | The short text describes the object sufficiently | |
208 | 314 | &1 data records deleted from InfoProvider '&2' | The short text describes the object sufficiently | |
209 | 315 | Start of final confirmation phase for request &1 | The short text describes the object sufficiently | |
210 | 316 | Near-line request &1 for archiving request &2 created | The short text describes the object sufficiently | |
211 | 317 | Data package &1 with ID '&2' opened | The short text describes the object sufficiently | |
212 | 318 | Data package &1 closed (&2 data records in &3 data objects) | The short text describes the object sufficiently | |
213 | 319 | Action '&1' on near-line connection '&2' failed (rc=&3) | The short text describes the object sufficiently | |
214 | 320 | Start of reload phase for archiving request &1 | The short text describes the object sufficiently | |
215 | 321 | Reload request &1 for archiving request &2 created | The short text describes the object sufficiently | |
216 | 322 | Continuation of processing with reload request &1 | The short text describes the object sufficiently | |
217 | 323 | Writer for InfoProvider '&1' successfully opened | The short text describes the object sufficiently | |
218 | 324 | Writer for InfoProvider '&1' successfully closed | The short text describes the object sufficiently | |
219 | 325 | Near-line request &1 deactivated | The short text describes the object sufficiently | |
220 | 326 | Near-line request &1 reactivated | The short text describes the object sufficiently | |
221 | 327 | Near-line request &1 invalidated and flagged for deletion | The short text describes the object sufficiently | |
222 | 328 | APO request &1 for reload request &2 created | The short text describes the object sufficiently | |
223 | 329 | APO request &1 for reload request &2 activated | The short text describes the object sufficiently | |
224 | 330 | APO request &1 for reload request &2 canceled | The short text describes the object sufficiently | |
225 | 331 | Reload request &1 can no longer be reloaded | Space: object requires documentation | |
226 | 332 | Archiving request &1 completely reloaded into InfoProvider '&2' | The short text describes the object sufficiently | |
227 | 333 | Check of reload area in DataStore object '&1' (current table) | The short text describes the object sufficiently | |
228 | 334 | Checked area is empty; reload/cancelation possible | The short text describes the object sufficiently | |
229 | 335 | Checked area contains &2 data records; reload is not possible | The short text describes the object sufficiently | |
230 | 336 | &1 data records for reload request &2 deleted from active table | The short text describes the object sufficiently | |
231 | 337 | Checked area contains more data records in active table than in archive | Space: object requires documentation | |
232 | 338 | Existence check for data in nearline table &1 failed | The short text describes the object sufficiently | |
233 | 339 | Lock in mode '&1' set for data package &2 in request &3 | The short text describes the object sufficiently | |
234 | 340 | Lock in mode '&1' for data package &2 in request &3 released | The short text describes the object sufficiently | |
235 | 341 | Automatic invalidation after error in copy or verification phase | The short text describes the object sufficiently | |
236 | 342 | Start of invalidation of request &1 | The short text describes the object sufficiently | |
237 | 343 | Error in data manager | The short text describes the object sufficiently | |
238 | 344 | Consistent data selection from database and archive not guaranteed | Space: object requires documentation | |
239 | 345 | Reload request &1 had to be terminated | Space: object requires documentation | |
240 | 346 | BWA index has been rebuilt | The short text describes the object sufficiently | |
241 | 347 | Rebuilding of BWA index scheduled in the background | The short text describes the object sufficiently | |
242 | 348 | Copy phase started: request &1 to near-line storage | The short text describes the object sufficiently | |
243 | 349 | Deletion of near-line request &1 started | The short text describes the object sufficiently | |
244 | 350 | Near-line request &1 deleted | The short text describes the object sufficiently | |
245 | 351 | Near-line request &1 already deleted | The short text describes the object sufficiently | |
246 | 352 | No near-line requests are flagged for deletion | The short text describes the object sufficiently | |
247 | 353 | No near-line requests are flagged for deletion for DAP &1 | The short text describes the object sufficiently | |
248 | 354 | Could not find any archiving requests for copying to near-line storage | The short text describes the object sufficiently | |
249 | 355 | Could not copy archiving requests to near-line storage | Space: object requires documentation | |
250 | 401 | Aggregate function &2 for field &1 not allowed with "FOR ALL ENTRIES" | The short text describes the object sufficiently | |
251 | 402 | Field &1 must be in drilldown when sorting by primary key | The short text describes the object sufficiently | |
252 | 403 | You may only sort by primary key with "FOR ALL ENTRIES" | The short text describes the object sufficiently | |
253 | 500 | *-------------------- Modelling (Contined) ----------------------------* | The short text describes the object sufficiently | |
254 | 501 | You cannot change storage type (ADK and/or near-line connection) | Space: object requires documentation | |
255 | 502 | You cannot change active near-line connection '&1' to '&2' | The short text describes the object sufficiently | |
256 | 503 | You cannot change selection scheme '&1' | The short text describes the object sufficiently | |
257 | 504 | You cannot change partitioning characteristic '&1' | The short text describes the object sufficiently | |
258 | 505 | No archiving connection specified | Space: object requires documentation | |
259 | 506 | Could not activate data archiving process | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 700 |