Comment 12 for bug 596862

You all are right. Users make mistakes and it should be possible reverting or "undo" badly made steps on a workflow, so... why not thinking about related actions on cancelling picking?
I think the most usefull functionality could be to make possible going back from cancelled status to confirmed / draft status on a picking analyzing all possible statuses and actions on related objects.

This is... Make a SO, confirm, creates a picking. Don't make moves done simply erase the picking... you could see that stock moves are cancelled not erased. Why? Make the SO come back to draft and confirm again. A new picking is created an new moves are created. If you cancel the first moves and they are there... why don't reactivate and rewrite existing moves instead of creating new ones? I can't see the objetive of this way of working.

Now.. go to an invoice. Confirm. Account moves are created. Now "allow cancelling moves on journal". Cancel the invoice, go back the invoice to draft. The account moves are generated and erased. This is a similar situation. Why is different on picking?

The only thing I try to say is that picking is the only critical object you can't make to go back on workflow. I think there is more as complicated as this one that is posible to revert. So I think we should make a complete analisys to try to include this new step on workflow instead of making a patch or manual buttons or something strange that for sure would break another thing. IMHO.