How To Fix FIN_FB_RECON584 - XLGCLR in BSEG contains '&3' instead of 'X' or ' '

FIN_FB_RECON584 - Overview

• Message type: E = Error

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

• Message number: 584

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

What causes this issue?

There are line items in table BSEG which contain "/" or "\" in field
clearing specific to ledger groups (XLGCLR). The clearing specific to
ledger group field is a 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_RECON584 - XLGCLR in BSEG contains '&3' instead of 'X' or ' ' ?

  The SAP error message FIN_FB_RECON584 indicates that there is an issue with the clearing status in the BSEG table (the line item table for accounting documents). Specifically, the error states that the field XLGCLR in the BSEG table contains an unexpected value (&3) instead of the expected values (X for cleared or a space for not cleared).
  
  Cause:
  
  
  Data Integrity Issue: The XLGCLR field is expected to have specific values, and if it contains an unexpected value, it may indicate a data integrity issue. This could happen due to:
  
  Manual data entry errors.
  Incomplete or incorrect data migration.
  Custom developments or modifications that did not adhere to the expected data standards.
  
  
  
  Custom Code or Enhancements: If there are custom programs or enhancements that manipulate the BSEG table, they might inadvertently set the XLGCLR field to an invalid value.
  
  
  System Bugs: There could be a bug in the SAP system or a specific version that leads to this