Skip to Content
Odoo model · Enterprise

l10n_be.hr.payroll.schedule.change.wizard

Change contract working schedule. Defined in module l10n_be_hr_payroll; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 7 fields added, 7 removed, 0 renamed.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 l10n_be_hr_payroll
  4. Odoo 19 l10n_be_hr_payroll
  5. Odoo 20 l10n_be_hr_payroll

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 17 to 18

Community only All changes in this step

Not covered: this step compares Community modules only and this model belongs to an Enterprise module.

Odoo 18 to 19

Community + Enterprise All changes in this step

Fields removed (4)

FieldTypeModuleNotes
absence_work_entry_type_idmany2onel10n_be_hr_payroll
contract_idmany2onel10n_be_hr_payroll
part_timebooleanl10n_be_hr_payroll
presence_work_entry_type_idmany2onel10n_be_hr_payroll

Fields added (1)

FieldTypeModule
version_idmany2onel10n_be_hr_payroll

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields removed (3)

FieldTypeModuleNotes
found_leave_allocationbooleanl10n_be_hr_payroll
leave_type_idmany2onel10n_be_hr_payroll
previous_contract_creationbooleanl10n_be_hr_payroll

Fields added (6)

FieldTypeModule
adapt_allocationbooleanl10n_be_hr_payroll
adapt_wagebooleanl10n_be_hr_payroll
initial_time_off_allocation_hoursfloatl10n_be_hr_payroll
remaining_time_off_allocationfloatl10n_be_hr_payroll
reorganisation_measure_idsmany2manyl10n_be_hr_payroll
time_off_allocation_hoursfloatl10n_be_hr_payroll

All fields declared on l10n_be.hr.payroll.schedule.change.wizard (32)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 32 fields
FieldTypeLabelModule1617181920
absence_work_entry_type_idmany2one hr.work.entry.typeAbsence Work Entry Typel10n_be_hr_payrollE
adapt_allocationbooleanl10n_be_hr_payrollE
adapt_wagebooleanl10n_be_hr_payrollE
company_idmany2onel10n_be_hr_payrollE
contract_idmany2one hr.contractContractl10n_be_hr_payrollE
currency_idmany2oneCurrencyl10n_be_hr_payrollE
current_resource_calendar_idmany2one resource.calendarCurrent Working Schedulel10n_be_hr_payrollE
current_wagemonetaryWagel10n_be_hr_payrollE
date_enddateEnd Datel10n_be_hr_payrollE
date_startdateStart Datel10n_be_hr_payrollE
employee_idmany2onel10n_be_hr_payrollE
found_leave_allocationbooleanl10n_be_hr_payrollE
full_resource_calendar_idmany2one resource.calendarWorking Hours Referencel10n_be_hr_payrollE
full_time_off_allocationfloatl10n_be_hr_payrollE
full_wagemonetaryFull Time Equivalent Wagel10n_be_hr_payrollE
initial_time_off_allocationfloatl10n_be_hr_payrollE
initial_time_off_allocation_hoursfloatl10n_be_hr_payrollE
leave_allocation_idmany2one hr.leave.allocationl10n_be_hr_payrollE
leave_type_idmany2one hr.leave.typeTime Off Typel10n_be_hr_payrollE
part_timebooleanl10n_be_hr_payrollE
presence_work_entry_type_idmany2one hr.work.entry.typel10n_be_hr_payrollE
previous_contract_creationbooleanPost Change Contract Creationl10n_be_hr_payrollE
remaining_time_off_allocationfloatl10n_be_hr_payrollE
reorganisation_measure_idsmany2manyl10n_be_hr_payrollE
requires_new_contractbooleanl10n_be_hr_payrollE
resource_calendar_idmany2one resource.calendarNew Working Schedulel10n_be_hr_payrollE
structure_type_idmany2onel10n_be_hr_payrollE
time_off_allocationfloatl10n_be_hr_payrollE
time_off_allocation_hoursfloatl10n_be_hr_payrollE
version_idmany2one hr.versionContractl10n_be_hr_payrollE
wagemonetaryNew Wagel10n_be_hr_payrollE
work_time_ratefloatl10n_be_hr_payrollE
Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.