Operating Unit in Purchase Requests
This module introduces the following features:
- Adds the Operating Unit (OU) to the Purchase Request.
- The user’s default Operating Unit (OU) is proposed at the time of creating the Purchase Request.
- Security rules are defined to ensure that users can only see the Purchase Request of that Operating Units in which they are allowed access to.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Adds an Operating Unit to purchase requests and their lines, so each request belongs to a specific business unit. Users only see requests from the operating units they are allowed to access.
This module links purchase requests to Operating Units (internal business divisions). When a user creates a purchase request, the Operating Unit is filled in automatically from the user's default operating unit.
The Operating Unit appears on the purchase request form and list, next to the company, and on request lines. Users can group and filter requests and lines by Operating Unit in the search views. The field is only shown to users who have the multi operating unit group.
Several automatic checks apply: - The company of the request and of the operating unit must be the same. - The warehouse linked to the request's operation type must belong to the same operating unit as the request. - The approver assigned to the request must have access to that operating unit.
Security rules restrict visibility: users can only read purchase requests and request lines whose operating unit is one of their allowed operating units (or has no operating unit).
When purchase requests are generated automatically from warehouse reordering rules, the operating unit of the warehouse is copied onto the request.
When creating a purchase order from selected request lines, all selected lines must belong to the same operating unit, otherwise an error is shown. The resulting purchase order is created with that operating unit.
Required by other modules
Models and fields (4)
- stock.rule · extends an existing model
- purchase.request · extends an existing modeloperating_unit_id (Operating Unit)
- purchase.request.line · extends an existing modeloperating_unit_id (Operating Unit)
- purchase.request.line.make.purchase.order · extends an existing modeloperating_unit_id (Operating Unit)
Text generated by AI (DeepSeek) from reading the Odoo 15.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: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/operating-unit.
terminal Installation and usage
OCA documentation · Odoo 15.0Usage
Source · Odoo 15.0Follow these steps:
- Create or use an existing Operating Unit (OU) in Settings -> Users & Configuration -> Operating Unit.
- Change the configuration of the Users. In Application Accesses, put an User as Request manager and another one as Request User.
- Create a Purchase Request Order. By default, if there is no Approver, any Manager with the same OU can accept the PO. If you specify an Approver, he must be in the same Operating Unit as the Purchase Request.
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.