Odoo Community
Odoo Enterprise
Viindoo Cloud
A purchase agreement that starts in the right warehouse
Warehouse-based access extended to Purchase Agreements, so a user restricted to their own sites can work with the purchase agreements that belong to them.
Multi-Warehouse Access Control - Purchase Requisition (technical name viin_multi_warehouse_access_control_purchase_requisition) is an Odoo 17.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for warehouse operator, site manager, head office, it.
At a Glance
The facts of Multi-Warehouse Access Control - Purchase Requisition, version 0.1.0, in one place. Published by Viindoo.
Technical name
viin_multi_warehouse_access_control_purchase_requisition
Odoo version
17.0 (Odoo Community, Odoo Enterprise, Viindoo Cloud)
Depends on
to_multi_warehouse_access_control_purchase, purchase_requisition
Best for
Warehouse operator; Site manager; Head office; IT
Not for
It grants read, not rights.
Key features
Operation type defaulted from the user's accessible warehouses, No more silently wrong default, Applies when creating a purchase agreement, No change to the agreement flow, Installed as a bridge when both apps are present, Nothing to configure
How It Works
Three screens.
1
What they can now read
Documents tied to the warehouses this user is responsible for.
2
The access behind it
Accessing users are listed on the warehouse itself.
3
And the operations
The warehouse work the documents relate to.
What You Get
Operation type defaulted from the user's accessible warehouses
No more silently wrong default
Applies when creating a purchase agreement
No change to the agreement flow
Installed as a bridge when both apps are present
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
It grants read, not rights.
Creating and confirming stay with the app's own groups.
It does not widen anything for other users.
Only Own Documents warehouse users are affected.
It needs the access control module.
Without warehouse assignments there is nothing to filter by.
It adds no screens.
The same lists, filtered differently.
Works Well With
Apps from the same stack, built to fit this one:
Who Should Use Multi-Warehouse Access Control - Purchase Requisition?
Warehouse operator
Sees the documents behind their own work.
Site manager
Plans with the information their team has.
Head office
Shares what is needed, not everything.
IT
One rule, applied consistently across apps.
Frequently Asked Questions
What does Multi-Warehouse Access Control - Purchase Requisition do?
Warehouse-based access extended to Purchase Agreements, so a user restricted to their own sites can work with the purchase agreements that belong to them.
What does Multi-Warehouse Access Control - Purchase Requisition not do?
It grants read, not rights. Creating and confirming stay with the app's own groups. It does not widen anything for other users. Only Own Documents warehouse users are affected. It needs the access control module. Without warehouse assignments there is nothing to filter by. It adds no screens. The same lists, filtered differently.
Who is Multi-Warehouse Access Control - Purchase Requisition for?
Warehouse operator: Sees the documents behind their own work. Site manager: Plans with the information their team has. Head office: Shares what is needed, not everything. IT: One rule, applied consistently across apps.
Which Odoo version and editions does it support?
Odoo 17.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: to_multi_warehouse_access_control_purchase, purchase_requisition. Odoo installs them with it.
What works well with it?
Multi-Warehouse Access Control (to_multi_warehouse_access_control): The access model this extends. With Purchase (to_multi_warehouse_access_control_purchase): Purchase orders by warehouse. Purchase extensions (viin_purchase): The buying side.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_multi_warehouse_access_control_purchase_requisition; pre-sales questions go to sales@viindoo.com.
Need help with Multi-Warehouse Access Control - Purchase Requisition?
For questions, implementation support or a custom feature, contact Viindoo.
Upgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: apps.odoo.com/apps/modules/browse?author=Viindoo
About Viindoo. Viindoo builds and maintains more than 1,000 apps on the Odoo App Store for the Community and Enterprise editions and runs them on Viindoo Cloud. A purchase of Multi-Warehouse Access Control - Purchase Requisition covers the 17.0 series: bug fixes on the module reach you through the store, questions go to apps.support@viindoo.com with the technical name viin_multi_warehouse_access_control_purchase_requisition, and moving to a newer Odoo series is a separate purchase for that series. Source code is delivered with the module and stays yours to read and adapt.
Technical Requirement
Editions: Odoo Community, Odoo Enterprise, Viindoo Cloud
Changes log
0.1.0 - Latest on the 17.0 line
- Access follows the 17.0 record rules of the bridged app.
Instruction
Instruction video: Multi-Warehouse Access Control - Purchase Requisition
For Example
At ABC company, employee A has the right to manage warehouse 1 and employee B has the right to manage warehouse 2. To secure the goods contract information and strictly control the quantity of the goods before inputting, these two employees can only see the purchase contracts related to the warehouse they manage. Viindoo's enterprise management software will provide you with the following features to solve this problem:
How it works
Step 1: Create an user account
Step 2: Grant user A with the User: Own Documents access right the Inventory app and the User access right of Purchase app. Navigate to Settings -> Manage Users.
Step 3: Create a purchase agreement and the related request for quotation (RFQ).
- Create a purchase agreement.
- Create RFQ. After creating the purchase agreement, press the Confirm button and then press New Quotation to create a new quotation.
Step 4: After the RFQ is confirmed, a product transfer sheet will be generated. Log in to the user A account to check the result. Navigate to Inventory -> Operations -> All Transfers. Find the stock transfer sheet. The purchase order and purchase agreement information will appear on the chatter section.
- Access the purchase agreement from the inventory app.
This software and associated files (the "Software") may only be
used
(executed, modified, executed after modifications) if you have
purchased a
valid license from the authors, typically via Odoo Apps,
or if you
have
received a written agreement from the authors of the
Software (see the
COPYRIGHT file).
You may develop Odoo modules that use the Software as a library
(typically
by depending on it, importing it and using its
resources), but
without
copying any source code or material from the
Software. You may distribute
those modules under the license of your
choice, provided that this
license
is compatible with the terms of
the Odoo Proprietary License (For
example:
LGPL, MIT, or proprietary
licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell
copies of the
Software or modified copies of the Software.
The above copyright notice and this permission notice must be
included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT
SHALL THE
AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING
FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE
SOFTWARE.