Required Apps |
•
Project (project)
• Manufacturing (mrp) • Inventory (stock) • Invoicing (account) • Purchase (purchase) • Employees (hr) |
Included Dependencies | Show |
Lines of code | 2846 |
Technical Name |
mrp_project_timesheets |
License | See License tab |
Website | http://www.openvalue.cloud |
Required Apps |
•
Project (project)
• Manufacturing (mrp) • Inventory (stock) • Invoicing (account) • Purchase (purchase) • Employees (hr) |
Included Dependencies | Show |
Lines of code | 2846 |
Technical Name |
mrp_project_timesheets |
License | See License tab |
Website | http://www.openvalue.cloud |
MRP Production Project
The “MRP Production Project” module purpose is to enhance the OpenValue Manufacturing Execution solution by integrating the Production module 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.
Bill of Materials
· 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.
Manufacturing Order
· 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 project assigned as cost object at manufacturing order level has to have the timesheet indicator set (a system error checks it)
· The analytic account is automatically filled with the one assigned to the project: all analytic postings (components consumption, workorder postings, …. see the product costing module for any detail) are posted on this analytic account.
· A check avoids to set incidentally an analytic account different to the one linked to the project
· 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
Tasks
· Tasks under the project assigned to the manufacturing order are automatically created at manufacturing order scheduling
· 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
· 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
All production times are collected in a proper page with the following figures calculated in real time:
· The standard times are related to the operations BoM as follows:
o Total setup time is calculated as the sum of all times before production entered at work-center level; the timesheet workorders are excluded
o Total working time is the overall working time for processing all workorders
o Total teardown time is calculated as the sum of all times after production entered at work-center level; the timesheet workorders are excluded
· The planned times are calculated from workorders and frozen at manufacturing order confirmation; in detail we have:
o Planned times as sum of all expected durations of workorders created with reference to a BoM operation
o Unplanned times as before for workorders created manually (not referenced to a BoM operation)
· The actual times are the sum of actual times entered at workorder confirmation phase
· The overall effort entered through timesheet is reported also
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