SR - RFC-Utilities
The following messages are stored in message class SR: RFC-Utilities.
It is part of development package SRFC in software component BC-MID-RFC. This development package consists of objects that can be grouped under "Middleware Runtime Environment".
It is part of development package SRFC in software component BC-MID-RFC. This development package consists of objects that can be grouped under "Middleware Runtime Environment".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & |
| 001 | Logical destination must begin with a letter from A to Z |
| 002 | No destination specified |
| 003 | No connection to & |
| 004 | Invalid destination name |
| 005 | Document destination |
| 006 | Function not supported |
| 007 | Destination cannot be changed |
| 008 | Destination & saved |
| 009 | Destination & deleted |
| 010 | Host name & unknown |
| 011 | Host name & is too long |
| 012 | Enter a destination |
| 013 | Destination already created |
| 014 | Create destination first |
| 015 | Select a valid line |
| 016 | This LUW cannot be executed either now or once again |
| 017 | Destination & not defined (see long text) |
| 018 | The job ARFC:DISTRIBUTOR begins with the distribution (see long text) |
| 019 | User & can delete this entry |
| 020 | Logical destination & deleted. Reference does not exist |
| 021 | Only user DDIC can delete the log file |
| 022 | Only user DDIC can distribute destinations |
| 023 | Destination & already exists |
| 024 | Last collector run: & & |
| 025 | Destination & is locked by user & |
| 026 | Lock table not currently accessible |
| 027 | Connection error: Gateway or target system not active |
| 028 | Error in target system |
| 029 | Gateway overloaded |
| 030 | Function module executed |
| 031 | Message sent |
| 032 | Message edited in target system |
| 033 | Transaction recorded |
| 034 | Transaction recorded (LUW with update records) |
| 035 | Status unknown |
| 036 | Transaction released for execution |
| 037 | Function not supported. System & has Release & |
| 038 | Transaction executing |
| 039 | This LUW must be executed in debugging |
| 040 | This transaction can only be executed in client & |
| 041 | LUW was reset |
| 042 | Unable to reset entry |
| 043 | Entries are inconsistent |
| 044 | Function was canceled |
| 045 | Trusted system entry already exists for system & |
| 046 | Trusted system entry &1 is locked by user &2 |
| 047 | Invalid name for destination with form & (see long text) |
| 048 | Trusted destination & has the wrong setting (see long text) |
| 049 | Setting for destination & reset |
| 050 | Trusting destination & has the wrong setting (see long text) |
| 051 | Destination type &1 not supported |
| 052 | System overloaded, repeat immediately by batch |
| 053 | &1 &2 |
| 054 | aRFC terminated with error '&' |
| 055 | User can be used for remote logon in target system |
| 056 | HTTP connections may not be secure |
| 057 | Not possible: internal connections are being generated |
| 058 | Selection not permitted for this connection type |
| 059 | Not all of your selection can be applied; see the long text |
| 060 | SSL client PSE ANONYM does not exist |
| 061 | Enter a timeout between 1 and 9999999 msec |
| 062 | HTTP/1.0 does not support active compression |
| 063 | SSL client PSE &1 does not exist |
| 064 | Perform the Unicode test (see long text) |
| 065 | Check the Unicode-compliance of the server program (see long text) |
| 066 | Inserted successfully in secure storage |
| 067 | Deleted successfully in secure storage |
| 068 | Updated successfully in secure storage |
| 069 | Destination & no longer exists |
| 070 | RFC destination cannot start with leading blank |
| 071 | You have no authorization to & a destination |
| 072 | You are not authorized for extended maintenance of the destinations |
| 073 | You have no authorization to &1 destination &2 |
| 074 | You have no authorization for & |
| 075 | Delete the gateway options (see long text) |
| 076 | Only "Special Options" can be modified |
| 077 | Entry &1 can be deleted in SMQ1 only (mismatch between tRFC and qRFC) |
| 078 | LUW with TID &1 is |
| 079 | Update terminated |
| 080 | Stop and restart entries cannot be executed |
| 081 | The LUW is not an LUW of the outbound queue |
| 082 | LUWs in status NOSEND must be picked up by the application |
| 083 | LUW update still running |
| 084 | LUW data is temporarily locked |
| 085 | A lock has been set for the queue |
| 086 | Restart condition set. Wait for queues with higher priority |
| 087 | This LUW has further predecessors |
| 088 | Generic stop set |
| 089 | Restart condition for individual queue set |
| 090 | Generic restart condition set |
| 091 | LUW for queue receiver cannot be sent |
| 092 | LUW in status EXECUTED is waiting for confirmation from target system |
| 093 | LUW in status SENT. LUW is being executed |
| 094 | LUW is not an LUW of the inbound queue |
| 095 | The queue is registered and therefore cannot be activated |
| 096 | No LUW found in the queue |
| 097 | No queue name passed |
| 098 | No destination name passed |
| 099 | No LUW exists in the specified queue |
| 100 | No & authorization to execute & |
| 101 | User & (client &) has no ICF authorization & for executing & |
| 102 | Set by host name: &1; transaction: &2; report: &3 |
| 103 | Wait for queue &1 |
| 104 | No connection type specified |
| 105 | No S_RFCREC authorization for activity &1 (&2) and user &3 |
| 106 | ICFRECORD entry &1 locked by user &2 (&3) |
| 107 | Error in ICFRECORD call (error code &1) |
| 108 | Error in Control Framework. Restart transaction. |
| 109 | Deletion run terminated |
| 110 | Requested object (&1) not recorded |
| 111 | Download complete (file: &1) |
| 112 | Upload complete (message ID: &1) |
| 113 | Error when converting time (error code: &1) |
| 114 | Select an entry |
| 115 | An attempt was made to access the secure passwords |
| 116 | Password length for R/2 destinations is 8 characters |
| 117 | Select an RFC destination |
| 118 | Use transaction SM59 only |
| 119 | Delete the flag for the "Send SAP Logon Ticket" checkbox |
| 120 | Could not determine parameter values of current server |
| 121 | IPv6 addresses are not yet supported |
| 122 | Check your input |
| 123 | Could not select classic qRFC version for destination &1 |
| 124 | Enter a valid RFC connection |
| 125 | Source system cannot be set to Unicode |
| 126 | Error in execution of database operations |
| 127 | User password not consistent for identifier &1 (see long text) |
| 128 | User password invalid for identifier &1 (see long text) |
| 129 | Proxy password not consistent for identifier &1 (see long text) |
| 130 | Proxy password invalid for identifier &1 (see long text) |
| 131 | Error in conversion of user password for destination &1 |
| 132 | Error in conversion of proxy password for destination &1 |
| 133 | Enter a timeout value greater than zero |
| 134 | User &1 does not have RFC authorization for function group &2 |
| 135 | Error in Control Framework |
| 136 | Function not possible when debugging in RFC context |
| 137 | Trust relationship is inactive; delete it in TA SMT1 and create it again |
| 138 | Password cannot be specified without user |
| 139 | Logon data changed; password initialized |
| 140 | Proxy password cannot be specified without proxy user |
| 141 | Changing the proxy data initializes the proxy password |
| 142 | Change of logon data; set new password |
| 143 | Error when creating destination for metadata provider |
| 144 | Error during bgRFC conversion: &1 |
| 145 | Could not create metadata destination; enter it again |
| 146 | basXML conversion not possible due to running conversion |
| 147 | &1 |
| 148 | Error when scheduling conversion job |
| 149 | No unconverted units exist after protocol switch |
| 150 | Job &1 started and destination &2 saved |
| 151 | Conversion job &1 started |
| 152 | Destination &1: &2 |
| 153 | Enter system ID and client for assertion ticket |
| 154 | Cannot check settings for SSL client certificate |
| 155 | Cannot determine code page for language &1, return code &2 |
| 156 | Enter an explicit code page |
| 157 | No authorization for following action in the ACL: &1 |
| 158 | Only "Callback Allowlist" can be changed |
| 159 | Destination type &1 is not supported |
| 160 | &1&2&3&4 |
| 161 | Changing the MQTT data (initializing MQTT password) |
| 162 | MQTT password not allowed if MQTT user is not specified |
| 163 | MQTT password is inconsistent for identifier &1 (see long text) |
| 164 | MQTT password is not valid for identifier &1 (see long text) |
| 174 | Text missing in dialog box |
| 175 | Internal error in dialog box |
| 182 | Save the destination before editing SNC settings |
| 185 | Destination &1 can only be deleted in its own client |
| 186 | System destination &1 can only be deleted in the system client |
| 190 | Kernel prerequisites of report not met |
| 191 | Hash error |
| 192 | Timeout must be between 1 and 300 seconds |
| 193 | No authorization to create HMAC security key |
| 194 | No authorization to read HMAC security key |
| 195 | No network administration authorization |
| 196 | No authorization to read own installation number |
| 197 | Internal error when creating table control |
| 198 | Internal error in table processing |
| 199 | Hash values do not match |
| 200 | Select at least one row in the table |
| 201 | Proxy setting is already being used by user &1 in client &2 |
| 202 | Only use numerical values for port (or service) |
| 203 | No authorization for trust relationship in &1/&2 |
| 204 | Error in delegation of manual logon |
| 205 | No documentation available for report |
| 206 | Double-click in "Delete" column |
| 207 | Relationships with security method 2 cannot be deleted here |
| 208 | Database table RFCSYSACL not deleted in full |
| 209 | Database table RFCTRUST not deleted in full |
| 211 | Could not create internal trust relationship |
| 212 | Missing authorization to create internal trust relationship |
| 213 | Error when reading own installation number |
| 214 | Missing network administration authorization |
| 215 | Missing authorization to delete internal trust relationship |
| 216 | Could not delete internal trust relationship |
| 217 | System destination can only be deleted in system client |
| 218 | HMAC security key is initial |
| 219 | Database key is initial |
| 220 | Could not execute mode "&1" |
| 221 | Function group &1 does not exist |
| 222 | Target system parameters changed; set new password |
| 223 | Change of destination authorization; set new password |
| 224 | No authorization to delete access control list |
| 225 | No authorization for extended maintenance of access control list |
| 226 | No authorization to display access control list |
| 227 | Specify a system ID |
| 228 | System ID missing (installation number specified) |
| 229 | Inconsistency in access control list; not deleted |
| 230 | Inconsistency in access control list; not updated |
| 231 | No authorization to edit access control for &1 &2 |
| 232 | Specify CROSS_CLIENT = 'X' for cross-client editing |
| 233 | Can be created only if access control list is empty |
| 234 | Trust relationship does not exist |
| 235 | Access control list is locked by user &1 |
| 236 | Lock table not currently accessible |
| 237 | No authorization to modify access control list |
| 238 | No alerts exist |
| 239 | Error when changing client |
| 240 | Initial fills only possible for empty dedicated user tables |
| 241 | Initial fill performed for dedicated target user table but not yet saved |
| 242 | No authorization to delete access control list |
| 243 | Access control list is already empty |
| 244 | Access control list deleted |
| 245 | No online manual available |
| 246 | Data saved |
| 247 | Select a valid entry |
| 248 | No authorization for initial fill |
| 249 | Correct or reset your input first |
| 250 | No authorization to display table |
| 251 | No authorization to change table |
| 252 | Missing transaction authorization for SMTACL_HIST |
| 253 | No authorization for cross-client reading of alerts |
| 254 | Placeholder for NGAP |
| 255 | Internal error in initial fill of access control list |
| 256 | Internal error when reading alerts |
| 257 | No usable entries exist in authorization S_RFCACL |
| 258 | Communication error when changing client |
| 259 | RFC &1 can be called in same system only |
| 260 | Callback of funtion module &1 forbidden by allowlist |
| 261 | &1 callback allowlist entries generated |
| 262 | Error in date input |
| 263 | No RFC callbacks made since specified date in security audit log |
| 264 | Destination for allowlist of dynamic destinations cannot be created |
| 265 | &1 callback allowlist entries generated and allowlist activated |
| 266 | All non-empty callback allowlists were activated |
| 267 | The user can have a maximum of 32 characters in a type H connection |
| 268 | Entries with empty function module or callback FM are deleted |
| 269 | Handler class &1 does not exist |
| 270 | No authorization to display file &1 (authorization object S_DATASET) |
| 273 | Class &1 does not implement the required interface &2 |
| 274 | Class &1 does not yet exist and will be created |
| 275 | This class cannot be used |
| 280 | Destination does not exist |
| 300 | Exception CX_BGRFC_RETRY_REQUEST caught by application |
| 301 | Queue names &1 and &2 are registered for different destinations |
| 302 | Queue name &1 is not registered for bgRFC |
| 320 | Destination &1 cannot be used for classic qRFC |
| 321 | Inbound queue name & cannot be used for classic qRFC |
| 322 | Destination cannot be used for bgRFC |
| 400 | Program &1 cannot reset the status RUNNING |
| 402 | Data can only be displayed in current client |
| 440 | New serialization is not supported for RFC communication |
| 441 | New serialization supports only Unicode destinations |
| 442 | New serialization supports only destination types 3, I, L, and T |
| 443 | New serialization is active on the target server |
| 444 | New serialization is not active on the target server |
| 445 | MQTT password not allowed if MQTT user is not specified |
| 446 | Outbound t/qRFC UCON RFC rejected |
| 500 | Function module does not exist |
| 501 | Only Fast Serialization is supported for this feature |
| 503 | Error in serialization/deserialization |
| 504 | No authorization to execute function module |
| 505 | TID not found |
| 506 | Invalid importing parameters |
| 600 | Queue name is empty |
| 601 | Invalid queue name &1 |
| 602 | Mode &1 not valid |
| 603 | Could not register queue name &1 |
| 605 | Queue name &1 registered |
| 606 | Queue name &1 removed |
| 888 | The destination NONE cannot be deleted |