stock moves order by date_expected problem

[Paulius Sladkevičius @ hbee]

Stock moves are order by "date_expected desc, id". When I create sale order with many lines it sometimes takes more then 2 sec to confirm and together create picking order with stock moves. So in the end I get stock picking with moves where data_expected are different by 1 sec., so in the end we have different picking lines order if we compare with sale order lines.

So I think to assign now() value for date_expected is not correct, same is mentioned in the bug #371262.

[Paulius Sladkevičius @ hbee (komsas)]

To solve this problem I attach patch for the stock moves date creating in the sale action_ship_create() method.

[Ujjvala Collins (uco-openerp)]

Hello Paulius Sladkevičius,

This problem has been solved in latest trunk addons.

You'll always get the stock moves according to the sequence of sale order lines as per the following line of code
on sale/sale.py : line #670,671
 date_planned = datetime.strptime(order.date_order, '%Y-%m-%d') + relativedelta(days=line.delay or 0.0)
 date_planned = (date_planned - timedelta(days=company.security_lead)).strftime('%Y-%m-%d %H:%M:%S')

I request you to update your code and check.

Hope this helps. And for now we're closing this issue.

Thanks,
Ujjvala

[Paulius Sladkevičius @ hbee (komsas)]

Thanks Mustufa,

you are right, better idea to take order date then now(). Please link to your branch, because I don't see any changes in the trunk.