SDEST - Nachrichten f�r RFC-Destinationen
The following messages are stored in message class SDEST: Nachrichten f�r RFC-Destinationen.
It is part of development package SRFC_DESTAPI in software component BC-MID-RFC. This development package consists of objects that can be grouped under "RFC: API for Destinations".
It is part of development package SRFC_DESTAPI in software component BC-MID-RFC. This development package consists of objects that can be grouped under "RFC: API for Destinations".
Message Nr ▲ | Message Text |
|---|---|
| 001 | SAVE and SET methods can be called for locked destinations only |
| 002 | Value & for keep-alive timeout is invalid |
| 003 | Destination & does not exist in system |
| 004 | tRFC: Inconsistent settings for response to connection errors |
| 005 | Error in Class Library; lock not possible |
| 006 | Value & for conversion error procedure is invalid |
| 007 | Value & for qRFC version is invalid |
| 008 | Value & for load check procedure in asynchronous RFC is invalid |
| 009 | Value & for communication method is invalid |
| 010 | Value & for start type of external program is invalid |
| 011 | Value & for CPIC timeout is invalid |
| 012 | Value & for forwarding of trace level to target system is invalid |
| 013 | Error when saving destination & to database |
| 014 | Value &1 invalid for &2 (supported values "Space" and "X") |
| 015 | Error when saving SNC parameters |
| 016 | Destination &1, type &2 already exists and cannot be created again |
| 017 | No authorization for action &1 (destination &2, type &3) |
| 018 | Error when locking destination |
| 019 | Update options for modifying destination are invalid |
| 020 | RFC destinations of type & are not supported by API |
| 021 | Password handling error in Class Library (error situation &1) |
| 022 | Error in destination; no save possible |
| 023 | Connection type & is unknown |
| 024 | Value & for HTTP timeout is invalid |
| 025 | Value & for HTTP version is invalid |
| 026 | Value & for status of HTTP compression is invalid |
| 027 | Value & for status of HTTP compression of response is invalid |
| 028 | Value & for handling of cookies is invalid |
| 029 | Value & for SSL client identity is invalid |
| 030 | HTTP compression for version & of HTTP protocol is not supported |
| 031 | Category &1 unknown for type &2 |
| 032 | You cannot edit a destination of category &2 |
| 033 | Internal error in class library (error sitation &) |
| 034 | Referenced destination & does not exist |
| 035 | Destinations with type & are not supported as references |
| 036 | Logon data inconsistent; user not unique |
| 037 | Logon data and logon procedure are inconsistent |
| 038 | Value & for system load analysis period is invalid |
| 039 | You cannot specify logon data for logon screen prompt |
| 040 | Could not switch to classic qRFC version |
| 041 | Value &1 for destination name is invalid (error situation &2) |
| 042 | Cannot use function module &2 for type &1 |
| 043 | Category &1 for destination &2 is invalid |
| 044 | Value & for logon procedure is invalid |
| 045 | Settings for load balancing are incomplete |
| 046 | Value &1 for basXML activation is invalid |
| 047 | Functional test for connections of type & not supported |
| 048 | Server name &2 ignored for method &1 when saving |
| 049 | Server name cannot be initial for communication method E |
| 050 | Unprocessed units exist; no deletion possible |
| 051 | Could not lock dependent bgRFC configuration data |
| 052 | Cannot send SSO ticket |
| 053 | Password cannot be specified without user |
| 054 | Proxy password cannot be specified without proxy user |
| 055 | Logon data changed; specify a new password |
| 056 | bgRFC cannot be used for RFC destinations with type & |
| 057 | Password is too long |
| 058 | basXML conversion requires transaction SM59 in dialog |
| 059 | Assertion ticket requires system ID and client of target system |
| 060 | Send either logon or assertion ticket, not both |
| 061 | Invalid value for BYPASS_BUF for reading destination &MSGV1& |
| 062 | Internal error when reading destination &MSGV1& |
| 063 | &MSGV1& is not an HTTP destination (type G or H) |
| 064 | Value &1 for RFC serialization is not permitted. |
| 065 | Value &1 for fast serialization compatibility mode is not permitted. |
| 091 | Target system data change; you must set a new password |
| 092 | Destination authorization change; you must set a new password |
| 093 | Reference destination change; you must set a new password |
| 094 | Technical proxy data change; you must set a new password |
| 100 | Dynamic RFC/HTTP destinations are not allowed in this context |
| 101 | Kernel too old: Please install a current kernel version. |
| 102 | Internal error while registering a dynamic destination in the kernel |
| 103 | Internal error while generating ID |
| 104 | Reference destination &1 does not exist or the type is invalid. |
| 105 | If the destination has a password, &1 must not be overridden. |
| 106 | Special characters are not allowed. |
| 107 | Fast serialization and basXML cannot be combined. |
| 108 | Alias user and normal user cannot be combined. |
| 110 | WebRFC destinations can only contain uppercase letters and numbers. |
| 183 | Enter client |
| 185 | No dynamic destination registered under this ID |
| 186 | Obligatory parameter "LOGON_USER" must not be empty |
| 187 | Obligatory parameter "LOGON_PASSWORD" must not be empty |
| 188 | Cannot register dynamic destination |