Security days bug

[Grzegorz Grzelak (OpenGLOBE.pl)]

I found that it is error in "Security days" under "Administration - Users - Company's Structure - Companys" on Tab "Settings". In small help is written that this time should be added to "Customer Lead Time" but is subtracted.

In OpenERP it is default (after db creation) 7 days in Customer lead time. And by default 5 days in Security days. But when creating Picking list by confirmation of SO I got 2 day lead time (7-5=2). I have checked some other number and it works this way.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello Grzegorz Grzelak (Cirrus) ,

Thank you for the post.

Its actually a counting like:
planned _date = current_date + delayed days from Sale order - company security lead time.
so, in your case, it could be,
planned_date = current_date + 7 - 5 .

Thank you.

[Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl)]

I think I understand the idea. The problem was that there is no explicit "delayed days from Sale order". I assume it it is the longest delay from SO lines. Which should be printed in Quotation as "Time of delivery (after receiving order) ....Days". But it is not counted and printed on standard Quotation or Order. And Security Days are subtracted to dispatch Packing earlier than promised. I think it should work that dispatching (packing to customer, planned date) should be at promised date and other dates (of Production and purchase orders) should be earlier than their lead times for security.
Thank you Jay, The most important is that I understand it now.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Thank you Grzegorz.

[TeMPO (info-tempo-consulting)]

Dear all,

I reopened this bug since I fully agree to what Grzegorz says.
The security days should impact the purchase/production process but not the sale process
As it is done now the Sale Order has a promised day of 7 days but a packing of 2 days delay
This is nonsense ; doing so you put yourself in the position to buy or produce 5 days in advance which
is absolutely not was the security days is meant for

[Ana Juaristi Olalde (ajuaristio)]

Hi:

+1 to tempo's post.

Security days can cause the packing planned date on past wich is absolutly wrong. Try to fix delivery date for customer 3 days, so you will obtain planned packing date for 2 days before today.
I think something similar to this bug has been discused in another post or bug but I could not find it.

I think planned data functionality should be heavilly reviewed for 6.0 if it's not possible for 5.0. I mean... In so many cases it's no sense fixing delivery for 7 days or 2 days... system should be able to calculate correct delivery data depending on availability of stock and supplier planned delivery data.

This is... if your procurement for product is against stock and you have got stock available for product your delivery time probably will be inmediate. If you haven't got stock, planned data should be calculated depending on your supplier's delivery time or your production delay time. In most of companies it's nosense fixing this delivery or delay datas. Actually, packing planned data has to be fixed by hand.

IMHO ... should we open a new blueprint with correct requierements for this functionality?

[Olivier Dony (Odoo) (odo-openerp)]

@TeMPO:
Sorry but it seems to me that this is exactly what the "Security Days" are meant for in OpenERP. The goal is to procure (buy/produce/deliver) the products X days in advance to what is really necessary, in case something in the process causes unforeseen delays. This also includes the final shipping to the customer.
There are also additional security delay fields for production and purchase specifically, that are also taken into account.
Please mark this bug as invalid again unless you have a precise scenario to show what is going wrong.
If you simply wish to suggest some changes to the way security days work in OpenERP, please open another wishlist bug.

@Ana Juaristi Olalde:
The fact that you can end up with dates in the past is normal in OpenERP, and means that according to the current setup it is impossible to satisfy the delivery date promised to the customer. This can be because:
- you have something wrong in the setup of your security days or customer lead times
- or you have specified a shorter lead time on the sale order line than is normally possible in your company
- or you simply want to deliver asap, but if you depend on the delivery of a supplier or a manufacturing operation there is a chance that you will not finish in time.
In any case, the system does not want to stop you from confirming the order, because that could be a big problem, and does not correct the dates in the past to use the current date instead because that would mean the final delivery is set to a date that does not match what you requested.
I'm sure there are valid ways to improve this but keep in mind that this is much complicated than it seems. For example estimating the complete time it takes to procure a given product requires to execute the full procurement workflow, which can take time, and the simulation could not even be correct depending on the way your procurement process normally works (think Just-In-Time versus nightly run, or an inventory that is depleted between the time of the simulation and the real confirmation of the sale order, etc.)
Anyway, feel free to open a Wishlist bug with a precise description of your proposed improvements, but make sure it is sufficiently detailed and takes all the cases into consideration, otherwise it will be useless.

I hope my answer is clear enough, MRP and Inventory management are one of the most complicated topics, and they often look more simple than they are because every company has corner cases that they want covered. I agree that there is room for improvement though (specifically user-friendliness).

[Vinay Rana (OpenERP) (vra-openerp)]

With the reference of above comment #6 I am closing this issue.
For Other issue discussion I suggesting you post a separate bug.

Thanks.