How To Fix FIN_FB_RECON585 - XLGCLR in BSEG_ADD contains '&3' instead of 'X' or ' '

FIN_FB_RECON585 - Overview

• Message type: E = Error

• Message class: FIN_FB_RECON - Conversion to S/4HANA: Reconciliation

• Message number: 585

• Message text: XLGCLR in BSEG_ADD contains '&3' instead of 'X' or ' '

What causes this issue?

There are line items in table BSEG_ADD which contain "/" or "\" in field
clearing specific to ledger groups (XLGCLR). The clearing specific to
ledger group field is a flag field which should only contain "X" or " ".

System Response

The system informs about this inconsistency which must be corrected in
your productive system before starting the data migration.

How to fix this error?

For more information, see
<DS:URLA.HTTPS://LAUNCHPAD.SUPPORT.SAP.COM/#/NOTES/2714344>SAP Note
2714344.</>

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FIN_FB_RECON585 - XLGCLR in BSEG_ADD contains '&3' instead of 'X' or ' ' ?

  The SAP error message FIN_FB_RECON585 indicates an issue related to the reconciliation of financial documents, specifically in the context of the BSEG (Accounting Document Segment) table. The error message states that the field BSEG_ADD contains an unexpected value ('&3') instead of the expected values ('X' or ' ').
  
  Cause:
  
  Data Integrity Issue: The value in the BSEG_ADD field is not as expected. This could be due to a data corruption issue, incorrect data entry, or a problem during data migration or integration processes.
  Custom Development: If there are custom programs or enhancements that manipulate the BSEG table, they might be incorrectly setting the value of BSEG_ADD.
  
  Configuration Issues: There might be configuration settings in the financial module that are not aligned with the expected values for the reconciliation process.
  
  
  Solution:
  
  
  Check Data: Investigate the specific entry in the BSEG table that is causing the error. You can do this by running a query on the BSEG