How To Fix /SAPAPO/DMRES591 - Start of shift cannot be set (Note 935672)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/DMRES -

• Message number: 591

• Message text: Start of shift cannot be set (Note 935672)

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 /SAPAPO/DMRES591 - Start of shift cannot be set (Note 935672) ?

  The SAP error message /SAPAPO/DMRES591 indicates that the start of a shift cannot be set in the system. This error is typically related to issues in the configuration of the shift definitions or the planning data in SAP Advanced Planning and Optimization (APO).
  Cause:
  The error can occur due to several reasons, including:
  
  Shift Definition Issues: The shift you are trying to set may not be properly defined in the system. This includes incorrect time intervals or overlapping shifts.
  Planning Data Conflicts: There may be conflicts in the planning data that prevent the shift from being set. This could be due to existing planned orders, production orders, or other scheduling constraints.
  Calendar Settings: The factory calendar or work schedule may not align with the shift you are trying to set, leading to inconsistencies.
  Authorization Issues: The user may not have the necessary authorizations to modify shift settings.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Shift Definitions:
  
  Go to the transaction code /SAPAPO/SHIFT to review the shift definitions.
  Ensure that the shifts are defined correctly without overlaps and that the time intervals are valid.
  
  
  
  Review Planning Data:
  
  Check for any existing planned orders or production orders that may conflict with the shift you are trying to set.
  Use transaction codes like /SAPAPO/ORD to view orders and their scheduling.
  
  
  
  Verify Calendar Settings:
  
  Ensure that the factory calendar and work schedule are correctly configured.
  Check the transaction code SCAL to review the calendar settings.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to make changes to shift settings.
  Consult with your SAP security team if needed.
  
  
  
  Refer to SAP Notes:
  
  The error message references SAP Note 935672. Check this note for any specific instructions or updates related to this error.
  You can access SAP Notes through the SAP Support Portal.
  
  
  
  Consult Documentation:
  
  Review the SAP APO documentation for any additional configuration or setup requirements related to shifts and scheduling.
  
  
  
  Related Information:
  
  SAP Notes: Always check for the latest SAP Notes related to your version of SAP APO, as they may contain important updates or fixes.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Testing: After making changes, conduct thorough testing to ensure that the shift can be set without errors.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.