How To Fix FINS_RECON158 - Field XLGCLR is set in BSEG_ADD but not 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: 158

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

  The SAP error message FINS_RECON158 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 set in the BSEG_ADD table but is not set in the SKB1 table. This typically occurs during the reconciliation process in financial accounting.
  Cause:
  
  Data Inconsistency: The primary cause of this error is a data inconsistency where the field XLGCLR (which is used for clearing) is populated in the BSEG_ADD table but does not have a corresponding entry in the SKB1 table (which contains company code data).
  Missing Configuration: There may be a configuration issue where the clearing account is not properly set up in the system.
  Custom Development: If there are custom developments or enhancements in the system, they might be causing this inconsistency.
  
  Solution:
  
  
  Check Data Consistency: 
  
  Verify the entries in both the BSEG_ADD and SKB1 tables. Ensure that the clearing account referenced in BSEG_ADD exists in SKB1.
  You can use transaction codes like SE16 or SE11 to view the data in these tables.
  
  
  
  Update SKB1: 
  
  If the clearing account is missing in SKB1, you may need to create or update the entry in the SKB1 table to include the necessary clearing account.
  
  
  
  Review Configuration: 
  
  Check the configuration settings for the clearing accounts in the Financial Accounting (FI) module. Ensure that all necessary accounts are properly configured.
  
  
  
  Custom Code Review: 
  
  If there are any custom programs or enhancements that manipulate these tables, review the code to ensure it is functioning correctly and not causing the inconsistency.
  
  
  
  Consult SAP Notes: 
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Testing: 
  
  After making the necessary changes, perform testing to ensure that the error does not reoccur and that the reconciliation process works as expected.
  
  
  
  Related Information:
  
  BSEG_ADD: This table contains additional line item data for accounting documents.
  SKB1: This table contains company code data for G/L accounts.
  Transaction Codes: Use transaction codes like FB03 (Display Document), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display) to analyze the documents and line items related to the error.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to involve your SAP Basis or technical team for further investigation.