How To Fix FINS_RECON159 - Field XLGCLR is not set in BSEG_ADD but set in SKB1: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 159

• Message text: Field XLGCLR is not set in BSEG_ADD but set in SKB1: &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_RECON159 - Field XLGCLR is not set in BSEG_ADD but set in SKB1: &1 message(s) ?

  The SAP error message FINS_RECON159 indicates that there is a mismatch between the fields in the BSEG_ADD table and the SKB1 table. Specifically, the error states that the field XLGCLR is not set in the BSEG_ADD table but is set in the SKB1 table. This typically occurs during the reconciliation process or when trying to post a document that involves clearing accounts.
  Cause:
  
  Data Inconsistency: The error usually arises due to inconsistencies in the data between the BSEG_ADD (which contains additional document segment data) and SKB1 (which contains master data for G/L accounts).
  Missing Data: The field XLGCLR (which is used for clearing) is expected to be populated in the BSEG_ADD table but is missing, leading to this error.
  Configuration Issues: There may be configuration issues in the financial settings or in the way the clearing accounts are set up.
  
  Solution:
  
  
  Check Data Consistency:
  
  Verify that the data in the BSEG_ADD and SKB1 tables is consistent. You can do this by checking the entries in both tables for the relevant account.
  Use transaction codes like SE16 or SE16N to view the data in these tables.
  
  
  
  Populate Missing Fields:
  
  If the field XLGCLR is indeed missing in BSEG_ADD, you may need to ensure that the posting logic populates this field correctly. This might involve debugging the posting process or reviewing the custom code if any exists.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the clearing accounts in the Financial Accounting (FI) module. Ensure that the clearing accounts are set up correctly and that the necessary fields are being populated during postings.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that might address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  
  
  
  Testing:
  
  After making any changes, perform testing to ensure that the error no longer occurs and that the postings are processed correctly.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. They can provide more detailed insights based on the specific configuration and version of your SAP system.
  
  
  
  Related Information:
  
  BSEG_ADD: This table contains additional data for accounting documents, which can include fields related to clearing and reconciliation.
  SKB1: This table contains master data for G/L accounts, including information about clearing accounts.
  Transaction Codes: Familiarize yourself with transaction codes like FB03 (Display Document), FB50 (Enter G/L Account Document), and others that may help in analyzing the issue.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.