| 1R532 |
Mandatory attribute & for objects in class & not entered |
| 1R533 |
Attribute & not assigned for objects in class & |
| 1R534 |
RFC destination & for transport controller cannot be determined |
| 1R535 |
Internal error & occurred in function & |
| 1R536 |
No physical document found for logical document & & |
| 1R537 |
No file name entered for file transfer to physical document (&, &) |
| 1R538 |
Document contents could not be deleted |
| 1R539 |
Compression of book structure (&, &) failed |
| 1R540 |
Uncompression of book structure (&, &) failed |
| 1R541 |
Error while calling operation &4 for storage system &3 |
| 1R542 |
Storage system &3 reports error while executing operation &4 |
| 1R543 |
Unexpected error while writing to HTTP server |
| 1R544 |
Error &1 while writing to HTTP server |
| 1R545 |
Error &1 while reading from HTTP server |
| 1R546 |
Unexpected error while reading from HTTP server |
| 1R547 |
Error when generating a signature |
| 1R548 |
Document forced out of shared memory |
| 1R549 |
Document had to be regenerated, cause: &3 |
| 1R550 |
Access to content repository &1 via application server |
| 1R551 |
File name is too long for upload/download |
| 1R552 |
Content repository &1 does not exist |
| 1R553 |
File was copied locally (path name too long) |
| 1R554 |
Colliding alias names for document files |
| 1R555 |
System error in RFC call of function module &1 |
| 1R556 |
Communication error in RFC call of function module &1 |
| 1R557 |
Content-Type &1 is not permitted |
| 1R558 |
Document with status "protected" has no component information |
| 1R559 |
Error indexing a document |
| 1R560 |
Error determining category attributes for index space |
| 1R561 |
Unknown index space for document class &1 |
| 1R562 |
Error in deindexing |
| 1R563 |
Error starting and registering RFC server &1 |
| 1R564 |
Error stopping and deregistering an RFC server |
| 1R565 |
No authorization to access physical information object |
| 1R566 |
Error writing from R/3 System to an FTP server |
| 1R567 |
Error reading from an FTP server to R/3 System |
| 1R568 |
Language &1 is not supported by the current application server |
| 1R569 |
Language (&1, &2) is not specified consistently |
| 1R570 |
Language &1 is unknown in the system |
| 1R571 |
Invalid file name &1 |
| 1R572 |
Text line for planned text table too long |
| 1R573 |
No document area free for web server assignment |
| 1R574 |
Web Server &2 assigned to document area &1 |
| 1R575 |
Unspecific exception when calling &1 |
| 1R576 |
Error uploading file & of length & via destination & |
| 1R577 |
Error downloading file & via destination & |
| 1R578 |
Error determining component lengths |
| 1R579 |
An error occurred when calling module &1 |
| 1R580 |
Document &1 of class &2 is overwritten. New document ID &3. |
| 1R581 |
No Header Table Can Be Determined for Relationship Class &1 |
| 1R582 |
Document &1 of class &2 does not exist in client &3 |
| 1R583 |
Error in TADIR access for object &1 &2 |
| 1R584 |
No PHIO could be calculated for LOIO &1 &2 (error &3) |
| 1R585 |
Error when getting translation for PHIO &1 &2 (error &3) |
| 1R586 |
Error caught with dynamic SQL - check table |
| 1R587 |
Update: Operation &1 is not supported for table type &2 |
| 1R588 |
Program error: Flag &1 can only be set in the update process |
| 1R589 |
Update: Operation &1 is not supported for indexing |
| 1R600 |
--- Messages for Archiving Errors (LOIO) --- |
| 1R601 |
Error while determining the properties for log. docu &1(&2) - &3 |
| 1R602 |
Error while creating logical document &1(&2) - &3 |
| 1R603 |
Error while deleting logical document &1(&2) - &3 |
| 1R620 |
--- Messages for Archiving Errors (PHIO) --- |
| 1R621 |
Error while determining properties for physical document &1(&2) - &3 |
| 1R622 |
Error while creating physical document &1(&2) - &3 |
| 1R623 |
Error when deleting physical documents &1(&2) - &3 |
| 1R640 |
--- Messages for archiving errors (REIO) --- |
| 1R641 |
Error when calculating properties for the relationship &1(&2) - &3 |
| 1R642 |
Error when creating the relationship &1(&2) - &3 |
| 1R643 |
Error when deleting the relationship &1(&2) - &3 |
| 1R644 |
Error when reading the relationship &1(&2) - &3 |
| 1R660 |
--- Messages for archiving errors (PHCO) --- |
| 1R661 |
Error when reading content of the physical document &1(&2) - &3 |
| 1R662 |
Error when writing the content of the physical document &1(&2) - &3 |
| 1R701 |
Table & does not exist in Data Dictionary |
| 1R702 |
No structure document can be determined for document &2 of class &1 |
| 1R703 |
No fragmentation configuration for document &2 of class &1 |
| 1R800 |
--- Messages for generated description texts --- |
| 1R801 |
Content Repository for &1 |
| 1S000 |
SSF operation successfully executed |
| 1S001 |
SSF error: Unable to find external security product |
| 1S002 |
SSF error: Invalid security format |
| 1S003 |
SSF error: No data transferred |
| 1S004 |
SSF error: insufficient SSF server main memory |
| 1S005 |
SSF error: Invalid signer |
| 1S006 |
SSF error: SSF server main memory insufficient for results |
| 1S007 |
SSF error: Address book unknown |
| 1S008 |
SSF error: Invalid password for address book |
| 1S009 |
SSF error: encryption failed |
| 1S010 |
SSF error: Invalid hash algorithm |
| 1S011 |
SSF error: Coding not possible |
| 1S012 |
SSF error: Decoding not possible |
| 1S013 |
SSF error: Unknown error in external security product |
| 1S014 |
SSF Error: Unknown error & |
| 1S015 |
SSF error: no valid license ticket for external security product |
| 1S016 |
SSF error: external security product does not support encryption |
| 1S017 |
SSF error: kernel update required |
| 1S020 |
Signer/recipient missing |
| 1S021 |
SSF information for SAP user &1 not found |
| 1S022 |
Canceled by User |