Contributors mailing list archives

contributors@odoo-community.org

Re: [stock_calendar] module removal in master

by
Tecnativa. S. L., Pedro M. Baeza
- 18/09/2017 15:54:53
And now it seems to be another base in https://github.com/OCA/contract/pull/95, with a possible extension agreement_purchase.

Regards.

2017-09-18 17:52 GMT+02:00 Denis Roussel <denis.roussel@acsone.eu>:
The DDMRP module seems to be great (few tests). I think an automatic procurement generation (on which criteria ?) could be greater!

I will move forward on the Jordi idea and dig into Scheduling Agreement which should go into purchase-workflow.

I see there is already some work in it that had never been ended (two PR's - Framework agreement).





On Fri, Sep 15, 2017 at 11:08 AM Jordi Ballester Alomar <jordi.ballester@eficent.com> wrote:
Oh, so what you describe seems to be in the lines of what SAP calls scheduling agreement:

In any case this influences the frequency in which the orderpoint should reorder. 

In DDMRP the desired or imposed supplier order frequency is one of the possible factors that defines the green zone of the buffer.

Green Buffer Zone = Average Daily Usage * Expected days between orders

Please note that you can have a scheduling agreement, but the quantity to reorder should be ideally be variable, based on the average daily usage. If you have more average demand, your supplier must send you more products, at the agreed frequency. Otherwise you'll soon face a stockout.

Regards,
Jordi.







On Fri, Sep 15, 2017 at 10:22 AM, Denis Roussel <denis.roussel@acsone.eu> wrote:
Hi Jordi,

In fact, my needs is quite more simple.

My functional demand is after the process you describe. In fact that's the process which supplant the minimum and maximum level on orderpoints.

I'm later in the process. I just want to represent supplier plannings with a little more complexity than the stock_calendar in Odoo. In fact, purchase calendars per supplier with in some cases a delivery planning linked to the order planning.

So, I wanted to reimplement that process in a generic way and with additional layers of complexity. It should be independent of the ddmrp or other I think.

On Fri, Sep 15, 2017 at 10:09 AM Jordi Ballester Alomar <jordi.ballester@eficent.com> wrote:
Denis, your problem probably has to do with what DDMRP calls qualified demand.

In DDMRP the criteria that defines when you should reorder is when the net flow position on a buffer (orderpoint) is below the top of yellow zone. See the screenshot below. The current situation identifies the need to reorder.

Net Flow Position = On Hand + Incoming - Qualified demand

The qualified demand is demand (stock moves that demand material) that is past due or due today + future demand in a future horizon called spike horizon, that is deemed as relevant (for example, because it is 50% greater than average daily usage).


Inline image 2



On Fri, Sep 15, 2017 at 9:37 AM, Denis Roussel <denis.roussel@acsone.eu> wrote:
If I have well read the introduction of DDMRP, this can be a part of the fourth step (Demand Driven Planning).

Indeed, we could do a subject on that part during OCA Sprint.

I'll look into it as I need a solution ASAP.

On Thu, Sep 14, 2017 at 8:08 PM Tom Blauwendraat <thomaspaulb@gmail.com> wrote:
Jordi, in which stage is the DDMRP project? Are there modules to be looked at, or is this ongoing development? 

On Thu, Sep 14, 2017 at 7:37 PM, Jordi Ballester Alomar <jordi.ballester@eficent.com> wrote:
I agree with Pedro. The DDMRP addresses this issue more elegantly, and with a thorough scientific approach behind it, proven by the people that created the MRP concepts itself. 

We can schedule a DDMRP session during the code sprint. In that case I encourage you to read this book in advance:





On Thu, Sep 14, 2017 at 7:07 PM, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Yeah, I think this is going to be very aligned with DDMRP efforts from Eficent. Maybe you can add a topic on the LLN code sprint about that and have some people working on it.

Regards.
2017-09-14 18:23 GMT+02:00 Denis Roussel <denis.roussel@acsone.eu>:
Hi Pedro,

I think there is a way to manage it anyway as they group logic into procurement groups.

I posted here to launch a discussion and maybe a brainstorming to make a 'new born solution'.

Indeed, the needs will affect customers in great distribution that have internal and external (suppliers) scheduling for ordering/delivering and real time constraints.

Regards,

On Thu, Sep 14, 2017 at 5:08 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
The problem is that in v11, as there are no procurement orders, you don't have an easy way to reflect waiting procurements to be satisfied, so the porting to 11 of this module or any other is going to be harder.

Regards.

2017-09-14 16:52 GMT+02:00 Denis Roussel <denis.roussel@acsone.eu>:
Hi all,

Today, Odoo removed the stock_calendar module from master :


This feature seems not to be supported anymore either in future versions or enterprise.

Even if the module code quality was not high, it had the good point to exist.

As we want to sustain this feature, we ask here if there is another existing solution ?

Thanks for your help
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : 
+352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : 
+352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : 
+352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : 
+352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : 
+352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : 
+352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : 
+352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : 
+352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : 
+352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : 
+352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe