How To Fix FINS_RECON199 - CoCd &1: Check BSEG for valid XLGCLR started at &2 and ended at &3

FINS_RECON199 - Overview

• Message type: E = Error

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

• Message number: 199

• Message text: CoCd &1: Check BSEG for valid XLGCLR started at &2 and ended at &3

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_RECON199 - CoCd &1: Check BSEG for valid XLGCLR started at &2 and ended at &3 ?

  The SAP error message FINS_RECON199 indicates an issue related to the reconciliation of financial documents in the system. Specifically, it points to a problem with the clearing of line items in the BSEG table (the line item table for accounting documents) for a specific company code (CoCd).
  
  Cause:
  The error message typically arises due to one of the following reasons:
  
  Invalid Clearing Document: The clearing document (XLGCLR) may not be valid or may not exist in the BSEG table for the specified company code.
  Inconsistent Data: There may be inconsistencies in the data related to the clearing process, such as missing or incorrect entries.
  Timing Issues: The clearing process may have started and ended at different times, leading to discrepancies in the data.
  
  Configuration Issues: There may be configuration issues in the financial settings that affect how clearing is processed.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check BSEG Entries: Use transaction codes like SE16