Skip to Content
Odoo model

purchase.report

Purchase Report. Defined in module purchase; exists in Odoo 16, 17, 18, 19, 20. Across the upgrade steps we tracked: 3 fields added, 3 removed, 1 renamed, 3 type changes.

  1. Odoo 16 purchase
  2. Odoo 17 purchase
  3. Odoo 18 purchase
  4. Odoo 19 purchase
  5. Odoo 20 purchase

Odoo 16 to 17

Community only All changes in this step

Fields removed (2)

FieldTypeModuleNotes
avg_days_to_purchasefloatpurchase
avg_receipt_delayfloatpurchase_stock

Odoo 17 to 18

Community only All changes in this step

Fields added (1)

FieldTypeModule
days_to_arrivalfloatpurchase_stock

Type changed (3)

FieldOdoo 17Odoo 18
price_average floatmonetary
price_total floatmonetary
untaxed_total floatmonetary

Odoo 18 to 19

Community + Enterprise All changes in this step

Renamed (1)

Odoo 18Odoo 19Confidence
product_uomproduct_uom_id possible (same type, name extended)

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields removed (1)

FieldTypeModuleNotes
product_uom_idmany2onepurchase

Fields added (2)

FieldTypeModule
project_idmany2oneproject_purchase
uom_idmany2onepurchase

All fields declared on purchase.report (35)

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 35 fields
FieldTypeLabelModule1617181920
avg_days_to_purchasefloatAverage Days to Purchasepurchase
avg_receipt_delayfloatAverage Receipt Delaypurchase_stock
category_idmany2one product.categoryProduct Categorypurchase
commercial_partner_idmany2one res.partnerCommercial Entitypurchase
company_idmany2one res.companyCompanypurchase
country_idmany2one res.countryPartner Countrypurchase
currency_idmany2one res.currencyCurrencypurchase
date_approvedatetimeConfirmation Datepurchase
date_orderdatetimeOrder Deadlinepurchase
days_to_arrivalfloatEffective Days To Arrivalpurchase_stock
delayfloatDays to Confirmpurchase
delay_passfloatDays to Receivepurchase
effective_datedatetimeEffective Datepurchase_stock
fiscal_position_idmany2one account.fiscal.positionFiscal Positionpurchase
nbr_linesinteger# of Linespurchase
order_idmany2one purchase.orderOrderpurchase
partner_idmany2one res.partnerVendorpurchase
picking_type_idmany2one stock.warehouseWarehousepurchase_stock
price_averagemonetaryAverage Costpurchase
price_totalmonetaryTotalpurchase
product_idmany2one product.productProductpurchase
product_tmpl_idmany2one product.templateProduct Templatepurchase
product_uommany2one uom.uomReference Unit of Measurepurchase
product_uom_idmany2one uom.uomReference Unit of Measurepurchase
project_idmany2one project.projectProjectproject_purchase
qty_billedfloatQty Billedpurchase
qty_orderedfloatQty Orderedpurchase
qty_receivedfloatQty Receivedpurchase
qty_to_be_billedfloatQty to be Billedpurchase
stateselectionStatuspurchase
untaxed_totalmonetaryUntaxed Totalpurchase
uom_idmany2one uom.uomReference Unit of Measurepurchase
user_idmany2one res.usersBuyerpurchase
volumefloatVolumepurchase
weightfloatGross Weightpurchase
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.