How To Fix HRPSGB_ABS173 - Abs.record (IT2001) &2-&3 cannot be created due to collision with &1.

HRPSGB_ABS173 - Overview

• Message type: E = Error

• Message class: HRPSGB_ABS -

• Message number: 173

• Message text: Abs.record (IT2001) &2-&3 cannot be created due to collision with &1.

What causes this issue?

The entered data record has a time overlap with a data record that has
already been created.

System Response

Your Absence Infotype record(IT 2001) &V1& - &V2&overlaps with a data
record of type &V3&. According to system Customizing, data records are
not permitted to have time overlaps. Your data record has therefore not
been accepted by the system.

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?

Check the dates you have entered for the data record. If in doubt,
contact your time administrator to deal with any issues.

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 HRPSGB_ABS173 - Abs.record (IT2001) &2-&3 cannot be created due to collision with &1. ?

  The SAP error message HRPSGB_ABS173 indicates that there is a collision when trying to create an absence record (IT2001) for an employee. This typically occurs when there is an attempt to create an absence record that overlaps with an existing record for the same employee.
  
  Cause:
  The error is caused by the following scenarios:
  
  Overlapping Absence Records: The absence you are trying to create overlaps with an existing absence record for the same employee. For example, if an employee already has an absence recorded from January 1 to January 5, and you try to create another absence for January 3 to January 4, this will trigger the error.
  Incorrect Date Entry: The dates entered for the new absence record may not be valid or may conflict with existing records.
  
  Configuration Issues: There may be configuration settings in the absence management module that are causing this issue.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check