On hand position distribution chart

Would be useful to add an on-hand position distribution chart to the buffer.
This would allow to see if the buffer is properly sized and we're achieving the optimal ROI.

See DDP slide 312

[Question] Is this DDMRP module, support customer sales forcast, at least to generate PO for purchasing of long lead time Raw Material?

Dear @jbeficent, and all,

Very interesting project.
I have question whether it is support to use sales forecast from customer as the input information (demand estimate) to generate purchase order of Raw Material especially with long lead time.

For common example:
Customer will give monthly qty of order as forecast for 6 to 12 months ahead, The accuracy will be +/- 20% of the estimated qty of order.

Since the lead time to buy raw material 3-4 months, we need to adopt the customer sales forecast as the base to order such raw materials.

Is this already supported with this DDMRP module? I read the dependencies seem already mention demand_estimate oca module, but no usage description yet on it.

would you please to give brief information on this, thank you.

with regards,
Bun Hin

Material synchronization alert in manufacturing orders

Display when there's a component of the MO that has a projected on-hand alert.

book, p.222

Allow to filter buffers by profile type (manufactured, purchased, distributed,..)

Book, page 215

V11 Issues NameError: name 'figure' is not defined

ddmrp\models\stock_warehouse_orderpoint.py", line 179, in _compute_ddmrp_chart
p = figure(plot_width=300, plot_height=400,
NameError: name 'figure' is not defined

replenish_overwrite same as replenish

currently there is replenish_overwrite option available, per the below definition, after select this option, system will not calculate ADU. but currently either replenish_overwrite or replenish function the same: calc ADU.

In Demand Driven Planning, parts are designated:
Replenished Parts – the parts strategically chosen to be managed as replenishment parts, via a color coded buffer management approach. These parts will have dynamic buffers – they’ll increase when demand increases, for example, and decrease when demand decreases.

Replenish Override – also buffered and color-coded but NOT dynamic.

Min/Max – a variation of the classic min/max, with advantages of also being Dynamic; for readily available parts without the strategic value of Replenished parts.

Implement projected on-hand alert

book, p.218

Tests failing on ddmrp_adjustment

Hello
Since 7cb743c, this test is failing : https://github.com/Eficent/ddmrp/blob/11.0/ddmrp_adjustment/tests/test_adu_dlt_adjustment.py#L13

What should we do in this case ?

We did ping @lreficent on the commit, but no answer.

ddmrp_alert - alerts not deleted after cron

Ignore reserved moves and stock on Buffers

Reservation of stock should not be recommended when carrying out a ddmrp methodology.

Extract Decoupled Lead Time (dlt) to product

I think the concept of dlt is really interesting and can be used outside the context of DDMRP.

What do you think of externalize it in a new module, and store it on the product.product and bom ?
[product.product].dlt will be stored, computed and depends of seller_ids, bom_ids.dlt
[product.template].dlt will be related of product_variant_ids.dlt
[mrp.bom.line].dlt will be a related to product_id.dlt
[mrp.bom].dlt will be stored, computed and depends of product_id.produce_delay, product_template.produce_delay , bom_line_ids.dlt

Access open purchase requests/purchase orders/manufacturing orders associated to a buffer

book, p.215

11.0-multi-level-mrp

Change logic to determine planned end date for MO. Should happen on the write method.

https://github.com/Eficent/ddmrp/blob/11.0-multi_level_mrp/ddmrp/models/mrp_production.py#L19

DDMRP and classic orderpoint rule in Odoo

Hello,
I was wondering it there was a strong reason to disable odoo native orderpoint when installing ddmrp?
Indeed, installing this (great) suite of module, can be quite a big step for a company, we were wondering if it could be done to install it and use it juste for some products, in order to get use to it, adjust the parameters, etc... And continue using the native Odoo orderpoint system for other products.

From what I saw, it could be done easily with some little changes (that could be done in an other small module for instance), like making this part : https://github.com/Eficent/ddmrp/blob/9.0/ddmrp/models/procurement_order.py#L31 optional, adding a flag on orderpoints to tell if it should compute with ddmrp logic or odoo native logic, to avoid recomputation by crons, etc...

Anyway, I am not asking to change the module, but I would like to have your opinion about this.
From my point of view, it is obviously always the goal to use the ddmrp logic for all products, but during a transition period, for big companies to adapt, I guess it could be nice to be able to use both.

To cut a long story short : the reason behind this limitation is more technical (it complicate the code to allow both method) or more functional ?

Thank you for this very good work!
@jbeficent @lreficent

[Question] When to explode BOM to generate components' demand of finish goods in sales order

After study all the available documentation and the source code of this project, I still have no idea how DDMRP generate components' demand base on BOM of finish goods( in sales order).
In current DDMRP logic, the BOM explosion is only applicable to demand adjustment which on one hand reply on the demand adjustment records to be created via the wizard, on the other hand it only have impact to ADU other than demand itself. if my above understanding of the logic is correct, then how the program generate recommend quantity for (buffered) components which never included directly in sales order.
Possibly there should be the following 2 features needed

Explode BOM for products/materials from sales order, to generate its components dependent demand
Define configurable parameter to allow system to explode BOM to generate its components demand adjustments even without the demand adjustment record( just like setting default demand adjustment factor as 1 for all materials if no demand adjustment record exist.)

Order Spikes

Implement:

The three methods to define the spike threshold.
A constrain/warning for the horizon, it must be greater than the DLT.
OST2 and OSH2.

Current on hand buffer status - red zone computation

The red status should occur when the current on hand < Oh hand alert.

On-hand alert = % of red zone (by default 50%).

There should also be an option to display the bufferts that are in alert.

[Question] How to create PO and WO after procure_recomended_qty and procure_recomended_date calculated

How to create PO and WO after procure_recomended_qty and procure_recomended_date calculated

subtract_procurements

Hi,

I was looking about how to take (not) into account long planned orders (expected date > decoupled lead time). add_to_net_flow_equation seams a good candidate to carry this information.

But def substract_procurements() seams dead code since this commit :
8e5ae98#diff-b886cdbc1da4eca803d4248195ecde52

Should it be renamed to def subtract_procurements_from_orderpoints ?

Migration to version 11.0

Moved to OCA/ddmrp#7

DDMRP 98% installed...

Have followed your recent instructions to clone the OCA/Web folder onto my odoo server. Everything copied over. The last module I need is web_widget_bokeh_chart which I moved from /web into /addons along with other required Web files. The other came across with no issue, except for the web_widget_bokeh_chart. It does not show up as can be installed, just shows 'Unknown'.