/BSNAGT/MESSAGE - Message Class for BSN agent
The following messages are stored in message class /BSNAGT/MESSAGE: Message Class for BSN agent.
It is part of development package /BSNAGT/MASTER_DATA in software component LOD-FSN-AGT. This development package consists of objects that can be grouped under "BSN agent master data".
It is part of development package /BSNAGT/MASTER_DATA in software component LOD-FSN-AGT. This development package consists of objects that can be grouped under "BSN agent master data".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 |
| 001 | Inbound message data is not correct |
| 002 | Error during creation of message information |
| 003 | Error while signing data |
| 004 | Error while signing data: &1 |
| 005 | Error while encrypting data |
| 006 | Error while encrypting data &1 |
| 007 | Error while decrypting data |
| 008 | Error while decrypting data &1 |
| 009 | Error while verifying data |
| 010 | Error while verifying data &1 |
| 011 | No message generated |
| 012 | No profile found for Sender/Receiver ID &1 Message Type &2 |
| 013 | Payment proposal only; payment media not created |
| 014 | No status object found in CRM_JSTO for &1 |
| 015 | No entries found for the selection criteria |
| 016 | No BAdI implementation found for message type &1 |
| 017 | Error while updating the message information |
| 018 | Message &1&2 is empty or invalid |
| 019 | Error while sending message. |
| 020 | Message &1 sent by &2 |
| 021 | Message &1 updated |
| 022 | No variant found for Sender ID &1 Message Type &2 |
| 023 | Error while opening job |
| 024 | Job &1 created |
| 025 | Error while processing message &1&2 |
| 026 | No physical file found for logical file name |
| 027 | Error while accessing file &1 |
| 028 | &1 messages processed; &2 messages sent; &3 messages failed |
| 029 | Failed to lock file |
| 030 | Error while creating an instance of class /BSNAGT/CL_SECURITY_SSF |
| 031 | Error while converting text data to binary data |
| 032 | No messages found for archiving in the given selection criteria |
| 033 | Message &1 is archived |
| 034 | &1 messages marked for archiving |
| 035 | Message status is missing |
| 036 | Message status &1 not supported |
| 037 | Error while parsing file |
| 038 | &1 parse errors occurred in file &2&3 |
| 039 | Row &1, column &2, &3 |
| 040 | Format of CreationDateTime is incorrect in message &1&2 |
| 041 | Batch &1 status updated |
| 042 | Message &1&2 processed |
| 043 | You are not authorized to perform this action |
| 044 | Enter the Signatory/Recipient |
| 045 | Enter a valid status |
| 046 | Select exactly one line |
| 047 | No message status needs to be changed |
| 048 | Choose at least one security operation |
| 049 | No reference ID exists for the selected message |
| 050 | Error while updating the message &1 |
| 051 | Error while sending the message &1 |
| 052 | &1 messages can be archived; set the status in production mode |
| 053 | Error during determination of alternative logical port |
| 054 | Message &1 set to status 01 (Message marked for archiving) |
| 055 | Message &1 can be set to status 01 (Message marked for archiving) |
| 056 | Message &1 can be archived |
| 057 | &1 messages can be archived; run archive in production mode |
| 058 | &1 messages archived |
| 059 | Message &1 can be deleted |
| 060 | Message &1 deleted |
| 061 | Message &1 will be reloaded; run reload in production mode |
| 062 | Message &1 reloaded from archive |
| 063 | &1 messages can be deleted; run deletion in production mode |
| 064 | &1 messages deleted |
| 065 | &1 messages can be reloaded; run reload in production mode |
| 066 | &1 messages reloaded |
| 067 | Determination of number of records failed (Run: &1, &2) |
| 068 | Missing run information for determination of number of records |
| 069 | Unknown command &1 in &2 |
| 070 | Error while creating ping test; creation failed |
| 071 | Error while sending ping test; send failed |
| 072 | Error while updating ping test status; update failed |
| 073 | No ping test data found |
| 074 | Error while updating message; message not found |
| 075 | Error while generating message hierarchy |
| 076 | Data is incorrect |
| 077 | Error in related messages data |
| 078 | Ping request sent. |
| 079 | Error in free text editor |
| 080 | Cannot display message; message empty |
| 081 | Free text window is open already |
| 082 | Bank Communication Management functionality is not available |
| 083 | No navigation is available for ping test messages |
| 084 | Message does not have a related business object |
| 085 | No Sender ID found in Customizing for Message Type &1/Receiver ID &2 |
| 086 | Error during determination of ping request message |
| 087 | Corresponding ping request message not found |
| 088 | Corresponding ping test is already finished |
| 089 | No navigation to related application available |
| 090 | Free text message saved |
| 091 | Error while saving free text message; data not saved |
| 092 | No changes in free text message |
| 093 | Sender ID &1 not maintained in table /BSNAGT/T_SENDID |
| 094 | Save free text message |
| 095 | Free text message sent to Multi-Bank Connectivity |
| 096 | Error while sending free text message |
| 097 | Select only one message as the parent message of a text message |
| 098 | Error while checking GUID of parent message for text message |
| 099 | Parent message GUID for text message does not exist in the database |
| 100 | Failed to update the status and parent GUID for a text message |
| 101 | Failed to determine a related payment message |
| 102 | No parent message found |
| 103 | Illegal access to a string (offset+length too large) |
| 104 | Sending a message with status &1 is not permitted |
| 105 | Internal error in function module &1; contact system administrator |
| 106 | No application log found for the selected file |
| 107 | Error during transformation of extended header data |
| 108 | Free text message created by &1 |
| 109 | Free text message updated by &1 |
| 110 | Free text message sent by &1 |
| 111 | Error during message creation |
| 112 | No message content for ping test message |
| 113 | None of the selected messages could be sent. |
| 114 | No content generated for payment message |
| 115 | Batch number not found for the payment message |
| 116 | Error while sending payment message |
| 117 | No messages could be reprocessed |
| 118 | Physical path access failed &1 |
| 119 | Physical file read failed &1&2&3&4 |
| 120 | No preview available |
| 121 | Error while parsing file name &1&2&3&4 |
| 122 | File &1 &2 moved from directory &3 to &4 |
| 123 | Error while moving file &1&2&3&4 |
| 124 | File name is not valid: &1 |
| 125 | Created &1 messages, sent &2, ignored &3, moved &4 |
| 126 | Message updated to database |
| 127 | Message &1 created |
| 128 | File &1&2&3&4 picked up |
| 129 | Failed to open file &1&2&3&4 |
| 130 | Message reprocessed successfully |
| 131 | Reason code is blank |
| 132 | Parent message of one message is itself |
| 133 | &1 messages set to processed status. |
| 134 | Select the messages to be sent. |
| 135 | Multiple BAdI implementations found for message type &1 |
| 136 | Error during creation of file name |
| 137 | IDoc &1 successfully sent to Multi-Bank Connectivity |
| 138 | Error while extracting bulk message; Message ID &1, Sender ID &2, Tag &3 |
| 139 | Bulk message extracted; Message ID &1, Sender ID &2 |
| 140 | Error while encoding message content; base64 encode error |
| 141 | Error while decoding message content; base64 decode error |
| 142 | Duplicate message - &1 messages found (&2 / &3 / &4) |
| 143 | Error while converting date &1 and time &2 to UTC format |
| 144 | Job finished successfully |
| 145 | Job scheduled successfully |
| 146 | Enter correct date/time format |
| 147 | Error during extraction of bulk message |
| 148 | Duplicate Message GUID &1 saved into database but not processed again |
| 149 | Duplicate message; MessageID &1 SenderID &2 failed to save to database |
| 150 | Bulk message saved |
| 151 | Bulk message database check failed |
| 152 | Message inserted into database with GUID &1 |
| 153 | Message with GUID &1 sent successfully |
| 154 | Failed to insert message into database |
| 155 | Error while converting XML message content to DDIC structure |
| 156 | No sending/receiving details available |
| 157 | Bulk message extracted successfully |
| 158 | &1 messages extracted from bulk message &2 |
| 159 | Message with message ID &1 sender ID &2 processed successfully |
| 160 | Error while processing MBC Message: Message ID &1 SenderID &2 |
| 161 | Enter the required data for your selected option |
| 162 | Ignoring duplicate file name &1&2&3&4 |
| 163 | Base64 decoding failed; displaying original message content |
| 164 | Error in application parameter settings for message type &1 SSID &2 |
| 165 | Check handler class method DETERMINE_HEADER_FIELDS for message type &1 |
| 166 | No security features active in SSF Customizing for MessageType &1 SSID &2 |
| 167 | Provide a fixed value for Message Type |
| 168 | No Sender ID provided in pick-up report; using default value |
| 169 | No Receiver ID provided in pick-up report; using default value |
| 170 | Related message ID &1 not found; no relation created for message ID &2 |
| 171 | Select both sign and verify |
| 172 | Select both encrypt and decrypt |
| 173 | Resending ping is not supported; create a new ping request |
| 174 | Receiver ID is not allowed to be empty while sending |
| 175 | Error while converting file codepage: file name &1 |
| 176 | IDoc &1 successfully handed to MBC Connector |
| 177 | Duplicate message; MessageID &1 SenderID &2 not saved during reprocessing |
| 178 | Failed to change status of some messages |
| 179 | No message selected |
| 180 | Error during creation of Pull-Receipt(s). |
| 181 | Message &1 was sent to the Multi-Bank Connectivity |
| 182 | Error during creation of extended header tag &1 |
| 183 | Error during determination of gv_exnm in /BSNAGT/PAYM_OPEN |
| 184 | Transport layer status displayed for &1 records only |
| 185 | &1 messages removed from processing/sending (from &2 selected messages) |
| 186 | Error while saving message to database |
| 187 | Error during conversion of binary data to text data (Message ID &1) |
| 188 | Bulk &1 received with &2 messages |
| 189 | Triggering the processing of &1 messages |
| 190 | Error during determination of payment transactions |
| 191 | Creation of fingerprint failed |
| 192 | Critical field &1 is initial or was not found |
| 193 | Error during determination of critical fields |
| 194 | Creating fingerprints for &1 transactions |
| 195 | Error during XML processing |
| 196 | Implementation error; &1 should not be called directly |
| 197 | Error during critical fields check; invalid &1 "&2" |
| 198 | Error during critical fields check; invalid &1 "&2" (Transaction ID &3) |
| 199 | Errors during critical fields check (Transaction ID &1) |
| 200 | Number of records (&1) differs from transactions found (&2) |
| 201 | Invalid file name "&1" |
| 202 | Invalid Sender ID "&1" |
| 203 | Invalid Receiver ID "&1" |
| 204 | File &1 uploaded; MBC Message created |
| 205 | Creating MBC Message for format &1 (&2). |
| 206 | Error during sending of Pull-Request to MBC. |
| 207 | Logical Port determined for sending MBC Message: &1 |
| 208 | Logical Port determined for sending receipt messages: &1 |
| 209 | Logical Port determined for sending request message: &1 |
| 210 | MessageContent decrypted. |
| 211 | MessageContent verified. |
| 212 | MessageContent signed. |
| 213 | MessageContent encrypted. |
| 214 | MBC Message created via API. |
| 215 | MBC Message received asynchronously. |
| 216 | No detail information available. |
| 217 | Error during processing of pull response message. |
| 218 | MBC Message created via workstation upload by user &1. |
| 219 | No authorization for transaction &1 |
| 220 | Receiver ID &1 replaced with &2. |
| 221 | Payload of MBC Message &1 displayed/downloaded by user &2 |
| 222 | Enter a MBC Message GUID and press Enter to read its content category. |
| 223 | You are not authorized to display MBC Messages (auth object FILE_MONI) |
| 224 | MBC Message read. Execute report to adjust content category. |
| 225 | You are not authorized to change MBC Messages (auth object FILE_MONI) |
| 226 | Content Category changed from &1 to &2 by user &3. |
| 227 | To really write changes to DB set the save parameter. |
| 228 | &1 is not a valid content category. |
| 229 | Inbound security executed by user &1. Results written to DB. |
| 230 | Error during processing in BCM. Please see app log for more details. |
| 231 | Payload handed over to BCM for processing. Return Code &1. |
| 232 | BCM return code (sy-subrc): &1 / Exception name: &2 |
| 233 | &1 &2 line endings found in payload. |
| 234 | MT940 Payload split by &1 |
| 235 | Using variant &1 for report &2 |
| 236 | Payload split by &1 |
| 237 | Relevant BCM functions not found. Please check BCM SP level and notes. |
| 238 | Inbound handler used for processing: &1 |
| 239 | Physical filename &2 determined from logical filename &1. |
| 240 | Error during determination of physical filename from logical filename &1 |
| 241 | Downloading MBC Message payload to application server file. |
| 242 | File &1 already exists. The existing file will not be overwritten. |
| 243 | Payload written to file &1. |
| 244 | Error opening file &1 for binary write access. |
| 245 | &1 bytes transferred. |
| 246 | Message ID &1 not found. |
| 247 | Missing parameter &1 in ExtendedHeader. |
| 248 | Unknown message status code &1 in ExtendedHeader. |
| 249 | No UETR found in ExtendedHeader. |
| 250 | Transition of status &1 to status &2 is not allowed. |
| 251 | Status of related message &1 not updated. |
| 252 | BCM Batch Number: &1 |
| 253 | Approval user &1 signed. |
| 254 | Approval user &1 not signed. |
| 255 | Creation of extended header failed. |
| 256 | Processing result of Bank Fee Analysis update: &1 |
| 257 | Technical error during Bank Fee Analysis update. |
| 258 | Bank Fee Analysis updated. |
| 259 | Error submitting report &1 as job &2 (SUBRC=&3). |
| 260 | MessageType &1 is not valid. |
| 261 | MessageType &1 is not allowed in scenario &2. |
| 262 | No Logical System found for client. LogicalSystem param not added. |
| 263 | No MessageType determined during creation of MBC Message via PMW. |
| 264 | MBC Message &1 cannot be sent because it has no MessageType set (&2). |
| 265 | Processing Step &1 finished with status &2. |
| 266 | Error during insert/update of DB table &1. |
| 267 | Invalid direction &1. |
| 268 | Base64 encode error; Payload of message &1 is already base64 encoded. |
| 269 | Base64 decoding error; Message &1 is not base64 encoded. |
| 270 | Package/Program &1/&2 is no valid ABAP program. |
| 271 | Original Message ID &1 found in payload. |
| 272 | Batch Number &1 found with RENUM &2. |
| 273 | No Processing Steps found for MessageType &1. |
| 274 | Message &1 set to status "For Manual Processing" |
| 275 | Step status updated to &1 according to status of job &2 |
| 276 | Job &1 not found. Step &2 updated to error status. |
| 277 | Job &1 created. |
| 278 | No inbound handler implementation found for application type &1 (step &2) |
| 279 | Several Messages found for Message ID &1. Status cannot be updated. |
| 280 | Error: Invalid value for parameter &1 |
| 281 | Pull Job is locked by User &1 |
| 282 | No processing steps defined. |
| 283 | Processing of steps triggered. |
| 284 | No step selected. |
| 285 | Selection restricted to &1 entries. |
| 286 | &1 entries selected. |
| 287 | Step &1 / &2 not found. |
| 288 | Status of Step &1 updated to &2. |
| 289 | Processing of step &1 triggered by user &2. |
| 290 | Processing of message &1 started by user &2. |
| 291 | Message GUID &1 not found |
| 292 | Payload cannot be displayed. Use download instead. |
| 293 | No MessageType mapping rule found. |
| 294 | UETR &1 received from payment run. |
| 295 | No UETR received from payment run. |
| 296 | No Reference ID found for selected messages. |
| 297 | AIF Configuration not found. |
| 298 | AIF Content for MBC Connector is already active. |
| 299 | Pull job scheduled. |
| 300 | Pull Job finished with status &1 |
| 301 | Error during creation of Message ID via number range &1 - &2. |
| 302 | Connector Monitor switched to test mode. |
| 303 | Connector Monitor switched to productive mode. |
| 304 | UETR &1 received via MBC Status message &2. |
| 305 | Related Message &1 already has UETR &2. No UETR update will take place. |
| 306 | Related Message &1 found for MBC Status message &2. |
| 307 | Status &1 found in MBC Status message &2 |
| 308 | Starting Processing Step &1 |
| 309 | Message &1 directly set to status &2 - &3 by user &4. |
| 310 | Status of message &1 changed to &2 - &3 after updating pending steps. |
| 311 | Message &1 has no Message Content. No inbound security will be applied. |
| 312 | Deletion of Message Type &1 not allowed |
| 313 | No conversion required (from/to codepage is &1) |
| 314 | Error during conversion of codepage (from &1 to &2) |
| 315 | Codepage &1 read from message |
| 316 | Codepage &1 written to message &2 |
| 317 | Codepage conversion executed (&1 to &2) for message &3 by user &4. |
| 318 | Canceled. |
| 319 | Existing codepage equals new codepage (&1). No change required. |
| 320 | No Codepage set. |
| 321 | Codepage conversion not possible for content category &1 |
| 322 | Codepage converted from &1 to &2 during outbound processing (message &3). |
| 323 | Refresh of Processing Step triggered |
| 324 | Defaulting codepage to &1 |
| 325 | Document &1 &2 not found. |
| 326 | &1 messages found with RelatedMessageId &2. |
| 327 | This message has no RelatedMessageId. |
| 328 | No related message found with ID &1. |
| 329 | Content Category &1 read from message. |
| 330 | Security attributes read from message. |
| 331 | Please select an entry from the list. |
| 332 | Message &1 was not sent yet. Please use normal Send function. |
| 333 | Sending again no longer possible. Latest Send-Again-Date was: &1 |
| 334 | Security related attributes reset by user &1 |
| 335 | Message &1 will be sent again. Triggered by user &2. |
| 336 | Message &1 sent again. Triggered by user &2. |
| 337 | Message successfully validated. |
| 338 | Message &1 created from Temse Data by user &2. |
| 339 | Conversion to character using codepage &1 triggered by user &2. |
| 340 | Reading XML Messages failed. Return Code &1 / &2 |
| 341 | No XML Messages found. |
| 342 | &1 XI Queues used by &2 checked MBC Messages. |
| 343 | &1 relevant XI Queues in status SYSFAIL. |
| 344 | &1 Messages found but only &2 messages will be selected. |
| 345 | Message content compressed (before: &1, after &2) |
| 346 | Message content decompressed (before &1, after &2) |
| 347 | Error during decompression of Message Content. |
| 348 | Error during compression of Message Content. |
| 349 | Action can only be performed for incoming messages |
| 350 | Action can only be performed for outgoing messages |
| 351 | Message filename &1 replaced with archive filename &2 |
| 352 | Error during reading the job log of &1 / &2 |
| 353 | Message &1 set to status &2 - &3 as BCM is not active. |
| 354 | &1 Swift Parameters added according to configuration. |
| 355 | Swift parameter &1 expected but not found. |
| 356 | &1 files found in zipped payload of message &2 |
| 357 | Message &1 created as sub message of message &2 |
| 358 | Message &1 updated to status &2 after decompression of &3 files. |
| 359 | No related message exists |
| 360 | No file found in compressed payload of message &1 |
| 361 | Message Content Decompressed by user &1 |
| 362 | &1 file(s) extracted. &1 sub messages created. |
| 363 | &1 Short IDs created during upload of bank statement. |
| 364 | Decompress Category &1 determined from configuration for message &2. |
| 365 | No Short Keys created during bank statement upload. |
| 366 | This message has several steps. Use the steps dialog for navigation. |
| 367 | &1 entries filtered/removed from pickup list. |
| 368 | &1 files found at pickup source directory. |
| 369 | &1 entries removed from pickup list due to pickup duplicate check. |
| 370 | &1 messages created. |
| 371 | &1 files moved to target directory. |
| 372 | &1 messages sent. |
| 373 | Message &1 created via Pickup report. |
| 374 | Expiration Date defaulted to &1 |
| 375 | Expiration date calculated for &1 messages. |
| 376 | No MBC Status Overview available. |
| 377 | MBC Status: &1&2&3&4 |
| 378 | No Message Content found. |
| 379 | Only select alerts containing a message ID |
| 380 | Routing message &1 locally. |
| 381 | Message &1 created via local routing from outgoing message &2. |
| 382 | Local Loop Count too high (&1). Please check routing configuration. |
| 383 | Message &1 created via Forwarding of message &2 |
| 384 | No relevant scope item is active. |
| 385 | Scope Item &1 is not active. |
| 386 | Scope Item &1 active. |
| 387 | Payloads of Ping Request and Ping Response messages do not match. |
| 388 | No payload contained in ping response &1 |
| 389 | Variant check failed. Report &1 not found. |
| 390 | Error during variant check (Report &1, Variant &2) |
| 391 | Pull Log status updated for job &1 / &2 |
| 392 | Sensitive Payload Flag set according to extended header parameter. |
| 393 | Sensitive Payload Flag set according to configuration. |
| 394 | You are not authorized to display sensitive data. |
| 395 | Sensitive Payload |
| 396 | Error, neither Message Content nor Logical File Name found. |
| 397 | Processing before Inbound Handling executed. |
| 398 | Processing before Inbound Handling for message &1 started by user &2. |
| 399 | Update Pending Step &1 of Message &2 |
| 400 | Error during update of pending step &1 of Message &2. |
| 401 | Error during XML parsing in &1 |
| 402 | Payload length after security is &1 (was &2 before security) |
| 403 | The successful verification resulted in a 0-length payload. |
| 404 | Outgoing Message has &1 files. The Message cannot be decompressed. |
| 405 | Error during conversion of Bank Statement Request. |
| 406 | Bank Statement Request message &1 created by user &2. |
| 407 | Parameter &1 received: &2 |
| 408 | Error during determination of SAP codepage by external codepage &1 |
| 409 | Statement was requested as a copy. No automatic processing. |
| 410 | This statement was requested by Bank Statement Request &1 |
| 411 | No alert configuration entries found. |
| 412 | CDS selection counted &1 entries, DB selection &2 entries. |
| 413 | &1 messages set to obsolete status. |
| 414 | Message &1 set to status Obsolete because of proposal run paym. creation. |
| 415 | Payment Proposal. MBC Message will be set to Obsolete status. |
| 416 | No Download Settings found. Default values are being used for download. |
| 417 | Message &1 created via Web API. |
| 418 | Switch ID &1 not found in configuration. |
| 419 | Message received via RFC interface. |
| 420 | Message received from logical system &1 |
| 421 | Origin Application Type defaulted to &1 |
| 422 | Sending message &1 via RFC API failed (error &2). |
| 423 | Unexpected routing category &1 |
| 424 | RFC API is not available. |
| 425 | MBC-Status &1 received for outgoing message &2. |
| 426 | Sender ID mapped from &1 to &2 |
| 427 | Receiver ID mapped from &1 to &2 |
| 428 | &1 / &2 is not a valid house bank. |
| 429 | Please select a statement category. |
| 430 | Bank Statement Request created. |
| 431 | Error during initialization of HTTP API with destination &1 |
| 432 | Error during sending of HTTP request (&1) |
| 433 | HTTP status &1 received during HTTP API call. |
| 434 | No CSRF Token could be fetched. |
| 435 | Error during receiving HTTP API response (&1). |
| 436 | Payload is not character based (Content Category: &1). |
| 437 | &1 pulled messages sorted by &2 |
| 438 | No sorting as one or more messages do not have &1 |
| 439 | &1 messages received as response to sending of message &2 |
| 440 | No RFC-API Settings found (Receiver-ID &1 / Origin &2) |
| 441 | Sending via RFC Destination &1 |
| 442 | Ping Response Message &1 created for Ping Request Message &2 |
| 443 | Message &1 collected for later sending. |
| 444 | Routing Category &1 determined for message &2 |
| 445 | Message &1 send as synchronous response via RFC interface. |
| 446 | Waited &1 seconds for parallel job to finish. |
| 447 | You are not authorized to display the details of batch &1 |
| 448 | You are not authorized to display item details of rule &1 |
| 449 | Neither a Parameter Set nor a Variant found for message &1 |
| 450 | Using parameter set &1 for report &2 |
| 451 | Pull Type &1 not found. |
| 452 | No Pull Type found. |
| 453 | Line &1 of CSB43 Statement exceeds length of &2 characters. |
| 454 | Duplicate Message - Inbound Handling not triggered (MessageId &1) |
| 455 | Processing of duplicate message &1 triggered by user &2 |
| 456 | Message &1 is corrupted and cannot be processed. |
| 457 | Parameter &1 not found in ExtendedHeader. |
| 458 | Error reading approval users. |
| 459 | No EBICS Order Type determined (&1) |
| 460 | EBICS Order Type &1 determined (&2). |
| 461 | Invalid activity &1 for authorization object &2. |
| 462 | No approver settings found for &1 |
| 463 | The Receipts RelatedMessageId &1 doesn't match the sent MessageId &2 |
| 464 | Sending Send-Receipts/Acks via RFC Destination &1 |
| 465 | Pulling via RFC Destination &1 (Pull Type &2) |
| 466 | RFC Destination &1 used for Pull Receipts/Acks (Pull Type &2) |
| 467 | No Receipt Message (Ack) received during send of message &1. |
| 468 | &1 messages received in send response. |
| 469 | &1 messages marked as Expired. |
| 470 | No EBICS Order Type configuration entry found. |
| 471 | XML Transformation Error - &1 |
| 472 | Related message &1 has status &2 and cannot be updated. |
| 473 | Routed Locally |
| 474 | Message sent to &1 |
| 475 | Message received from &1 |
| 476 | Message received by &1 |
| 477 | Error sending Send-Receipts (Send Acks) |
| 478 | Error sending Message via HTTP-API (Send Request) |
| 479 | &1 invalid characters contained in Message ID: &2 |
| 480 | Receiver ID defaulted to &1 |
| 481 | Due to local routing no outbound security is applied. |
| 482 | This pain.002 payload is not relevant for BCM. |
| 483 | Expiration date &1 calculated for message &2 |
| 484 | Check-only mode is active. |
| 485 | Error reading step result. |
| 486 | Payload of message &1 is already character based (content category &2) |
| 487 | Payload of message &1 is already binary (content category &2). |
| 488 | Updated &1 steps of &2 messages. |
| 489 | You are not authorized to display/download payload of message &1 |
| 505 | Error during reading of parameter set &1 |
| 507 | Pull Lock set. |
| 508 | Pull Lock removed. |
| 509 | Invalid Step Config: Step Number &1 occurrs multiple times (&2) |