SAP ABAP Message Class XS (SAPconnect: All messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷
SCON (Package) SAPconnect - External Communication
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony⤷
SCON (Package) SAPconnect - External Communication 
Attributes
| Message class |  |
XS |
| Short Description |  |
SAPconnect: All messages |
| Changed On |  |
20141121 |
| Last Changed At |  |
124020 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
*** Codes 000-199 are reserved for SAP internal messages (see text)*** | Space: object requires documentation | |
| 2 | 001 |
SAPconnect system error: & & & & | ||
| 3 | 002 |
Node & not allowed for address type & | ||
| 4 | 003 |
You cannot specify an address for a generic address type | ||
| 5 | 004 |
For Internet addresses, '*' must be at the beginning | ||
| 6 | 005 |
For a generic address entry, '*' must be at the end (exception: Internet) | ||
| 7 | 006 |
Recipient & in another SAP system | Space: object requires documentation | |
| 8 | 007 |
Address & invalid | ||
| 9 | 008 |
Call of & with & & & | ||
| 10 | 009 |
Address type & invalid | ||
| 11 | 010 |
Invalid version specified & (must contain numbers only) | ||
| 12 | 011 |
Version & incompatible with version used | ||
| 13 | 012 |
Version & is different, but compatible | ||
| 14 | 013 |
Message ID for status/response is incorrect | ||
| 15 | 014 |
Node & from status message cannot be reached | ||
| 16 | 015 |
Device type & not allowed | ||
| 17 | 016 |
E: No format for node & and address type & specified | Space: object requires documentation | |
| 18 | 017 |
Table SXADMINTAB still contains no entry | ||
| 19 | 018 |
Could not save administration data | ||
| 20 | 019 |
Administration data was saved | ||
| 21 | 020 |
Could not determine variants | ||
| 22 | 021 |
Could not determine address type | ||
| 23 | 022 |
Error when displaying list | ||
| 24 | 023 |
Start of selection for documents to be sent with address type & | ||
| 25 | 024 |
End of selection for addr. type &. Statistical info follows. | ||
| 26 | 025 |
End of send process &1. Number of selected objects: &3 | Space: object requires documentation | |
| 27 | 026 |
Fax number to be replaced has an incorrect format | ||
| 28 | 027 |
Address type & is not assigned to SAPconnect | ||
| 29 | 028 |
Specify a job name | ||
| 30 | 029 |
Error when accessing contents of document & | ||
| 31 | 030 |
Document cannot be converted: Invalid structure | ||
| 32 | 031 |
No conversion known for & to & | ||
| 33 | 032 |
Conversion from & to &: Termination in &, return code & | Space: object requires documentation | |
| 34 | 033 |
No suitable conversion found for & | ||
| 35 | 034 |
Could not find any jobs | ||
| 36 | 035 |
Cannot display help for this field | ||
| 37 | 036 |
No address type specified | ||
| 38 | 037 |
Error when transferring status information to table Rec_List | ||
| 39 | 038 |
Document type: &. Send attribute class: &. No. of recipients: & | ||
| 40 | 039 |
Send attributes: No entry found for & in table SXCOS | ||
| 41 | 040 |
Error when converting fax number | ||
| 42 | 041 |
Function not yet supported. Index=&. N=&, UCOMM=&. | ||
| 43 | 042 |
No jobs found | ||
| 44 | 043 |
Converting & to &: Temporary spool request & created | ||
| 45 | 044 |
Function not supported (&) | ||
| 46 | 045 |
Combination of address type + send method is not supported | Space: object requires documentation | |
| 47 | 046 |
Node name '*' is reserved for the system | ||
| 48 | 047 |
Device Type for Format &1 Not Defined | Space: object requires documentation | |
| 49 | 048 |
The device type specified has an invalid driver | ||
| 50 | 049 |
Country not specified for node & | ||
| 51 | 050 |
CDG group was set to a generic value | ||
| 52 | 051 |
Routing entry specified already exists | ||
| 53 | 052 |
Converting Document Format from & to & & & | Space: object requires documentation | |
| 54 | 053 |
Error in function module ICON_CREATE. Error number = & | ||
| 55 | 054 |
No variants created for report & | ||
| 56 | 055 |
Read contents of document & | ||
| 57 | 056 |
Node data was saved | Space: object requires documentation | |
| 58 | 057 |
Node data was not changed | Space: object requires documentation | |
| 59 | 058 |
Address type data for node was not changed | Space: object requires documentation | |
| 60 | 059 |
Send times for node were not changed | Space: object requires documentation | |
| 61 | 060 |
Fax no. outbound modification for node was not changed | Space: object requires documentation | |
| 62 | 061 |
& deleted | Space: object requires documentation | |
| 63 | 062 |
Deletion of & was canceled | Space: object requires documentation | |
| 64 | 063 |
Node & has not been created | Space: object requires documentation | |
| 65 | 064 |
Node & already exists | Space: object requires documentation | |
| 66 | 065 |
Table SXROUTE contains a line with an empty address area | Space: object requires documentation | |
| 67 | 066 |
Enter RFC destination for node | Space: object requires documentation | |
| 68 | 067 |
Received ISO country code for language is invalid | Space: object requires documentation | |
| 69 | 068 |
Route from node & overwritten | Space: object requires documentation | |
| 70 | 069 |
Send times for priority & are invalid | Space: object requires documentation | |
| 71 | 070 |
Enter a valid RFC destination | Space: object requires documentation | |
| 72 | 071 |
Node &1 already exists. | Space: object requires documentation | |
| 73 | 072 |
Generic format '*' is not allowed when excluding formats | Space: object requires documentation | |
| 74 | 073 |
Message sent to & | Space: object requires documentation | |
| 75 | 074 |
Default domain or office settings are currently being edited | Space: object requires documentation | |
| 76 | 075 |
Error when reading default domain from SAPoffice profile | Space: object requires documentation | |
| 77 | 076 |
Default domain contains disallowed characters | Space: object requires documentation | |
| 78 | 077 |
No Conversion: Function &1 Does Not Exist or Is Not Active | Space: object requires documentation | |
| 79 | 078 |
Start send process &1 on server &2 in client &3. | Space: object requires documentation | |
| 80 | 079 |
Send process started synchronously for document &1 | Space: object requires documentation | |
| 81 | 080 |
*** SAPconnect Administration *** | Space: object requires documentation | |
| 82 | 081 |
Position cursor on valid object | Space: object requires documentation | |
| 83 | 082 |
Resending only possible via SAPconnect Administration | Space: object requires documentation | |
| 84 | 083 |
Sender & not on the list | Space: object requires documentation | |
| 85 | 084 |
Error when exchanging data with the external software | Space: object requires documentation | |
| 86 | 085 |
SAPconnect &1: &2 (0x&3) | Space: object requires documentation | |
| 87 | 086 |
Error when accessing the external software: Test not possible | Space: object requires documentation | |
| 88 | 087 |
Version &1 of the external software has an incorrect format | Space: object requires documentation | |
| 89 | 088 |
Error (&) in monitor display. Monitor name = &. | Space: object requires documentation | |
| 90 | 089 |
Node no longer exists. | Space: object requires documentation | |
| 91 | 090 |
Data collection method for SAPphone ran with no errors. | Space: object requires documentation | |
| 92 | 091 |
Data collection method was completed with errors (error code &) | The short text describes the object sufficiently | |
| 93 | 092 |
Data collection method for SAPconnect ran with no errors. | Space: object requires documentation | |
| 94 | 093 |
Data collection method could not be started. | Space: object requires documentation | |
| 95 | 094 |
Action cannot be executed because ESMTP plug-in XString empty | Space: object requires documentation | |
| 96 | 095 |
SMTP Node Cannot Be Deleted or Copied | Space: object requires documentation | |
| 97 | 096 |
SMTP Node Is Not Available | Space: object requires documentation | |
| 98 | 097 |
Specify Mail Host and Mail Port for Node | Space: object requires documentation | |
| 99 | 098 |
Queue for incoming messages is active | Space: object requires documentation | |
| 100 | 099 |
Queue for incoming messages deactivated | Space: object requires documentation | |
| 101 | 100 |
Enter password consistently | Space: object requires documentation | |
| 102 | 101 |
Conversion into character set selected or no character set specified | Space: object requires documentation | |
| 103 | 102 |
Address areas without special characters saved since not relevant | Space: object requires documentation | |
| 104 | 103 |
Specify at least one address area | Space: object requires documentation | |
| 105 | 104 |
A send process is already running for &1/prio &2 | Space: object requires documentation | |
| 106 | 105 |
Error occurred when locking the send dispatcher | The short text describes the object sufficiently | |
| 107 | 106 |
Send process started asynchronously: Package &1; No.: &2; Destination: &3 | Space: object requires documentation | |
| 108 | 107 |
Starting send process locally: Package &1 number: &2 | The short text describes the object sufficiently | |
| 109 | 108 |
Package &1; Number: &3; Destination: &2 | The short text describes the object sufficiently | |
| 110 | 109 |
Waiting for aRFC: Maximum wait time of &1 exceeded | Space: object requires documentation | |
| 111 | 110 |
Package &1 processed; duration: &2; &3 requests sent | Space: object requires documentation | |
| 112 | 111 |
Error in package &1: &2 | Space: object requires documentation | |
| 113 | 112 |
Wait time exceeded | Space: object requires documentation | |
| 114 | 113 |
Job data saved | The short text describes the object sufficiently | |
| 115 | 114 |
Unable to save job data | The short text describes the object sufficiently | |
| 116 | 115 |
Job deleted | The short text describes the object sufficiently | |
| 117 | 116 |
Job currently being processed by user & | Space: object requires documentation | |
| 118 | 117 |
Unable to find job; refresh display | Space: object requires documentation | |
| 119 | 118 |
Error occurred when calling &1; return code &2 | The short text describes the object sufficiently | |
| 120 | 119 |
Job data not changed | The short text describes the object sufficiently | |
| 121 | 120 |
Job selection unclear; refresh display | Space: object requires documentation | |
| 122 | 121 |
No messages sent | The short text describes the object sufficiently | |
| 123 | 122 |
Variant saved | The short text describes the object sufficiently | |
| 124 | 123 |
Variant & already exists | The short text describes the object sufficiently | |
| 125 | 124 |
Active jobs cannot be deleted | The short text describes the object sufficiently | |
| 126 | 125 |
Only one server group can be selected within a transaction | Space: object requires documentation | |
| 127 | 126 |
No values were changed | The short text describes the object sufficiently | |
| 128 | 127 |
Server group is not relevant for a work process | Space: object requires documentation | |
| 129 | 128 |
Specify a target format | Space: object requires documentation | |
| 130 | 129 |
The data has been transferred | The short text describes the object sufficiently | |
| 131 | 130 |
Data already exists | Space: object requires documentation | |
| 132 | 131 |
Specify a device type | The short text describes the object sufficiently | |
| 133 | 132 |
Device type and formats are not compatible | Space: object requires documentation | |
| 134 | 133 |
Device type for conversion is different from OTF device type | Space: object requires documentation | |
| 135 | 134 |
No device type exists for format &1 | The short text describes the object sufficiently | |
| 136 | 135 |
Determined device type: &1. &2 &3 | The short text describes the object sufficiently | |
| 137 | 136 |
Generic internet addresses with special characters are not allowed | The short text describes the object sufficiently | |
| 138 | 137 |
MIME version does not exist | Space: object requires documentation | |
| 139 | 138 |
Email address & is invalid | Space: object requires documentation | |
| 140 | 142 |
Complete your input | The short text describes the object sufficiently | |
| 141 | 143 |
There is already an entry in language & | The short text describes the object sufficiently | |
| 142 | 144 |
Error in monitor display; check your input | The short text describes the object sufficiently | |
| 143 | 195 |
A | Space: object requires documentation | |
| 144 | 196 |
B | Space: object requires documentation | |
| 145 | 197 |
C | Space: object requires documentation | |
| 146 | 198 |
D | Space: object requires documentation | |
| 147 | 199 |
E | Space: object requires documentation | |
| 148 | 200 |
*** SAPconnect XPRA&: &(&) *** | Space: object requires documentation | |
| 149 | 201 |
XPRA & does not run under Release & | Space: object requires documentation | |
| 150 | 202 |
XPRA processing not required for online, program terminated | Space: object requires documentation | |
| 151 | 203 |
XPRA log cannot be saved due to system error | Space: object requires documentation | |
| 152 | 204 |
Database error preventing action & in table & | Space: object requires documentation | |
| 153 | 205 |
No nodes defined, SAPconnect initialized | Space: object requires documentation | |
| 154 | 206 |
No nodes support sending externally | Space: object requires documentation | |
| 155 | 207 |
XPRA debug note: & | Space: object requires documentation | |
| 156 | 208 |
XPRA & for converting & ran successfully | Space: object requires documentation | |
| 157 | 209 |
No Node Exists Whose RFC Destination Must Be Converted | Space: object requires documentation | |
| 158 | 210 |
No Node Exists Whose Formatting Must Be Converted | Space: object requires documentation | |
| 159 | 211 |
No RFC Destination Is Maintained for Node &, Retrieve Entry | Space: object requires documentation | |
| 160 | 212 |
Enter a destination | Space: object requires documentation | |
| 161 | 300 |
*** SAPconnect - Spool - Connection *** | Space: object requires documentation | |
| 162 | 301 |
Output request for device &1, user &2 | Space: object requires documentation | |
| 163 | 302 |
Formatted data (&1 bytes, from row &2, &3 rows) | Space: object requires documentation | |
| 164 | 303 |
Text data (from line &1, &2 lines) | Space: object requires documentation | |
| 165 | 304 |
Spool request with ID &1 generated | Space: object requires documentation | |
| 166 | 305 |
Error occurred when creating spool request (&1 &2 &3 &4) | Space: object requires documentation | |
| 167 | 370 |
*** Messages for routing details *** | The short text describes the object sufficiently | |
| 168 | 371 |
Step 2: Determine node | The short text describes the object sufficiently | |
| 169 | 372 |
Step 3: Convert address into an external format | The short text describes the object sufficiently | |
| 170 | 373 |
Step 1: Check entered addresses | The short text describes the object sufficiently | |
| 171 | 374 |
In this step, the following error was identified: | The short text describes the object sufficiently | |
| 172 | 375 |
No error in this step | The short text describes the object sufficiently | |
| 173 | 376 |
Step 4: Creation of a Test URL (Only with HTTP Nodes) with Dummy Data | The short text describes the object sufficiently | |
| 174 | 377 |
&1 | The short text describes the object sufficiently | |
| 175 | 378 |
Checking/converting following address: Type=&1, Address=&2 | The short text describes the object sufficiently | |
| 176 | 379 |
No sender specified, therefore CDG routing not possible | The short text describes the object sufficiently | |
| 177 | 380 |
Sender &1 is assigend to the following sender group (CDG):&2 | The short text describes the object sufficiently | |
| 178 | 381 |
Following sender was assigned to no sender group: &1 | The short text describes the object sufficiently | |
| 179 | 382 |
Number of limited, relevant routing entries: &1 | The short text describes the object sufficiently | |
| 180 | 383 |
A fully qualified entry was found in the routing table: | The short text describes the object sufficiently | |
| 181 | 384 |
Sender group (if one exists): &1 | The short text describes the object sufficiently | |
| 182 | 385 |
Address type and address value (shortened): &1 &2 | The short text describes the object sufficiently | |
| 183 | 386 |
Node: &1 | The short text describes the object sufficiently | |
| 184 | 387 |
Node cannot be used because it is not active | The short text describes the object sufficiently | |
| 185 | 388 |
Searching for most suitable routing entry... | The short text describes the object sufficiently | |
| 186 | 389 |
The following more suitable node was found: &1 | The short text describes the object sufficiently | |
| 187 | 390 |
Following entry was not suitable: &1 | The short text describes the object sufficiently | |
| 188 | 391 |
Search was ended | The short text describes the object sufficiently | |
| 189 | 392 |
Search with CDG parameter '&1' was unsuccessful | The short text describes the object sufficiently | |
| 190 | 393 |
Searching default routing entries (CDG=*).... | The short text describes the object sufficiently | |
| 191 | 394 |
Fax number starts with '&1', therefore no fax number conversion | The short text describes the object sufficiently | |
| 192 | 600 |
*** Codes for temporary errors *** | The short text describes the object sufficiently | |
| 193 | 602 |
Currently no delivery to &, as recipient is unknown | Space: object requires documentation | |
| 194 | 603 |
Currently no delivery to &, as message expired | Space: object requires documentation | |
| 195 | 604 |
Currently no delivery to &, as transfer parameter is invalid | Space: object requires documentation | |
| 196 | 605 |
Currently no delivery to &, as too many recipients | Space: object requires documentation | |
| 197 | 606 |
Currently no delivery to &, as recipient address is invalid | Space: object requires documentation | |
| 198 | 607 |
Currently no delivery to &, as recipient no longer valid | Space: object requires documentation | |
| 199 | 608 |
Currently no delivery to &, as no route known | Space: object requires documentation | |
| 200 | 609 |
Currently no delivery to &, as recipient cannot be reached | Space: object requires documentation | |
| 201 | 610 |
Currently no delivery to &, as transfer attempt failed | Space: object requires documentation | |
| 202 | 612 |
Currently no delivery to & | Space: object requires documentation | |
| 203 | 613 |
Currently no delivery, as sender address & is invalid | Space: object requires documentation | |
| 204 | 617 |
Message cannot currently be edited | Space: object requires documentation | |
| 205 | 618 |
Message in node cannot be processed at this moment | Space: object requires documentation | |
| 206 | 631 |
Message cannot be processed at the moment: invalid version details (&) | Space: object requires documentation | |
| 207 | 632 |
Message in node cannot be processed at the moment due to author. problem | Space: object requires documentation | |
| 208 | 634 |
Message cannot be processed at the moment as it cannot be converted | Space: object requires documentation | |
| 209 | 637 |
Currently no delivery to &, as recipient cannot be reached | Space: object requires documentation | |
| 210 | 638 |
Currently no delivery to &, due to problems with system resources | Space: object requires documentation | |
| 211 | 643 |
Currently no delivery to &, as error occurred during encoding/signing | Space: object requires documentation | |
| 212 | 644 |
Currently no delivery to & as security requirements are not fulfilled | Space: object requires documentation | |
| 213 | 647 |
Currently no delivery to &, as message contents incorrect | Space: object requires documentation | |
| 214 | 648 |
Currently no delivery to &, as message type is not supported | Space: object requires documentation | |
| 215 | 658 |
Currently no delivery to &1 due to error with authentication | Space: object requires documentation | |
| 216 | 699 |
*** Codes 700 - 899 reserved for SAPconnect status codes *** | ||
| 217 | 700 |
*** Information Codes *** | ||
| 218 | 701 |
Delivered to & | ||
| 219 | 702 |
No information on delivery to & | ||
| 220 | 703 |
Message read by & | ||
| 221 | 704 |
Message processed by & | ||
| 222 | 705 |
Message deleted by & | ||
| 223 | 706 |
Message not read by & | ||
| 224 | 707 |
Message not processed by & | ||
| 225 | 708 |
Recipient does not allow 'Read' or 'Processing' notifications | ||
| 226 | 709 |
Recipient refuses to accept the message | ||
| 227 | 710 |
Message transferred to node & | ||
| 228 | 711 |
Message transferred by node to communication system | Space: object requires documentation | |
| 229 | 712 |
General message from node & (see long text) | ||
| 230 | 713 |
Transmission costs incurred for message & | ||
| 231 | 714 |
Node & started | ||
| 232 | 715 |
Node & stopped | ||
| 233 | 716 |
Status successfully sent | ||
| 234 | 717 |
Node is not responsible for recipient & | ||
| 235 | 718 |
Recipient &1 Is Valid. Delivery Attempted | Space: object requires documentation | |
| 236 | 719 |
Recipient &1 is valid, message still forwarded | Space: object requires documentation | |
| 237 | 720 |
Message was forwarded to serveral recipients | Space: object requires documentation | |
| 238 | 721 |
Message was forwarded, possibly no further status messages | Space: object requires documentation | |
| 239 | 722 |
Message could not be delivered, will try again later | Space: object requires documentation | |
| 240 | 723 |
Message successfully transferred to service agent | Space: object requires documentation | |
| 241 | 750 |
*** Warning Codes *** | ||
| 242 | 751 |
Message cannot currently be transferred to node & due to connection error | Space: object requires documentation | |
| 243 | 752 |
Node & reports partial system error, throughput impaired | ||
| 244 | 753 |
Status cannot be transferred to node & at present due to RFC error | Space: object requires documentation | |
| 245 | 754 |
Sender specification is initial or syntactically incorrect | Space: object requires documentation | |
| 246 | 800 |
*** Error codes *** | ||
| 247 | 801 |
Status cannot be sent | ||
| 248 | 802 |
No delivery to &, as recipient unknown | ||
| 249 | 803 |
No delivery to &, as message expired | ||
| 250 | 804 |
No delivery to &, invalid transfer parameters | ||
| 251 | 805 |
No delivery to &, as too many recipients | ||
| 252 | 806 |
No delivery to &, invalid recipient address | ||
| 253 | 807 |
No delivery to &, as recipient is no longer valid | ||
| 254 | 808 |
No delivery to &, as no route known | ||
| 255 | 809 |
No delivery to &, as recipient cannot be reached at present | ||
| 256 | 810 |
No delivery to &, as max. transfer attempts failed | ||
| 257 | 811 |
No delivery to &, as part of message cannot be transferred | ||
| 258 | 812 |
No delivery to & | Space: object requires documentation | |
| 259 | 813 |
No delivery, as sender address & is invalid | Space: object requires documentation | |
| 260 | 814 |
No delivery, as type & of sender address is invalid | ||
| 261 | 815 |
No delivery, as reference & cannot be resolved | ||
| 262 | 816 |
Message cannot be transferred to node & due to connection error (final) | Space: object requires documentation | |
| 263 | 817 |
Cannot process message in SAP System | Space: object requires documentation | |
| 264 | 818 |
Cannot process message in node | Space: object requires documentation | |
| 265 | 819 |
Cannot process message in node, since recipient is invalid | Space: object requires documentation | |
| 266 | 820 |
Cannot process message in node, since message cannot be coded | Space: object requires documentation | |
| 267 | 821 |
Cannot process message in node, parameters cannot be converted | Space: object requires documentation | |
| 268 | 822 |
Message in node cannot be transferred to communication system | Space: object requires documentation | |
| 269 | 823 |
Node reports a system error, system was stopped | Space: object requires documentation | |
| 270 | 824 |
Cannot process message in node, as service & not available | Space: object requires documentation | |
| 271 | 825 |
Cannot process message, table & is not filled | ||
| 272 | 826 |
Cannot process message; no node determined for &2 | Space: object requires documentation | |
| 273 | 827 |
Cannot process message, node & is unknown | ||
| 274 | 828 |
Message cannot be processed due to missing authorizations | ||
| 275 | 829 |
Internal error: & & & & | ||
| 276 | 830 |
Message in node & cannot be processed due to release incompatibility | ||
| 277 | 831 |
Message cannot be processed: Invalid version specified (&) | ||
| 278 | 832 |
Message in node cannot be processed due to authorization problem | Space: object requires documentation | |
| 279 | 833 |
Status could not be assigned to a message or was not sent | ||
| 280 | 834 |
Message cannot be processed as it cannot be converted | ||
| 281 | 835 |
Message cannot be edited, send data cannot be determined | Space: object requires documentation | |
| 282 | 836 |
Send operation canceled by administrator | Space: object requires documentation | |
| 283 | 837 |
No delivery to &, as recipient cannot be reached at present | Space: object requires documentation | |
| 284 | 838 |
No delivery to & due to problems with system resources | Space: object requires documentation | |
| 285 | 839 |
No delivery to & due to problem with communication connection | Space: object requires documentation | |
| 286 | 840 |
No delivery to & because pager/SMS service returned an error | Space: object requires documentation | |
| 287 | 841 |
No delivery to & because message too long, maximum length & bytes | Space: object requires documentation | |
| 288 | 842 |
No delivery to & due unsuitable attachments | Space: object requires documentation | |
| 289 | 843 |
Message cannot be edited due to error during encryption or signing | Space: object requires documentation | |
| 290 | 844 |
No delivery to & as security requirements are not fulfilled | Space: object requires documentation | |
| 291 | 845 |
Message cannot be processed because Secure E-mail is not activated | Space: object requires documentation | |
| 292 | 846 |
Message cannot be processed because Secure E-mail possible by SMTP only | Space: object requires documentation | |
| 293 | 847 |
No delivery to &, as message contents incorrect | Space: object requires documentation | |
| 294 | 848 |
No delivery to &, as message type is not supported | Space: object requires documentation | |
| 295 | 849 |
Message cannot be processed as codepage information is missing | Space: object requires documentation | |
| 296 | 850 |
Cannot process message; maximum size exceeded | Space: object requires documentation | |
| 297 | 851 |
Message not editable since delivery address &1 is invalid | Space: object requires documentation | |
| 298 | 852 |
Message cannot be edited, sender address invalid | Space: object requires documentation | |
| 299 | 853 |
No delivery to &1, authentication required | Space: object requires documentation | |
| 300 | 854 |
Message cannot be edited, maximum number of send attempts reached | Space: object requires documentation | |
| 301 | 855 |
No delivery as sender or receiver address is invalid | Space: object requires documentation | |
| 302 | 856 |
No delivery to &1, authentication required | Space: object requires documentation | |
| 303 | 857 |
No delivery to &1 as logon data invalid | Space: object requires documentation | |
| 304 | 858 |
No delivery to &1 due to error with authentication | Space: object requires documentation | |
| 305 | 899 |
No information on delivery, status invalid | Space: object requires documentation |
History
| Last changed on/by | |
20141121 | SAP |
| SAP Release Created in |
