Do you have any question about this error?
Message type: E = Error
Message class: HRPSGB_ABS -
Message number: 171
Message text: Collision occured with dependent records. Record cannot be created
The entered data record triggers a time overlap of dependent records
that have already been created.
Your data record triggers a time overlap for &V1& and &V2&. According to
system Customizing, these data records are not permitted to have time
overlaps. Your data record has therefore not been accepted by the
system.
Check the dates you have entered for the data record. If in doubt,
contact your time administrator to deal with any issues.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
HRPSGB_ABS171
- Collision occured with dependent records. Record cannot be created ?The SAP error message HRPSGB_ABS171: Collision occurred with dependent records. Record cannot be created typically occurs in the context of the SAP Human Capital Management (HCM) module, particularly when dealing with absence management or time management functionalities. This error indicates that there is a conflict with existing records that prevents the creation of a new record.
Causes:
- Overlapping Absences: The most common cause is that the new absence record you are trying to create overlaps with an existing absence record for the same employee.
- Dependent Records: There may be dependent records (like time evaluation results, payroll results, etc.) that conflict with the new record you are trying to create.
- Incorrect Date Ranges: The start and end dates of the new record may not align correctly with existing records.
- Configuration Issues: There may be configuration settings in the absence management module that are causing conflicts.
Solutions:
- Check Existing Records: Review the existing absence records for the employee in question. Ensure that the new absence does not overlap with any existing records.
- Adjust Dates: If there is an overlap, adjust the start and end dates of the new absence record to ensure they do not conflict with existing records.
- Delete or Modify Conflicting Records: If the existing records are no longer valid, consider deleting or modifying them to resolve the conflict.
- Consult with HR or Payroll: If you are unsure about the records, consult with your HR or payroll department to understand the implications of modifying or deleting records.
- Check Configuration: If the issue persists, review the configuration settings in the SAP system related to absence management to ensure they are set up correctly.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to engage with your SAP support team or a consultant who specializes in SAP HCM for further assistance.
Get instant SAP help. Start your 7-day free trial now.
HRPSGB_ABS170
OxP mapping not possible,T5GPSB31 'out of sync' with T554S (Note 738710)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPSGB_ABS169
OxP mapping not possible, T5GPSB31 has no entries
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPSGB_ABS172
Collision occured with dependent records
What causes this issue? The entered data record triggers a time overlap of dependent records that have already been created.System Response Your dat...
HRPSGB_ABS173
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 Inf...
Click on this link to search all SAP messages.