How To Fix W/035 - Number of calendar days cannot be greater than 10 years

SAP Error Message - Details

• Message type: E = Error

• Message class: W/ -

• Message number: 035

• Message text: Number of calendar days cannot be greater than 10 years

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 W/035 - Number of calendar days cannot be greater than 10 years ?

  SAP Error Message:
  
  W/035 Number of calendar days cannot be greater than 10 years
  
  Cause:
  This warning message occurs when a date range or a period entered in a transaction or configuration exceeds the maximum allowed duration of 10 years (approximately 3650 days). SAP standard validations restrict calendar day intervals to a maximum of 10 years to avoid data inconsistencies, performance issues, or logical errors in date-dependent processes.
  Typical scenarios where this might happen include:  
  
  Entering validity periods for master data (e.g., condition records, infotypes, or custom tables) that span more than 10 years.  
  Defining date ranges in reports, queries, or selection screens that exceed 10 years.  
  Setting up time-dependent data in HR, Finance, or Logistics modules with overly long validity periods.
  
  
  Solution:
  
  
  Check the Date Range Entered:
  
  Review the start and end dates you have entered. Ensure that the difference between these dates does not exceed 10 years.
  
  
  Adjust the Validity Period:
  
  If the period is too long, shorten it to be within the 10-year limit. For example, if you need to cover a longer period, split the data into multiple records with shorter validity intervals.
  
  
  Review Configuration or Master Data:
  
  If the error occurs during configuration or master data maintenance, adjust the validity periods accordingly.
  
  
  Customizing or Development:  
  
  If this limitation is too restrictive for your business scenario, you may consider discussing with your SAP technical team whether a custom solution or enhancement is feasible.  
  However, increasing this limit is generally not recommended as it may cause performance or data integrity issues.
  
  
  
  
  Related Information:
  
  This message is a warning (W), not an error, so the system allows you to proceed but advises caution.  
  The message number is W035 and is part of standard SAP validation checks for date intervals.  
  Common modules where this might appear include HR (Personnel Administration), MM (Material Management), SD (Sales and Distribution), FI (Financial Accounting), and others where date ranges are critical.  
  Always ensure date intervals are realistic and aligned with business requirements.
  
  
  Example:
  If you enter a validity period from 01.01.2000 to 31.12.2011 (which is 12 years), SAP will trigger this warning. You should adjust the end date to 31.12.2009 or earlier to comply with the 10-year limit.
  
  If you need the exact message text or want to check the message in your system, you can use transaction SE91 and enter message class and number (e.g., message class related to your module and message number 035).
  
  Summary:  
  
  Cause: Date range exceeds 10 years.  
  Solution: Reduce the date range to 10 years or less.  
  Note: This is a warning, not an error, but should be addressed to maintain data integrity.