How To Fix FB906 - Internal error: Error was noted but no memo records written

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 906

• Message text: Internal error: Error was noted but no memo records written

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 FB906 - Internal error: Error was noted but no memo records written ?

  The SAP error message FB906 ("Internal error: Error was noted but no memo records written") typically indicates that there was an internal issue during the processing of a financial transaction, particularly in the context of posting documents in the Financial Accounting (FI) module. This error can occur for various reasons, and while the exact cause may vary, here are some common causes, potential solutions, and related information:
  Causes:
  
  System Configuration Issues: There may be inconsistencies or misconfigurations in the system settings related to financial postings.
  Data Integrity Issues: Corrupted or inconsistent data in the database can lead to errors during document processing.
  Authorization Problems: The user may not have the necessary authorizations to perform the transaction.
  Program Errors: Bugs or issues in the underlying ABAP code or custom enhancements can lead to this error.
  Locking Issues: If another process is locking the necessary tables or records, it may prevent the transaction from completing successfully.
  
  Solutions:
  
  Check System Logs: Use transaction codes like SLG1 (Application Log) to check for detailed error logs that can provide more context about the issue.
  Review Configuration: Ensure that all relevant configuration settings in the FI module are correct and consistent.
  Data Consistency Check: Run consistency checks on the relevant tables to identify and resolve any data integrity issues.
  User Authorizations: Verify that the user has the necessary authorizations to perform the transaction.
  Debugging: If you have access to development tools, consider debugging the transaction to identify the exact point of failure.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve known issues.
  Contact SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP Support for assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB01 (Post Document), FB50 (G/L Account Document), and others that may be related to the transaction you are attempting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review SAP documentation related to financial postings and error handling for additional insights.
  
  Conclusion:
  The FB906 error can be frustrating, but by systematically checking the potential causes and applying the suggested solutions, you can often resolve the issue. If all else fails, leveraging SAP's support resources can provide the necessary guidance to address the problem.