1R - SAP Knowledge Provider
The following messages are stored in message class 1R: SAP Knowledge Provider.
It is part of development package SDOK in software component BC-SRV-KPR-DMS. This development package consists of objects that can be grouped under "SAP Knowledge Provider".
It is part of development package SDOK in software component BC-SRV-KPR-DMS. This development package consists of objects that can be grouped under "SAP Knowledge Provider".
Message Nr ▲ | Message Text |
---|---|
000 | Test message: & & & & |
001 | No browser call is supported for your frontend |
002 | The document is locked by user &1 |
003 | Error in calling web browser on your frontend |
004 | Front-end functions cannot be executed in the background |
005 | Successfully deleted |
006 | Error while deleting the PHIO |
007 | Indexing successful |
008 | Error while indexing the PHIO |
009 | Deindexing successful |
010 | Error while deindexing the PHIO |
011 | Office Integration for Java-GUI is not supported |
012 | Source archive &1 ARC_DOC_ID &2: copy is OK |
013 | Deletion is not allowed as hold flag is initial. |
014 | Deletion is not allowed as expiration date was reached for the document. |
015 | Deletion is not allowed |
016 | Failed to reset attributes at KPro level. |
017 | Failed to set attributes at KPro level. |
020 | &1 is not permitted as a derived category since it is a logical category |
021 | &1 is not permitted as a logical category since it is a derived caregory |
022 | Category &1 can only be derived from a logical category |
023 | Repository &1 has document area &2 |
024 | Repository &1 has no document area |
050 | PHIO_ID list is empty |
051 | There are &1 documents without administrative data on the content server |
052 | There are no documents without administrative data on the content server |
053 | Removed |
054 | &1 documents removed from the content server |
055 | There are &1 documents with inconsistent details |
056 | All document details are consistent |
057 | The hit list for selecting repositories is empty |
058 | Error while determining document classes |
059 | Error while finding attributes of document class &1 |
060 | Error in the search |
061 | No document space can be determined for connection area &1 |
062 | Full text search availability for document space &1 cannot be determined |
100 | The removal was not successful; the new link is not possible |
101 | The copying did not work |
200 | --- Messages for connection to translation system (log and interface) --- |
201 | System could not retrieve component information |
202 | System could not retrieve current directory |
203 | Error when calling front-end services |
204 | System could not retrieve file list for a directory |
205 | File system will not allow file to deleted |
206 | System cannot delete a file |
207 | File system will not allow directory to be deleted |
208 | System could not delete a directory |
209 | System could not create a directory |
210 | File system refused access to a directory |
211 | System cannot start the application for file extension &2 |
212 | System cannot find the application for file extension &2 |
213 | Error occurred when calculating document class for a document |
214 | Error when calculating description texts for a document |
215 | Error when writing description texts for a document |
216 | The document is not for translation |
251 | Update mode cannot be changed |
300 | --- Messages for reports --- |
301 | No standard content repository exists |
302 | Standard contents repository is not a file server |
303 | Enter FTP server password in both fields |
304 | Passwords entered do not match; try again |
305 | RFC destination & is currently locked |
306 | Entries made successfully |
307 | Do not enter a password for this selection |
308 | No server is maintained |
309 | The following file cannot be written: &1 |
310 | Enter source and target categories in pairs |
311 | Source and target categories link to different repositories |
312 | Transport requests do not contain documents on HTTP content servers |
313 | The location &1 does not exist |
314 | You have no authorization |
315 | Unexpected Error Number &1 in Module &2. Parameter1: &3 Parameter2: &4 |
316 | Choose a document |
317 | Table &1 field &2 points nonexistent table &4 for &3 |
318 | Table &1 field &2: initial value not allowed |
319 | Table &1 field &2: invalid characters (also contains empty characters) |
320 | Table &1 field &2: The first character must be a letter |
321 | Table &1 field &2: &3 for class &4 is not a valid value |
322 | Table &1 field &2: &3 for document area &4 is not a valid value |
323 | Table &1 field &2: &3 for attribute &4 does not exist |
324 | Table &1 field &2: initial value for class &3 not allowed |
325 | Table &1 field &2: &3 for category is not a valid value |
326 | Table &1 field &2: Repository &3 for category &4 does not exist |
327 | Table &1 field &2: document area &3 for category does not exist |
328 | Table &1 field &2: &3 contains invalid characters |
329 | Table &1 field &2: &3 does not begin with a letter or '/' |
330 | Table &1 field &2: &3 is not a valid value |
331 | Table &1 field &2: &3 is not a valid document area |
332 | Table &1 field &2: &3 is not an active table |
351 | RFC destination &1 does not exist |
352 | Client &1 does not exist |
353 | Specify a document area and/or document classes |
354 | Unchanged target security level |
355 | Invalid security level &1 |
356 | Specify a temporary repository as a temporary memory |
357 | Invalid temporary repository &1 |
358 | Action canceled by user |
359 | Specify a URL or document ID |
360 | Error while resolving URL &1 |
361 | Error while determining LOIOs for PHIO (&1, &2) |
362 | Error while reading the expiry time of the object (&1, &2) |
363 | Error while reading the indicator "individual expiry time" (&1, &2) |
364 | Error while determining the parent of the object (&1, &2) |
366 | Error while writing the expiry time of the object (&1, &2) |
367 | Error while determining the subnode of the object (&1, &2) |
371 | Error while determining the URL of the object (&1, &2) |
372 | No authorization to include this in a transport request |
373 | Error in the transport layer |
400 | --- Messages for transport log --- |
401 | &1 &2 &3 &4 |
402 | Begin processing for RFC destination &1 |
403 | End processing for RFC destination &1 |
404 | Transport file could not be deleted from file server |
405 | Transport file could not be copied to file server |
406 | Transport file successfully copied to file server |
407 | FTP connection to server &1 was set up |
408 | Error while creating FTP connection to server &1 |
409 | Error while executing FTP command |
410 | File directory in R/3 System: &1 |
411 | Directory on file server: &1 |
412 | File &1 copied to file server |
413 | Error while closing connection to file server |
414 | Connection to file server closed |
415 | Transport file deleted from file server again |
416 | Document &1 file &2 cannot be uncompressed |
417 | Directory &1 cannot be created on file server |
418 | Document &1 file &2: Not found in ZIP archive |
419 | Document &1 file &2: Unexpected error occurred |
420 | Transport file not found on file server |
421 | Insufficient disk space on file server |
422 | Problems occurred while uncompressing transport file |
423 | ZIP archive could not be opened |
424 | Fatal error while uncompressing transport file |
425 | Unexpected error while uncompressing transport file |
426 | Transport file successfully decompressed on file server |
427 | Transport file could not be decompressed on file server |
428 | Transport file name &1 has errors |
429 | No transport file name entered |
430 | Transport file name is too long |
431 | Directory name &1 is too long |
432 | File name &1 is too long |
433 | Unexpected error while splitting transport file name |
434 | Files successfully compressed in transport file |
435 | Problems while compressing transport file |
436 | ZIP archive could not be created |
437 | Fatal error while compressing transport file |
438 | Unexpected error while compressing transport file |
439 | Transport file not filled on file server |
440 | Transport file could not be retrieved from file server |
441 | Transport file successfully retrieved from file server |
442 | File &1 retrieved from file server |
443 | File &1 is not available |
444 | Error while compressing file &1 |
445 | Unexpected error. File &1 cannot be compressed. |
446 | No connection to RFC destination &1 |
447 | System termination on file server |
448 | Old transport file deleted from file server |
449 | No old transport files found on file server |
450 | Error while shutting down file server |
451 | RFC destination for file server could not be determined |
452 | File server transport function deactivated |
453 | File server transport function started |
454 | No subsequent handling required for transport |
455 | No transport preparation required |
456 | Start of processing for request &1, time &2 |
457 | Error when reading transport request &1 |
458 | Transport request &1 does not exist |
459 | No authorization to read transport request &1 |
460 | No suitable transport request of form &1 was found |
461 | Begin post-transport processing for order &1 |
462 | Table &1 does not exist. It is used by repository &2. |
463 | End of post-transport processing for order &1 |
464 | No program generation for database storage required |
465 | No program generation for remaining database repositories required |
466 | Program for database archives generated |
467 | Program for remaining database archives generated |
468 | Begin processing for repository &1, time &2 |
469 | Begin final cross-repository work, time &1 |
470 | End of processing for request &1, time &2 |
471 | Start of packing process for category &1, time &2 |
472 | End of packing process for category &1, time &2 |
473 | Archive file for category &1 was collected |
474 | Archive file for category &1 was deleted |
475 | Start of recovery for logically motivated categories |
476 | Inconsistenciees in the management data for document class &1 |
477 | Inconsistencies in the management data for document distribution |
478 | No recovery of logically motivated categories required |
479 | Missing documents when recovering categories |
480 | Table &1: Cateogry &3 of category &2 restored |
481 | Table &1: No restoring neceessary for category &2 |
482 | End of restoring for logically motivated categories |
483 | Category &1 does not exist |
484 | Storage category &1 of document &2 does not have type R3DB storage |
485 | Go to application processing, module &1, time &2 |
486 | Return from application processing, module &1, time &2 |
487 | Error in application processing, module &1 |
489 | System update in progress. Locking of objects started. |
490 | Object ID &1 is locked by pre-lock method. |
491 | Object ID &1 could not be locked. |
500 | --- Messages for Application Log Entries --- |
501 | & is not a valid class for information objects |
502 | & is not a valid class for logical documents |
503 | & is not a valid class for physical documents |
504 | & is not a valid class for relationship objects |
505 | & is not a valid class for structure objects |
506 | Partner for object (&, &) in relationship (&, &) is missing |
507 | Error during deletion of physical document (&, &) from cluster table & |
508 | Exit function & returns error & for object (&, &) |
509 | Content category & is unknown |
510 | Connection to FTP server & using RFC connection & failed |
511 | Error & for FTP command '&' |
512 | Error during import of physical document (&, &) from cluster table & |
513 | Error during export of physical document (&, &) from cluster table & |
514 | File & in cluster for physical document (&, &) not found |
515 | Error during upload of file & with length & |
516 | Error during download of file & |
517 | Error while writing (update) to database table & |
518 | Error while writing (insert) to database table & |
519 | Error during deletion from database table & |
520 | Deletion of physical document (&, &) is not allowed (status &, &) |
521 | Deletion of phys. document (&, &) not allowed due to relationship (&, &) |
522 | Check-out of physical document (&, &) is not allowed (status &, &) |
523 | Check-out release for physical document (&, &) not allowed (status &, &) |
524 | Physical document (&, &) may not be copied (status &, &) |
525 | Physical document (&, &) may not be reserved (status &, &) |
526 | Reservation release for phys. document (&, &) not allowed (status &, &) |
527 | Check-in for physical document (&, &) is not allowed (status &, &) |
528 | No directory specified for file transfer to physical document (&, &) |
529 | Class for log. documents & has invalaid PHIO partner class & |
530 | Phys. document (&, &) in status (&, &) not suitable as version template |
531 | Phys. document (&, &) with status (&, &) not suitable for use as template |
532 | Mandatory attribute & for objects in class & not entered |
533 | Attribute & not assigned for objects in class & |
534 | RFC destination & for transport controller cannot be determined |
535 | Internal error & occurred in function & |
536 | No physical document found for logical document & & |
537 | No file name entered for file transfer to physical document (&, &) |
538 | Document contents could not be deleted |
539 | Compression of book structure (&, &) failed |
540 | Uncompression of book structure (&, &) failed |
541 | Error while calling operation &4 for storage system &3 |
542 | Storage system &3 reports error while executing operation &4 |
543 | Unexpected error while writing to HTTP server |
544 | Error &1 while writing to HTTP server |
545 | Error &1 while reading from HTTP server |
546 | Unexpected error while reading from HTTP server |
547 | Error when generating a signature |
548 | Document forced out of shared memory |
549 | Document had to be regenerated, cause: &3 |
550 | Content repository &1 is accessed using the application server |
551 | File name is too long for upload/download |
552 | Content repository &1 does not exist |
553 | File was copied locally (path name too long) |
554 | Colliding alias names for document files |
555 | System error in RFC call of function module &1 |
556 | Communication error in RFC call of function module &1 |
557 | Content-Type &1 is not permitted |
558 | Document with status "protected" has no component information |
559 | Error indexing a document |
560 | Error determining category attributes for index space |
561 | Unknown index space for document class &1 |
562 | Error in deindexing |
563 | Error starting and registering RFC server &1 |
564 | Error stopping and deregistering an RFC server |
565 | No authorization to access physical information object |
566 | Error writing from R/3 System to an FTP server |
567 | Error reading from an FTP server to R/3 System |
568 | Language &1 is not supported by the current application server |
569 | Language (&1, &2) is not specified consistently |
570 | Language &1 is unknown in the system |
571 | Invalid file name &1 |
572 | Text line for planned text table too long |
573 | No document area free for web server assignment |
574 | Web Server &2 assigned to document area &1 |
575 | Unspecific exception when calling &1 |
576 | Error when uploading file & of length & using destination & |
577 | Error when downloading file & using destination & |
578 | Error determining component lengths |
579 | An error occurred when calling module &1 |
580 | Document &1 of class &2 is overwritten. New document ID &3. |
581 | No Header Table Can Be Determined for Relationship Class &1 |
582 | Document &1 of class &2 does not exist in client &3 |
583 | Error in TADIR access for object &1 &2 |
584 | No PHIO could be calculated for LOIO &1 &2 (error &3) |
585 | Error when getting translation for PHIO &1 &2 (error &3) |
586 | Error caught with dynamic SQL - check table |
587 | Update: Operation &1 is not supported for table type &2 |
588 | Program error: Flag &1 can only be set in the update process |
589 | Update: Operation &1 is not supported for indexing |
600 | --- Messages for Archiving Errors (LOIO) --- |
601 | Error while determining the properties for log. docu &1(&2) - &3 |
602 | Error while creating logical document &1(&2) - &3 |
603 | Error while deleting logical document &1(&2) - &3 |
620 | --- Messages for Archiving Errors (PHIO) --- |
621 | Error while determining properties for physical document &1(&2) - &3 |
622 | Error while creating physical document &1(&2) - &3 |
623 | Error when deleting physical documents &1(&2) - &3 |
640 | --- Messages for archiving errors (REIO) --- |
641 | Error when calculating properties for the relationship &1(&2) - &3 |
642 | Error when creating the relationship &1(&2) - &3 |
643 | Error when deleting the relationship &1(&2) - &3 |
644 | Error when reading the relationship &1(&2) - &3 |
660 | --- Messages for archiving errors (PHCO) --- |
661 | Error when reading content of the physical document &1(&2) - &3 |
662 | Error when writing the content of the physical document &1(&2) - &3 |
701 | Table & does not exist in ABAP Dictionary |
702 | No structure document can be determined for document &2 of class &1 |
703 | No fragmentation configuration for document &2 of class &1 |
800 | --- Messages for generated description texts --- |
801 | Content Repository for &1 |