SWL_WP - Nachrichten f�r Workflow im Workplace
The following messages are stored in message class SWL_WP: Nachrichten f�r Workflow im Workplace.
It is part of development package SWLWP in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Workflow: Workplace Server Part".
It is part of development package SWLWP in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Workflow: Workplace Server Part".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Work item with ID & cannot be read |
| 001 | &1: Handler (&2,&3) has been updated successfully |
| 002 | &1: Error updating handler (type &2) |
| 003 | &1: Handler (type &2) has been deleted successfully |
| 004 | &1: Error deleting handler (type &2) |
| 005 | &1: Handler (type &2) has been created successfully |
| 006 | &1: Error creating handler (type &2) |
| 007 | &1: Handler (type &2) did not exist and has not been deleted |
| 008 | Error during local update of the handler table |
| 009 | Error reading the logical systems |
| 010 | Could not determine an RFC destination for system &1 |
| 011 | Error occurred during RFC call against &1 |
| 012 | Error updating handler table in system & |
| 013 | Handler tables updated successfully |
| 014 | Errors occurred during remote update of the handler table |
| 015 | No locally entered handlers matched the selection criteria |
| 016 | Local Handler Customizing tables read successfully |
| 017 | Error reading the handler Customizing table in system & |
| 018 | Error reading the local handler Customizing table |
| 019 | Error reading the remote handler Customizing table |
| 020 | Error reading the local and remote handler Customizing table |
| 021 | Could read the requested handler successfully |
| 022 | Syntax check completed successfully |
| 023 | The RFC destination of one or more component systems could not be found |
| 024 | Handler update was not successful in all components |
| 025 | RFC destination for logical system & could not be determined |
| 026 | RFC to logical system & failed |
| 027 | Error updating handler in logical system & |
| 028 | Handler entries distributed successfully |
| 029 | Error reading the assignment of tasks to services (&1) |
| 030 | No service ID could be found for task &1 |
| 031 | You did not enter required import parameters |
| 032 | Error changing the task to service relationship (&1/&2) |
| 033 | Error creating the task to service relationship (&1/&2/&3) |
| 034 | Error saving handler entries |
| 035 | Handler entries saved successfully |
| 036 | You did not select a handler category |
| 037 | No handler has been maintained for the selected handler category |
| 038 | Browser could not be started |
| 039 | No handlers were entered |
| 040 | Work item &1 was executed successfully |
| 041 | RFC destination for system & is empty |
| 042 | Top label "&" contains invalid characters |
| 043 | Domain label "&" contains invalid characters |
| 044 | Segment number &1 in IP address "&2" contains more than three characters |
| 045 | Segment number &1 in IP address "&2" is empty |
| 046 | Segment number &1 in IP address "&2" contains non-numeric characters |
| 047 | Network number of IP address "&" is greater than 223 |
| 048 | Segment number &1 of IP address "&2" is greater than 255 |
| 049 | IP port no. "&" contains non-numeric characters |
| 050 | User information "&" contains invalid characters |
| 051 | Registry-based name "&1" contains invalid characters |
| 052 | Error in structure of AUTHORITY part "&" of URI |
| 053 | Error in AUTHORITY part "&" of URI |
| 054 | Parameter "&1" in path segment &2 contains invalid characters |
| 055 | Part "&1" of path segment &2 contains invalid characters |
| 056 | Absolute path "&" does not begin with "/" |
| 057 | Error in part "&" of absolute path of URI |
| 058 | Query parameter name "&1" contains invalid characters |
| 059 | Query portion "&1" in the URI is invalid |
| 060 | Query portion "&1" contains invalid characters |
| 061 | Query parameter value "&1" contains invalid characters |
| 062 | Query parameter "&1" could not be written |
| 063 | The query syntax does not allow you to change parameters |
| 064 | Query string does not contain any parameters with the name "&1" |
| 065 | Query syntax does not allow you to read parameters |
| 066 | Relative URI "&1" does not contain any path components |
| 067 | Absolute URI "&1" does not contain any path components |
| 068 | Query portion "&1" in the URI is invalid |
| 069 | Error when creating URIs |
| 070 | Error creating the query component |
| 071 | URI has no query component |
| 072 | Query parameter "&1" could not be read |
| 073 | Error deleting query parameter "&1" |
| 074 | URI schema "&1" contains invalid characters |
| 075 | URI has invalid structure |
| 076 | HTTP is not activated on this application server |
| 077 | Do not enter a handler |
| 078 | Error when saving the handler entry |
| 079 | Saving of handler entry successful |
| 080 | Error creating callback dialog URLs |
| 081 | Error reading callback dialog server information |
| 082 | Handler successfully read from the database |
| 083 | Generation of the base URL information failed |
| 084 | Saving the callback dialog of the base URL successful |
| 085 | No callback dialog base URL entered |
| 086 | Entries saved successfully |
| 087 | Error when saving the entries |
| 088 | No entries changed - saving not necessary |
| 089 | Handler entry successfully generated |
| 090 | Base URL of callback dialogs successfully generated |
| 199 | Maintenance of WebFlow service handler is locked by user &1 |
| 200 | System is immediately operated as the handler server |
| 201 | There are still dependent logical systems maintained |
| 202 | System was set to the initial status |
| 203 | A separate logical system could not be determined |
| 204 | Database errors when saving the system status |
| 205 | System status was not changed |
| 206 | System status was set to 'handler client' |
| 300 | No row selected |
| 301 | '&1' is not a valid Basis release |
| 302 | RFC destination '&1' does not exist in the system |
| 303 | Local entry cannot be changed |
| 304 | Entries saved successfully |
| 305 | Saving of entries failed |
| 306 | Local entry cannot be deleted |
| 307 | Only select one single row |
| 308 | Logical system '&1' was removed from the handler client table |
| 309 | Error when deleting the logical system '&1' |
| 310 | Service entries exist for the logical system '&1' |
| 311 | An empty row already exists |
| 312 | Enter a logical system |
| 313 | Complete the row |
| 314 | The logical system '&1' is already maintained |
| 315 | The logical system '&1' is not maintained |
| 316 | Error when saving the handler entry |
| 317 | Error when saving the logical handler server system |
| 318 | System is a handler server |
| 319 | Handler server of this system is the logical system '&1' (not '&2') |
| 320 | Update of Handler Table Failed |
| 321 | System Status Was Set to 'Handler-Client' |
| 322 | Update of Handler Table Successful |
| 323 | System status could not be set to 'initial' |
| 324 | Error when deleting the handler service entry from the database |
| 325 | System status was set to 'initial' |
| 326 | Error when deleting the remote handler entry |
| 327 | Basis release could not be determined |
| 328 | System '&1' is already client system of '&2'. |
| 329 | Saving unnecessary, since no entries were changed |
| 330 | System '&1': Enter Basis release |
| 331 | Are you sure you want to remove system '&1' from the list? |
| 400 | Error in the task generation |
| 401 | Task generation canceled by user |
| 500 | Task does not exist |
| 501 | Service definition does not exist |
| 502 | Logical system is no handler client |