How To Fix FINS_RECON059 - &1: Field XLGCLR is not set in BSEG_ADD but set in SKB1


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 059

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

  • Show details Hide details


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

    The SAP error message FINS_RECON059 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 financial reconciliation processes or when trying to post documents that involve clearing accounts.

    Cause:

    1. Data Inconsistency: The primary cause of this error is a data inconsistency between the BSEG_ADD (which contains additional document segment data) and SKB1 (which contains master data for G/L accounts).
    2. 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 the error.
    3. Configuration Issues: There may be configuration issues in the financial accounting settings that lead to this inconsistency.

    Solution:

    1. Check Data Entries: Verify the entries in both the BSEG_ADD and SKB1 tables. Ensure that the XLGCLR field is populated correctly in BSEG_ADD for the relevant entries.
    2. Update BSEG_ADD: If the XLGCLR field is indeed required for the operation you are performing, you may need to update the BSEG_ADD table to include the necessary data.
    3. Review Configuration: Check the configuration settings in the SAP system related to financial accounting and clearing accounts. Ensure that all necessary fields are correctly set up.
    4. Repost Documents: If the error occurred during document posting, consider reposting the documents after ensuring that all required fields are populated.
    5. Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
    6. Debugging: If you have access to development tools, you may want to debug the process to see where the data is being lost or not set correctly.

    Related Information:

    • Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary) to view the structure of the BSEG_ADD and SKB1 tables, and SE16N to view the data in these tables.
    • SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered the same issue.
    • Documentation: Review SAP documentation related to financial accounting and document posting for any additional context on the XLGCLR field and its usage.

    If the issue persists after trying the above solutions, it may be beneficial to involve your SAP Basis or technical team for further investigation.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker