How To Fix FBZI201 - Message and request created

FBZI201 - Overview

• Message type: E = Error

• Message class: FBZI - Payments via Internet

• Message number: 201

• Message text: Message and request 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 FBZI201 - Message and request created ?

  The SAP error message FBZI201 ("Message and request created") typically indicates that a message has been generated in the system, often related to the processing of a financial document or transaction. This message is not necessarily an error but rather an informational message indicating that a request has been created for further processing.
  
  Cause:
  
  Document Processing: This message can occur during the processing of financial documents, such as invoices, payments, or other accounting entries.
  Batch Processing: It may also appear during batch processing jobs where multiple documents are being processed at once.
  Workflow Trigger: The message could be triggered by a workflow that requires further action or approval.
  
  
  Solution:
  
  Check the Message Log: Review the message log to understand the context in which the message was generated. This can provide insights into what action is required next.
  Follow Up on Requests: If the message indicates that a request has been created, check the status of that request.