How To Fix 5E635 - Absence &1 detected as a relapse in period &2 to &3

SAP Error Message - Details

• Message type: E = Error

• Message class: 5E - Error messages for Spanish infotypes module pools

• Message number: 635

• Message text: Absence &1 detected as a relapse in period &2 to &3

What causes this issue?

The system has detected the absence &v1& is a relapse. This means that
days from the first absence period are added to the period from &v2& to
&v3& when counting days for the bracket split to start or finish benefit
payments.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5E635 - Absence &1 detected as a relapse in period &2 to &3 ?

  The SAP error message 5E635, which states "Absence &1 detected as a relapse in period &2 to &3," typically occurs in the context of absence management within the SAP Human Capital Management (HCM) module. This error indicates that an employee has been recorded with an absence that is considered a relapse of a previous absence, which can violate the rules set in the system regarding how absences are managed.
  Cause:
  
  Relapse Definition: The system identifies that the absence type (e.g., sick leave) is being recorded again within a specified period after a previous absence of the same type. This is often governed by specific rules or configurations in the system that define what constitutes a relapse.
  Configuration Settings: The configuration settings in the absence management module may define certain absence types as relapses if they occur within a certain timeframe after a previous absence of the same type.
  Data Entry Error: There may be an error in data entry, where the absence is incorrectly recorded or overlaps with a previous absence.
  
  Solution:
  
  Review Absence Records: Check the employee's absence records to confirm if the absence being recorded indeed falls within the relapse period of a previous absence. If it does, you may need to adjust the absence dates or types accordingly.
  Adjust Configuration: If the relapse detection is too strict or not aligned with your organization's policies, consider reviewing and adjusting the configuration settings in the SAP system. This may involve working with an SAP HCM consultant or administrator.
  Consult Documentation: Refer to the SAP documentation or help resources for specific guidelines on how to handle absence types and relapses. This can provide insights into how to configure the system to better suit your needs.
  Use Different Absence Type: If the absence is not a true relapse, consider using a different absence type that does not trigger the relapse error.
  Seek Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  Related Information:
  
  Absence Management Configuration: Understanding how absence types are configured in SAP HCM can help in managing and preventing such errors.
  Legal and Compliance Considerations: Ensure that your absence management practices comply with local labor laws and organizational policies, especially regarding sick leave and relapses.
  User Training: Providing training for HR personnel on how to correctly enter absence data can help minimize errors and improve compliance with the system's rules.
  
  By addressing the underlying causes and following the suggested solutions, you should be able to resolve the error message 5E635 effectively.