3789426 - Average Working Hours Per Week Calculated Incorrectly Due to Decimal Conversion of Planned Hours (hh:mm)

When configuring a Work Schedule (Period Model) with Planned Hours entered in hh:mm format (for example, 07:20), the resulting Average Working Hours Per Week does not match the expected total.

Example:
- Planned Hours entered as 07:20 for 3 days (Monday–Wednesday)
- Expected total: 22:00 hours per week
- System calculates: 21.99 hours per week

- SAP SuccessFactors Employee Central
- Time Off / Work Schedule (Period Model)

1. Go to Admin Center → Manage Data.
2. Create a new Work Schedule (Period Model).
3. Enter External Name, Starting Date, Country/Region, and Model.
4. Go to Work Schedule Days for Period Model.
5. Enter the Day, select Category as Planned Hours, and click Details.
6. In the pop-up, enter Planned Hours and Minutes (hh:mm) as 07:20.
7. Click Finished.
8. Repeat steps 4–7 for two additional days (total of 3 days).
9. Check the resulting Average Working Hours Per Week.

When Planned Hours are entered in hh:mm format, the system converts the value into a decimal equivalent for calculation purposes. For example, 07:20 (7 hours 20 minutes) is converted to 7.333333... hours.

This is a repeating (non-terminating) decimal. When this converted value is used in subsequent calculations — such as summing multiple days to determine Average Hours Per Week — any rounding applied during or after that conversion (either by the system's internal decimal precision handling or by custom logic evaluating these fields) can produce a result that does not exactly match the sum of the original hh:mm values (3 x 07:20 = 22:00 exactly, but 3 x 7.333333... rounded may equal 21.99).

This is expected behavior related to decimal precision/rounding during hh:mm → decimal conversion, and is not a product defect. There is no standard SAP function that adjusts this rounding to force the result to match the exact hh:mm sum in all scenarios.

This is not a product defect and there is no standard configuration to override this decimal rounding behavior.

If your instance uses custom Business Rules to derive fields such as Average Hours Per Week, Average Hours Per Day, or similar calculated values on the Work Schedule object, review the rounding logic (Round() function, precision, and threshold settings) within those rules with your Implementation Partner. Adjusting custom rule logic is considered a configuration change and falls under Consulting rather than Product Support.

Work Schedule, Period Model, Planned Hours, hh:mm, decimal conversion, Average Working Hours Per Week, rounding, 21.99, 22.00, Time Off, Employee Central , KBA , LOD-SF-EC-TIM-REC , Recalculation , How To