RMPS_TRF - Message for transfer run time
The following messages are stored in message class RMPS_TRF: Message for transfer run time.
It is part of development package RMPS_DOD_TRF_RUNTIME in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "DoD Transfer Run Time".
It is part of development package RMPS_DOD_TRF_RUNTIME in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "DoD Transfer Run Time".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 100 | Export run has been created |
| 101 | Export run already exists |
| 102 | Export run does not exist |
| 103 | Item has been added successfully |
| 104 | Item already in export run |
| 105 | Element has been removed succesfully |
| 106 | Element could not be removed |
| 107 | &1 |
| 110 | Enter the name of an export stack |
| 111 | Export stack not found |
| 112 | Export stack already exists |
| 113 | Export stack not specified |
| 114 | Method '&1' called with wrong parameters |
| 115 | Public Sector Records Management Export Workbench: Severe Internal Error |
| 116 | Export stack &1 has been deleted for configuration &2 |
| 117 | Element type &1 is not supported by the PSRM transfer workbench |
| 118 | Entity &1 has already been transported successfully |
| 119 | No element with POID '&1' found in the buffer for export stack '&2' |
| 120 | Element '&1' cannot be displayed |
| 121 | An element with POID &1 is already part of the export stack '&2' |
| 122 | Export stack &1 cannot contain any of the following characters: &2 |
| 123 | External entity &1 cannot contain any of the following characters: &2 |
| 124 | Classification &1 cannot contain any of the following characters: &2 |
| 125 | Requesting write lock failed |
| 126 | Export stack &1 is edited by user &2 |
| 127 | Designtime configuration &1 is being edited by user &2 |
| 151 | Import stack not found |
| 152 | Import stack already exists |
| 158 | The configuration ID has been changed |
| 159 | No file with ID '&1' is available in the buffer for import stack '&2' |
| 160 | Successfully imported XML files cannot be removed from the import stack |
| 163 | Import stack not specified |
| 164 | Method '&1' called with wrong parameters |
| 167 | |
| 170 | Enter the name of an import stack |
| 171 | Import stack '&2' already contains an element with FILE_NAME &1 |
| 174 | Error while fetching model poid for sps &1 |
| 176 | Import stack &1 is being edited by user &2 |
| 177 | Import stack &1 has been deleted for configuration &2 |
| 180 | Import stack &1 does not contain any elements |
| 200 | Import run has been created successfully |
| 201 | Import run already exists |
| 202 | This POID is not a container |
| 203 | File is already in import list |
| 204 | Creation of spreadsheet failed |
| 220 | Send date could not be defined |
| 221 | Error while creating sender address for &1 |
| 222 | Sender address of email could not be assigned |
| 223 | Error while creating recipient adress for &1 |
| 224 | Recipient address of email could not be assigned |
| 225 | Unable to determine document format for this RMS ID: &1 |
| 226 | Following attribute is rejected: &1 |
| 227 | POID determination failed |
| 228 | Document type not defined for the following RMS ID: &1 |
| 229 | Incoming post item could not be created |
| 230 | Subject could not be defined |
| 231 | Attribute &1 has an invalid value: &2 |
| 232 | |
| 233 | Unable to create paper document |
| 300 | Start export |
| 301 | Export trial started at &3 for entity '&1', type '&2' |
| 302 | Export failed at &3 for entity '&1', type '&2' |
| 303 | Entity '&1' of type '&2' exported successfully at &3 |
| 399 | End export |
| 400 | Start import |
| 401 | Property '&1' cannot be imported. Value is '&2' |
| 402 | Property '&1' does not exist for case type '&2' |
| 403 | Case type must not be initial |
| 404 | Case type '&1' does not exist |
| 405 | Case type '&1' is obsolete |
| 406 | RMS ID must not be initial |
| 407 | RMS ID '&1' does not exist |
| 408 | Element type must not be initial |
| 409 | Element type '&1' does not exist |
| 410 | Property '&1' does not exist for element type '&2' |
| 411 | File name is missing |
| 412 | Content of file '&1' is missing |
| 413 | Content of file with missing file name is missing |
| 414 | MIME type is missing and cannot be derived from file name |
| 415 | Input file size was '&1'. New file size is '&2' |
| 416 | Start validation of properties |
| 417 | End validation of properties |
| 418 | Validating property '&1' |
| 419 | Data loss for property '&1'. Original value was '&2' |
| 420 | Value '&1' is not valid for property '&2' |
| 421 | Validating value for property '&1' |
| 422 | Value '&1' has not been validated for property '&2' |
| 423 | Value '&1' is valid for property '&2' |
| 424 | RMS ID '&1' is not valid for element type '&2' |
| 425 | Unexpected error |
| 426 | Start simulation of import |
| 427 | End simulation of import |
| 428 | Import aborted |
| 429 | Configuration &1 does not contain a transfer for XML element &2 |
| 430 | No ST template found for configuration &1 transfering &2 to &3 |
| 431 | Error in class &1: POID is not bound |
| 432 | Error in class &1: POID is not of state Instance |
| 433 | External ID is initial |
| 434 | Object was already imported with XML file &1 |
| 435 | Configuration &1 does not contain a transfer for internal entity &2 |
| 436 | XML root element could not be determined |
| 437 | Internal entity for XML root element &1 could not be determined |
| 438 | Customizing error |
| 497 | Import completed successfully |
| 498 | Import failed |
| 499 | End import |
| 500 | Start creating hierarchy |
| 501 | Hierarchy created successfully |
| 502 | Hierarchy creation failed |
| 503 | Start creating relation |
| 504 | Relation created successfully |
| 505 | Relation creation failed |
| 506 | Object has already been reloaded in the system |
| 600 | Creating XML stream reader failed |
| 601 | Root element length exceeds "external entity" length |
| 602 | XML stream reader error: &1 |