Purchase Request Usage Department
Introduce usages in hr departments. It automatically selects the default usage of the department of the user when creating purchase requests.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Lets you set a default product usage on each HR department, and automatically fills that usage on purchase request lines when the department is chosen.
This module links HR departments to product usages used in purchase requests. On the department form (in the HR configuration area), a new field called Default Usage is added, where you can pick the usage that should normally apply to purchases made by that department.
When a purchase request is created or edited and a department is selected, the module automatically copies the department's default usage onto every line of the request. This saves users from setting the usage manually on each line.
- Adds a Default Usage field to
hr.department. - Adds an automatic behaviour on
purchase.request: changing the department updates the usage on all request lines. - The department form view is extended to show the new field.
It relies on the purchase request department and product usage modules, so those must be installed. No new menus, reports, emails or scheduled jobs are added by this module.
Models and fields (2)
- hr.department · extends an existing modelusage_id (Default Usage)
- purchase.request · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 12.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/purchase-workflow.
terminal Installation and usage
OCA documentation · Odoo 12.0Usage
Source · Odoo 12.0Add a default usage to departments. When creating purchase requests the usage is auto selected.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.