v 14.0 Third Party 1
Required Apps Manufacturing (mrp)
Inventory (stock)
Invoicing (account)
Purchase (purchase)
Included Dependencies
MRP Product Costing (1131 lines of code)
MRP Shop Floor Control (1213 lines of code)
Openvalue Warehouse Calendar (19 lines of code)
Lines of code 2755
Technical Name mrp_mto_analytic
LicenseSee License tab
Websitehttp://linkedin.com/in/openvalue-consulting-472448176
Also available in version v 13.0
You bought this module and need support? Click here!
Required Apps Manufacturing (mrp)
Inventory (stock)
Invoicing (account)
Purchase (purchase)
Included Dependencies
MRP Product Costing (1131 lines of code)
MRP Shop Floor Control (1213 lines of code)
Openvalue Warehouse Calendar (19 lines of code)
Lines of code 2755
Technical Name mrp_mto_analytic
LicenseSee License tab
Websitehttp://linkedin.com/in/openvalue-consulting-472448176
Also available in version v 13.0

MTO ANALYTIC

 

The purpose of the “MRP MTO Analytic” module is to support the overall Make to Order process management from sales to purchase for both analytic accounting and logistics perspectives also.

This is achieved by implementing a strong integration between the logistics modules (sales, mrp, purchase and inventory), and the analytic accounting and planning backwards, based on a working calendar, of all the supply chain replenishment proposal elements, i.e. manufacturing orders and purchase quotations.

 

 

Accounting view

An analytic account has to be assigned a MTO sale order for collecting all the revenues and the costs related to an MTO process; therefore, it is possible to monitor in real time all accounting figures related to a MTO process and its margin.

 

Starting from a sales order, the analytic account is required (system check issuing an error message) when an MTO item has been included in the items; therefore, MTO sale order item is the starting point for triggering the MTO process.

A tool is provided to support the automatic creation of analytic account in sales order.


The analytic account is propagated from the sale order to the MTO overall supply chain, as shown in the picture below.


The analytic account is propagated in some business cases in the sale delivery for posting cost of sales in analytic accounting, as shown in the picture below:

 

 


 

The following business cases are managed:

·       MTO Finished Product (storable product internally produced)

·       MTO Commercial Part (storable product purchased on demand and sold)

·       MTS Spare Part (storable product on stock)

·       MTO Consumable (consumable product purchase on demand and sold)

·       MTS Consumable (consumable product available on the premises)

·       Purchased Service (Services purchased on demand from a third party and sold)

·       Internal Service (Service internally provided)

 

 

MTO Finished Product


The analytic account in the sales order is propagated to the all manufacturing orders along the supply chain.

Through the “MRP Product Costing” module, all direct costs are collected in the analytic account.

The Cost of Sales and Revenues are posted also on the analytic account.

 

 

MTO Commercial


The costs of sales is not relevant for the analytic accounting perspective, so no analytic posting are performed at customer delivery goods movement. This is to avoid to post the cost twice.

 

 

MTS Spare Part


The cost is posted on analytic account when the spare part is withdrawal from the stock. Therefore the outbound delivery goods movement is relevant for the analytic accounting perspective.

 

 

MTO Consumable


The analytic account is propagated from the sales order to the purchase order at item level. Revenues and Costs are collected on the analytic account when invoice has been validated.

 

 

MTS Consumable

This business case does not make sense in the MTO process scenario. Therefore, a check has been implemented to avoid to enter a sales item with an MTS consumable item with price different to zero. That means MTS consumable can be included in MTO sales order as free goods only.

 

 

Purchased Service

For a Service purchased from a third party (purchase automatically indicator set on master data) the analytic account is propagated from the sales order to the purchase order at item level. The analytic accounting posting for both costs and revenues are performed at invoices posting.

 

 

Internal Service

The revenues are collected on the analytic account when posting the customer invoice.

All internal costs are to be collected on the same analytic account, e.g. in timesheets for internal personnel costs.

 

 

Logistics view

All the proposal elements along the MTO supply chain are planned in backwards mode, as shown in the picture below:


Therefore, planned pivot dates (implemented in the MRP Shop Floor Control) in MTO manufacturing orders and purchase order dates and receipt dates in MTO purchase orders are determined by planning backwards in working days (based on the working calendar assigned to the warehouse in sale order) starting from sale order delivery date and taking into account all safety times.

In detail, we have as follows:

·       The schedule date in the sale delivery document is determined starting from the sale delivery date in backwards mode by taking into account the sales safety time; the schedule date is the pivot end date for the all the supply chain replenishment proposal elements created by confirming the sale order.

·       The manufacturing order pivot start date is determined in backwards mode in working day starting from the pivot start date of its demand element in MTO supply chain, i.e. the sales order item delivery date or the manufacturing order start pivot date either; the manufacturing lead time and the manufacturing safety time are both taken into account in working days according the working calendar defined at warehouse level.

·       The purchase order planned receipt date is determined from the pivot start date of its demand element in MTO supply chain, i.e. the sales order item delivery date or the manufacturing order start pivot date either; it is planned backwards in calendar days by the purchase safety time; the purchase order date is determined in backwards scheduling from the planned receipt date by taking away the delivery lead time in calendar days defined at vendor level and the days to purchase lead time. A purchase order is created for each requirement.

 

 

MTO Supply Chain Report

A custom report is available to list for a sales order all the related procurement MTO elements, i.e. MTO manufacturing orders and MTO purchase order items, with their dates and quantities. Therefore, in only one report a recap of all necessary figures is provided to monitor the overall MTO supply chain and to fulfill the customer expected delivery date.

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.

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.