How To Fix 72121 - Daily WS not displayed as daily WS = '****'

SAP Error Message - Details

• Message type: E = Error

• Message class: 72 - Message Class for Time Management Reports

• Message number: 121

• Message text: Daily WS not displayed as daily WS = '****'

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 72121 - Daily WS not displayed as daily WS = '****' ?

  The SAP error message 72121, which states "Daily WS not displayed as daily WS = '****'", typically relates to issues with the Work Schedule (WS) configuration in the SAP system. This error can occur in various contexts, such as when trying to display or process work schedules in the SAP Human Capital Management (HCM) module.
  Cause:
  
  Invalid Work Schedule: The specified work schedule (denoted by '****') may not exist or may not be correctly configured in the system.
  Authorization Issues: The user may not have the necessary authorizations to view or access the specified work schedule.
  Data Inconsistency: There may be inconsistencies in the data related to the work schedule, such as missing entries or incorrect settings.
  Configuration Errors: The work schedule may not be properly defined in the system, leading to issues when trying to display it.
  
  Solution:
  
  
  Check Work Schedule Configuration:
  
  Go to the transaction code PA30 (Maintain HR Master Data) or PT03 (Maintain Work Schedules) and verify if the work schedule exists and is correctly configured.
  Ensure that the work schedule is active and has the correct validity period.
  
  
  
  Verify Authorizations:
  
  Check if the user has the necessary authorizations to access the work schedule. This can be done by reviewing the user's roles and authorizations in the system.
  
  
  
  Data Consistency Check:
  
  Run consistency checks for the work schedule data. You can use transaction codes like PT60 (Time Evaluation) to check for any inconsistencies in time data.
  
  
  
  Review Configuration Settings:
  
  If you have access to configuration settings, navigate to SPRO (SAP Reference IMG) and check the settings under Personnel Management > Personnel Administration > Work Schedule to ensure everything is set up correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant context.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30, PT03, and SPRO for managing work schedules and HR data.
  SAP Notes: Search for SAP Notes related to error message 72121 in the SAP Support Portal for any known issues or fixes.
  User Forums: Check SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.