TP - Transportsteuerung
The following messages are stored in message class TP: Transportsteuerung.
It is part of development package STTO in software component BC-CTS. This development package consists of objects that can be grouped under "Transport Tools".
It is part of development package STTO in software component BC-CTS. This development package consists of objects that can be grouped under "Transport Tools".
Message Nr ▲ | Message Text |
---|---|
001 | Enter a release |
002 | Specify an output level |
003 | Program does not support output level 4 |
004 | Caution: You have not entered a program name |
005 | Log file does not exist |
009 | Filter file does not exist |
010 | Error accessing file & |
019 | ######################################################################### |
020 | General header messages ....................................... (020-039) |
021 | Executed program_______& |
022 | Executed function______& |
023 | Request number_________& |
024 | Start date_____________& |
025 | Start time_____________& |
040 | General footer messages ....................................... (040-059) |
041 | Record statistics |
042 | Input records & |
043 | ... Errors & |
044 | ... Warnings & |
045 | ... Edited & |
051 | End date & |
052 | End time & |
053 | >>>> RETURNCODE & <<<< |
100 | ---- Messages from tp (100-199) ---- |
101 | Transport request : & |
102 | System : & |
103 | User : & |
108 | tp path : & |
109 | Version and release: & & |
110 | End date and time : & |
111 | Ended with return code: ===> & <=== |
120 | & not found |
121 | Cannot execute & |
122 | & incorrect transport type - never imported |
123 | Could not write entry to buffer file for & |
124 | Target system & not defined in TPPARAM file |
125 | Could not delete & |
126 | Could not rename & |
127 | & renamed |
128 | No target system defined; & not a transport request |
129 | Export from non-ABAP system - only object type FILE is permitted. |
130 | No target system is defined for &1. No forwarding at export time. |
140 | Temporary log &1 not found; using &2 instead |
141 | Temporary log &1 not found |
142 | Deployment of request in overtaker collection &1 is skipped |
150 | Main export |
151 | Export of application-defined objects |
152 | Test import |
153 | Dictionary import |
154 | Main import |
155 | ABAP Dictionary: Activation |
156 | Generation of Programs and Dynpros |
157 | Import application-defined objects |
158 | Release of corrections with C sources |
159 | Kernel copy |
160 | Export of C programs |
161 | Execution of programs before import (XPRB) |
162 | Execution of programs after import (XPRA) |
163 | Import table entries |
164 | Import SVERS entry |
165 | ABAP Dictionary: Activation (TACOB) |
166 | Activating enhancement objects/table conversion (TBATG) |
167 | Start database |
168 | Stop database |
169 | Start SAP System |
170 | Stop SAP System |
171 | Activate inactive reports |
172 | Activate inactive nametabs |
173 | Distribution of DD objects |
174 | Update version management |
175 | Matchcode and enqueue activations |
176 | Import of object list of a request |
177 | Logical import of Customizing data |
178 | Shared import |
179 | Generate cofile from data file |
180 | Unknown action |
181 | Conversion of ADO data file |
182 | Checking whether buffer can be written to |
183 | Preparation for export |
184 | Generate object versions before import of objects |
185 | Generate object versions after import of objects |
186 | R3trans Connect to database |
187 | R3trans import into shadow tables |
188 | Confirmation |
189 | Deployment |
193 | SAP HANA deployment |
195 | Incomplete log ==> & terminated for unknown reasons |
196 | & return code not sent correctly. See SAP Note 43552. |
197 | & harmless errors |
200 | Error in export; request not imported |
201 | Checking buffer of target system: & |
202 | Checking buffer of a test system: & |
203 | Buffer & can be written to |
204 | Buffer & cannot be written to |
205 | Error was: & |
206 | Buffer of source system (&) does not need to be checked |
300 | --- dipgntab messages (300 - 399) --- |
301 | ------------------------------------------------------------------------- |
302 | & & not supported |
303 | Activation of sample nametabs: & nametabs activated |
304 | Activation of sample nametabs: & nametabs activated |
305 | End : & |
306 | Lasted: & |
307 | Start : & |
308 | & objects found |
309 | Following programs activated: |
310 | Activation of programs |
311 | Activation of programs: & programs activated |
312 | Activation of programs: & programs activated |
313 | Activation of programs: & programs deleted |
314 | Activation of programs: & programs deleted |
315 | Activation of programs: & programs with errors |
316 | Activation of programs: Rollback executed |
317 | Cannot determine host name |
318 | No parameters |
319 | No table specified for comparison |
320 | No table specified for printing |
321 | Parameter error: & & |
322 | Unknown parameter: & & |
323 | & is activated |
324 | & is deleted |
325 | Only the first & programs were output |
326 | No source found for & |
327 | Error & with program & |
328 | & deleted & |
329 | & activated & |
330 | Activation of sample nametabs with appended fields |
331 | Output of sample nametabs with appended fields |
332 | Table & not in sample nametab |
333 | Nametab for & would be activated |
334 | No DDL commands found for activation of & |
335 | & activated, DDL executed |
336 | Only the first & tables are activated |
337 | Activation of shadow nametabs |
338 | Output of shadow nametabs |
339 | & activated |
340 | Output nametab & |
341 | Compare & version & against nametab |
342 | Activate & version & |
343 | Foreign key for &-& not found |
344 | SQL error & occurred at position & (object &) |
345 | Error & when executing ADD-FIELD of & |
346 | Output of shadow nametabs (deletes) with DDL |
347 | Activation of shadow nametabs (deletes) with DDL |
348 | & deleted, DDL executed |
349 | Only the first & nametabs are deleted |
350 | Nametab for & would be deleted |
351 | Maximum number of fragments (&) for & exceeded |
352 | Possible activation of nametab for & |
353 | Table & not found in ABAP Dictionary during activation |
354 | SQL error & occurred at location & (object &) - IGNORED |
355 | Commands: |
356 | executed (&) |
357 | COMMIT due to long DDL execution ( & ) |
358 | Handle this error message after the upgrade |
359 | & total time = & |
360 | Begin: Activation of shadow nametabs with DDL (&) |
361 | & shadow nametabs activated; DDL executed |
362 | & shadow nametab activations resulted in errors |
363 | End: Activation of shadow nametabs with DDL (&) |
364 | Begin: Activation of shadow nametabs (&) |
365 | & shadow nametabs activated |
366 | End: Activation of shadow nametabs (&) |
367 | Start: Activation of shadow nametabs (deletions) with DDL (&) |
368 | & shadow nametabs deleted; DDL executed |
369 | Deletion of & shadow nametabs resulted in errors |
370 | End: Activation of shadow nametabs (deletions) with DDL (&) |
371 | Error & in db_syflush - end activation of & |
372 | SQL trace not activated |
373 | SQL trace not deactivated |
374 | Return code &: SQL error & for object & - handling possible later |
375 | & is being processed by another process |
376 | & shadow name tabs processed by another process |
377 | Delete shadow nametab & |
378 | Successful, DDL executed |
379 | Activating shadow nametab & |
380 | Successful |
381 | Error when activating shadow nametabs |
382 | Termination of activation of shadow nametabs |
399 | & & & & (dummy, do not translate) |
400 | @@@ Messages 400-599 for ADO exporter/importer @@@ |
401 | --- Transport messages for self-defined transport objects (400 - 599) --- |
403 | Date and time: & - & |
404 | System : & |
405 | Release: & User: & Date: & Time: & |
412 | & & (program with screens and CUA) |
413 | & & (functions group) |
414 | & & (function module) |
415 | & & (work area messages) |
416 | & & (single message) |
417 | & & (transaction) |
418 | & & (dialog module) |
419 | & & (SAP table) |
420 | & & (domain) |
421 | & & (data element) |
422 | & & (SQL table) |
423 | & & (application class) |
424 | & & (parameter ID) |
428 | & & (CUA definition) |
429 | & & (command file) |
430 | & & (documentation) |
431 | Summary: |
434 | Number of errors : & |
435 | Number of warnings: & |
436 | Date and time: & - & |
437 | Command file & does not exist |
438 | Function group & does not exist |
439 | Function module & does not exist |
440 | FUNCT for & |
441 | Messages of application area & do not exist |
442 | Header of message application area & exported |
443 | Single message & & exported |
444 | Single message & does not exist |
445 | Transaction & does not exist |
446 | Dialog module & does not exist |
447 | Application class & does not exist |
448 | Parameter ID & does not exist |
449 | Table & does not exist |
450 | Domain & does not exist |
451 | Data element & does not exist |
452 | SQL table & does not exist |
453 | Transport ABAP/4 program source & with SAPLIMU |
454 | ABAP source & does not exist |
455 | & & (ABAP/4 program source) |
456 | Transport screen source & with SAPLIMU |
457 | Screen & does not exist |
458 | & & (screen) |
459 | Transport CUA definition & with SAPLIMU |
460 | CUA definition & does not exist |
461 | & & (CUA definition) |
462 | Docu & & does not exist |
463 | Docu & & exported |
469 | & Release error: & |
470 | CUA transport no longer possible, CUA & not transported |
474 | Objects already imported and will be overwritten |
497 | No data file for request &1 or file cannot be read |
499 | ########################################## |
500 | ADO import: Transport header does not exist |
501 | Version of export program: & |
502 | Version of import program: & |
503 | Character set not converted |
504 | Restrict to object type: & |
505 | Transport format invalid |
506 | Delivery from & |
507 | Target system & is incorrect |
508 | Data file: & |
509 | Import objects |
510 | Transport format error (error number &) |
512 | & & & already imported |
513 | Object list does not contain ADO objects -> ADO import not started |
514 | & & & not deleted, since it does not exist |
515 | Function "D" not possible, & & & not imported |
516 | Invalid function 'I', & & & not imported |
517 | Start of import & & & ... |
518 | End of import & & & |
519 | & & & components not imported (see above) |
520 | & & & nametab does not match |
521 | & & & error when saving (see above) |
522 | & & & error & in IMPOBJECT |
523 | Interface check |
524 | & & & interface does not exist |
525 | Object type minimum/average/maximum (sec): & & & & |
526 | & & & is not imported, since object type invalid |
527 | & & & not in request |
528 | & & & original object not overwritten |
529 | & & & object is being repaired, not overwritten |
530 | & package does not exist |
531 | & & package different for & & |
532 | & & & original object will be overwritten due to umode 2 |
533 | & & & not overwritten in consolidation system |
534 | & nametab not found |
535 | Documentation & error when saving |
536 | Documentation & & saved |
537 | Unknown object type & |
538 | Object import program & does not observe read restrictions |
539 | Transport format error |
540 | Command file & error when saving & |
541 | Command file & saved |
542 | Dynpro & & error when saving |
543 | Dynpro & & was saved |
544 | CUA definition & error when saving |
545 | CUA definition & saved |
546 | Documentation & & error when saving |
547 | Documentation & & saved |
548 | & & not imported |
549 | Cannot delete CUA definition |
550 | Cannot delete function groups |
551 | Cannot delete function modules |
552 | Deletion of ABAP Dictionary objects with mass activator |
553 | Transport format error |
554 | Function module & belongs to function group & |
555 | & not saved, since it is already being processed |
556 | & not saved: Authorization missing |
557 | & not saved: ABAP Dictionary error number: & |
558 | & saved |
559 | & & & not saved |
560 | ABAP program source code & not saved |
561 | ABAP program source code & saved |
562 | Message & not saved |
563 | Message & saved |
564 | & nametab does not exist in target system |
565 | & nametab different in target and source systems |
566 | Cannot read past end of object |
567 | Target system incorrect |
568 | &1, &2, &3 not imported, object list not sorted |
599 | ######################################### |
600 | &1 &2 &3 &4 |
601 | tp command &1 not supported |
602 | tp command &1 unknown |
603 | Parameter &1 missing |
604 | Parameter &1 incorrect |
605 | Could not determine TPPARAM path |
606 | RFC destination &1 incorrect |
607 | User &3 has no authorization for tp command &1 |
608 | Could not start transport control program tp |
609 | Status entry in TPSTAT failed |
610 | Log entry in TPLOG failed |
611 | tp call failed: &1 &2 &3 &4 |
618 | Transport profile not up-to-date |
619 | Transport profile not managed by Transport Management System |
620 | No authorization to delete log entries from table &1 |
650 | Could not read profile parameter &1 (transport directory) |
651 | Could not create directory path from &1 and &2 |
652 | Could not determine name of &1 file for transport request &2 |
653 | Transport buffer does not contain any entries |
654 | Errors detected when checking transport files |
680 | No authorization to read file &1 |
681 | No write authorization for file &1 (&2) |
682 | File &1 could not be opened for reading (&2) |
683 | File &1 could not be opened for writing (&2) |
684 | File &1 empty |
685 | File &1 has invalid format (&2 > &3) |
686 | Table TPPARAMS empty |
687 | Table TPPROFIL empty |
690 | Could not determine tp profile parameter &1 |
701 | Invalid start date |
702 | No log entries in selection |
703 | tp ALOG read error |
704 | Unknown log file type |
705 | File &1 contains non-analyzable data in line &2: '&3' |
750 | Ended with return code: & |
908 | & & & & |