How To Fix L6022 - Inconsistency between status record and communication record

L6022 - Overview

• Message type: E = Error

• Message class: L6 - LVS Link R/2 - ECC

• Message number: 022

• Message text: Inconsistency between status record and communication record

What causes this issue?

The communication record was retransmitted and an inconsistency was
found between the record sent and the existing status record. The
receiving program checks each record received for double transmissions.
The system recognizes the record that was retransmitted, marks it
accordingly and checks to see if the record type is the same as in the
status record that already exists. If not, the transmission is
interrupted.

How to fix this error?

Check the communication records that were interrupted in the ERP and R/2
Systems. If they are identical, repeat the transmission procedure.
If the transmission is interrupted again with the same error, check the
contents of the communication record in both systems. If they are
identical, check to see if the communication record in R/3 was processed
successfully. If this is the case, you can delete the communication
record out of the Queue in the R/2 System.
If the communication record in the ERP System has not been processed,
post it manually. Afterwards, you can delete the communication record
in the R/2 system.
If the record types in the R/2 and ERP Systems are different, but the
contents of the data are the same, you can process them as if they were
the same.
If the contents are different, the error occurred when the communication
document number was assigned. Check the number range interval for
communication records. (Object = DTIN, Group = DZLV ).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message L6022 - Inconsistency between status record and communication record ?

  The SAP error message L6022, which states "Inconsistency between status record and communication record," typically occurs in the context of logistics and inventory management, particularly when dealing with handling units (HUs) or warehouse management processes. This error indicates that there is a mismatch between the status of a handling unit and the communication record associated with it.
  Causes:
  
  Data Inconsistency: The most common cause is a data inconsistency between the status record (which tracks the current state of the handling unit) and the communication record (which logs the actions taken on the handling unit).
  System Errors: Issues during data processing, such as system crashes or interruptions, can lead to incomplete updates of the status or communication records.
  Manual Changes: Manual interventions or changes in the database that do not follow the standard processes can lead to inconsistencies.
  Custom Developments: If there are custom programs or enhancements that manipulate handling unit data, they may not be