RMPS_GENERAL - Allg. Nachrichtenklasse Records Management for Public Sector
The following messages are stored in message class RMPS_GENERAL: Allg. Nachrichtenklasse Records Management for Public Sector.
It is part of development package RMPS_GENERAL in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "General Package for Records Management for Public Sector".
It is part of development package RMPS_GENERAL in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "General Package for Records Management for Public Sector".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | Storage period &1 does not exist in the storage catalog |
| 002 | Internal error (access to DDIC) |
| 003 | Internal error; provider status &1 unknown |
| 004 | Enter a unique description for the storage period |
| 005 | Enter a unique description for the storage location |
| 006 | Print (attributes and contents) |
| 007 | Reassign |
| 008 | &1&2 &3&4 not found |
| 009 | Element list |
| 010 | Display location of contents |
| 011 | Location list |
| 012 | Send as Mail |
| 013 | Display record elements chronologically |
| 014 | Print standard letter |
| 015 | Error when printing bar code; contact technical support |
| 016 | Bar code printed successfully |
| 017 | Create letter of reply |
| 018 | Change Attributes |
| 019 | Display Attributes |
| 020 | ***** Messages 20 - 30 reserved for links **** |
| 021 | Reflexive links cannot be created |
| 022 | Link cannot be created, it already exists |
| 024 | Display of &1 &2 was started in an external mode |
| 025 | Display of &1 &2 failed (&3) |
| 026 | Move |
| 030 | E-mail address of user &1 unknown |
| 031 | Select at least one document (temporary objects) in the list |
| 032 | Storage item & could not be deleted (note following message) |
| 033 | No authorization for deleting storage items in RMS ID & |
| 034 | Key date for deleting temporary items could not be determined |
| 035 | Sign |
| 036 | Check signature |
| 037 | Customizing: Element type for signed doc not defined or incorrect |
| 038 | Document not signed digitally yet |
| 039 | Digital signature for & checked successfully |
| 040 | Printing not possible; no addressee found for standard letter |
| 041 | Standard letter printed successfully |
| 042 | Error during printing: &1; check the standard Windows printer |
| 043 | Verification of digital signature for & still open |
| 050 | Major system error; contact technical support |
| 051 | Object not saved; save the object first |
| 061 | You do not have authorization for &1 |
| 062 | Residence time not saved in customizing for RMS ID &1 |
| 071 | A letter of reply can only be created from a record or case |
| 072 | Record/case does not contain any incoming post items to be answered |
| 080 | Temporay objects deleted successfully |
| 090 | Output "&1" (&2) for object type &3 classified as general |
| 091 | Output "&1" (&2) for object type &3 already classified as general |
| 092 | Output "&1" (&2) for object type &3 classified as general failed |
| 093 | Linkage output &1 with event &2(object type &3) activated successfully |
| 094 | Error in linkage task &1 with event &2 (object type &3) |
| 095 | No log entries can be written |
| 100 | Record already opened for changes; activity cannot be carried out |
| 101 | Save attribute changes |
| 102 | Reject attribute changes |
| 103 | Reset Inherited Attributes |
| 104 | Table name &1 exceeds maximum name length (15 characters) |
| 105 | Table &1 already exists |
| 106 | Table &1 created for attribute &2 |
| 107 | Data element &1 does not exist |
| 108 | Error when writing table &1 to transport request |
| 109 | Error when writing table &1 for attribute &2 |
| 110 | Display Signature History |
| 111 | Display Verification Result |
| 112 | Select an entry for the log display |
| 113 | Check log cannot be read |
| 114 | No check log exists |
| 115 | Certificate was withdrawn |
| 116 | OCSP responder not available; execute verification again |
| 117 | OCSP request rejected; inform your administrator |
| 118 | Certificate unknown |
| 119 | OCSP Verification: Check log cannot be read |
| 120 | Check log cannot be displayed - signature invalid (CRC= &1 RESULT = &2) |
| 121 | Table type &1 already exists |
| 122 | Error occurred when creating table type &1 for attribute &2 |
| 123 | Table type &1 was created for attribute &2 |
| 124 | Error occurred when creating table type &1 in the transport request |
| 140 | Customizing: There is more than one element type for the key words |
| 150 | Cannot insert this element (&1) in element type &2 |
| 200 | No transport request specified (only optional when simulated) |
| 201 | Start log for conversion of table SCMGPARAM to SRM_PARA_PROFILE |
| 202 | Table was already converted |
| 203 | Start conversion process |
| 204 | Read mapping table |
| 205 | Mapping table could not be read |
| 206 | Read source data from SCMGPARAM |
| 207 | Table SCMGPARAM could not be read |
| 208 | Write data in SRM_PARA_PROFILE |
| 209 | No entry exists for &1 in the mapping table |
| 210 | Write transport entry |
| 211 | Set parameter 'USE_SCMGPARAM' to <FALSE> |
| 212 | Conversion not successful, all database changes reversed |
| 213 | Conversion completed successfully |
| 214 | Exception rc=&1 for transport interface (see longtext) |
| 215 | Transport entry successfully written (&1) |
| 216 | Compare with data in client 000 |
| 217 | Different value for &1 in client 000: &2 (&3) - &4 (000) |
| 218 | Different value for &1 in client 000: &2 (&3) - &4 (000) |
| 219 | Entry for ID = &1 missing in SCMGPARAM |
| 220 | Conversion of ID &1 to &3/&4 for value &2 |
| 221 | No conversion for ID = &1 needed since value &2 for &3\&4 already there |
| 240 | This application object is already assigned to a mode |
| 241 | Document already exists |
| 242 | Document does not exist |
| 243 | Document status is incorrect |
| 244 | Could not update document status |
| 245 | Incorrect document status; no deletion possible |
| 246 | Documents still exist; cannot delete mode |
| 247 | Session does not exist |
| 248 | Could not delete mode |
| 249 | No documents exist for this mode |
| 250 | Could not find scenario |
| 251 | Business object does not exist |
| 252 | Remote system does not exist |
| 253 | History already exists |
| 254 | Cannot refresh history |
| 255 | Error when saving data element &1 in request |
| 256 | Only values 1, 2, 3, 4, or 9 valid for log level |
| 257 | Data has been saved |
| 258 | Select a line |
| 259 | Logging for element type &1 is inactive; activation not possible |
| 300 | PHIO parameter error |
| 301 | Internal PHIO error |
| 302 | Other PHIO error |
| 303 | LOIO parameter error |
| 304 | Internal LOIO error |
| 305 | Other LOIO error |
| 400 | Structure &1 does not exist yet and will be created |
| 401 | Component &1 of structure &2 must start with prefix ZZ |
| 402 | Data element &1 not defined for attribute &2 |
| 403 | Error when writing structure &1 |
| 404 | Enter a data element as a data reference for attribute &1 |
| 405 | Enter an attribute description for attribute &1 |
| 406 | Enter an attribute |
| 407 | No search help is available for the "Create Attribute" function |
| 408 | Attribute name must start with ZZ |
| 409 | Attributes for documents and classes must start with Y or Z |
| 410 | Attribute name &1 is invalid since it contains blanks |
| 411 | Attribute name &1 exceeds maximum length of &2 characters |
| 412 | Case type &1 does not exist |
| 413 | Could not derive table for RMS ID &1 |
| 414 | Attribute &1 already exists |
| 415 | Attribute &1 does not exist |
| 416 | Attribute &1 does not exist or is not part of customer include &2 |
| 417 | Attribute name must start with Z or Y |
| 418 | Data element &1 is not active |
| 419 | Package &1 is an SAP package |
| 420 | Package &1 does not exist |
| 421 | Use the F4 help to select a data element for structure &1 |
| 422 | Entry &1 deleted from table &3 for attribute &2 |
| 423 | No attribute properties exist for attribute &1 |
| 424 | Terminology ID &1 deleted from table &3 for attribute &2 |
| 425 | Terminology ID &1 does not exist in table &3 for attribute &2 |
| 426 | Attribute properties for attribute &1 deleted from table &2 |
| 427 | Texts for terminology profile &1 deleted from table &3 for attribute &2 |
| 428 | Terminology profile &1 does not exist in table &3 for attribute &2 |
| 429 | Terminology ID &1 created in table &3 for attribute &2 |
| 430 | Error when creating terminology ID &1 for attribute &2 in table &3 |
| 431 | Terminology ID &1 added to terminology profile &2 in table &3 |
| 432 | Error when adding terminology ID &2 to terminology profile &1 in table &3 |
| 433 | Error when converting table &1 |
| 434 | Table &1 converted successfully |
| 435 | Attribute &1 already assigned to profile &2 in table &3 |
| 436 | Attribute &1 assigned to profile &2 in table &3 |
| 437 | Error when assigning attribute &1 to profile &2 in table &3 |
| 438 | Attribute &1 deleted from profile &2 in table &3 |
| 439 | Attribute &1 not assigned to profile &2 in table &3 |
| 440 | Technical error; structure &1 does not exist and cannot be changed |
| 441 | Table/structure &1 created/changed |
| 442 | Table/structure &1 activated |
| 443 | Enter a package |
| 444 | Cannot assign attribute &1 to class &2 |
| 445 | No attribute profile exists for case type &1 |
| 446 | No terminology profile exists for case type &1 |
| 447 | Error when deleting structure &1 |
| 448 | Attribute name &1 changed for attribute &2 |
| 449 | Enter a name for attribute &1 |
| 450 | Virtual PHIO class is initial |
| 451 | LOIO cannot be derived uniquely from disposal document type |
| 452 | Data element &1 for attribute &2 already exists |
| 453 | Data element &1 created for attribute &2 |
| 454 | Data element &1 activated for attribute &2 |
| 455 | Data element &1 not created for attribute &2 |
| 456 | Data element &1 not activated for attribute &2 |
| 457 | Data element &1 does not exist in active version |
| 458 | Error when activating table/structure and &1 |
| 459 | Error when activating structure &1; check activation log |
| 460 | Error occurred activating table type &1 |
| 461 | Table type &1 was activated |
| 462 | Paper document successfully imported |
| 463 | Electronic document successfully imported |
| 500 | Target RMS ID &1 already exists |
| 501 | Source RMS ID &1 does not exist |
| 502 | &1 &2 is not found in a valid namespace |
| 503 | Determination of system data failed |
| 504 | Action is not allowed in the production system |
| 505 | System settings do not allow &1 to be changed |
| 506 | &1 &2 already exists |
| 507 | Creation of RMS ID &1 failed |
| 508 | Creation of &1 &2 failed |
| 509 | Reading data for &1 &2 failed |
| 510 | Record model content copied from &1 to &2 |
| 511 | Creation of transport request &1 / &2 failed |
| 512 | Termination by user (action &1) |
| 513 | &1 failed |
| 514 | &1 &2 created successfully |
| 515 | &1 does not exist |
| 516 | Error occurred when creating &1. No &1 was saved |
| 517 | Caution: &1 have already been created and must be deleted manually |
| 518 | Record model &1 could not be copied |
| 519 | Reading of source record model &1 failed. A blank copy will be created |
| 520 | Reading record model content &1 failed. A blank copy will be created |
| 521 | Unable to create record model &1 |
| 522 | Record model &1 inserted in &2 &3 |
| 523 | Record model &1 (&2) created with initial values |
| 524 | Creation of record model failed. Placeholder &1 used! |
| 525 | Customizing entry written for &1 &2 in table &3 |
| 526 | Customizing entry for &1 &2 in table &3 not possible |
| 527 | Transport request &1 &2 created |
| 528 | All checks successful. Objects can be created |
| 529 | Virtual PHIO class not found |