Id | Title |
---|---|
XS088 | Error (&) in monitor display. Monitor name = &. |
XS089 | Node no longer exists. |
XS090 | Data collection method for SAPphone ran with no errors. |
XS091 | Data collection method was completed with errors (error code &) |
XS092 | Data collection method for SAPconnect ran with no errors. |
XS093 | Data collection method could not be started. |
XS094 | Action cannot be executed because ESMTP plug-in XString empty |
XS095 | SMTP Node Cannot Be Deleted or Copied |
XS096 | SMTP Node Is Not Available |
XS097 | Specify Mail Host and Mail Port for Node |
XS098 | Queue for incoming messages is active |
XS099 | Queue for incoming messages deactivated |
XS100 | Enter password consistently |
XS101 | Conversion into character set selected or no character set specified |
XS102 | Address areas without special characters saved since not relevant |
XS103 | Specify at least one address area |
XS104 | A send process is already running for &1/prio &2 |
XS105 | Error occurred when locking the send dispatcher |
XS106 | Send process started asynchronously: Package &1; No.: &2; Destination: &3 |
XS107 | Starting send process locally: Package &1 number: &2 |
XS108 | Package &1; Number: &3; Destination: &2 |
XS109 | Waiting for aRFC: Maximum wait time of &1 exceeded |
XS110 | Package &1 processed; duration: &2; &3 requests sent |
XS111 | Error in package &1: &2 |
XS112 | Wait time exceeded |
XS113 | Job data saved |
XS114 | Unable to save job data |
XS115 | Job deleted |
XS116 | Job currently being processed by user & |
XS117 | Unable to find job; refresh display |
XS118 | Error occurred when calling &1; return code &2 |
XS119 | Job data not changed |
XS120 | Job selection unclear; refresh display |
XS121 | No messages sent |
XS122 | Variant saved |
XS123 | Variant & already exists |
XS124 | Active jobs cannot be deleted |
XS125 | Only one server group can be selected within a transaction |
XS126 | No values were changed |
XS127 | Server group is not relevant for a work process |
XS128 | Specify a target format |
XS129 | The data has been transferred |
XS130 | Data already exists |
XS131 | Specify a device type |
XS132 | Device type and formats are not compatible |
XS133 | Device type for conversion is different from OTF device type |
XS134 | No device type exists for format &1 |
XS135 | Determined device type: &1. &2 &3 |
XS136 | Generic internet addresses with special characters are not allowed |
XS137 | MIME version does not exist |
XS138 | Email address & is invalid |
XS142 | Complete your input |
XS143 | There is already an entry in language & |
XS144 | Error in monitor display; check your input |
XS195 | A |
XS196 | B |
XS197 | C |
XS198 | D |
XS199 | E |
XS200 | *** SAPconnect XPRA&: &(&) *** |
XS201 | XPRA & does not run under Release & |
XS202 | XPRA processing not required for online, program terminated |
XS203 | XPRA log cannot be saved due to system error |
XS204 | Database error preventing action & in table & |
XS205 | No nodes defined, SAPconnect initialized |
XS206 | No nodes support sending externally |
XS207 | XPRA debug note: & |
XS208 | XPRA & for converting & ran successfully |
XS209 | No Node Exists Whose RFC Destination Must Be Converted |
XS210 | No Node Exists Whose Formatting Must Be Converted |
XS211 | No RFC Destination Is Maintained for Node &, Retrieve Entry |
XS300 | *** SAPconnect - Spool - Connection *** |
XS301 | Output request for device &1, user &2 |
XS302 | Formatted data (&1 bytes, from row &2, &3 rows) |
XS303 | Text data (from line &1, &2 lines) |
XS304 | Spool request with ID &1 generated |
XS305 | Error occurred when creating spool request (&1 &2 &3 &4) |
XS370 | *** Messages for routing details *** |
XS371 | Step 2: Determine node |
XS372 | Step 3: Convert address into an external format |
XS373 | Step 1: Check entered addresses |
XS374 | In this step, the following error was identified: |
XS375 | No error in this step |
XS376 | Step 4: Creation of a Test URL (Only with HTTP Nodes) with Dummy Data |
XS377 | &1 |
XS378 | Checking/converting following address: Type=&1, Address=&2 |
XS379 | No sender specified, therefore CDG routing not possible |
XS380 | Sender &1 is assigend to the following sender group (CDG):&2 |
XS381 | Following sender was assigned to no sender group: &1 |
XS382 | Number of limited, relevant routing entries: &1 |
XS383 | A fully qualified entry was found in the routing table: |
XS384 | Sender group (if one exists): &1 |
XS385 | Address type and address value (shortened): &1 &2 |
XS386 | Node: &1 |
XS387 | Node cannot be used because it is not active |
XS388 | Searching for most suitable routing entry... |
XS389 | The following more suitable node was found: &1 |
XS390 | Following entry was not suitable: &1 |
XS391 | Search was ended |
XS392 | Search with CDG parameter '&1' was unsuccessful |