How To Fix 5F653 - Employee has already been absent from &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 5F - HR F: Error Messages (France)

• Message number: 653

• Message text: Employee has already been absent from &1 to &2

What causes this issue?

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

Vous avez essayT de sauvegarder un arrOt de travail dans l'infotype 0424
ou 0080. Cette absence chevauche une absence qui existe dTja dans
l'infotype 2001.

System Response

Le systFme envoie un message d'avertissement affichant les dates
correspondant a l'absence de l'infotype 2001 qui chevauche l'arrOt de
travail.

How to fix this error?

VTrifiez les dates saisies dans l'infotype 0424 ou 0080. Corrigez, le
cas TchTant, les dates de l'infotype 2001.
Note :
En rFgle gTnTrale, la saisie d'une absence dans l'infotype 0424 ou 0080
gTnFre automatiquement une absence dans l'infotype 2001.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5F653 - Employee has already been absent from &1 to &2 ?

  The SAP error message 5F653 indicates that an employee has already been recorded as absent for a specific period, which prevents the system from processing a new absence entry for the same timeframe. This error typically arises in the context of time management and absence management modules within SAP.
  Cause:
  The error occurs when:
  
  An attempt is made to record a new absence for an employee during a period where they are already marked as absent.
  There may be overlapping absence records in the system for the same employee, which violates the rules set in the absence management configuration.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Absences:
  
  Review the employee's absence records for the specified period (from &1 to &2) to confirm that there is indeed an existing absence.
  Use transaction codes like PA20 (Display HR Master Data) or PT50 (Display Absences) to view the employee's absence history.
  
  
  
  Modify or Delete Conflicting Absence:
  
  If the existing absence is incorrect or needs to be adjusted, you can modify or delete it using the appropriate transaction (e.g., PA30 for maintaining HR master data).
  Ensure that the new absence does not overlap with any existing records.
  
  
  
  Consult with HR or Time Management Team:
  
  If you are unsure about modifying or deleting absence records, consult with your HR or time management team to ensure compliance with company policies.
  
  
  
  Check Configuration Settings:
  
  If this error occurs frequently, it may be worth reviewing the configuration settings in the absence management module to ensure that the rules for overlapping absences are set correctly.
  
  
  
  Use Correct Absence Type:
  
  Ensure that the absence type being used is appropriate and does not conflict with existing entries.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data), PT50 (Display Absences), and PT60 (Time Evaluation).
  Documentation: Refer to SAP Help documentation for detailed information on absence management and error handling.
  User Roles: Ensure that you have the necessary permissions to view and modify absence records in the system.
  
  By following these steps, you should be able to resolve the error message 5F653 and successfully process the employee's absence.