When an absence function is configured to split absences at the end of the month, the system correctly reflects the split in the Absence Periods window. However, the calculation based on the reporting date in the Absence Limit Day window appears to be incorrect.
Example Scenario:
For November 2025, an absence is entered from 28.11.2025 to 01.12.2025.
Since 29th and 30th November fall on weekends, the expected absence duration should be:
- 1 day for November
- 1 day for December
Although the system correctly splits the absence period across the two months, the Absence Limit Day calculation does not reflect this split accurately.
Environment Details:
- Reference Case: CS0466379
- Test Environment: 25R1 TEST LKP
Steps to Reproduce:
- Configure an absence type with a function to split absences at month-end.
- Enter an absence that spans across the end of a month.
- Observe the results in both the Absence Periods and Absence Limit Day windows.
Observation: According to the defined absence functions, the logic applies only to the splitting of absence periods and does not alter the absence record itself. As a result, the absence period is correctly divided into two. However, in the absence limit day, the used days are not reduced to 1 for the selected working date. Because the working date falls within the absence period, the system evaluates the entire absence and therefore counts the used days as 2.
Expected Behavior:
The Absence Limit Day calculation should align with the split absence periods and reflect only the applicable working days within each month (i.e., 1 day for November and 1 day for December in the given example).
Conclusion / Requirement:
This behavior appears to be a system limitation, where the absence split logic applies only to period division and not to limit day calculations. Therefore, we request this to be considered as a new enhancement requirement to ensure consistency between absence period splitting and absence limit day calculations.