How To Fix HRPAY99CEE1_U2_UTIL035 - Unable to read RGDIR from cache.

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAY99CEE1_U2_UTIL - CEE01[UTIL2] - Messages for utilities

• Message number: 035

• Message text: Unable to read RGDIR from cache.

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 HRPAY99CEE1_U2_UTIL035 - Unable to read RGDIR from cache. ?

  The SAP error message HRPAY99CEE1_U2_UTIL035: Unable to read RGDIR from cache typically occurs in the context of payroll processing within the SAP HR module. This error indicates that the system is unable to retrieve the RGDIR (Register Directory) data from the cache, which is essential for payroll calculations.
  Causes:
  
  Cache Corruption: The cache that stores the RGDIR data may be corrupted or not properly initialized.
  Missing Data: The RGDIR data may not be available in the database or may not have been generated correctly.
  Configuration Issues: There may be issues with the configuration of the payroll schema or related settings.
  System Performance: High system load or performance issues may prevent the cache from being accessed properly.
  Authorization Issues: The user may not have the necessary authorizations to access the RGDIR data.
  
  Solutions:
  
  
  Clear Cache: You can try clearing the cache for the payroll process. This can often resolve issues related to corrupted cache data.
  
  Use transaction code SM12 to check for and delete any lock entries that may be causing issues.
  Use transaction code SM21 to check the system log for any related errors.
  
  
  
  Rebuild RGDIR: If the RGDIR data is missing or corrupted, you may need to regenerate it.
  
  This can typically be done by running the payroll process again or using specific transaction codes related to payroll processing.
  
  
  
  Check Configuration: Review the payroll configuration settings to ensure that everything is set up correctly.
  
  Verify that the payroll schema and related settings are correctly configured.
  
  
  
  System Performance: Monitor system performance and check for any bottlenecks that may be affecting the ability to read from the cache.
  
  Consider running performance analysis tools to identify any issues.
  
  
  
  Authorization Check: Ensure that the user executing the payroll process has the necessary authorizations to access the RGDIR data.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data), PC00_MXX_CALC (Payroll Calculation), and SM37 (Job Monitoring) to help diagnose and resolve issues.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Documentation: Review SAP documentation related to payroll processing and caching mechanisms for further understanding.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.