I submitted this ticket under warranty and received the following responses: We have checked the issues reported on bug link given in Issue i.e. https://bugs.launchpad.net/openobject-addons/+bug/1153107. We have been working on the solution for issues reported on the bug, as we can see that bug has multiple issue reported, so we are working on the issue block by block on the bug. For now we have fixed the following issues reported on bug : ------------------------------------------------------------------- CASE 1: All lead times at zero (company lead times & product lead times at zero) Case 1.1: Creating a SO, looking at the related DO Problem: Order date on DO = order date on SO - 1 day (Therefore: wrong order date on DO, wrong expected date on DO, wrong date on stock move, wrong scheduled date on stock move. ) Solution: Order date on DO = order date on SO Problem: Picking policy 'Deliver all at once' as no impact on the expected date of the DO. Solution: If 'Deliver at once' is chosen the expected date on DO should take the max scheduled date of related stock moves, not the min. (By the way, it is possible to partially deliver a DO even when picking policy is 'Deliver all at once' on related SO. If picking policy is not only for information, this should be considered as a bug). Case 1.2: Creating a PO, looking at the related PO lines & IS Problem: Scheduled date on PO lines = order date on PO - 1 day Solution: Scheduled date on PO lines = order date on PO Problem: Order date on IS = order date on PO - 1 day Solution: Order date on IS = order date on PO Case 1.3: With scheduler - Product is to be produced - Creating a SO, looking at the related MO Problem: Scheduled date on MO = order date on SO - 1 day Solution: Scheduled date on MO = order date on SO Problem: date on stock moves for MO (for component and finished product) = order date on SO - 1 day Solution: date on stock moves for MO = order date on SO Problem: Scheduled date on stock moves for MO = order creation date (server time stamp) Solution: Scheduled date on stock moves for MO = order date on SO Case 1.4: With scheduler - Product is to be bought - Creating a SO, looking at the related PO Problem: Order date on PO = order date on SO - 1 day Solution: Order date on PO = order date on SO Problem: Scheduled date on PO lines = order date on PO + 1 day Solution: Scheduled date on PO lines = order date on PO ------------------------------------------------------------------- The Solutions for above issue has been fix and committed in : lp:~openerp-dev/openobject-addons/6.1-opw-590221-jam, so you can check the fix done. Technically issue in above cases was related timezone and date to datetime conversation. AND Regarding issue, "CASE 1: All lead times at zero (company lead times & product lead times at zero)". As we have explained earlier, it was issue regarding date to datetime conversion and affected by User Timezone (i.e. web browsers timezone). We investigates the issue and and found that System does not preform Date - 1 Operation on Expected Dates (Deliver/receive)(i.e. Deduction) when we have all lead time to zero, instead while converting Order date to Expected datetime system assumes the Operation time to UTC 00:00:00 time and system stores 00:00:00 time database and when user try to see this date in timezone which are below UTC/GMT 00, that time will convert UTC datetime to user timezone, For example If I have system which is in PST and if My SO date is 2012-03-27 and When I confirm my SO it calculates the expected DO Date like [Sale Order Date (on the SO) + Customer Lead Time (on the SO line, coming from the product) - Security Days (on the company)] so expected date shown to according to my browser will be 2012-03-26 17:00:00 instead of 2012-03-27 00:00:00. After discussion with level 2 Expert, the solution has been updated and Have proposed the fix for merging in Stable v7, it will be soon reviewed and merged by Level 2 Experts. Issue : CASE 2 Working with company lead times (all product lead times at zero) This Whole section issue Focuses On Security Days, Purchase Lead Time and Manufacturing lead time, Which we can define on Company. In OpenERP Security days can defined at Two levels 1) Company Level and 2) Product level as already Explained in Bug. Company Level Leads Days is supposed to be the delay that the company gives to itself to be sure that delivery/reception will be insured Within: Order Date + Lead Time. OpenERP will respect the delay to be sure that company will send the pickings before it reaches the limit date provided to the client : order date + customer lead time, so to avoid any possible encountered problem, we take the security lead time and deducted from the theoretical date or delivery/reception. The company level security delay for purchases is the average time between the order generated by OpenERP and the real purchase time from the supplier by your purchasing department. This delay takes into account the order process in your company, including order negotiation time. The goal of Lead time on Company is to procure (receive/manufacture/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. Using the Company Level lead time is purely dependent on company requirements. However I do agree with you if you say the tooltip on those field are confusing, so I am also improving the tooltip for company level lead times in same branch. And On Product Level Lead time we can define Customer Lead Time, Manufacturing Lead Time and Supplier Delivery Lead Time. Here Customer Lead Time is the average delay in days between the confirmation of the customer order and the delivery of the finished products. Usually It's the time you promise to your customers. Now here if User Company want security days in delivery then they can configure Company Level Security days to be removed from theoretical date. Manufacturing Lead Time is the average delay in days to produce this product. In the case of multi-level BOM, the manufacturing lead times of the components will be added, and Supplier Delivery Lead Time is the Lead time in days between the confirmation of the purchase order and the reception of the products in your warehouse. Used by the scheduler for automatic computation of the purchase order planning. In normal case Company Level lead time stays but again it depends on company implementation and driven by company policies. And Both Level of lead time has individual meaning and explanation that i explained above. With above consideration 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. Case 3 issue basically Combines the Timezone related problem explained above and Mis-configuration of the Company level lead time and Products level Lead times and can be any of problem explained above.