How To Fix W0059 - No time period of 2nd day can contain a day change

SAP Error Message - Details

• Message type: E = Error

• Message class: W0 - Customizing - ISR

• Message number: 059

• Message text: No time period of 2nd day can contain a day change

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 W0059 - No time period of 2nd day can contain a day change ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  W0059 - No time period of 2nd day can contain a day change
  
  Cause:
  This warning message occurs in SAP Time Management when you try to define or record a time period (e.g., working time, absence, or attendance) that spans over two days and includes a "day change" within the second day’s time period. 
  In simpler terms, the system does not allow a time period on the second day to itself contain a day change (midnight crossing). For example, if you have a time period that starts on day 1 and ends on day 2, the time period on day 2 cannot again cross midnight into day 3.
  This is typically related to time evaluation rules or time data entry where the time intervals are incorrectly defined or overlapping in a way that violates the system’s logic for day changes.
  
  Explanation:
  
  SAP Time Management handles time periods on a daily basis.
  A "day change" means the time period crosses midnight (00:00).
  The first day’s time period can contain a day change (e.g., 22:00 to 02:00 next day).
  However, the second day’s time period cannot again contain a day change (e.g., 23:00 to 01:00 next day).
  This restriction prevents ambiguous or overlapping time intervals that complicate time evaluation.
  
  
  Solution:
  
  
  Check the time periods entered:
  
  Review the time intervals for the employee’s attendance, absence, or working time records. Make sure that the time period on the second day does not cross midnight again.
  
  
  Split the time periods properly:
  
  If the working or absence time spans multiple days, split the time periods so that each day’s time period does not contain a day change. For example:  
  
  Day 1: 22:00 to 24:00  
  Day 2: 00:00 to 06:00 (no day change here)  
  Day 3: 00:00 to 02:00 (if applicable)
  
  
  
  Adjust time evaluation rules if necessary:
  
  If the error occurs during time evaluation, check the custom rules or schemas that process time periods. Ensure that the logic does not create or expect time periods on the second day that cross midnight.
  
  
  Use correct time entry transactions:
  
  When entering time data (e.g., via CAT2, PA30, or CATS), ensure that the time intervals are entered correctly and do not violate the day change rule.
  
  
  
  Related Information:
  
  Time Management Concepts: SAP Time Management processes time data on a daily basis, and day changes are critical for correct time evaluation.
  Day Change Indicator: In some configurations, a day change indicator (e.g., in table T510S or time schema) controls how day changes are handled.
  Time Evaluation (Schema): The time evaluation schema (e.g., SAPPTIME) processes time data and may generate this warning if time periods are incorrectly defined.
  Transactions to Check:  
  
  PA30 (Maintain HR Master Data)  
  CAT2 (Time Sheet: Maintain Times)  
  PT60 (Time Evaluation)  
  
  
  SAP Notes: Check for any SAP Notes related to W0059 for specific patches or updates.
  
  
  Summary:
  
  Cause: Time period on the second day contains a day change (crosses midnight), which is not allowed.
  Solution: Adjust time periods so that the second day’s time period does not cross midnight; split time intervals properly.
  Check: Time entries, time evaluation rules, and day change settings.
  
  
  If you provide the exact scenario or transaction where this error occurs, I can help you with more specific guidance.