How To Fix COM_DML_CUST087 - Simple date validity: checks cannot be made more stringent

COM_DML_CUST087 - Overview

• Message type: E = Error

• Message class: COM_DML_CUST - MDF Messages

• Message number: 087

• Message text: Simple date validity: checks cannot be made more stringent

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message COM_DML_CUST087 - Simple date validity: checks cannot be made more stringent ?

  The SAP error message COM_DML_CUST087 indicates that there is an issue with the validity checks for a date in the context of a configuration or master data setting. This error typically arises when you attempt to make the validity period for a certain object (like a condition record, master data, etc.) more stringent than what is currently allowed by the system.
  
  Cause:
  The error occurs when:
  
  You are trying to set a validity date range that is narrower than the existing range for the same object.
  The system has constraints that prevent you from making the validity checks more stringent than they already are.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review Existing Validity Dates:
  
  Check the current validity dates for the object you are trying to modify. You can do this by navigating to the relevant transaction or table where the data is stored.
  
  
  
  Adjust Validity Dates:
  
  If you need to change the validity period,