Contributors mailing list archives
Re: Overtime calculation in Odoo 15 and OCAby
grounding your work on Odoo Standard is what we usually do as
well, as it limits the upstream work and even more importantly the
maintenance effort. However, i am genuinly not a friend of "dirty"
work arounds like the one you described, even if that is
definitely pragmatic. The reason is simple: Attendance of 0
effectively means, a given employee was attending but technically
less than the minimum recordable time. So if the authorities see
that record at a given time in the future, they might be tempted
to belive there was an error with regard to the recorded time.
Moreover an attendenance cron job means, the entry has not been
made by the employee or a manager (human), which mit might not be
favourable either (with regard to law and credibility of the
Overall i believe, your strategy is pragmatic but less favourable
from a legal standpoint.
So why not patching the standard functionality, so that it
calculates "0" when there is no entry and sent this patch for
upstream inclusion? I know this is generally a bumpy road with
Odoo but to me that would be the best solution for the given
I pained about the same issues, you are all telling about. I just can speak for version 16. Probably 15 too, but I‘am not sure. Our module depends to Odoo Core only.
Our biggest pain was, that the overtime is not reduced on days without attendance, where you normally have to work.
For that problem we found a really simple solution.The approach was, when you have attendances, then overtime calculation is correct.The trick is, we create an attendance with zero time for days, where no attendance entries exist.
Therefore we have implemented a cronjob which runs every night and creates missing attendances for days where are no entries. We use here the „generate_series“ method from postgres.
You also have got a new field „count_attendance_from“ in employee. Starting from that date, all missing attendances are generated with zero time.
If anyone is interested, here is a link to the code.I just uploaded it to github, while primarily we are using gitlab.
In this repository there are two more modules. Once for generating public holidays worldwide using pythons holiday library and one module, for updating overtime when creating the holidays later.
hr_attendance_no_gaps:Module for correct overtime calculation
hr_generate_public_holidays:Module for generating holidays
hr_holidays_attendance_overtime:Bridge module between hr_attendance and hr_holidays to update overtime.
We also would contribute them to oca, but haven‘t written any tests yet. Feel free to contribute :)
Vielen Dank und Viele Grüße
Am 08.08.2023 um 15:11 schrieb Rafael Blasco <firstname.lastname@example.org>:
Hello Florian, Holger:
After testing and testing in runbot I don’t catch up the “issue” for me is working properly.
I will try to test the OCA PR to get in a defined user cases (we can write down) the difference.
> Is your proposal to transfer times from time-sheet / attendance -> payslip> CODE according to some rules (like the Salary Rules). I am running older> version of Odoo and upgrading to 16 ATM and would like to incorporate a> feature like this.no, it might be built on top of my proposal though. I'm now exclusivelytalking about populating hr.attendance.overtime in a way thatovertime = (time recorded in hr.attendance records) - (expected working hoursas per working calendar)holds--Your partner for the hard Odoo problems
Post to: mailto:email@example.com
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: firstname.lastname@example.org Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247