How To Fix FINS_RECON517 - &1: Mismatch of Field &2 between NewGL line item (&3) and BKPF/BSEG (&4)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 517

• Message text: &1: Mismatch of Field &2 between NewGL line item (&3) and BKPF/BSEG (&4)

What causes this issue?

This check compares field from entry view (BKPF, BSEG or BSEG_ADD) and
the NewGL line items (like FAGLFLEXA). The field &V2& differs. It is
&V3& in the NewGL line item and &V4& in either BKPF or BSEG
respectivelyBSEG_ADD.

System Response

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

How to fix this error?

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 FINS_RECON517 - &1: Mismatch of Field &2 between NewGL line item (&3) and BKPF/BSEG (&4) ?

  The SAP error message FINS_RECON517 indicates a mismatch between the fields in the New General Ledger (NewGL) line item and the corresponding entries in the BKPF (Accounting Document Header) and BSEG (Accounting Document Segment) tables. This error typically arises during reconciliation processes or when trying to post documents that involve both NewGL and classic GL.
  Cause:
  The mismatch can occur due to several reasons, including:
  
  
  Data Inconsistency: There may be inconsistencies in the data between the NewGL line items and the classic GL tables (BKPF/BSEG). This can happen if there were manual changes or if data was not properly migrated during a system upgrade or conversion.
  
  
  Configuration Issues: Incorrect configuration settings in the NewGL or classic GL can lead to discrepancies in how data is stored or processed.
  
  
  Document Splitting: If document splitting is enabled, there may be issues with how the splitting is handled, leading to mismatches in the fields.
  
  
  Custom Developments: Any custom programs or enhancements that manipulate financial data could inadvertently cause mismatches.
  
  
  Solution:
  To resolve the FINS_RECON517 error, you can take the following steps:
  
  
  Check Data Consistency:
  
  Use transaction codes like SE16 or SE11 to examine the BKPF and BSEG tables for the specific document numbers mentioned in the error message.
  Compare the fields in the NewGL line item with those in BKPF/BSEG to identify the specific discrepancies.
  
  
  
  Review Configuration:
  
  Ensure that the configuration settings for NewGL and classic GL are correctly set up. This includes checking document types, account assignments, and any settings related to document splitting.
  
  
  
  Analyze Document Splitting:
  
  If document splitting is enabled, review the splitting rules and ensure they are correctly defined. Check if the splitting is being applied consistently across all relevant documents.
  
  
  
  Run Reconciliation Reports:
  
  Use SAP standard reconciliation reports to identify and analyze discrepancies. Reports like F.2 (Reconciliation of New GL) can help in identifying issues.
  
  
  
  Check for Custom Code:
  
  If there are any custom developments that interact with financial postings, review the code to ensure it is not causing the mismatch.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on similar issues.
  
  
  
  Engage SAP Support:
  
  If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), and FBL5N (Customer Line Item Display) to analyze the documents involved.
  Documentation: Review SAP documentation on NewGL and document splitting for a deeper understanding of how these components interact.
  Testing: If changes are made to configurations or custom code, ensure thorough testing in a development or quality assurance environment before applying changes to production.
  
  By following these steps, you should be able to identify and resolve the cause of the FINS_RECON517 error.