Skip to Content
Odoo model · Enterprise

sale.commission.plan.target

Commission Plan Target. Defined in module sale_commission; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 3 fields added, 0 removed, 0 renamed.

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

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 added (2)

FieldTypeModule
payment_amountmonetarysale_commission
payment_datedatesale_commission

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields added (1)

FieldTypeModule
target_typeselectionsale_commission

All fields declared on sale.commission.plan.target (9)

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 9 fields
FieldTypeLabelModule1617181920
amountmonetaryTargetsale_commissionE
currency_idmany2one res.currencysale_commissionE
date_fromdateFromsale_commissionE
date_todateTosale_commissionE
namecharPeriodsale_commissionE
payment_amountmonetarysale_commissionE
payment_datedatesale_commissionE
plan_idmany2one sale.commission.plansale_commissionE
target_typeselectionsale_commissionE

Related models

Linked by its relational fields: res.currencysale.commission.plan

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.