How To Fix RMSA_VRS059 - Replacement is inconsistent; validity period contains an overlap

RMSA_VRS059 - Overview

• Message type: E = Error

• Message class: RMSA_VRS - RMS: Versioning

• Message number: 059

• Message text: Replacement is inconsistent; validity period contains an overlap

What causes this issue?

You want to replace an object. The validity periods of the objects
overlap, however. In Customizing for versioning, you specified that
overlaps are not permitted or that they are permitted but that the
system is to output a warning.

System Response

If overlaps are not permitted, processing is canceled.
If overlaps are permitted, you can replace the object but the system
outputs this warning.

How to fix this error?

If overlaps are not permitted or if you do not want the validity
periods to overlap: when replacing an object, enter a predecessor
object with a validity period directly before the validity period of
the successor object (without gaps or overlaps) or change the validity
period of the predecessor object.
INCLUDE RMS_VRS_INFO_FOR_CHECKS OBJECT DOKU ID TX

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 RMSA_VRS059 - Replacement is inconsistent; validity period contains an overlap ?

  The SAP error message RMSA_VRS059, which states "Replacement is inconsistent; validity period contains an overlap," typically occurs in the context of managing replacement parts or materials in the SAP system, particularly within the SAP Retail or SAP S/4HANA environments. This error indicates that there is an inconsistency in the validity periods of replacement items, meaning that the time frames for the replacements overlap in a way that is not allowed by the system.
  
  Cause:
  
  
  Overlapping Validity Periods: The most common cause of this error is that two or more replacement records have overlapping validity periods. For example, if Replacement A is valid from January 1 to March 31, and Replacement B is also set to be valid from March 15 to June 30, this creates an overlap.
  
  
  Incorrect Data Entry: Manual data entry errors can lead to incorrect validity dates being set for replacements.
  
  
  Data Migration Issues: If data has been migrated from another