How To Fix FINS_RECON679 - Inconsistency of open item flag between SKB1 and BSEG_ADD: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 679

• Message text: Inconsistency of open item flag between SKB1 and BSEG_ADD: &1 message(s)

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 FINS_RECON679 - Inconsistency of open item flag between SKB1 and BSEG_ADD: &1 message(s) ?

  The SAP error message FINS_RECON679 indicates an inconsistency between the open item flag in the SKB1 (G/L Account Master Data) and BSEG_ADD (Additional Document Segment) tables. This inconsistency can occur when the open item status of a G/L account does not match the status of the corresponding line items in the document segment.
  Cause:
  
  
  Data Inconsistency: The most common cause is a mismatch between the open item flag in the G/L account master data (SKB1) and the line items in the BSEG_ADD table. This can happen due to:
  
  Manual changes to the G/L account settings.
  Data migration or upload errors.
  Incomplete or incorrect postings that did not update both tables correctly.
  
  
  
  Custom Developments: If there are custom programs or enhancements that manipulate financial data, they might not be updating the open item status correctly.
  
  
  System Upgrades or Patches: Sometimes, inconsistencies can arise after system upgrades or patches if the data migration processes are not handled properly.
  
  
  Solution:
  
  
  Check Data Consistency:
  
  Use transaction codes like SE16 or SE11 to check the entries in the SKB1 and BSEG_ADD tables.
  Compare the open item flags in both tables for the affected G/L accounts.
  
  
  
  Correct the Inconsistency:
  
  If you find discrepancies, you may need to manually correct the open item flag in the SKB1 table or the corresponding entries in the BSEG_ADD table.
  Use transaction FB02 to change the document if necessary, ensuring that the open item status is updated correctly.
  
  
  
  Run Consistency Checks:
  
  Use the SAP standard report FINS_RECON to run consistency checks for financial documents. This report can help identify and resolve inconsistencies.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or recommendations for resolving this issue.
  
  
  
  Engage SAP Support:
  
  If the issue persists or if you are unsure about making changes, consider reaching out to SAP Support for assistance. They can provide guidance based on the specific details of your system and configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like FB03 (Display Document), FB02 (Change Document), and FBL3N (G/L Account Line Item Display) to analyze the documents and their statuses.
  Data Dictionary: Understanding the structure of the SKB1 and BSEG_ADD tables can help in troubleshooting.
  Backup: Always ensure that you have a backup of your data before making any changes to the database.
  
  By following these steps, you should be able to identify and resolve the inconsistency indicated by the FINS_RECON679 error message.