$ 2126.40
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) • Inventory (stock) • Invoicing (account) • Purchase (purchase) |
Lines of code | 1234 |
Technical Name |
purchase_procurement_plan |
License | See License tab |
Website | http://linkedin.com/in/openvalue-consulting-472448176 |
Versions | 17.0 |
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) • Inventory (stock) • Invoicing (account) • Purchase (purchase) |
Lines of code | 1234 |
Technical Name |
purchase_procurement_plan |
License | See License tab |
Website | http://linkedin.com/in/openvalue-consulting-472448176 |
Versions | 17.0 |
PROCUREMENT PLAN
Procurement Plan Management from Version (collecting more procurement plan) to Procurement Plan creation and its deployment (purchase order creation) comparing planned with actual figures (amount, price and quantity) with variance analysis (price variance, quantity variance and overall variance).
Two monitors are provided to check quantity and amount figures for the follow up purchase process, i.e. goods receipt and invoice receipt.
Two authorization roles are involved in the overall process: Purchase User and Purchase Manager
the following picture provides an overall process overview:
Prerequisites:
• configuration of an outgoing email server is to be set up for sending out notification mail in approval processes to purchase manager
• in purchase setting the following features should be activated through setting the proper indicator:
◦ purchase agreement
◦ vendor pricelist
• in user master data the following settings have to be performed:
◦ notification via email (for purchasing manager only)
◦ manage vendor price list
Procurement Plan Version
• approval process involving purchase manager (responsible of procurement plan version) who is informed via email
• document attachment management
• logical archiving features
• activating standard activity features for managing activities in approval process
• rejection text mandatory for entering reject reason
• after approving it, the procurement plan version is visible in procurement plan management
• in closing it, all related procurement plans are frozen, so all figures are frozen (this should be done after performing all transactions related to the involved purchase orders, i.e. goods receips and invoice receipts)
• kanban view is available also for providing an overview of procurement version status
• in kanban view all Odoo standard activities can be planned and performed
Procurement Plan
• each Procurement Plan has to be assigned to a Procurement Plan Version; hence procurement plans are collected through the assigned procurement plan version
• approval process involving purchase manager who is informed via email
• document attachment management
• logical archiving features
• activating standard activity features for managing activities in approval process
• rejection text mandatory for entering reject reason
• vendor price list sub-screen for supporting unit price and target saving management
• when approving it, a purchase agreement is automatically created with the agreement type entered at header level; this is for supporting the follow-on procurement process
• POs are collected with reference to a procurement plan
• new items can be entered at PO level (extra budget) and are taken into account in the follow-on analyses also
• kanban view is available also for providing an overview of procurement plan status ordered (in column) by their version (see picture below)
• in kanban view all Odoo standard activities can be planned and performed
Procurement Plan Version UPLOAD
all data should be uploaded into the related data structure before performing the three analyses detailed below:
· variance analysis
· quantity monitor
· amount monitor
Variance Analysis
• the overall variance is breakdown in price and quantity variances to detail the reason for it.
• Extra budget lines are point out also (the overall amount is calculated as delta)
• actual saving is calculated also to be compared with the target one
• pivot view is available also to sum up delta figures
Quantity Monitor
• the following figures are calculated according the control policy set at product master level:
◦ quantity to receive
◦ quantity to be invoiced (negative figured are related to a credit note to be asked)
Amount Monitor
• similar figures are provided in amount monitor:
◦ amount to receive
◦ amount to be invoiced (negative amount is related to credit note to be asked)
• pivot view is also available for summing up indicators related to the follow-on purchase process (goods receipt and invoice receipt)
Odoo Proprietary License v1.0 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.
Please log in to comment on this module