How To Fix FBZI226 - Request to be sent to bank created

SAP Error Message - Details

• Message type: E = Error

• Message class: FBZI - Payments via Internet

• Message number: 226

• Message text: Request to be sent to bank created

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FBZI226 - Request to be sent to bank created ?

  The SAP error message FBZI226, which states "Request to be sent to bank created," typically indicates that a payment request has been successfully generated in the SAP system but has not yet been sent to the bank for processing. This message is not necessarily an error but rather an informational message indicating the status of the payment request.
  Cause:
  
  Payment Request Created: The message is triggered when a payment run is executed, and the system has created a payment request file that is ready to be sent to the bank.
  Pending Transmission: The request is in a pending state, waiting for the next step in the process, which is usually the transmission of the payment file to the bank.
  Configuration Issues: There may be issues with the configuration of the payment medium or communication settings with the bank.
  
  Solution:
  
  Check Payment Medium: Ensure that the payment medium format is correctly configured in the SAP system. This includes verifying the settings in transaction code OBPM1 (Payment Medium Workbench).
  Transmit Payment Request: If the request is ready to be sent, you may need to execute the transaction to transmit the payment file to the bank. This can often be done through transaction code FBZ0 (Post Payment Run) or through the specific transaction for your bank's communication method.
  Review Logs: Check the logs for any additional messages or errors that may provide more context. You can use transaction code SLG1 to view application logs related to payment processing.
  Bank Communication: Ensure that the communication channel with the bank is properly set up and that any necessary credentials or configurations are in place.
  Consult Documentation: Refer to the SAP documentation or your organization's internal guidelines for handling payment runs and bank communications.
  
  Related Information:
  
  Transaction Codes:
  
  FBZ0: Post Payment Run
  FBZ5: Display Payment Run
  OBPM1: Payment Medium Workbench
  SLG1: Application Log
  
  
  Payment Medium Formats: Different banks may require different formats (e.g., SEPA, ACH). Ensure that the correct format is being used.
  Bank Master Data: Verify that the bank details in the vendor master data are correct and up to date.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to payment processing or the FBZI226 message.
  
  If the issue persists or if you need further assistance, it may be beneficial to consult with your SAP support team or a functional consultant specializing in financial processes.