How To Fix CM_EHFND_BO_TDEF035 - Recurrence with too many instances; end date should not be after &1

CM_EHFND_BO_TDEF035 - Overview

• Message type: E = Error

• Message class: CM_EHFND_BO_TDEF - Message Class for the Task Definition BO

• Message number: 035

• Message text: Recurrence with too many instances; end date should not be after &1

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 CM_EHFND_BO_TDEF035 - Recurrence with too many instances; end date should not be after &1 ?

  The SAP error message CM_EHFND_BO_TDEF035 typically indicates that there is an issue with a business object (BO) definition related to recurrence settings in a scheduling or planning context. The specific message "Recurrence with too many instances; end date should not be after &1" suggests that the recurrence configuration has exceeded the allowed number of instances or that the end date of the recurrence is incorrectly set.
  
  Cause:
  
  Excessive Instances: The recurrence definition may be set to generate too many instances (e.g., daily, weekly, or monthly occurrences) that exceed the system's limits.
  End Date Misconfiguration: The end date for the recurrence might be set incorrectly, possibly extending beyond a defined limit or the current date.
  Business Object Constraints: There may be specific constraints or rules defined for the business object that limit the number of instances or the duration of recurrences.
  
  
  Solution:
  
  
  Review Recurrence Settings:
  
  Check the recurrence settings in the relevant business object configuration. Ensure that the