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

SAP Error Message - Details

• 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 frequency and duration are set correctly and do not exceed the allowed limits.
  If the recurrence is set to a very frequent interval (e.g., every minute or hour), consider adjusting it to a more reasonable frequency.
  
  
  
  Adjust End Date:
  
  Verify the end date of the recurrence. Ensure that it is set to a valid date that does not exceed the maximum allowed date or the current date.
  If necessary, modify the end date to align with the business requirements and system constraints.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation for the specific business object you are working with to understand any limitations or guidelines regarding recurrence settings.
  
  
  
  Testing:
  
  After making adjustments, test the configuration to ensure that the error does not reoccur and that the recurrence behaves as expected.
  
  
  
  Seek Support:
  
  If the issue persists after making the necessary adjustments, consider reaching out to SAP support or your internal SAP team for further assistance. They may provide insights based on the specific configuration and version of your SAP system.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  System Limits: Be aware of any system-defined limits regarding recurrence instances, which may vary based on the version and configuration of your SAP system.
  Business Object Documentation: Review the documentation for the specific business object to understand its configuration options and constraints.
  
  By following these steps, you should be able to resolve the error message CM_EHFND_BO_TDEF035 and ensure that your recurrence settings are correctly configured.