| 1R420 |
Transport file not found on file server |
| 1R421 |
Insufficient disk space on file server |
| 1R422 |
Problems occurred while uncompressing transport file |
| 1R423 |
ZIP archive could not be opened |
| 1R424 |
Fatal error while uncompressing transport file |
| 1R425 |
Unexpected error while uncompressing transport file |
| 1R426 |
Transport file successfully decompressed on file server |
| 1R427 |
Transport file could not be decompressed on file server |
| 1R428 |
Transport file name &1 has errors |
| 1R429 |
No transport file name entered |
| 1R430 |
Transport file name is too long |
| 1R431 |
Directory name &1 is too long |
| 1R432 |
File name &1 is too long |
| 1R433 |
Unexpected error while splitting transport file name |
| 1R434 |
Files successfully compressed in transport file |
| 1R435 |
Problems while compressing transport file |
| 1R436 |
ZIP archive could not be created |
| 1R437 |
Fatal error while compressing transport file |
| 1R438 |
Unexpected error while compressing transport file |
| 1R439 |
Transport file not filled on file server |
| 1R440 |
Transport file could not be retrieved from file server |
| 1R441 |
Transport file successfully retrieved from file server |
| 1R442 |
File &1 retrieved from file server |
| 1R443 |
File &1 is not available |
| 1R444 |
Error while compressing file &1 |
| 1R445 |
Unexpected error. File &1 cannot be compressed. |
| 1R446 |
No connection to RFC destination &1 |
| 1R447 |
System termination on file server |
| 1R448 |
Old transport file deleted from file server |
| 1R449 |
No old transport files found on file server |
| 1R450 |
Error while shutting down file server |
| 1R451 |
RFC destination for file server could not be determined |
| 1R452 |
File server transport function deactivated |
| 1R453 |
File server transport function started |
| 1R454 |
No subsequent handling required for transport |
| 1R455 |
No transport preparation required |
| 1R456 |
Start of processing for request &1, time &2 |
| 1R457 |
Error when reading transport request &1 |
| 1R458 |
Transport request &1 does not exist |
| 1R459 |
No authorization to read transport request &1 |
| 1R460 |
No suitable transport request of form &1 was found |
| 1R461 |
Begin post-transport processing for order &1 |
| 1R462 |
Table &1 for document contents does not exist |
| 1R463 |
End of post-transport processing for order &1 |
| 1R464 |
No program generation for database storage required |
| 1R465 |
No program generation for remaining database repositories required |
| 1R466 |
Program for database archives generated |
| 1R467 |
Program for remaining database archives generated |
| 1R468 |
Begin processing for repository &1, time &2 |
| 1R469 |
Begin final cross-repository work, time &1 |
| 1R470 |
End of processing for request &1, time &2 |
| 1R471 |
Start of packing process for category &1, time &2 |
| 1R472 |
End of packing process for category &1, time &2 |
| 1R473 |
Archive file for category &1 was collected |
| 1R474 |
Archive file for category &1 was deleted |
| 1R475 |
Start of recovery for logically motivated categories |
| 1R476 |
Inconsistenciees in the management data for document class &1 |
| 1R477 |
Inconsistencies in the management data for document distribution |
| 1R478 |
No recovery of logically motivated categories required |
| 1R479 |
Missing documents when recovering categories |
| 1R480 |
Table &1: Cateogry &3 of category &2 restored |
| 1R481 |
Table &1: No restoring neceessary for category &2 |
| 1R482 |
End of restoring for logically motivated categories |
| 1R483 |
Category &1 does not exist |
| 1R484 |
Storage category &1 of document &2 does not have type R3DB storage |
| 1R485 |
Go to application processing, module &1, time &2 |
| 1R486 |
Return from application processing, module &1, time &2 |
| 1R487 |
Error in application processing, module &1 |
| 1R500 |
--- Messages for Application Log Entries --- |
| 1R501 |
& is not a valid class for information objects |
| 1R502 |
& is not a valid class for logical documents |
| 1R503 |
& is not a valid class for physical documents |
| 1R504 |
& is not a valid class for relationship objects |
| 1R505 |
& is not a valid class for structure objects |
| 1R506 |
Partner for object (&, &) in relationship (&, &) is missing |
| 1R507 |
Error during deletion of physical document (&, &) from cluster table & |
| 1R508 |
Exit function & returns error & for object (&, &) |
| 1R509 |
Content category & is unknown |
| 1R510 |
Link initiation to FTP server & via RFC connection & failed |
| 1R511 |
Error & for FTP command '&' |
| 1R512 |
Error during import of physical document (&, &) from cluster table & |
| 1R513 |
Error during export of physical document (&, &) from cluster table & |
| 1R514 |
File & in cluster for physical document (&, &) not found |
| 1R515 |
Error during upload of file & with length & |
| 1R516 |
Error during download of file & |
| 1R517 |
Error while writing (update) to database table & |
| 1R518 |
Error while writing (insert) to database table & |
| 1R519 |
Error during deletion from database table & |
| 1R520 |
Deletion of physical document (&, &) is not allowed (status &, &) |
| 1R521 |
Deletion of phys. document (&, &) not allowed due to relationship (&, &) |
| 1R522 |
Check-out of physical document (&, &) is not allowed (status &, &) |
| 1R523 |
Check-out release for phys. document (&, &) not alllowed (status &, &) |
| 1R524 |
Physical document (&, &) may not be copied (status &, &) |
| 1R525 |
Physical document (&, &) may not be reserved (status &, &) |
| 1R526 |
Reservation release for phys. document (&, &) not allowed (status &, &) |
| 1R527 |
Check-in for physical document (&, &) is not allowed (status &, &) |
| 1R528 |
No directory specified for file transfer to physical document (&, &) |
| 1R529 |
Class for log. documents & has invalaid PHIO partner class & |
| 1R530 |
Phys. document (&, &) in status (&, &) not suitable as version template |
| 1R531 |
Phys. document (&, &) with status (&, &) not suitable for use as template |