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

SAP Error Message - Details

• 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, ensure that the new dates do not conflict with existing records. You may need to extend the existing validity period or adjust your new dates accordingly.
  
  
  
  Check Configuration Settings:
  
  If you are working with configuration settings, ensure that the settings allow for the changes you are trying to make. Sometimes, the configuration may have restrictions that need to be reviewed.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidelines on validity checks related to the object you are working with.
  
  
  
  Seek Help from SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support or your internal SAP team for assistance. They may provide insights based on the specific configuration of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use specific transaction codes to view or modify the data (e.g., VK11 for condition records, MM02 for material master data).
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context.
  User Authorization: Ensure that you have the necessary authorizations to make changes to the data or configuration settings.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.