How To Fix FINS_RECON060 - &1: Field XLGCLR is set in BSEG but not set in SKB1

FINS_RECON060 - Overview

• Message type: E = Error

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

• Message number: 060

• Message text: &1: Field XLGCLR is set in BSEG but not set in SKB1

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_RECON060 - &1: Field XLGCLR is set in BSEG but not set in SKB1 ?

  The SAP error message FINS_RECON060 indicates a reconciliation issue between the line item table BSEG (which contains accounting document line items) and the master data table SKB1 (which contains G/L account master data). Specifically, the error message states that the field XLGCLR (which indicates whether a line item is cleared) is set in the BSEG table but not in the SKB1 table.
  
  Cause:
  The error typically arises due to one of the following reasons:
  
  Data Inconsistency: There may be inconsistencies between the accounting document line items and the G/L account master data. This can happen if the G/L account has been modified or if there are issues with the clearing process.
  Missing Data: The G/L account in question may not have been properly set up or may be missing necessary data in the SKB1 table.
  Custom Development: If there are custom programs or enhancements that manipulate these tables, they may not be handling the clearing