How To Fix FIN_FB_RECON395 - Shifted BUZEI, but no posting via accounting interface

SAP Error Message - Details

• Message type: E = Error

• Message class: FIN_FB_RECON - Conversion to S/4HANA: Reconciliation

• Message number: 395

• Message text: Shifted BUZEI, but no posting via accounting interface

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 FIN_FB_RECON395 - Shifted BUZEI, but no posting via accounting interface ?

  The SAP error message FIN_FB_RECON395 typically indicates an issue related to the reconciliation of financial documents, specifically when there is a discrepancy in the document numbers or line items (BUZEI) during the posting process via the accounting interface. This error can occur in various scenarios, such as during the posting of financial documents, reconciliation processes, or when interfacing with other systems.
  Cause:
  
  Shifted BUZEI: This means that the line item number (BUZEI) in the document does not match the expected sequence. This can happen if there are gaps in the line item numbers due to deletions or if the document was modified after it was created.
  Missing Posting: The error suggests that there is an attempt to post a document that does not have a corresponding entry in the accounting interface, which could be due to a failed previous posting or an incomplete document.
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as incorrect document types, missing fields, or incorrect configurations in the accounting interface.
  
  Solution:
  
  Check Document Consistency: Review the document in question to ensure that all line items are correctly numbered and that there are no gaps. You can do this by checking the document in the SAP GUI.
  Repost the Document: If the document was not posted correctly, try reposting it. Ensure that all required fields are filled out correctly.
  Review Accounting Interface Settings: Check the configuration of the accounting interface to ensure that it is set up correctly and that it can handle the document types being posted.
  Analyze Logs: Use transaction codes like SLG1 (Application Log) to analyze logs for more detailed error messages that can provide insights into what went wrong during the posting process.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like FB03 (Display Document), FB02 (Change Document), and FB01 (Post Document) to manage and troubleshoot financial documents.
  Documentation: Review SAP documentation related to financial postings and the accounting interface for best practices and troubleshooting steps.
  User Roles: Ensure that the user attempting the posting has the necessary authorizations to perform the action.
  
  By following these steps, you should be able to identify the root cause of the FIN_FB_RECON395 error and implement a solution to resolve it.