FBZI - Zahlungswesen �ber das Internet
The following messages are stored in message class FBZI: Zahlungswesen �ber das Internet.
It is part of development package FBZI in software component FI-BL-PT. This development package consists of objects that can be grouped under "Payments via Internet".
It is part of development package FBZI in software component FI-BL-PT. This development package consists of objects that can be grouped under "Payments via Internet".
Message Nr ▲ | Message Text |
---|---|
100 | >>> OFX-specific Messages <<< |
101 | One field in line & is too long |
102 | Syntax error in line &1 &2. |
103 | OK! (test for the test program ofx_test) |
104 | Day &1 could not be found |
105 | Day &1 from line &2 could not be assigned to a field |
106 | &1 lines were added |
150 | The required entry field &1 in &2 structure is empty |
151 | There is no entry in parameter &1 of function &2 |
200 | >>>> Internet Banking Messages During Processing <<<<< |
201 | Message and request created |
202 | Request sent |
203 | Unable to connect to bank |
204 | OFX: SignOn data cannot be converted from OFX format to SAP format |
205 | Error in HTTP address: Server error at bank |
206 | Error in HTTP address: Client error - incorrect request data |
207 | Error in HTTP address (unknown error) |
208 | Error creating the request |
209 | Response created |
210 | Error creating the response |
211 | Response successfully converted to SAP format |
212 | Error converting response |
213 | Application error when processing response |
214 | Message set missing for logical address &1 and accounting transaction &2 |
215 | OFX message sets &1 and &2 cannot be used for accounting transaction &3 |
216 | OFX application function module missing for accounting transaction & |
217 | Attributes for logical address & are not maintained |
218 | Physical address for logical address & is not maintained |
219 | Attributes for OFX version & are not maintained |
220 | No OFX message sets are maintained for logical address & |
221 | Error: Response cannot be processed any further |
222 | OFX partner for house bank &1 &2 not found |
223 | Response received from bank (HTTP address OK) |
224 | Error in HTTP address: Client error: Invalid URL (WWW address) |
225 | Error in HTTP address: Client error |
226 | Request to be sent to bank created |
227 | Request sent to bank |
228 | Response received from bank |
229 | Response transferred to application |
230 | Response successfully processed by the application |
231 | Response re-transferred to the application |
232 | Request to be resent to bank |
233 | Error occurred during processing by application; repetition not possible |
234 | Error occurred during processing by application; repetition possible |
235 | HTTP address contains an error: HTTP status & status text: & |
236 | Error connecting to bank (incorrect user or password) |
237 | This option is not permitted for messages with status & |
238 | Message manually set to completed by user & |
239 | Message contained errors; no repetition possible |
250 | Error occurred in password encryption for function module & |
280 | >>>> Messages during message display <<<< |
281 | No messages found for the selection criteria entered |
282 | No authorization exists for the display of messages |
300 | >>>>>> Messages in ABAP Objects Classes CL_*_FIEB <<<<<< |
301 | Element in list not found |
302 | Element not found in list, the element was not deleted. |
303 | Object belonging to class & could not be created |
304 | Status object with ID & could not be loaded |
305 | Request with ID & could not be found |
306 | Response with ID & could not be found |
307 | No request found for the message object |
308 | No response found for the message object |
309 | You do not have authorization for the required action |
350 | >>>>>> Messages for OFX Account Statement <<<<<<<<<<< |
351 | Statement for this account already processed today |
352 | Bank reports error during OFX transaction "Account statement" |
353 | You are not authorized to request a statement for this account |
400 | >>>>>>>>> Messages for the OFX payment <<<<<<<<<< |
401 | The country/region with country/region key &1 does not exist |
402 | No 3-character ISO code exists for country/region with c/r key &1 |
403 | Bank reports error in OFX transaction "payment" |
404 | Payment not carried out because the data is from the payment proposal |
405 | The data necessary for the check register could not be read |
406 | The check number could not be written in the check register |
410 | OFX code 0: Payment successful |
411 | OFX code 2000: General error |
412 | OFX code 2002: Bank account general error |
413 | OFX code 2006: Bank account of the payer not found |
414 | OFX code 2007: Bank account of the payer is closed |
415 | OFX code 2008: No authorization for bank account of the payer |
416 | OFX code 2009: Bank account of the payment recipient not found |
417 | OFX code 2010: Bank account of the payment recipient is closed |
418 | OFX code 2011: No authorization for bank account of the payment recipient |
419 | OFX code 2012: Invalid amount |
420 | OFX code 2014: Date is too early |
421 | OFX code 2015: Date is too far in the future |
422 | OFX code 2016: Payment already confirmed |
423 | OFX code 2017: Payment already deleted |
424 | OFX code 2018: Server ID is unknown |
425 | OFX code 2019: Payment sent several times |
426 | OFX code 10501: Invalid payment recipient |
427 | OFX code 10502: Invalid address of the payment recipient |
428 | OFX code 10503: Invalid account number of the payment recipient |
429 | OFX code 10505: Not possible to modify the element |
430 | OFX code 10510: The ID of the payment recipient is invalid |
431 | OFX code 10511: The town of the payment recipient is invalid |
432 | OFX code 10512: The region of the payment recipient is invalid |
433 | OFX code 10513: The postal code of the payment recipient is invalid |
434 | OFX code 10517: The name of the payment recipient is invalid |
435 | OFX code 10519: The ID of the payment recipient list is invalid |
436 | An unknown error occurred during OFX transmission |
437 | &1 payments were sent of which &2 were successful and &3 were erroneous |
441 | The account number of the paying bank account is missing |
442 | The payment amount is missing |
443 | The name of the payment recipient is missing |
444 | The address of the payment recipient is missing |
500 | >>> Messages re: Storing of FI Messages with KPro (FG: FPIS) <<< |
501 | Error creating a logical object of class &1 using SAP Knowledge Provider |
502 | Error creating a physical object of class &1 using SAP Knowledge Provider |
503 | Physical object &1 could not be locked |
504 | Error storing data of phyical object & |
505 | Error creating a new version of physical object & |
506 | Unable to determine most recent FI request of FI message & |
507 | Unable to determine most recent FI response for FI message & |
508 | Error determining requests/responses for FI message & |
509 | Error creating a status object |
510 | Error updating a status object |
511 | Error deleting a status object |
512 | Error reading the FI message & |
513 | Error setting the attributes for FI message & |
600 | Invalid class ID & when reinstantiating the object |
601 | The object with class ID & could not be registered. |
602 | The object having class ID & could not be found. |
603 | The object & could not be blocked |
604 | The status of an object belonging to class &1 could not be updated |
605 | New object having class ID &1 could not be registered. |
650 | Error occurred when displaying messages |
700 | Password contains one or more invalid characters |
701 | One password with identifier &1 already exists. |
702 | The password could not be entered |
703 | No password for the identifier &1 exists |
704 | The password could not be changed |
705 | No password for the identifier &1 exists |
706 | Identifier &1 does not exist |
707 | Technical error during deletion of identifier &1 |
801 | Technical error when writing data to database |
802 | Technical error when writing data to database |