How To Fix ECM_VAL007 - Error in continuity check

SAP Error Message - Details

• Message type: E = Error

• Message class: ECM_VAL - Engineering Change Management Validity

• Message number: 007

• Message text: Error in continuity check

What causes this issue?

The current context contains an organizational unit and a phase. The
<LS>continuity check</> is active for both objects.
For this reason, there cannot be gaps between the validities of orders.
This ensures that all objects that were changed with the current order
are valid continuously on specific validity dates.
Example of a continuous validity:
Order A is valid from 01/01 to 03/01
Order B is valid from 03/02 to 10/31
Order C is valide from 11/01 to 12/31

System Response

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

How to fix this error?

Change your entry so that the validities are continuous.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ECM_VAL007 - Error in continuity check ?

  The SAP error message ECM_VAL007, which indicates "Error in continuity check," typically arises in the context of Electronic Document Management (EDM) or when dealing with electronic invoices and documents. This error is often related to issues with the continuity of document numbers or sequences, which are critical for maintaining the integrity of electronic documents.
  Causes:
  
  Missing Document Numbers: The error may occur if there are gaps in the sequence of document numbers. For example, if a document number is skipped or not generated correctly, the continuity check will fail.
  Incorrect Configuration: The configuration settings for document number ranges may not be set up correctly, leading to inconsistencies.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies in the document number sequences.
  Manual Entry Errors: Manual entry of document numbers that do not follow the expected sequence can trigger this error.
  
  Solutions:
  
  Check Document Number Ranges: Verify the configuration of document number