How To Fix FIN_FB_RECON391 - Shifted BUZEI between BSEG and NewGL Line item

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 391

• Message text: Shifted BUZEI between BSEG and NewGL Line item

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

For more information, see
<DS:URLA.HTTPS://LAUNCHPAD.SUPPORT.SAP.COM/#/NOTES/2714344>SAP Note
2714344.</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FIN_FB_RECON391 - Shifted BUZEI between BSEG and NewGL Line item ?

  The SAP error message FIN_FB_RECON391 indicates a discrepancy between the line items in the BSEG table (which stores accounting document segments) and the New General Ledger (New GL) line items. Specifically, the error suggests that there is a mismatch in the document number (BUKRS) and the line item number (BUZEI) between these two tables.
  Cause:
  
  
  Data Inconsistency: This error typically arises due to inconsistencies in the data between the classic General Ledger (G/L) and the New G/L. This can happen if:
  
  Documents were posted in the classic G/L and then migrated to the New G/L without proper synchronization.
  Manual changes were made to the line items in one of the ledgers without corresponding updates in the other.
  Errors during data migration or system upgrades.
  
  
  
  Document Splitting: If document splitting is enabled in the New G/L, discrepancies can occur if the splitting logic is not applied consistently across both ledgers.
  
  
  Custom Developments: Custom programs or enhancements that manipulate financial documents may inadvertently cause inconsistencies.
  
  
  Solution:
  
  
  Data Reconciliation: 
  
  Perform a reconciliation between the BSEG and New GL line items to identify the specific discrepancies. This may involve running reports or using transaction codes like FB03 (Display Document) to review the documents in question.
  Use transaction FBL1N (Vendor Line Item Display) or FBL3N (G/L Account Line Item Display) to check for inconsistencies.
  
  
  
  Correcting Entries: 
  
  If discrepancies are found, you may need to reverse or adjust the incorrect entries. This could involve posting correcting entries or using transaction FB08 (Reverse Document) to reverse erroneous postings.
  
  
  
  Data Migration Tools: If the issue arose during a migration process, consider using SAP's data migration tools or services to ensure that all data is correctly synchronized between the ledgers.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on resolving similar issues. SAP Notes can provide patches or recommendations for known issues.
  
  
  System Configuration: Review the configuration settings for both the classic G/L and New G/L to ensure they are aligned, especially regarding document splitting and posting rules.
  
  
  Engage SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for assistance. They may provide specific guidance based on your system configuration and version.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE16 (Data Browser) to view table contents, FB03 for document display, and FBL1N/FBL3N for line item displays.
  Tables Involved: Understand the structure of the BSEG and New GL tables (like ACDOCA) to better analyze the discrepancies.
  Documentation: Review SAP documentation on New G/L functionality, document splitting, and data migration best practices.
  
  By following these steps, you should be able to identify the root cause of the FIN_FB_RECON391 error and implement a solution to resolve it.