SAP ABAP Message Class PU (Upgrade and Transport Log Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CTS-ORG (Application Component) Transport Organizer
⤷ SCTS_EXE (Package) CTS: Transport Services
⤷ BC-CTS-ORG (Application Component) Transport Organizer
⤷ SCTS_EXE (Package) CTS: Transport Services
Attributes
Message class | PU | |
Short Description | Upgrade and Transport Log Messages | |
Changed On | 20141121 | |
Last Changed At | 124016 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *** Messages for Transport Dispatcher RDDIMPDP and Function Gr. STRS | ||
2 | 001 | &1 is not a valid client | Space: object requires documentation | |
3 | 002 | The entered target client & is invalid | ||
4 | 003 | Background job & is not scheduled in client & | ||
5 | 004 | Background job could not be scheduled (see system log) | Space: object requires documentation | |
6 | 005 | Background job & has already been scheduled in client & | Space: object requires documentation | |
7 | 006 | Background job &1 successfully scheduled in client &2 (job class &3) | Space: object requires documentation | |
8 | 007 | Error scheduling background job & in client & | Space: object requires documentation | |
9 | 008 | Event for starting &1 triggered in client &2 | Space: object requires documentation | |
10 | 009 | Table TRBAT still contains requests for other clients | Space: object requires documentation | |
11 | 010 | & & & & | ||
12 | 011 | Table TRBAT contains lock entry: &1 | Space: object requires documentation | |
13 | 012 | At present there is no header entry in table TRBAT | Space: object requires documentation | |
14 | 013 | Header &1: Contains HALT indicator, no action | ||
15 | 014 | Header &1: No actions currently required | Space: object requires documentation | |
16 | 015 | Header &1: Unknown status &2; no action | Space: object requires documentation | |
17 | 016 | Header &1: Unknown function, no action | Space: object requires documentation | |
18 | 017 | Header &1: Is edited in another client | Space: object requires documentation | |
19 | 018 | Header &1: Was already edited by an external job | Space: object requires documentation | |
20 | 019 | Header &1: Job identification deleted from TRJOB | Space: object requires documentation | |
21 | 020 | Header &1: Return code reset to 'start' | Space: object requires documentation | |
22 | 021 | Header &1: Return code set to 'ended' | Space: object requires documentation | |
23 | 022 | Header &1: Job ID is missing in TRJOB | Space: object requires documentation | |
24 | 023 | Header &1: Acc. to TRBAT, job &2 is still running. Checking job status | Space: object requires documentation | |
25 | 024 | Header &1: Job ID in TRBAT is incorrect | Space: object requires documentation | |
26 | 025 | Header &1: Job &2 terminated | Space: object requires documentation | |
27 | 026 | Header &1: Job &2 has already ended | Space: object requires documentation | |
28 | 027 | Header &1: Job &2 still has status scheduled | Space: object requires documentation | |
29 | 028 | Header &1: Job &2 still has status ready | Space: object requires documentation | |
30 | 029 | Header &1: Job &2 is still running | Space: object requires documentation | |
31 | 030 | Header &1: Job &2 still has status released | Space: object requires documentation | |
32 | 031 | Header &1: No more requests exist in TRBAT | Space: object requires documentation | |
33 | 032 | Header &1: Error updating dependent TRBAT entries | Space: object requires documentation | |
34 | 033 | Header &1: Error updating TRBAT | Space: object requires documentation | |
35 | 034 | Header &1: Invalid target client &2 for individual requests | Space: object requires documentation | |
36 | 035 | Header &1: Background job &2 is not scheduled in client &3 | Space: object requires documentation | |
37 | 036 | Header &1: Invalid target client &2 | Space: object requires documentation | |
38 | 037 | Header &1: Job ID &2 entered in TRJOB | Space: object requires documentation | |
39 | 038 | Header &1: Job has started | Space: object requires documentation | |
40 | 039 | Event to start &3 in client &4 could not be triggered | Space: object requires documentation | |
41 | 040 | No authorization for scheduling transport programs | ||
42 | 041 | Background job &1 in client &2 has not been scheduled | Space: object requires documentation | |
43 | 042 | Background job &1 did not end correctly | Space: object requires documentation | |
44 | 043 | Header &1: Background job according to TRJOB still active | ||
45 | 044 | Header &1: Return code set to 'active' | Space: object requires documentation | |
46 | 045 | Header &1: Ended acc. to TRBAT, but there are still requests in TRBAT | ||
47 | 046 | Header &1: Entries for requests in TRBAT checked and cleaned up | ||
48 | 047 | Header &1: Job &2 has status descheduled | Space: object requires documentation | |
49 | 048 | Scheduling of Transport Scheduler canceled | Space: object requires documentation | |
50 | 050 | Program &1 is running in client &2 | Space: object requires documentation | |
51 | 060 | Specify a directory | The short text describes the object sufficiently | |
52 | 061 | Specify an application | The short text describes the object sufficiently | |
53 | 062 | Specify a deployment | The short text describes the object sufficiently | |
54 | 100 | *** Messages for XPRA control programs RDDEXECL/U | ||
55 | 101 | Program &1 does not exist | Space: object requires documentation | |
56 | 102 | &1 is not an executable program | Space: object requires documentation | |
57 | 103 | Global memory was destroyed after execution of XPRA &1 | Space: object requires documentation | |
58 | 104 | Global memory was destroyed after execution of method &1 | Space: object requires documentation | |
59 | 105 | Global memory destroyed after transport methods executed | Space: object requires documentation | |
60 | 106 | Internal mode is destroyed after execution of method &3 | Space: object requires documentation | |
61 | 107 | Report &1 not executed since it is not active in this system | Space: object requires documentation | |
62 | 110 | Execute reports for change/transport request: & | ||
63 | 111 | on the application server: & | Space: object requires documentation | |
64 | 112 | Change-/transport request & does not exist | ||
65 | 113 | There are no reports to execute | ||
66 | 114 | XPRA & has already been executed in a previous step | ||
67 | 115 | Report & started: & | Space: object requires documentation | |
68 | 116 | Report & ended: & | Space: object requires documentation | |
69 | 117 | Reports for change/transport request & have been executed | ||
70 | 118 | Start of................ & | ||
71 | 119 | End of.................. & | ||
72 | 120 | Time... & Run time... & | ||
73 | 121 | Subsequent processing of & & already carried out in previous step | Space: object requires documentation | |
74 | 122 | Post-import method & started for & &, date and time: & | Space: object requires documentation | |
75 | 123 | Post-import method & completed for & &, date and time: & | Space: object requires documentation | |
76 | 124 | Function module & does not exist (subsequent processing for & &) | ||
77 | 125 | The object & & has not been imported successfully yet | Space: object requires documentation | |
78 | 126 | Post-import methods for change/transport request: & | ||
79 | 127 | Post-import methods of change/transport request & completed | ||
80 | 128 | Start of subsequent processing ... & | ||
81 | 129 | End of subsequent processing... & | ||
82 | 130 | Transport step &: Background job & ended correctly | Space: object requires documentation | |
83 | 131 | No objects requiring post-import methods exist | Space: object requires documentation | |
84 | 132 | Errors occurred executing report & | ||
85 | 133 | Errors occurred during post-handling & for & & | ||
86 | 134 | Report &1 belongs to package &2 | Space: object requires documentation | |
87 | 135 | &1 belongs to package &2 | Space: object requires documentation | |
88 | 136 | The errors affect the following components: | Space: object requires documentation | |
89 | 137 | &1 (&2) | ||
90 | 138 | in client : & | Space: object requires documentation | |
91 | 139 | Postprocessing necessary when upgrade has been completed | Space: object requires documentation | |
92 | 140 | **** Log messages for mass generation program RDDDIC3L/0 | ||
93 | 141 | Generation of programs and screens for transport request & | Space: object requires documentation | |
94 | 142 | on application server & | Space: object requires documentation | |
95 | 143 | Only generates programs with LOAD versions | ||
96 | 144 | ------------------------------------------------------------------------- | ||
97 | 145 | Start on & at & | ||
98 | 146 | Generation of the transported programs | Space: object requires documentation | |
99 | 147 | Generation of the users of the transported Includes | Space: object requires documentation | |
100 | 148 | Cross reference generation triggered | ||
101 | 149 | Ended on & at & | ||
102 | 150 | No. of programs /Min/Avg/Max (sec): & & & & | Space: object requires documentation | |
103 | 151 | No. of variants /Min/Avg/Max (sec): & & & & | ||
104 | 152 | No. of screens /Min/Avg/Max (sec): & & & & | ||
105 | 153 | Database COMMIT executed | ||
106 | 154 | & & & already generated | ||
107 | 155 | & & & not yet imported | ||
108 | 156 | Program & does not exist | Space: object requires documentation | |
109 | 157 | Report & : Variant catalog was updated | ||
110 | 158 | Screen &1 &2 not generated since it is not activated | Space: object requires documentation | |
111 | 159 | Program &1 will not be generated since it is not activated | Space: object requires documentation | |
112 | 160 | Program &: Generation error in line & | Space: object requires documentation | |
113 | 161 | Program &: Syntax error in line & | Space: object requires documentation | |
114 | 162 | Program &, Include &: Generation error in line & | Space: object requires documentation | |
115 | 163 | Program &, Include &: Syntax error in line & | Space: object requires documentation | |
116 | 164 | && | Space: object requires documentation | |
117 | 165 | Program $ successfully generated | Space: object requires documentation | |
118 | 166 | Program & contains no syntax errors | Space: object requires documentation | |
119 | 167 | Screen &1 &2: Generation error | Space: object requires documentation | |
120 | 168 | Screen &1 &2 successfully generated | Space: object requires documentation | |
121 | 169 | Post-import actions for change request/transport request: & | Space: object requires documentation | |
122 | 170 | All DB buffers of application server &1 were synchronized | Space: object requires documentation | |
123 | 171 | Error synchronizing DB buffers of application server &1 | Space: object requires documentation | |
124 | 175 | Prelock method & started for & & | The short text describes the object sufficiently | |
125 | 176 | Function module & does not exist (prelock for & &) | The short text describes the object sufficiently | |
126 | 177 | Errors occurred when executing the prelock method & for & & | The short text describes the object sufficiently | |
127 | 180 | &1 &2 &3 was already imported into client &4 | Space: object requires documentation | |
128 | 181 | Post-import methods called without specified client | Space: object requires documentation | |
129 | 182 | Post-processing for &2 &3 was already performed successfully earlier | Space: object requires documentation | |
130 | 183 | Object &2 &3 has not yet been imported successfully | Space: object requires documentation | |
131 | 184 | Post-processing for &2 &3 in client &4 was already performed earlier | Space: object requires documentation | |
132 | 185 | The object &2 &3 has not yet been imported successfully into client &4 | Space: object requires documentation | |
133 | 186 | Post-processing taking place in client &2 | Space: object requires documentation | |
134 | 187 | Termination of post-import methods after TRBATC communication error | Space: object requires documentation | |
135 | 188 | Code page type for system could not be determined | Space: object requires documentation | |
136 | 189 | Cannot transport ADO objects for Unicode systems | Space: object requires documentation | |
137 | 190 | Post-import methods called without unique client | Space: object requires documentation | |
138 | 191 | Recursive call of activation methods of Switch Framework | Space: object requires documentation | |
139 | 192 | Post-import method &1 in client &2 already ran | Space: object requires documentation | |
140 | 193 | Error in call when executing XPRA reports | Space: object requires documentation | |
141 | 200 | * Messages for upgrade control program put | ||
142 | 201 | Log analyzed partially | ||
143 | 202 | Current restarting point | ||
144 | 203 | --> Messages from log file & | Space: object requires documentation | |
145 | 204 | Post-import method & started for & &, date and time: & | Space: object requires documentation | |
146 | 205 | Post-import method & ignored for & &, date and time: & | Space: object requires documentation | |
147 | 206 | Post-import method & deleted for & &, date and time: & | Space: object requires documentation | |
148 | 207 | User: & | Space: object requires documentation | |
149 | 226 | Request &1 | Space: object requires documentation | |
150 | 227 | There are &1 requests to process (key &2) | Space: object requires documentation | |
151 | 228 | Start: Executing method &1 for business add-on &2 | Space: object requires documentation | |
152 | 229 | End: Executing method &1 for business add-on &2 | Space: object requires documentation | |
153 | 230 | Execution of the export pre-processing methods for request &1 | Space: object requires documentation | |
154 | 231 | Start: Adjusting the object directory for the objects of the request &1 | Space: object requires documentation | |
155 | 232 | End: Adapting the object directory for the objects of the request &1 | Space: object requires documentation | |
156 | 233 | Start: Execution of object-specific export pre-processing methods | Space: object requires documentation | |
157 | 234 | End: Execution of object-specific export pre-processing methods | Space: object requires documentation | |
158 | 235 | Start: Version creation of the objects of the request &1 | Space: object requires documentation | |
159 | 236 | End: Version creation of the objects of the request &1 | Space: object requires documentation | |
160 | 237 | Version creation started as update request | Space: object requires documentation | |
161 | 238 | Error in pre-export methods for request &1 | Space: object requires documentation | |
162 | 239 | Database rollback executed | Space: object requires documentation | |
163 | 240 | Request &1 is modifiable after error during release | Space: object requires documentation | |
164 | 241 | Function module &1 does not exist (export pre-processing for &2 &3) | Space: object requires documentation | |
165 | 242 | Start: Execution of method &1 | Space: object requires documentation | |
166 | 243 | End: Execution of method &1 | Space: object requires documentation | |
167 | 244 | Start: Check for existence of inactive objects | Space: object requires documentation | |
168 | 245 | End: Check for existence of inactive objects | Space: object requires documentation | |
169 | 246 | Start: Check for unreleased tasks | Space: object requires documentation | |
170 | 247 | End: Check for unreleased tasks | Space: object requires documentation | |
171 | 248 | Start: Creating project information | Space: object requires documentation | |
172 | 249 | End: Creating project information | Space: object requires documentation | |
173 | 250 | Start: Sorting and compressing the object list | Space: object requires documentation | |
174 | 251 | End: Sorting and compressing the object list | Space: object requires documentation | |
175 | 252 | Start: Writing nametab information for key entries | Space: object requires documentation | |
176 | 253 | End: Writing nametab information for key entries | Space: object requires documentation | |
177 | 254 | &1 is not a transportable request | Space: object requires documentation | |
178 | 255 | Start: Adjusting namespace settings | Space: object requires documentation | |
179 | 256 | End: Adjusting namespace settings | Space: object requires documentation | |
180 | 257 | No action required: Adjustment already made successfully | Space: object requires documentation | |
181 | 258 | Error accessing the database (for namespace tables) | Space: object requires documentation | |
182 | 259 | Load invalidation for request &1 | The short text describes the object sufficiently | |
183 | 260 | Requests with archived keys are not released | The short text describes the object sufficiently | |
184 | 261 | End of load invalidation for request &1 | The short text describes the object sufficiently | |
185 | 293 | Log contains no entries | Space: object requires documentation | |
186 | 294 | Log empty | Space: object requires documentation | |
187 | 295 | Log expanded completely | Space: object requires documentation | |
188 | 296 | Log collapsed completely | Space: object requires documentation | |
189 | 297 | Log in current section expanded to level & | Space: object requires documentation | |
190 | 298 | Log in current section collapsed to level & | Space: object requires documentation | |
191 | 299 | Log expanded to level & | Space: object requires documentation | |
192 | 300 | Log collapsed to level & | Space: object requires documentation | |
193 | 303 | Specify a transport request | Space: object requires documentation | |
194 | 304 | Specify a system name | Space: object requires documentation | |
195 | 305 | Specify an action type | Space: object requires documentation | |
196 | 306 | Specify a valid directory type: T(ransport), P(ut) | Space: object requires documentation | |
197 | 307 | Specify a log name | Space: object requires documentation | |
198 | 308 | Specify a valid log type: F(ile system) | Space: object requires documentation | |
199 | 309 | Could not write database log completely | Space: object requires documentation | |
200 | 310 | Position cursor on a log message | Space: object requires documentation | |
201 | 311 | Required log section not found | Space: object requires documentation | |
202 | 312 | Job ran in system &1, make the analysis in that system | Space: object requires documentation | |
203 | 313 | Enter a valid log type | Space: object requires documentation | |
204 | 314 | Specify a log name | Space: object requires documentation | |
205 | 315 | Log & could not be found | Space: object requires documentation | |
206 | 316 | Log is already fully expanded | Space: object requires documentation | |
207 | 317 | Log is already fully collapsed | Space: object requires documentation | |
208 | 318 | Log was reread | Space: object requires documentation | |
209 | 319 | !! Messages 320 to 340 reserved for TRINT_DISPLAY_LOG!! | Space: object requires documentation | |
210 | 320 | See job log | Space: object requires documentation | |
211 | 321 | See object & & | Space: object requires documentation | |
212 | 322 | Request &1 | Space: object requires documentation | |
213 | 323 | See log &2&3&4 | Space: object requires documentation | |
214 | 324 | See log for request &1 (timestamp &2, system &3) | Space: object requires documentation | |
215 | 325 | Selection log (internal number &1, for delivery request &2) | Space: object requires documentation | |
216 | 340 | Versions not made | Space: object requires documentation | |
217 | 350 | *** Messages for TDEVC conversion reports ******************************* | ||
218 | 351 | Transport layer from & to & | ||
219 | 352 | Transport layer & created (INTSYS &, CONSYS &) | ||
220 | 353 | Transport layer for SAP standard objects | ||
221 | 354 | Layer for objects not to be transported | ||
222 | 355 | Text created for layer & in language & | ||
223 | 356 | Text for package & in language & converted | Space: object requires documentation | |
224 | 357 | Text for SAP System & converted into language & | Space: object requires documentation | |
225 | 358 | Entry created in object directory TADIR for package & | Space: object requires documentation | |
226 | 359 | Entry updated in object directory TADIR for package & | Space: object requires documentation | |
227 | 360 | Entry for table TDEVC for package & converted | Space: object requires documentation | |
228 | 361 | Entry in table TSYST converted for SAP System & | Space: object requires documentation | |
229 | 362 | Error creating transport layer & (INTSYS &, CONSYS &) | ||
230 | 363 | Error creating text for transport layer & in language & | Space: object requires documentation | |
231 | 364 | Error converting text for package & in language & | Space: object requires documentation | |
232 | 365 | Error converting text for system & in language & | ||
233 | 366 | Error creating the object directory entry (TADIR) for package & | Space: object requires documentation | |
234 | 367 | Error converting the TDEVC entry for package & | Space: object requires documentation | |
235 | 368 | Error converting the TSYST entry for SAP System & | Space: object requires documentation | |
236 | 369 | Error updating the object directory entry for package & | Space: object requires documentation | |
237 | 370 | Respond to the following errors only after completing the upgrade | Space: object requires documentation | |
238 | 371 | Layer & already exists. Creating the new layer & (&,&). | Space: object requires documentation | |
239 | 372 | Error determining installed languages | ||
240 | 373 | Texts are only created in language E (English) | ||
241 | 380 | Request does not contain any namespaces to be activated | Space: object requires documentation | |
242 | 381 | Namespace &1 was deleted successfully | Space: object requires documentation | |
243 | 382 | Namespace &1 activated successfully | Space: object requires documentation | |
244 | 383 | Namespace assigned successfully for &1 package(s) | Space: object requires documentation | |
245 | 384 | Component assigned successfully for &1 package(s) | Space: object requires documentation | |
246 | 385 | Checking namespace and component assignment of packages | Space: object requires documentation | |
247 | 386 | Package check completed successfully | Space: object requires documentation | |
248 | 387 | Activating namespaces delivered by SAP | Space: object requires documentation | |
249 | 388 | Namespace &2 created for SAP partner project &1 | Space: object requires documentation | |
250 | 389 | Namespaces activated successfully | Space: object requires documentation | |
251 | 390 | Obsolete namespace &1 successfully deleted | Space: object requires documentation | |
252 | 412 | Test import can only be triggered for released requests | ||
253 | 414 | Position the cursor on a transport request | Space: object requires documentation | |
254 | 415 | Position the cursor on a transport or a repair | Space: object requires documentation | |
255 | 416 | Position the cursor on a transport request | Space: object requires documentation | |
256 | 417 | Position the cursor on a reference to a log | Space: object requires documentation | |
257 | 418 | Position the cursor on a transport request | Space: object requires documentation | |
258 | 420 | Cannot find import steps that are independent of requests | Space: object requires documentation | |
259 | 450 | ******Messages for handling Support Packages***************************** | ||
260 | 451 | Object &1 &2 &3 cannot be processed in Support Package | Space: object requires documentation | |
261 | 452 | Request &1 is assigned to Support Package request; linking not possible | Space: object requires documentation | |
262 | 453 | System change option "&1" cannot be changed here | Space: object requires documentation | |
263 | 454 | System change option: & | ||
264 | 499 | &1: Conversion actions in the Transport Organizer area | Space: object requires documentation | |
265 | 600 | *****Messages for File Deployment - RDDDEPLOY&CL_CTS_FILE_SERVICE***** | The short text describes the object sufficiently | |
266 | 601 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
267 | 602 | &1&2&3&4 | The short text describes the object sufficiently | |
268 | 603 | File name cannot be longer than 260 characters; length is &1 | The short text describes the object sufficiently | |
269 | 604 | Cannot open file &1 | The short text describes the object sufficiently | |
270 | 606 | Double-stack system &1 | The short text describes the object sufficiently | |
271 | 607 | Non-ABAP system &1 (communication system &2) | The short text describes the object sufficiently | |
272 | 608 | System &1 is unknown | The short text describes the object sufficiently | |
273 | 609 | Opening log for step &1, system &2, request &3, log key &4 | The short text describes the object sufficiently | |
274 | 610 | Writing and closing log of &1 message(s) | The short text describes the object sufficiently | |
275 | 611 | HTTP destination &1 is unknown | The short text describes the object sufficiently | |
276 | 612 | System &1 is not valid; configure Organizer client in TMS | Space: object requires documentation | |
277 | 613 | Error when executing Web service &1, exception is &2 | The short text describes the object sufficiently | |
278 | 614 | CTS Import Service - Version 0.95 - 19.08.2008 | The short text describes the object sufficiently | |
279 | 615 | Deploy Web service destination: &1 | The short text describes the object sufficiently | |
280 | 616 | Directory: &1 | The short text describes the object sufficiently | |
281 | 617 | &1 Deploy URL: &2 | The short text describes the object sufficiently | |
282 | 618 | CTS Deploy Service - Version 0.93 - 06.03.2007 | The short text describes the object sufficiently | |
283 | 619 | Highest return code is &1 | The short text describes the object sufficiently | |
284 | 620 | Could not export request &1 | The short text describes the object sufficiently | |
285 | 621 | Request &1 is already locked | The short text describes the object sufficiently | |
286 | 622 | Request &1 is already locked against changes by &2 | The short text describes the object sufficiently | |
287 | 623 | Changes to system &2 locked; request was &1 | The short text describes the object sufficiently | |
288 | 624 | File &1 already exists in request &2 | The short text describes the object sufficiently | |
289 | 625 | Could not create request | The short text describes the object sufficiently | |
290 | 626 | Could not release request &1; see release log | The short text describes the object sufficiently | |
291 | 627 | Could not check in file &1 | The short text describes the object sufficiently | |
292 | 628 | User &1 does not have authorization for action &2 | The short text describes the object sufficiently | |
293 | 629 | Object &1 &2 &3 is not permitted in the file service | The short text describes the object sufficiently | |
294 | 630 | Could not assign attributes to request &1 | The short text describes the object sufficiently | |
295 | 631 | Overflow in request numbers for external system &1 | The short text describes the object sufficiently | |
296 | 632 | Request &1 can no longer be modified | The short text describes the object sufficiently | |
297 | 633 | Request &1 is unknown | The short text describes the object sufficiently | |
298 | 634 | Invalid or unknown system &1, client &2 | The short text describes the object sufficiently | |
299 | 635 | Request &1 is invalid or has an incorrect status | The short text describes the object sufficiently | |
300 | 636 | File &1 not found | The short text describes the object sufficiently | |
301 | 637 | No standard request defined for user &1 | The short text describes the object sufficiently | |
302 | 638 | Project &1 is unknown | The short text describes the object sufficiently | |
303 | 639 | Target system &1 is not allowed | The short text describes the object sufficiently | |
304 | 640 | Documentation of request &1 not found | The short text describes the object sufficiently | |
305 | 641 | Could not update documentation for request &1 | The short text describes the object sufficiently | |
306 | 642 | Request &1 cannot contain locked objects | The short text describes the object sufficiently | |
307 | 643 | Release preconditions for &1 not met | The short text describes the object sufficiently | |
308 | 644 | Could not create or change port &1 | The short text describes the object sufficiently | |
309 | 645 | Could not create or change RFC destination &1 | The short text describes the object sufficiently | |
310 | 646 | Request &1 (type &2) cannot have tasks | The short text describes the object sufficiently | |
311 | 647 | Request/task &1 not deleted; see long text | Space: object requires documentation | |
312 | 648 | User &1 is unknown | The short text describes the object sufficiently | |
313 | 649 | File identifier &1 does not exist | Space: object requires documentation | |
314 | 650 | URL not configured for system &1 (type &2) | The short text describes the object sufficiently | |
315 | 651 | CTS+ port or http destination &1 does not exist | The short text describes the object sufficiently | |
316 | 652 | Could not update configuration for system &1 | The short text describes the object sufficiently | |
317 | 653 | Destination for system &1, client &2 does not exist or does not work | The short text describes the object sufficiently | |
318 | 654 | Deploy proxy only permits restricted functions | The short text describes the object sufficiently | |
319 | 655 | Deploy proxy features: &1 &2 &3 &4 | The short text describes the object sufficiently | |
320 | 656 | Request &1 flagged in target &1.&2(&3) | The short text describes the object sufficiently | |
321 | 657 | Unknown system &1 from domain &2 with client &3 | Space: object requires documentation | |
322 | 658 | Service &2 does not exist for system &1 or is not active | The short text describes the object sufficiently | |
323 | 660 | File deployer: Log instance not found for request &1 | The short text describes the object sufficiently | |
324 | 661 | File import canceled | The short text describes the object sufficiently | |
325 | 662 | File ID &1 of application &2 skipped due to missing configuration | The short text describes the object sufficiently | |
326 | 663 | File ID &1 (type &2) not executed | The short text describes the object sufficiently | |
327 | 664 | Files of type &1 not deployed | The short text describes the object sufficiently | |
328 | 665 | Request attribute &1 is mandatory | The short text describes the object sufficiently | |
329 | 666 | Request attribute &1 must have a value | The short text describes the object sufficiently | |
330 | 667 | Start of Web Service Log | The short text describes the object sufficiently | |
331 | 668 | End of Web Service Log | The short text describes the object sufficiently | |
332 | 669 | No file deployment required for &1 | The short text describes the object sufficiently | |
333 | 670 | Deploy for &1 | The short text describes the object sufficiently | |
334 | 671 | Deploy file &1 | The short text describes the object sufficiently | |
335 | 672 | Web service destination &1 is not configured, deployment skipped | The short text describes the object sufficiently | |
336 | 673 | Internal communication error with destination &1 | The short text describes the object sufficiently | |
337 | 674 | No URL configured for deployment of &1 | The short text describes the object sufficiently | |
338 | 675 | &1 deployment skipped due to missing configuration | The short text describes the object sufficiently | |
339 | 676 | Start deployment of &1 | The short text describes the object sufficiently | |
340 | 677 | Stop deployment of &1 | The short text describes the object sufficiently | |
341 | 678 | tp import of attached requests ended with return code &1 | The short text describes the object sufficiently | |
342 | 679 | R3TRANS deployment skipped for following requests (see long text): | Space: object requires documentation | |
343 | 680 | Download failed | The short text describes the object sufficiently | |
344 | 681 | Download complete | The short text describes the object sufficiently | |
345 | 682 | Internal error; assertion skipped (see long text) | Space: object requires documentation | |
346 | 683 | No destination found for system &1 from domain &2 | The short text describes the object sufficiently | |
347 | 684 | Requests for R3trans import | The short text describes the object sufficiently | |
348 | 685 | TMS alert: &3 in service &1, function &2 | The short text describes the object sufficiently | |
349 | 686 | Additional information: &1 | The short text describes the object sufficiently | |
350 | 687 | Request &1 flagged for client '&2' (&4) [&3] | The short text describes the object sufficiently | |
351 | 688 | CTS R3trans File Import Service - Version 0.90 - 08.09.2009 | The short text describes the object sufficiently | |
352 | 689 | CTS File Import Service - Version 1.00 - 08.09.2009 | The short text describes the object sufficiently | |
353 | 690 | CTS Deploy Service - Version 1.00 - 08.09.2009 | The short text describes the object sufficiently | |
354 | 691 | No action required in this step | The short text describes the object sufficiently | |
355 | 692 | CTS Check Deploy Service | The short text describes the object sufficiently | |
356 | 693 | Requests to be checked | The short text describes the object sufficiently | |
357 | 694 | Request &1 fully imported into system &2 | The short text describes the object sufficiently | |
358 | 695 | Parts of request &1 imported into system &2 | The short text describes the object sufficiently | |
359 | 696 | Request &1 not yet imported into system &2 | The short text describes the object sufficiently | |
360 | 697 | Request &1 unknown in system &2 (not yet imported) | The short text describes the object sufficiently | |
361 | 698 | Deployment check ended with return code &1 | The short text describes the object sufficiently | |
362 | 699 | - &1 | The short text describes the object sufficiently | |
363 | 700 | Request &1 flagged for reimport into system &2 | The short text describes the object sufficiently | |
364 | 701 | Details in log for step '&4' of request &1 (&3 - &2) | The short text describes the object sufficiently | |
365 | 702 | Skipped requests (no action required) | The short text describes the object sufficiently | |
366 | 703 | Not executed due to canceled import tool | The short text describes the object sufficiently | |
367 | 704 | Deploy proxy server not running or Web service not installed | The short text describes the object sufficiently | |
368 | 705 | Error stack trace | The short text describes the object sufficiently | |
369 | 706 | Invalid path &1&2&3 | The short text describes the object sufficiently | |
370 | 710 | Plug-in not installed in target system &1 | The short text describes the object sufficiently | |
371 | 711 | Import transport targets | The short text describes the object sufficiently | |
372 | 712 | &1.&2@&3 | The short text describes the object sufficiently | |
373 | 713 | &1.&2@&3 for requests from &4 | The short text describes the object sufficiently | |
374 | 714 | &1.&2@&3 filtered out | The short text describes the object sufficiently | |
375 | 715 | &1.&2@&3 filtered out for requests from &4 | The short text describes the object sufficiently | |
376 | 716 | Action &1 canceled due to timeout | Space: object requires documentation | |
377 | 717 | Import options: | The short text describes the object sufficiently | |
378 | 718 | Unknown import option: &1 | The short text describes the object sufficiently | |
379 | 719 | No further actions required for this transport | Space: object requires documentation | |
380 | 720 | Distribution to system &2 canceled with error &1 | Space: object requires documentation | |
381 | 721 | Configuration distributed to &1 system(s) | The short text describes the object sufficiently | |
382 | 730 | Overtaker transport; leave in queue for further imports | The short text describes the object sufficiently | |
383 | 731 | Import transport again | The short text describes the object sufficiently | |
384 | 732 | Overwrite object originals | The short text describes the object sufficiently | |
385 | 733 | Ignore predecessor relationships | The short text describes the object sufficiently | |
386 | 734 | Ignore invalid component version | The short text describes the object sufficiently | |
387 | 735 | Unknown option: 5 | The short text describes the object sufficiently | |
388 | 736 | Overwrite objects in unconfirmed repairs | The short text describes the object sufficiently | |
389 | 737 | Unknown option: 7 | The short text describes the object sufficiently | |
390 | 738 | Ignore table class | The short text describes the object sufficiently | |
391 | 739 | Ignore invalid transport type | The short text describes the object sufficiently | |
392 | 750 | Transport object &1 &2 &3 cannot be used | The short text describes the object sufficiently | |
393 | 751 | Communication error: System &1 (see below for details) | The short text describes the object sufficiently | |
394 | 752 | Service &1 is not available | Space: object requires documentation | |
395 | 800 | **** Messages for function group STRF | ||
396 | 801 | Invalid file access mode "&" | Space: object requires documentation | |
397 | 802 | Type "&" invalid for transport directory | Space: object requires documentation | |
398 | 803 | Identifier "&" invalid for naming convention | Space: object requires documentation | |
399 | 804 | Invalid system name "&" | Space: object requires documentation | |
400 | 805 | Error when calling the operating system | Space: object requires documentation | |
401 | 806 | Transfer parameters inconsistent | ||
402 | 807 | No authorization to read file & | Space: object requires documentation | |
403 | 808 | No authorization to change file & | Space: object requires documentation | |
404 | 809 | You are not authorized to delete file & | Space: object requires documentation | |
405 | 810 | Invalid date/week number for logging file | Space: object requires documentation | |
406 | 811 | No system name for system log file | Space: object requires documentation | |
407 | 812 | Type "&" invalid for logging file | Space: object requires documentation | |
408 | 813 | Command file for & locked by another process | Space: object requires documentation | |
409 | 814 | Cannot access file & | Space: object requires documentation | |
410 | 815 | SAP names file for & locked by another process | Space: object requires documentation | |
411 | 816 | Error occurred when deleting file & | ||
412 | 817 | Specify a name unique in the Change & Transport System | Space: object requires documentation | |
413 | 818 | Error when changing sapnames file if user & | ||
414 | 819 | Information entries that are no longer relevant were deleted (total &) | ||
415 | 820 | No transport information for specified user/transport found | Space: object requires documentation | |
416 | 821 | Inaccurate information entries were corrected (in total &) | Space: object requires documentation | |
417 | 822 | Selected information entries were deleted (in total &) | Space: object requires documentation | |
418 | 823 | Global information cannot be read | Space: object requires documentation | |
419 | 824 | Global information cannot be read | Space: object requires documentation | |
420 | 825 | No deletable entries found | Space: object requires documentation | |
421 | 826 | Log too large (& bytes); messages displayed up to level 3 only | Space: object requires documentation |
History
Last changed on/by | 20141121 | SAP | |
SAP Release Created in |