$ 9037.20
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Project (project)
• Manufacturing (mrp) • Inventory (stock) • Discuss (mail) • Invoicing (account) • Purchase (purchase) • Employees (hr) |
Community Apps Dependencies | Show |
Lines of code | 5931 |
Technical Name |
mrp_engineering |
License | See License tab |
Website | http://www.openvalue.cloud |
Versions | 16.0 |
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Project (project)
• Manufacturing (mrp) • Inventory (stock) • Discuss (mail) • Invoicing (account) • Purchase (purchase) • Employees (hr) |
Community Apps Dependencies | Show |
Lines of code | 5931 |
Technical Name |
mrp_engineering |
License | See License tab |
Website | http://www.openvalue.cloud |
Versions | 16.0 |
MRP Engineering
The “MRP Engineering” module purpose is to support the “new product development” process management by implementing the following main features:
· Engineering BoM for new products in prototyping phase: the engineering BoM is converted in Manufacturing BoM at the closure of the new product development phase
· Engineering Manufacturing Order for managing prototyping production process
The Engineering Manufacturing Order features have been built starting from the OpenValue Manufacturing Execution solution and integrating it with the Project and Timesheets ones. Therefore, it is possible to achieve as follows:
· to assign a project as cost object to a manufacturing order (all analytic lines are posted on the analytic account set at project level) and
· to charge timesheets on tasks linked to workorders for collecting engineering hours in production process
Engineering Bill of Materials
· a new BoM type is available: Engineering BoM for segregating the eBoM from the other ones
· An operation can be set as a “timesheet” one (timesheets indicator has to be set) to collect timesheets; its expected duration is automatically set as zero and a system check avoids to set incidentally a time cycle different to zero.
· All the features related to a normal BoM for product costing management are available also for engineering BoM also
· At new product development process closure, it is possible to convert the engineering BoM in a Manufacturing BoM; the conversion is multi-level, that means all sub-finished engineering BoM will be converted also
· The engineering BoM reference is reported to the Manufacturing BoM to link each other’s
· It is possible to convert it only once: a check has been implemented to avoid by incident to convert twice an engineering BoM
· After converting it, the engineering BoM is automatically archived
Engineering Manufacturing Order
· An Engineering Manufacturing Order is identified by entering an Engineering BoM
· A project is requested as cost object for collected all prototyping direct costs related to the prototyping production phase
· The timesheet indicator is checked to be active on project; therefore, the project assigned as cost object at manufacturing order level has to have the timesheet indicator set (a system error checks it)
· The timesheets indicator is set automatically on a workorder created with reference to a timesheet operation in a BoM; the expected duration is set automatically to zero and a system check at confirmation phase avoids to set incidentally an expected duration different to zero
· A timesheet workorder can be created manually also by setting its timesheets indicator: the expected duration is set automatically to zero and a system error checks to have incidentally a value different to zero
· The analytic account related to the project is automatically assigned: all direct analytic are posted on this analytic account.
· When scheduling manufacturing orders, a task is automatically created for each timesheet workorder and both are automatically linked each other’s
· It is not possible to start or block manually a timesheet workorder; therefore, for closing it the confirmation tool has to be used
Engineering Tasks
· Tasks under the project assigned to the manufacturing order are automatically created at manufacturing order confirmation
· A task is created for each timesheet workorder (workorder with the timesheet indicator set)
· Timesheets can be entered and reported on manufacturing order
· It is not possible (system check) to enter timesheet when the linked workorder has been closed or cancelled either
· Timesheets are collected at workorder level and at manufacturing order level
Workorder Confirmation
· The workorder confirmation tool has been enhanced for managing timesheet workorders also
· For timesheet workorders all times are set to zero and both the start date and end date are automatically set as the current date
Manufacturing Times
· The overall Planned and Actial Effort entered through timesheet are reported.
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. 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